Skip to main content
Run your business · Start
Start

Build and hand over a client operation

Reuse the business foundation, adapt one client workflow and give the team an operation they can run.

Updated October 10, 2026 3 min read

An agency can start each client project with customer records, sales workflows, delivery tasks, billing and AI services already available. Spend the custom work on the client's process: its qualification rules, handoff, reporting or dedicated App.

For a first pilot, choose one complete job. A client engagement could become an assigned access-and-kickoff checklist, or an inquiry could become an opportunity with an owned callback. Use the existing recipes and extension examples as starting patterns.

A fictional workspace directory used to manage client workspaces.
The workspace directory in a fictional installation. Platform administration owns provisioning; client users work inside their authorized workspace. Select the image to view it full size.

Reuse the foundation and adapt the process

Use the first report exercise to learn the source path. For a larger change, give your coding agent the customer's starting situation, example records, required decisions and success check. App design explains how an App can own its own lifecycle while linking to shared customers and work.

A deployment is the application and database your technical owner operates. A workspace is one business's context inside it. Write down which model you are implementing and who owns hosting, provider accounts, updates, support and the eventual handoff.

Prepare a client workspace

These steps require platform administration in a connected installation.

  1. Open Workspaces, create the business with a recognizable name and unique slug, and inspect the returned result.
  2. Invite its administrator. Confirm the invitation, sign-in and selected workspace separately.
  3. Configure branding, enabled Apps and required connections in that business context. Follow Setup.
  4. Run the agreed workflow with controlled records. Check both the business result and the receiving person's view.
  5. Record the installed version, custom capabilities, account ownership and any unresolved limitation.

Keep the platform owner's login separate from client accounts. Provider credentials belong to the business whose messages, data or payments they reach.

Verify separation and recovery

Have the technical owner test two fictional workspaces with different users, including copied URLs, direct record requests, revoked membership and suspension. Also test a duplicate request and a failed provider call through the normal recovery path before importing client data.

Hand over usable work

Give the client its workspace URL, administrator, enabled workflows, operating guide, provider ownership list and escalation contact. Walk through the job together, then have the client complete it independently. Explain how updates are checked and who can restore service.

For an ended engagement, review pending work and access before suspending or archiving the workspace. Agree retention and data transfer separately and use the installed version's verified procedures.

Next: Build with a coding agent or follow the connected installation guide.