In this guide
What you’ll finish with
A documented plan choice and service scope with a cost basis you can review as the client grows.
Before you begin
- The intended channels and workflows.
- An estimate of reply volume and required features.
- Your setup, review and support costs.
Calculate the monthly contribution
Enter your live client count, retainer, delivery hours and other costs in the free agency pricing calculator. It uses the current Kuga plan prices in GBP or USD and keeps one-off setup fees separate from the recurring service.
Review what remains after the costs you have entered. Include shared overhead and acquisition expenses where relevant; the example is a cost model, not a forecast of client sales.
How do platform costs grow with your client count?
The following GBP examples assume each live agent uses the same plan. These are Kuga subscription costs, not suggested client fees. Each agent keeps its own reply allowance; the allowances are not pooled.
An agency could, for example, charge £249 per month for a managed service using a £39 Pro subscription. The £210 difference still needs to cover delivery time, support, other tools and business costs. It is not net profit or a promise about what your clients will pay.
| Live client agents | Essential / month | Pro / month | Advanced / month |
|---|---|---|---|
| 1 | £19 | £39 | £79 |
| 5 | £95 | £195 | £395 |
| 10 | £190 | £390 | £790 |
What does the client need?
Start with the brief. Record whether the client needs Website Chat, social messaging, Insights, portal access or Human Handover. Decide what the service needs at launch and what can be added later.
Estimate usage from evidence where possible, such as existing chat activity. Treat a new deployment’s estimate as a starting assumption and agree when it will be reviewed. A conversation can contain several AI replies.
- Launch channels and workflows are named.
- The required integrations are supported.
- The estimated volume has a stated basis.
- The review and support work is defined.
Match the requirements to a plan
In KugaClient workspace › Subscription & Usage
Use Subscription & Usage to check the client’s current plan and allowances. Preview is for building and testing, with 50 lifetime AI replies. Choose a paid client plan when the service is ready for its intended live use.
The plan differences affect more than reply volume. Essential includes one chosen deployment: Website Chat, WhatsApp or Instagram. Pro combines deployments and adds Insights, Client Dashboard and Webhooks. Advanced adds Human Handover and higher allowances. Confirm the current price and included features on the pricing page before quoting.
- Open Subscription & Usage for the correct client.
- Check the required features against current plan inclusions.
- Review reply volume and other allowances.
- Record the selected plan and current price in the proposal.
| Plan | AI replies | Selected allowances |
|---|---|---|
| Preview | 50 lifetime | Build and test the client agent |
| Essential | 1,000 per month | 5 MB knowledge storage; one chosen deployment |
| Pro | 5,000 per month | 25 MB; 2 portal seats |
| Advanced | 10,000 per month | 100 MB; unlimited portal seats; 2 handover seats |
Separate setup from ongoing delivery
Estimate the one-off work: client brief, source review, instructions, channel configuration, appearance, installation and acceptance testing. A client with conflicting documents or several channels needs more preparation than a single clear website.
Then define the recurring work. Specify how often you review conversations, update knowledge, test changes, prepare a report and respond to the client. Avoid selling undefined ongoing optimisation without a delivery limit.
Example scope record
Setup: one client workspace, approved website sources, Website Chat appearance, Contact Requests, one booking route, installation and agreed launch tests. Monthly service: one conversation review, one report, an agreed allowance for source and workflow changes, and support during the stated service hours. Additional work: new channels, new enquiry journeys, a website rebuild or changes outside the included allowance are scoped separately.
Build a cost model
Add the platform fee, delivery time, support allowance and any tools your agency needs for this client. Use your own internal cost rate and allow for the time spent communicating, checking changes and handling exceptions.
Keep the maths visible. A service price should make sense at the level of delivery you have promised, rather than relying on a headline markup alone. Review the margin when actual support or usage differs from the estimate.
Illustrative calculation, not a price recommendation
Monthly delivery cost = platform fee + review hours × internal hourly cost + support allowance + other client-specific costs. Monthly contribution = service revenue − monthly delivery cost. Setup contribution = setup fee − setup delivery cost. Record the assumptions alongside the calculation and replace estimates with actuals after the first review period.
Write the client-facing terms clearly
Name the selected plan, the included delivery work and the conditions for additional work. Explain who approves source changes, who follows up enquiries and how usage or plan changes are handled.
Link the current privacy information and data processing terms where relevant. Keep the client’s operational obligations clear, including maintaining accurate sources and providing the team that handles enquiries or handover.
- The client plan and service fee are distinguishable.
- Included work has a cadence and limit.
- Extra work and plan changes have an agreed process.
- The client has a source and enquiry owner.
- Results are described without unverified guarantees.
Review the first live period
In KugaClient workspace › Subscription & Usage
Compare actual usage and delivery time with the estimate. Review conversation quality and enquiries alongside the costs. Recommend a change when a feature, volume or service requirement justifies it.
Use a monthly report to explain what changed and why. Keep usage, verified client outcomes and commercial assumptions as separate entries so the client can assess the recommendation.