Client App Requirement Triage (Onboarding)

Client App Requirement Triage (Onboarding)

1. 01

   Inventory the client's must-have native capabilities before opening any builder account

   List every feature the client named in discovery (offline mode, biometric login, camera upload, Bluetooth hardware pairing) and mark each as native-required or webview-tolerant. This single pass determines whether the project fits the category at all.

2. 02

   Classify the build as webview wrapper, template-based, or fully custom

   A retail client whose site already works on mobile is a wrapper candidate (Median, MobiLoud, AppMySite). A membership or events client with standard screens fits a template builder (GoodBarber, Shoutem, BuildFire). Only the third bucket needs a canvas tool like Adalo or Draftbit.

3. 03

   Score the client's data model complexity on a 1 to 5 scale

   Count the distinct record types (users, orders, bookings, messages) and the relationships between them. Anything above three related types with role-based permissions should be flagged for a custom backend or a tool with a hosted relational database.

4. 04

   Confirm the client's app store accounts and legal entity are in place

   Apple and Google both require a registered developer account under the client's legal name for a client-owned listing. If the client wants the app published under the agency's account, document that in writing before build starts.

5. 05

   Map every third-party integration the app must touch

   Payments (Stripe, PayPal), CRM, email, and analytics each add build time and a potential failure point. Note which integrations the chosen platform supports natively versus through Zapier or a custom API call.

6. 06

   Set the resale and white-label terms in the statement of work

   Decide whether the agency resells the app under its own brand (BuildFire, GoodBarber, and Shoutem all offer full white-label programs) or hands the client a direct platform subscription. This choice affects margin, support obligations, and who owns the store listing.

7. 07

   Write a one-page scope decision memo and get client sign-off

   The memo states the chosen build path, the platform category, the integrations in scope, and the features explicitly deferred to phase two. Sign-off here prevents the mid-build scope creep that kills no-code project margins.