Implementation BlueprintExecution layer

AppMaker Internal Tools Prototype Sprint (5-7 days)

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. Time: 5-7 days.

By InnovaAI ResearchPublished

App Builder

How do you implement it?

Blueprint

AppMaker Internal Tools Prototype Sprint (5-7 days)

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.

Prerequisites
  • Signed client discovery notes covering one workflow, its data fields, and the user roles that touch it
  • Agency AppMaker account created and one internal reference app generated to learn the Build mode and Design mode split
  • Written client acknowledgement that AppMaker is in public beta for evaluation and development, not production use
  • Named client reviewer available for two 45-minute walkthroughs during the sprint
  • Agreed definition of the single workflow in scope, with anything outside it parked for a later phase
Execution Timeline
  • 1.Create the client project in AppMaker and draft the natural language description of the target workflow
  • 2.Generate the first app version in Build mode and log which forms, tables, and roles the AI produced versus what the client asked for
  • 3.Confirm the built-in database, auth, users, and roles defaults before any customisation
  • 1.Move into Design mode and reshape generated forms so field labels and required fields match the client's vocabulary
  • 2.Adjust the data model and table relationships to reflect how the client actually records the workflow today
  • 3.Set user roles so each client team member sees only the records their job requires
  • 1.Write the server logic and jobs that drive the workflow's state changes
  • 2.Use SQL and JavaScript editing in Design mode where the visual builder cannot express a client rule
  • 3.Seed the app with a sample of anonymised client records so reviewers see realistic screens
  • 1.Run the first client walkthrough and capture every change request in a single list
  • 2.Apply the highest-value refinements conversationally in Build mode rather than rebuilding screens by hand
  • 3.Re-test role permissions after the refinement pass to confirm nothing widened unintentionally
  • 1.Configure any remaining workflows and jobs, then run an end-to-end pass through the full workflow as each role
  • 2.Document the app's data fields, roles, and logic in a handover note the client's team can follow
  • 3.Prepare the export path: confirm the app can be pulled out as a standalone Node.js application if the client later wants it on their own infrastructure
  • 1.Deliver the second walkthrough and record sign-off or a written list of remaining gaps
  • 2.Hand the client team a short training session on app usage and the self-service edits they can safely make
  • 3.Close the sprint with a written recommendation on whether to continue in AppMaker or pause until it leaves public beta
$3 to $12 in AppMaker AI credits across the sprint (billed at $3 per month of AI credits), plus 30 to 40 internal hours; the client-facing prototype fee sits in the $510/mo Starter App band if the engagement converts to an ongoing retainer.5-7 days
ROI Logic

AppMaker's only published cost is $3 per month in AI credits, so the tool line on a prototype sprint is effectively noise against 30 to 40 hours of delivery labour. That gap is the margin: the agency sells scoped discovery, generation, refinement, and sign-off, and the platform charge never threatens the retainer. Because AppMaker is in public beta and not approved for production use, price this as a paid evaluation or prototype phase rather than a build-and-run retainer, and convert to the $510/mo Starter App offer only once the client accepts the beta constraint in writing.

Deliverables
  • A working AppMaker prototype covering the single in-scope workflow, with forms, data model, and role permissions configured
  • A written scope and gap log listing every change request raised in the two client walkthroughs and its resolution
  • A role and permissions matrix documenting what each client user can see and edit
  • A handover note covering data fields, server logic, jobs, and the safe self-service edits the client team can make
  • A go or pause recommendation stating whether the app should stay in AppMaker's beta environment or wait for production approval
Definition of Done

The client signs off in writing that the AppMaker prototype reproduces their in-scope workflow end to end across every configured role, with the beta limitation acknowledged in the same document.

Open the AppMaker courseAppMaker decision recordBrowse the Academy

More on AppMaker

More for App Builder