Challenge
EZBuild is an AI operating system for residential contractors in the US. Home builders, remodelers and specialty trades use it to run leads, proposals, projects, schedules and finances. Its founders had spent close to a year with a previous vendor. Delivery had fallen behind the roadmap and quality problems were reaching customers, while the founders were onboarding their first paying contractors.
Parts of the product were half-built: notifications, the mobile calendar and an AI assistant that could not read a contractor's live data. Designs, specifications and the running app had drifted apart. There was no handover. Deployments ran on the previous team's personal credentials, most automated pipelines were failing, releases were moved between environments by hand, and the mobile app's store identity blocked push notifications.
EZBuild is an AI operating system for residential contractors in the US. Home builders, remodelers and specialty trades use it to run leads, proposals, projects, schedules and finances. Its founders had spent close to a year with a previous vendor. Delivery had fallen behind the roadmap and quality problems were reaching customers, while the founders were onboarding their first paying contractors.
Parts of the product were half-built: notifications, the mobile calendar and an AI assistant that could not read a contractor's live data. Designs, specifications and the running app had drifted apart. There was no handover. Deployments ran on the previous team's personal credentials, most automated pipelines were failing, releases were moved between environments by hand, and the mobile app's store identity blocked push notifications.
Solution
We began with a paid two-week trial sprint on the real product, then took over development in June 2026, working alongside the founders' own engineers. We started from the code in the main repository, moved access and deployments into the company's own cloud account, and repaired the failing pipelines. The live setup is now written down as code and errors are monitored.
We set up two-week sprints with design, code-review and release approval gates, a weekly path from development to staging to production, and feature flags the product team switches on and off.
On mobile we fixed the app's store identity and added push notifications, Apple sign-in, a field calendar with check-in, signatures and maps, and voice notes turned into summaries. On the web we added partial payments and invoices, a cash-flow dashboard, a reports builder and a new lead pipeline. We rebuilt the AI assistant to answer from each contractor's own data, with access rules enforced in the database and AI costs tracked per company. A public lead API sends leads from a contractor's website forms straight into EZBuild.
We began with a paid two-week trial sprint on the real product, then took over development in June 2026, working alongside the founders' own engineers. We started from the code in the main repository, moved access and deployments into the company's own cloud account, and repaired the failing pipelines. The live setup is now written down as code and errors are monitored.
We set up two-week sprints with design, code-review and release approval gates, a weekly path from development to staging to production, and feature flags the product team switches on and off.
On mobile we fixed the app's store identity and added push notifications, Apple sign-in, a field calendar with check-in, signatures and maps, and voice notes turned into summaries. On the web we added partial payments and invoices, a cash-flow dashboard, a reports builder and a new lead pipeline. We rebuilt the AI assistant to answer from each contractor's own data, with access rules enforced in the database and AI costs tracked per company. A public lead API sends leads from a contractor's website forms straight into EZBuild.
Results
The first production release under LNOKS shipped about a month after the trial sprint began. Releases now go out on a fixed two-week rhythm and no longer depend on anyone's personal login. Access, deployments and monitoring are under the company's control. The subcontractor app is live on the App Store and Google Play, and the main Android app has been released. Considerably more changes are merged each month than before the switch, with an independent QA check on every ticket.
The first production release under LNOKS shipped about a month after the trial sprint began. Releases now go out on a fixed two-week rhythm and no longer depend on anyone's personal login. Access, deployments and monitoring are under the company's control. The subcontractor app is live on the App Store and Google Play, and the main Android app has been released. Considerably more changes are merged each month than before the switch, with an independent QA check on every ticket.
