App Builder Rule: Price the Exit Before You Price the Build
If a client's app outgrows a no-code builder in 18 months, who pays for the rebuild and can we bill for it? Before signing a build retainer, write the migration clause: name the platform, the data export format, and the hourly rate for a native rebuild.
By InnovaAI ResearchPublished
“If a client's app outgrows a no-code builder in 18 months, who pays for the rebuild and can we bill for it?”
Before signing a build retainer, write the migration clause: name the platform, the data export format, and the hourly rate for a native rebuild.
Agencies quote the build as a one-time project and treat the platform as permanent, then discover at renewal that the client wants features the builder cannot express and the rebuild has no line item in the contract.
No-code builders publish real native binaries, but the app's logic lives inside the vendor's runtime, so a rebuild means re-implementing screens, data models, and integrations rather than porting files. Forrester's October 2026 warning that distinct AI providers converge on shared infrastructure and data sources describes the same concentration problem agencies accept when a client's entire mobile presence sits on one builder. The pricing pressure is real in the other direction too: Anthropic cut Haiku 5.5 token prices by up to 90% on October 7, 2026, which means the AI features clients now expect inside an app get cheaper every quarter while your platform lock-in does not.
- •The client's roadmap includes user accounts, payments, or data models that will keep changing after launch
- •The retainer depends on the app staying live through at least two OS release cycles
- •The client asks for custom logic that no plugin in the builder's marketplace covers
- •You plan to white-label the app and resell it under your own brand
- •The client's internal team will edit content or data without your involvement