Build an agency offer from delivery costs, usage assumptions, and support obligations. Includes a clearly hypothetical unit-economics example and a pricing worksheet framework.
An AI receptionist price should cover the work and risk of delivering the agreed service. A per-minute platform quote describes only part of that cost. The agency may also configure routing, maintain knowledge, operate integrations, inspect calls, answer support requests, and manage an outage. Pricing becomes fragile when those responsibilities are sold inside an undefined “unlimited” promise.
Separate the commercial decision into three questions: what must be built, what must be operated every month, and which costs change with usage. A setup fee and a recurring service fee can make that distinction clearer, but neither automatically produces a healthy margin. Estimate the work, test the assumptions, and review the result after launch.
Start with a complete cost map
| Cost group | What to include | What changes the estimate |
|---|---|---|
| Implementation | Discovery, conversation design, routing, integration, testing, training, and project management. | Number of workflows, systems, locations, and approval rounds. |
| Platform and telephony | Conversation processing, carrier legs, number rental, recording, storage, and optional features. | Call duration, routing topology, selected components, destination, and vendor terms. |
| Ongoing delivery | Monitoring, exception review, content updates, reporting, and support. | Review frequency, service hours, change volume, and incident obligations. |
| Commercial overhead | Payment processing, account administration, sales effort, and relevant insurance or professional advice. | Client requirements and the agency’s operating model. |
Use a realistic call model
Estimate connected calls and billable minutes separately. A hundred short calls can create different support work from a hundred long calls. Ask how transfers, retries, voicemail, concurrent calls, and different destinations are billed. Some configurations involve multiple telephony legs. Check actual invoices during the pilot rather than multiplying one advertised unit price by an optimistic call count.
Use three planning scenarios: expected, high volume, and operational trouble. The trouble scenario should include additional human review or support even if call volume is unchanged. A broken CRM integration can make a quiet week expensive. Keep vendor prices in a dated working model and link to official pricing; do not treat the hypothetical figures below as a current platform quote.
A hypothetical monthly example
Assume an agency charges a client $900 per month for a defined service. For illustration only, suppose combined platform and telephony spend is $160, direct monitoring and support labor is $180, allocated integration operation is $40, and direct payment costs are $30. These are invented planning inputs, not vendor prices, recommended market rates, or a forecast of any agency’s results.
| Illustrative item | Amount |
|---|---|
| Monthly service revenue | $900 |
| Direct delivery costs: $160 + $180 + $40 + $30 | $410 |
| Gross profit before general overhead and tax | $490 |
| Gross margin: ($900 − $410) ÷ $900 | 54.4% |
If direct support labor rises from $180 to $360, total direct costs become $590. Gross profit falls to $310 and gross margin becomes 34.4%. The same subscription revenue now supports a much smaller contribution to overhead. Gross profit is not net profit; salaries outside direct delivery, sales, rent, taxes, and other operating costs may still need to be paid.
Margin and markup also differ. With $410 of direct cost, $490 of gross profit represents a 119.5% markup on cost, but a 54.4% margin on revenue. Label the denominator in every spreadsheet. Otherwise, a proposal and a finance review can appear to agree while using different definitions.
Define the setup fee by deliverable
Estimate hours for each implementation stage and specify the assumptions behind them. Include technical access checks and client review time. Name the integration and the permitted action: creating a callback task is different from searching multiple calendars, collecting payment, and rescheduling an existing appointment. Price additional workflows through an agreed change process rather than silently absorbing them.
Make the recurring fee understandable
- State the included monitoring and review cadence, not just “optimization.”
- Define supported service hours and how urgent incidents are reported.
- Specify included changes, approval rounds, and what counts as a new project.
- Explain usage allowances or pass-through billing, overage approval, and spending alerts.
- Set a process for pausing the service or routing callers to a human when a limit is reached.
- Document cancellation, number transfer, data export, and offboarding work.
Keep value claims tied to evidence
A client may value faster response or better intake, but do not convert every answered call into claimed new revenue. Track qualified inquiries, confirmed appointments, show rates where available, and the attribution limits. Compare the pilot with a documented baseline. Some calls would have reached a human anyway, and some callers are outside the client’s service area.
Review actual direct costs after the pilot and on an agreed cadence. Reprice material scope changes transparently. If the offer cannot support the required service standard at a price the client accepts, simplify the deliverable or decline the work. Recurring revenue is useful only when the recurring obligation is understood.
Sources and editorial approach
Reviewed October 23, 2026. The operational frameworks and hypothetical examples are Business Meets AI editorial guidance, not vendor promises or measured client results. Verify contractual and technical requirements for your own implementation.
- Twilio: official Voice pricing, including separately listed services
- Retell: current official pricing
- Vapi: current official pricing
Keep building your agency playbook
Explore the Agency Hub, research the AI Tools Directory, or compare platforms side by side. For a conversation about practical implementation, listen to How Businesses Actually Deploy AI.