How Voice AI Vendors and Services Partners Should Scope the First Deal

A first partner-led voice AI deal goes wrong in a predictable place: the client, the services partner and the platform vendor each assume one of the others owns a piece of the work. The fix is a written scope with one discovery owner, one call type, a named owner for every workstream, vendor services only where the deal actually needs them, and services priced separately from usage.

This is the scoping path we would hand a partner before their first quote goes out. If you are the client, it is also the list of things to ask your partner to put in writing.

TL;DR

• The partner owns discovery, because the partner owns the client relationship and runs the agent after launch.
• Scope the first deployment to one call type, one entry point, one system of record and one transfer path.
• Bring in vendor implementation support when the risk sits in the platform layer: contact center telephony, enterprise contract terms, or capacity above standard limits.
• Write the split as a table with a single owner per row, including the client's own rows.
• Price the services portion separately from platform usage, and confirm any vendor services cost before you quote.
• Commission, minimum deal sizes and vendor services pricing are questions to agree with the vendor, not assumptions to build into a quote.

Who should own discovery in a partner-led deal?

The partner should. The partner holds the client relationship, writes the statement of work, and will be the one fixing the agent in month three, so discovery has to produce answers the partner can deliver against.

The vendor joins discovery for a narrow set of questions: whether the client's telephony, compliance and volume requirements fit a standard plan or need an enterprise contract. Settle those before scope is written, not after the client has signed.

Discovery should come back with these answers in writing:

• Call types and monthly volume for each, from the client's own reporting rather than an estimate.
• Entry point: a new number, an existing number, or a transfer from an existing IVR or contact center platform.
• Systems of record the agent must read from or write to.
• Where calls go when the agent cannot help, and during which hours.
• Compliance requirements, such as a BAA for health data, custom contract terms, data retention limits or SSO.
• Who on the client side approves the agent's script and signs off on go-live.
• Who changes the agent after launch, and how often the client expects changes.
• The one number that decides whether the first deployment worked.

If the compliance or capacity answers point to custom terms, the vendor conversation moves earlier. On Retell, a custom MSA, DPA or BAA, SSO and role-based access control are listed on the Enterprise plan, not pay-as-you-go, per the pricing page. A deal that needs any of them is an Enterprise conversation from the start.

What should the first deployment include?

One call type, done well enough to expand. Picking the call type, and testing it on real calls, is covered in how to evaluate a voice agent platform before go-live. The scoping job here is drawing the line between phase one and phase two.

Two scoping checks change the size of the build.

Is the system of record a built-in integration? Retell's integrations page lists HubSpot, Salesforce, Microsoft Dynamics 365, GoHighLevel and Zoho CRM for CRM, Zendesk for support tickets, Calendly, Cal.com and GoHighLevel for scheduling, and Google Drive, Microsoft OneDrive and Notion as knowledge base sources. Anything else is a custom function calling the client's own API, which is development work and should be scoped as such.

Does the client keep their existing telephony? Retell connects to existing carriers through elastic SIP trunking or by dialing a SIP URI, and its docs include setup guides for Five9, Genesys Cloud, Amazon Connect and Avaya. A contact center integration involves the client's telephony team, so name that person in the scope.

Build in a test path from the start. Retell supports simulation testing with graded test cases, and agent versions with prod and staging environment tags, so a change can be tested on a new version before the prod tag, which the production number follows, is moved to it.

When is vendor professional services worth bringing in?

Bring the vendor in when the risk in the deal sits in the platform layer rather than in the client's business. Partners know the client's process; the vendor knows how its platform behaves at the edges.

Retell's pricing page lists Dedicated Implementation Support as an add-on to the Enterprise plan, alongside a named account manager and 24/7 support with a dedicated portal. Retell does not publish a price or a minimum deal size for that add-on, so treat both as questions for the vendor.

Signals that vendor involvement is worth the cost:

• The agent sits behind a contact center platform over SIP, and transfers have to return calls to human queues.
• The client needs a custom MSA, DPA or BAA, or SSO.
• The client needs volume pricing, a dedicated stable server, or concurrency well beyond the 20 concurrent calls a pay-as-you-go workspace includes by default.
• It is the partner's first deployment of this pattern, and a mistake would cost the client relationship.

Signals the partner can deliver alone: a single location, a built-in integration, a new or forwarded number, and standard volume. Retell's pay-as-you-go plan includes full platform access with no commitment, which suits that shape of deal.

How should work split between partner and vendor?

Write it as a table with one owner per row. Shared rows are where first deals stall.

Workspace setup decides much of what follows. Retell isolates agents, numbers, API keys, members, webhooks and billing per workspace, and roles are assigned per workspace. The operating detail, including billing attribution and support tiers, is in running voice AI for clients.

How should a partner price the services portion?

Price it separately from platform usage. The client should see three things: platform usage, a one-time build, and an ongoing management fee with a defined change allowance.

Usage on Retell is published: $0.07 to $0.31 per minute for voice agents on pay-as-you-go, with Enterprise on custom pricing. Whether usage passes through at cost or carries a markup is a commercial choice. The four models that hold up at renewal are compared in how agencies price AI voice agents.

Two rules for the first deal:

• Confirm any vendor services cost before you quote. If implementation support is in the deal, find out whether it is billed to you or to the client, and whether it is fixed or scoped per project.
• Quote phase two as a separate line. Clients often read a low first quote as the full price of the program.

What should partner and vendor agree before the first quote?

Retell's partner pages state what certified partners get: referrals of potential customers, a listing in the Solution Partner Directory, co-marketing for higher tiers, early access to new features (especially at higher tiers), and dedicated partner support. They do not publish commission rates, minimum deal sizes or professional services pricing. Agree these with your partner contact in writing:

• How partner-sourced deals and vendor-referred leads are tracked, and what happens when both touch the same client.
• Commission, margin or profit-sharing terms, and whether partner tier changes them.
• Whether there is a minimum deal size for Enterprise terms or implementation support.
• How implementation support is priced and what it delivers.
• Who holds the platform contract: the partner, or the client directly.
• The escalation path for a platform issue during a client's go-live.

Start with the partner program

Partners building on Retell can apply through the Solution Partner Program; applicants are assessed on technical skills, industry experience and their potential to add value to the program. Clients who want a partner to run the first deployment can filter the Solution Partner Directory by region, language and integration. Either way, agree the scope above before the first quote, then run one call type on real calls before you expand.

Related reading: Why load tests must follow the real call path, the CRM-to-voice AI workflow, and more guides in the Retell Learn hub.