In this guide
What you’ll finish with
A proposal the client can review with a clear delivery scope and definition of launch readiness.
Before you begin
- An agreed client brief and customer task.
- A tested example or an accurate account of the proposed setup.
- The selected plan and delivery cost assumptions.
State the customer problem
Describe the current situation in the client’s terms. Identify the questions customers ask, what information is available and where the next step becomes unclear. Avoid opening with a general claim about how every business needs AI.
Name the outcome the proposed service supports, such as a useful enquiry or an approved booking route. Keep the business result you hope to influence separate from what the agent is configured to do.
Proposal opening
[Client] receives [type of customer question or enquiry]. The proposed service will help visitors [specific task] using [approved information]. When visitors need [booking or follow-up], it will use [agreed route]. The client team remains responsible for [confirmation, advice, quotes or fulfilment].
Describe the configuration
In KugaClient workspace › Actions
List the actual sources and workflows. Include the launch channels, Website Chat appearance, request fields, booking method and external delivery where it is in scope.
If social channels, portal access or Human Handover are included, name the required plan and configuration. Avoid describing a planned or unconnected integration as part of the working service.
- List the approved sources and launch channels.
- Record the workflows and their intended outcomes.
- Identify the plan and connection dependencies.
- Compare the proposal with the tested demonstration.
Configuration schedule
Client workspace: [name]. Launch channels: [Website Chat and any agreed social channel]. Knowledge: [approved website scope and file versions]. Response instructions: [tone, role and boundaries]. Contact Requests: [capture trigger and summary requirements]. Scheduling: [approved booking page or connection]. Appearance: [approved client identity and placement]. Delivery: [notification recipients and any tested webhook]. Additional features: [portal or handover, with the required plan].
Define delivery and acceptance
Specify what your agency will build, what the client must provide and how both parties will review it. Include the expected answer for each important test and the destination of any request or booking.
A launch date depends on accurate sources, working connections and client review. Make those dependencies visible rather than treating the date as a substitute for acceptance.
Acceptance schedule
Before launch, the client approves the source set, public wording and enquiry process. The agency tests the agreed routine questions, unknown questions, request capture and booking paths. The live website is checked on desktop and mobile. A complete test request reaches the agreed recipient. Outstanding issues and their owners are recorded before approval.
Separate fees and ongoing ownership
State the setup fee, ongoing agency service and selected client plan. Describe the included review cadence, support hours and change allowance. Explain how additional work or plan changes are approved.
Name the client’s source owner and follow-up owner. The service needs both current information and a person or team who acts on the results. Include the relevant privacy and data processing information.
Commercial and ownership schedule
Setup fee: [amount and payment terms]. Client plan: [plan and current platform fee]. Ongoing service: [fee, review cadence and included allowance]. Additional work: [scope and approval process]. Agency owner: [name and support contact]. Client source owner: [name]. Client enquiry owner: [name and review process]. Data handling: [agreed roles and applicable terms].
Set a useful first review
Agree the first review period and evidence you will use. Include conversation quality, enquiry usefulness and confirmed client outcomes where available. State how you will gather those outcomes.
Finish the proposal with the decisions the client needs to make: scope, source approval, plan, ownership and acceptance process. Once approved, use the onboarding brief to turn the document into a build record.
- The proposed service matches the tested example.
- Dependencies and exclusions are visible.
- The chosen plan supports the scope.
- Both parties have named responsibilities.
- The first review uses evidence that can be obtained.