GuideAgency services

Build a repeatable client delivery process

Standardise the brief, build sequence and review record while keeping each client’s configuration specific to their business. Use actual delivery time to check capacity before taking on more clients.

In this guide

What you’ll finish with

A delivery system you can reuse without treating different clients as identical deployments.

Before you begin

  • One completed or in-progress client service.
  • A record of setup time and ongoing work.
  • A clear view of the team’s delivery capacity.

Use one intake record

Collect business information, sources, customer tasks, tone, boundaries and follow-up ownership in a consistent brief. Record the approval status and source version rather than relying on details scattered across messages.

Use the same headings for every client, but let the answers drive the configuration. A dental clinic’s administrative scope and a store’s catalogue questions need different sources and tests.

Create a build sequence

In KugaAgency workspace › Clients

Create the client workspace and review Business details. Prepare Knowledge, then the workflows required by the customer task. Configure the launch channel and its appearance. Choose the plan that supports the complete scope.

Record the settings and connections you need to check. Keep client credentials and private invitation links outside a general delivery document.

  1. Review the brief and source approval.
  2. Create and configure the client workspace.
  3. Prepare Knowledge and configure the actions you need.
  4. Configure the channel and appearance.
  5. Test the visitor journey and saved results.
  6. Install and verify the live service.

Reuse the delivery process while keeping each client’s data, sources and configuration in its own workspace.

Maintain a small acceptance suite

In KugaClient workspace › Agent › Configuration

Write a reusable test structure: routine answer, missing information, unclear intention, enquiry capture and the configured booking or handover path. Supply client-specific questions and expected results inside that structure.

After a relevant source or workflow change, repeat the affected tests. Keep a date and reviewer with the result so another team member can understand what was checked.

Reusable test record

Client and date: [record]. Question or action: [exact test]. Expected source or workflow: [record]. Expected result: [answer, request or booking outcome]. Observed result: [record]. Saved record or destination checked: [record]. Issue and next action: [record]. Reviewer: [name].

Schedule the operating work

Define the review cadence and who owns each client. Record source updates, conversation findings, request feedback and planned changes in one place. Use available Insights reports when their coverage is suitable.

Give the client an agreed report and support route. Set up Client Portal access when the plan and service include it, and share private setup links through the agreed channel.

Calculate capacity before increasing client numbers

Use actual setup and review time to estimate what the team can support. Include client communication, testing and exception handling. A revenue target should be checked against this workload.

For illustration, £5,000 of monthly recurring revenue could mean ten services priced at £500. That is arithmetic, not a forecast. The margin depends on platform fees, delivery time, support and the cost of finding and retaining those clients.

  • Setup and recurring work are measured separately.
  • There is capacity for the promised reviews.
  • Service revenue is considered alongside delivery cost.
  • A new client has a named owner before launch.

Improve the process from evidence

After each deployment, identify which step caused rework. Improve the brief, source checklist, acceptance record or client instructions at that point.

Keep product-specific configuration current as Kuga develops. A reusable process is useful because it supports careful work, not because it removes the need to understand the client.

Pick a client you know.

Show them their AI.

Use their website to build a demo. Put your name on it and let them try it.