LNOKS began with a paid two-week trial sprint on the real product.
LNOKS took over development of EZBuild, an AI operating system for US home builders and remodelers, from a previous vendor, with no handover: production releases on a fixed two-week rhythm, infrastructure in the company's own accounts and a subcontractor app live on the App Store and Google Play.
About
About this project
EZBuild is an AI operating system for residential contractors in the US: home builders, remodelers and specialty trades run leads, proposals with e-signature, projects, schedules, finances and a customer portal in one product, with field and subcontractor apps and an AI assistant that answers over WhatsApp. Its founders had spent close to a year with a previous vendor and needed faster, more reliable delivery. LNOKS took over development in June 2026 after a paid two-week trial sprint, working alongside the founders' own engineers. Since then releases go out on a steady schedule, the infrastructure is under the company's control, and new mobile and web features ship every sprint.
Services behind this project
Starting point
The challenge
- 01
Delivery had fallen behind the roadmap, and quality problems were reaching customers. The founders were onboarding their first paying contractors and could not afford releases that broke things or features that arrived months late.
- 02
Parts of the product were left half-built: notifications, the mobile calendar and an AI assistant that could only answer from a fixed set of endpoints, without access to a contractor's live data. Designs, specifications and the running app had drifted apart.
- 03
There was no handover to rely on. Deployments ran on personal credentials of the previous team, most automated pipelines were failing, releases were moved between environments by hand, and the mobile app's store identity blocked push notifications.
Deliverables
What we delivered
-
A controlled, documented infrastructure
Deployments no longer depend on anyone's personal login. Access now sits in the company's own cloud account, the live setup is written down as code, errors are monitored and test runs are split to run in parallel.
-
A release process the team can trust
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.
-
Mobile apps in the stores
The app's store identity fixed and resubmitted, push notifications and Apple sign-in, a field calendar with check-in, signatures and maps, and voice notes turned into summaries and action items. The subcontractor app is live on the App Store and Google Play.
-
Finance, dashboards and reports
Partial payments and invoices, a dashboard with key figures and cash flow, a reports builder, and a new lead pipeline with statuses, filters and bulk export.
-
An AI assistant that works on live data
The assistant was rebuilt to answer from each contractor's own data with access rules enforced in the database, with models chosen per role and AI costs tracked per company.
-
Leads from the contractor's own website
A public lead API lets a contractor's website forms send new leads straight into EZBuild, the first step towards connecting more lead sources.
Result
What the project delivered.
-
Every sprint
Production releases on a fixed two-week rhythm, replacing manual moves between environments.
-
In the stores
Subcontractor app live on the App Store and Google Play, and the main Android app released.
-
Faster delivery
Considerably more changes merged each month after the switch, with an independent QA check on every ticket.
-
Own infrastructure
Access, deployments and monitoring under the company's control, with the setup captured as code.
Process
How we worked
-
Step 1 / 4 -
Step 2 / 4 We started from the code in the main repository, moved access and deployments into the company's own accounts, and repaired the failing pipelines.
-
Step 3 / 4 The first production release under LNOKS shipped about a month after the trial sprint began, followed by a fixed two-week sprint rhythm.
-
Step 4 / 4 With the release process in place, each sprint adds features across web, mobile and the AI assistant, planned together with the founders' own engineers.
Reviews
From a client on a similar project.
This client hasn’t published a review yet. This one comes from another client.
Read on Clutch
“Our app now works well and the users are very happy with it. The glitches have all been resolved and it runs smoothly, as do the new features we requested. They're organized and extremely quick to respond.”
AuthorPilot
A course app taken over from another company, fixed and extended for two book publishers who teach new authors online.
Tell us about your project.
We reply within one business day.
