Every engagement starts with a conversation and a written proposal. Choose a fixed-scope pilot, a build project or a managed service, or combine them as you grow.
A defined first step with an agreed scope, timeline and success measures. It goes live on real work, and we review results with you before you decide what comes next.
Agreed scope and success measures
Live on your real calls, leads or data
Regular reviews and tuning during the pilot
A clear decision point at the end
Typically used for AI Front Office, AI Receptionist and the Prompt & Eval Tune-up.
B
Build project
Designed, built and handed over.
We design and build a workflow, document process or private AI system to a fixed scope, test it with your real examples, and hand it over with documentation your team can use.
Fixed scope, agreed before work starts
Built on the tools you already use
Tested with your real examples
Plain-English documentation and handover
Typically used for workflow automation, document automation and Private AI.
C
Managed service
Run and improved by the same team.
We run, monitor and keep improving what we built. You get regular reviews, support from the people who know your setup, and changes as your business evolves.
Monitoring and support
Regular reviews and tuning
Small changes as your business changes
Optional for build projects; core to customer response
Ongoing for customer response; optional care for automation, Private AI and tune-ups.
Indicative investment
Where engagementstypically start.
A guide to help you plan. Your proposal sets out the final scope and price before any work starts.
$2,500 per featureOngoing tuning optional, $1,000/mo.
Indicative figures in US dollars, based on our published rates. Usage allowances, overage, pilot and cancellation terms are set out in your proposal. Hardware and cloud usage are paid directly by you.
Your proposal
Everything agreedin writing.
Before any work starts, you get a short written proposal in plain English. It covers:
01
Scope and deliverables
Exactly what we will design, build and run, and what is out of scope.
02
Timeline and stages
What happens in Discovery, Design, Build and Run, and when.
03
Price and payment schedule
One-off and monthly fees, and when each is due.
04
Usage and allowances
Included call minutes, texts or other usage, and how anything extra is handled.
05
Pilot, notice and cancellation
How the pilot works, notice periods and what happens if you stop.
06
Data handling and access
Where your data lives, what we can access and how support sessions work.
Delivery method
How we deliver.Four clear stages.
Every engagement follows the same path, so you always know what happens next and what you get at each step.
01
Discovery
We learn how your business works today and where AI will help most.
What you get
Assessment or fit check
Map of tools, people and hand-offs
Agreed goals and success measures
02
Design
We design the solution around your rules, with people in charge of what matters.
What you get
Solution design in plain English
Approval and hand-off rules
A written proposal with scope, timeline and terms
03
Build
We build it on your tools and test it with real examples before anything goes live.
What you get
Connected to the tools you already use
Tested with your real examples
Go-live plan and team briefing
04
Run
We look after it, keep improving it and report back in plain English.
What you get
Monitoring and support
Regular reviews and tuning
Handover notes you keep
Frequently asked questions
Are these final prices?
They are indicative starting figures based on our published rates. Your proposal sets out the final scope and price, agreed in writing before any work starts.
Where are allowances, overage and cancellation terms?
They are set out in your proposal, so they match the scope we agree with you. We walk you through them before you sign.
Do we have to start with a pilot?
No. For customer response, a pilot is the usual first step. For automation and Private AI, most clients start with a fixed-scope build project. We recommend the right starting point on the first call.
Is ongoing care required after a build project?
No. Care is optional for build projects. You own the workflow, system and documentation either way.
Who pays for hardware and cloud usage?
You do, directly. Private AI hardware is bought by you, and cloud or AI processing usage is billed to your own account, so you always see the real running cost.
Start witha conversation.
Tell us what you want to improve. We'll recommend the right engagement, and send a written proposal with scope, timeline and terms.