Custom application development
A residential home builder and developer needed one application to replace several disconnected tools used to track insurance claims and warranty spending. Ollon built a custom portal covering warranty transactions, insurance policies and deductibles, and homeowner records, backed by a C# and .NET API with Entity Framework and MySQL, with a ReactJS frontend for daily use. The application included dedicated screens for policies, warranty transactions, and reports, built through regular collaboration with the organization's own project managers and end users. That custom build replaced separate manual tools with one system built around how legal and accounting teams actually worked.
ETL pipeline design and development
Insurance and warranty data for a residential home builder and developer lived in CSV exports from three separate core applications, and reconciling them by hand was the bottleneck the new application needed to remove. Ollon built a staged data pipeline that grew into three stages as requirements changed: ingestion that standardized raw CSV data into SQL tables, transformation that matched transactions to legal case records and generated new records against policy mappings, and analytics that produced verification reports for review before generating standardized reports for insurance providers. That staged approach let the system keep up as the manual process for splitting transactions by legal case outcome changed over time.
Identity and Access Management (IAM)
The new application needed a way for the right people to sign in without a separate login system, so Ollon integrated it directly with the organization's own Active Directory through single sign on. Ollon ran that SSO integration as its own project, coordinating with the client's IT team on app registration and permissions, and later delivered a second SSO integration for an administrative web portal built for the same client. The team also revised the SSO implementation to move away from cookie based session handling for better security, and built role based routing so users saw only what their role allowed. Two separate applications for the same organization ended up sharing one identity foundation.
Business System Integrations
A residential home builder and developer tracked insurance claims and warranty spending across three separate core business systems, each exporting data as CSV files with no shared structure. Ollon connected the new application directly to those existing systems, pulling policy, warranty, and homeowner records into one platform without changing how the underlying systems themselves operated. Legal case records and insurance policy mappings from those source systems now feed automatically into the reporting flow. The organization's existing infrastructure continues running as it always did, now feeding one connected reporting platform.
Workflow Engine
Generating an insurance report for a single claim used to mean a staff member manually pulling data from multiple systems, a process that could take weeks for complex cases. Ollon built automated workflows that took over that process, connecting transaction records to legal case outcomes and applying insurance policy mapping rules to generate new transaction records automatically. The system also handles class action claims, which apply to an entire neighborhood at once instead of a single homeowner, aggregating that data through the same automated flow. A process that took weeks by hand now completes in seconds, with staff reviewing the output instead of assembling it themselves.
Managed Services and Application Monitoring
Support for a residential home builder and developer's warranty and insurance reporting application continued well past its original build, running from November 2024 through the present. Ollon has handled staging and production deployment issues, ranging from environment misconfigurations to CSV upload failures, and performed direct database maintenance including cleanup of soft deleted records and data syncing. Bug fixes and report corrections, such as an issue with how erosion reports split transaction data, have continued alongside the maintenance work. That ongoing presence has kept the application running reliably as the organization's own reporting needs and data continued to change.