The Short Answer
An off-the-shelf AI receptionist subscription is a templated platform you configure yourself and switch on the same day, with no setup fee. A custom voice agent from us is built around your own systems and rules, priced once we know what you need it to do.
If you want to find out whether an AI can answer your phone at all, take a subscription. It is quicker to start, faster to switch on and easy to cancel. Build when the agent has to do something the subscription cannot, which in practice means booking into your own system, following rules specific to your business, or handling data you cannot hand to a shared platform.
This guide sets out what sits underneath both options, because the mechanics are the same in each and understanding them is what stops you overpaying for the wrong one.
Both Options Run on the Same Engine
This is the part most comparisons skip. Whether you subscribe or commission a build, the call is handled by roughly the same stack: speech recognition, a language model, a voice, and a telephony connection. The infrastructure providers behind that stack bill on a usage basis, charging per minute of call handling rather than a flat rate.
That tells you something useful. Usage-based infrastructure billing is the floor under every option on the market. A subscription bundles that into a monthly fee and takes a margin. A build passes it through and charges you for the engineering around it.
Neither approach is dishonest. But if a provider will not tell you how minutes are actually charged and what happens as your volume changes, you cannot properly compare anything.
What You Actually Get for a Subscription
Subscriptions are genuinely good at a specific job: answering calls with information you can express in a script, and taking a message.
You typically get a phone number or a divert from yours, a configurable greeting, answers to questions you write out, message taking, and an email or text summary after each call. Setup is usually self-service and measured in hours. Many providers offer a trial or a limited free tier, which is the strongest argument for starting here.
Where they run out of road is integration. A subscription can usually book into a mainstream calendar. It generally cannot look up whether a caller is an existing client in your system, check what they had done last time, apply your own rules, or write the outcome back to the record your team actually works from.
What You Get for a Build
A build is worth paying for when the value is in what happens around the call rather than in the call itself.
Our own tiers, from /services/ai-voice-agents, scale from simple call answering, through booking into a live diary or CRM and recognising callers from your records, up to several locations or outbound work. What determines the price at every tier is how many systems the agent has to read from and write to, not a flat rate card — and the running cost reflects the same usage-based call billing described above rather than a marked-up bundle.
The practical difference is that a build reads and writes your data. It knows the caller is a patient due a recall, an applicant mid-referencing, or a customer with an order in transit, and it can act on that.
The Comparison
| Subscription | Custom build | |
|---|---|---|
| To start | Configure and switch on yourself, no setup fee | Scoped and quoted on a discovery call |
| What drives the ongoing cost | A flat platform plan plus call usage | How many systems it connects to and how it is supported |
| Live in | Hours to days | 1–2 weeks, or 2–4 with booking |
| Try before you buy | Trials and free tiers are common | No; scoped on a discovery call |
| Books into your diary | Mainstream calendars usually | Your actual system |
| Knows who is calling | Rarely | Yes, from your records |
| Follows your own rules | Within a script | Fully |
| Where data sits | The vendor decides | You decide |
| If you leave | Cancel, keep nothing | You own it |
Being Straight About Our Own Weakness
A subscription lets you try an AI receptionist this afternoon for very little commitment. We cannot match that speed, and it would be silly to pretend otherwise.
What we would say is that the setup fee is not a markup on the same thing. It buys the work of connecting the agent to your systems, writing the rules for your business, and testing it against the calls you actually get. If your requirement is "answer the phone and take a message", that work is not worth paying for and a subscription is the better buy. If your requirement is "book it, check the record, and tell the right person", it is the only thing that makes the agent useful.
The failure mode we see is running subscription fees for years for something that never quite fits, because each individual bill felt too small to bother reviewing.
The Thing That Goes Wrong on Both
Neither option fails in the way people expect. The agent almost never breaks. What happens is quieter: it keeps answering confidently while the business changes around it.
Your services change and the script still describes the old ones. You stop offering something and it keeps booking people in for it. A member of staff leaves and calls still route to them. None of this shows up as an error, because from the system's point of view nothing is wrong. You find out when a customer arrives expecting something you no longer do.
On a subscription this is your job and nobody will remind you. On a build it is a support conversation, which is part of what the monthly fee covers, but it still depends on somebody telling us when the business changes.
Whichever route you take, put half an hour in the diary once a month to read a handful of real transcripts. It is the single highest-value habit around either option, and skipping it is the most common reason people conclude that AI phone answering does not work when what actually happened is that nobody maintained it.
How to Decide in Ten Minutes
Answer these five, honestly.
- 1. What do you want the agent to do beyond taking a message? If the answer is nothing, subscribe.
- 2. Where does an appointment need to land? A mainstream calendar suits a subscription; a practice or agency system usually needs a build.
- 3. Does the agent need to know who is calling? If yes, it needs access to your records.
- 4. What would go wrong if it got something wrong? A missed message is an annoyance. A wrong appointment in a clinic diary, or the wrong answer about a legal matter, is not, and that argues for rules you control.
- 5. Who is asking about your data? If a client, insurer or regulator will ask where call recordings and transcripts are held, you need to be able to answer precisely.
Two or more answers pointing at your own systems means a build. Otherwise start with a subscription and revisit in six months.
Whichever You Choose, Get These Right
Call recording notices. If calls are recorded, callers need telling. Confirm your wording and your lawful basis with whoever handles data protection for your business.
Where transcripts live. Conversations are personal data. Ask any provider where it is processed, how long it is kept and who can see it, and get the answer in writing.
The handover. Decide before launch what the agent must never handle and what happens when it meets one. This matters more in some sectors than others; /industries/dental-practices sets out how it works where clinical urgency is involved.
Something to measure. Calls answered, calls resolved without a person, appointments booked. Without these you cannot tell whether either option is working.
What We Do
We build the custom side, and on a free discovery call we will tell you when a subscription is the better buy for what you need. If you are already running one and it has stopped fitting, that is a good place to start from: the calls it handled badly are the specification for the build.
For the fuller picture of what drives cost see /blog/ai-voice-agent-cost-uk, and for the comparison against employing someone see /blog/ai-phone-answering-vs-receptionist-cost-uk-2025.
Want an honest read on which side you fall? Book a free discovery call at /contact.
Frequently Asked Questions
Is a subscription AI receptionist good enough for a small business?
For answering calls, giving out information you can write down and taking messages, usually yes. It stops being enough when the agent needs to book into your own system, recognise existing customers, or follow rules specific to how you work.
Why is there a setup fee on a custom build when subscriptions have none?
The fee covers connecting the agent to your systems, writing your rules and testing it against your real calls. If you only need message taking, that work is not worth paying for and a subscription is the better buy — we will say so on the call, and give a fixed quote once we know what you actually need.
How are call minutes actually charged?
The underlying voice AI infrastructure bills on a usage basis, per minute of call handling, and both subscriptions and custom builds sit on top of that same billing model. A subscription bundles it into its monthly plan; a build passes the usage through. Ask any provider how their pricing scales with your call volume before you compare quotes.
Can we start on a subscription and move to a build later?
Yes, and it is often the sensible order. Six months of real calls tells us exactly which ones the subscription handled badly, and those become the specification. You get a better agent for having waited.
Who holds the call recordings and transcripts?
With a build, you decide: we set where data is processed and how long it is kept, typically the UK or EU under a data processing agreement. With a subscription the vendor decides, so ask and get the answer in writing. Confirm your own obligations, including call recording notices, with whoever handles data protection for your business.