Backendless Client Workspace Setup (Onboarding)

Backendless Client Workspace Setup (Onboarding)

1. 01

   Create the agency Backendless account and open the team access panel

   Register the agency account first, not the client's, so app ownership and billing stay with the agency. Add delivery staff as team members; the Free Plan allows unlimited development team size, so seat count is not the constraint at this stage.

2. 02

   Review App Blueprints and choose a hosting model before building

   Backendless supports cloud, self-hosted, and managed hosting. Pick the model per client contract now, because migrating a live real-time database later costs delivery hours you cannot bill back.

3. 03

   Create the client app and set the database schema in the real-time relational database

   Define tables and relations for the core client workflow. The Free Plan caps you at 20 database tables and 1 GB file storage, so map the schema against those ceilings before the pilot ships.

4. 04

   Build the pilot feature with the Visual UI Builder and Codeless Logic Blocks

   Assemble one end-to-end feature (for example booking plus confirmation) rather than a full app. Wire authentication providers and role-based access control at this point so client user roles are testable in the pilot.

5. 05

   Connect external tools through the integration layer

   Attach FlutterFlow, Bubble, Adalo, Zapier, or Make depending on what the client already runs. If the client's frontend lives in FlutterFlow, Backendless carries the backend and the client keeps their existing UI investment.

6. 06

   Walk the client through the pilot and confirm the branding decision

   Show the working feature, then settle white-labeling in writing. Deployed apps carry Backendless branding unless the agency holds the Partner Plan at $75/month billed annually or $90/month billed monthly, and that cost belongs in the retainer conversation, not absorbed silently.

7. 07

   Deploy to the client domain and document the handoff

   Point the app at the client's domain, record API request limits (50 requests/minute on the Free Plan), and leave the client a short runbook. Keep admin credentials with the agency so support stays inside the retainer.