Operating ProcedureExecution layer

AppMaker Beta Sandbox Provisioning (Onboarding)

A checklist with 7 steps: Create the agency AppMaker account and confirm the public beta status banner before any client work begins.

By InnovaAI ResearchPublished

What are the steps?

checklist

AppMaker Beta Sandbox Provisioning (Onboarding)

  1. 01

    Create the agency AppMaker account and confirm the public beta status banner before any client work begins

    AppMaker is labeled for evaluation and development, not production use. Record that constraint in the engagement file so no delivery lead promises a live client deployment on this build.

  2. 02

    Generate one internal reference app in Build mode from a plain-language description

    Describe a workflow your own agency runs (intake form, timesheet, asset tracker) so the team sees how the AI maps a sentence to forms, database tables, server logic, and user roles before a client workflow is involved.

  3. 03

    Audit the generated database, auth, users, and roles in Design mode

    Inspect every table, field type, and role permission the generator produced. Beta output needs line-by-line review; treat generated schema as a draft, not a spec.

  4. 04

    Refine forms, SQL, and JavaScript in Design mode and log each manual edit

    Keep a change log of what the AI produced versus what your team rewrote. That log becomes the estimate basis for the $510/mo Starter App offer and its 20h setup budget.

  5. 05

    Test the standalone Node.js export on agency infrastructure

    Export the reference app and run it outside AppMaker. Confirm the export carries the schema, auth, and logic intact, since client handoff may eventually depend on that path rather than the hosted beta.

  6. 06

    Set the AI credit ceiling at the $3 monthly credit tier and monitor consumption

    Track credit burn per generated app during evaluation. If a single client workflow exhausts the monthly allowance, that cost must be priced into the retainer before scoping grows.

  7. 07

    Write the beta disclosure clause into the client SOW before any build starts

    State plainly that apps built on AppMaker during public beta are prototypes for internal evaluation, and that production hosting decisions wait until the vendor lifts the beta restriction.