App Builder Rule: Price the Exit Before You Price the Build
If this client app has to leave the platform in 18 months, what does the migration cost and who owns the code, data, and store listings? Before signing a build retainer, document the data export path, store account ownership, and rebuild estimate, then price the exit into the contract.
By InnovaAI ResearchPublished
“If this client app has to leave the platform in 18 months, what does the migration cost and who owns the code, data, and store listings?”
Before signing a build retainer, document the data export path, store account ownership, and rebuild estimate, then price the exit into the contract.
Agencies quote the build at platform speed and never model the migration, so a client who outgrows the template (or a vendor who reprices) turns a profitable retainer into an unpaid rebuild the agency absorbs to keep the account.
Platform concentration is the structural risk in this category: a handful of vendors control pricing and access, and product churn is accelerating, so any client app built on a single no-code stack inherits that vendor's continuity risk. The same concentration pattern is visible across the AI stack agencies already depend on, where a single tool shutting down can halt client delivery unless a fallback is documented. No-code builders publish native binaries, but the screens, data models, and business logic usually do not travel, which makes the rebuild estimate the real cost of the engagement.
- •The client's app depends on workflows, integrations, or data models that no template covers, so custom logic will accumulate over time
- •The retainer assumes multi-year app maintenance but the platform's pricing, ownership terms, or roadmap are outside the agency's control
- •The client operates in a regulated or high-sensitivity sector where data residency and export rights must be contractual
- •The agency plans to white-label and resell the app under its own brand to several clients on the same build