AppMaker

AppMaker turns a plain-language brief into a running business app with forms, database, auth, and roles, then exports it as a standalone Node.js app, which collapses the scoping phase of custom client work. But the platform is in public beta and explicitly not approved for production use, so no agency can bill a retainer against it today. The strategic play is to absorb the $3 monthly AI credit cost now, build internal reference apps, and hold delivery capacity ready for the moment production approval lands.

AppMaker's public beta status is the framework: treat the platform as a generation engine, not a hosting layer. Agencies describe a client workflow in plain language, let Build mode produce forms, database, auth, and roles, then refine in Design mode. The moment the app must touch live client data, export it as a standalone Node.js application and run it on infrastructure the agency controls. That split keeps the $3 monthly AI credit spend confined to evaluation and prototyping, while billable delivery sits on exported code. A concrete case: an agency scoping a $510/mo Starter App builds the first version in AppMaker in under a day, exports it, and hands the client a Node.js deployment with no beta dependency in the retainer. The rule protects the client contract from a vendor still labeled for development, not production.

The Resale Ceiling Test asks one question before an agency commits a client app to a no-code platform: how far can this build travel before the platform's own limits cap what you can charge? Three variables set the ceiling. White-label depth determines whether the app ships under the agency brand or the vendor's. Customization headroom determines whether complex client requirements force a migration to hand-coded work. Publishing control determines who owns the App Store and Google Play accounts, and therefore the client relationship. BuildFire and GoodBarber both run full white-label reseller programs, so an agency can present the app as its own product and bill a retainer rather than a one-time build fee. AppMySite converts existing WooCommerce or Shopify storefronts into native apps, which keeps scope narrow and the ceiling low but predictable. The framework matters because platform dependency is the category's stated risk, and the ceiling is measurable before the first screen is designed.

Platform Exit Cost is the framework for pricing how much of a client app you can actually walk away with. No-code builders let agencies publish native iOS and Android apps fast, but the asset usually lives inside the vendor's runtime: screens, data models, and integrations are configured in a hosted editor rather than owned as source. The framework asks three questions before signing a retainer: can the app be exported or rebuilt elsewhere, who holds the App Store and Google Play developer accounts, and what happens to client data if the subscription lapses. BuildFire and GoodBarber both run white-label reseller programs, which raises the stakes because the client sees your brand on a dependency you do not control. Forrester's October 2026 warning that distinct AI providers converge on shared infrastructure is the same concentration logic applied to app delivery: redundancy on paper, one failure point in practice.

Adopt AppMaker as an internal prototyping and scoping tool now, and do not attach it to a client retainer or billable deliverable until it exits public beta.

Before signing a build retainer, write the migration clause: name the platform, the data export format, and the hourly rate for a native rebuild.

IF your agency needs to prototype a data-driven internal tool or client workflow and can absorb the public beta limitation, THEN AppMaker is worth a $3 monthly AI credit spend to generate apps from natural language and refine them in Design mode. IF the deliverable must go live for a paying client on a retainer, THEN defer: AppMaker is labeled for evaluation and development only, not production use, so nothing built on it can be billed as a running client app yet. The Node.js export path is the escape hatch to watch, since it would let an agency self-host a generated app once the beta clears.

A fixed-scope sprint that turns one client's plain-language workflow description into a working AppMaker prototype with forms, roles, and server logic, delivered as a clickable evaluation build the client can sign off before any production commitment.