You have three quotes for the same Genesys Cloud project. One is half the price of the other two.
It is tempting to call that the better deal. But a lower quote may cover less work. If key items are missing, you may pay for them later as change orders, when the project is already underway and the deadline is closer.
That is how a low implementation quote can turn into a more expensive project.
Implementation cost follows complexity more than headcount. A 60 agent contact center can be harder to build than a 500 agent one.
Genesys Cloud licensing is priced per user per month. Implementation is quoted separately. The price depends on integrations, channels, routing, regulation, and how much of the current environment needs to be discovered. Costs that were not clearly scoped can show up later as change orders for integrations, flows, reporting, and training.
Licensing Has a Published Price. Implementation Does Not.
Genesys publishes license pricing by tier and user. Every partner bidding on your project can see it. The bigger difference between proposals is usually the work each partner included.
Implementation is professional services, priced around the scope and effort involved. There is no list price. Often, the difference comes down to what each partner included and how complex the work is.
The Number of Agents Matters. The Work Behind the Project Matters More.
It is common to start with the number of agents. That helps with licensing, but it does not tell you enough about the implementation.
Agent count is a useful starting point for estimating license cost. Implementation depends on what needs to be built, connected, tested, and supported.
A 500 agent contact center with voice, eight queues, and one CRM connection may be a straightforward build. A 60 agent contact center with four digital channels, two CRMs, payment workflows, regulated outbound campaigns, and years of undocumented routing may take more work and cost more to implement.
We have seen smaller contact centers need more implementation work than larger ones. The difference was in the systems, routing, and requirements, not the number of agents.
What complexity is made of
| Driver | Why it can matter more than headcount |
|---|---|
| Integrations | Each connection needs design, build, and testing. Three integrations for 60 agents may take more work than one for 500. |
| Channels | Each added channel can require routing, reporting, and training work. |
| Routing logic | Forty queues with skills, proficiency levels, and overflow rules can take more work than eight simple queues for 400 agents. |
| Regulation | Healthcare, financial services, and collections may have requirements that affect the design as well as the documentation. |
| Undocumented history | Years of accumulated rules may need to be discovered before the team can design the new system. |
| Number of stakeholders | Decisions involving several departments can take longer than decisions with one owner. That time can affect project effort. |
| AI and outbound | Each can be a separate build with ongoing work, regardless of agent count. |
When you compare quotes, look at how the partner scoped the work. A price based mostly on agent count and one short call may not reflect what your environment needs. Any gaps can come back later as change orders.
A small team does not always mean a simple project. Digital channels, several integrations, or outbound campaigns with compliance requirements can add real work. Make sure the quote reflects those needs.
A large contact center does not automatically mean a costly implementation. If the routing is straightforward and there are few integrations, the scope should reflect that.
What Drives a Genesys Cloud Implementation Number
Here are the main areas that can change the scope and price:
- Integrations. Connecting a CRM, ticketing system, or line of business application takes design, build, and testing. A standard Salesforce connection and a custom API are different projects.
- Channels. A voice only setup has a different scope from one that includes voice, chat, messaging, email, and SMS.
- Routing. Ten queues are different from forty. Skills based routing with proficiency levels takes more design than a basic hunt group.
- Self-service. An IVR that looks up customer or account information needs more work than one that only directs callers to a queue.
- Workforce engagement. Workforce management and quality configuration may be scoped separately. Check whether they are included in the quote.
- Migration source. Moving from Avaya or Cisco can require time to find and document routing rules that were never written down. That discovery takes work and should be part of the scope.
- AI. Bots, virtual agents, agentic virtual agents, Agent Copilot, and AI scoring each need their own design and build. Usage may also be metered. More on that below.
- Outbound. Dialing, list management, and compliance configuration can each add work. Ask whether outbound is included, planned for a later phase, or left out.
- Number porting. The number of phone numbers and carriers affects the coordination required.
- Reporting. Rebuilding the reports your leaders rely on takes time. It is easy to overlook when defining scope.
- Training. Admins, supervisors, and agents need different training. Ask what is included for each group.
- Testing and hypercare. User acceptance testing and support after go live take time. If they are missing from the quote, the price may look lower, but your team may have more work to do.
See how VDS scopes a Genesys Cloud implementation.
The Costs the Quote Does Not Include
These are common sources of change orders. Ask about each one before you sign.
| Often excluded | How it can show up later | Ask before signing |
|---|---|---|
| Discovery of undocumented logic | The team finds routing rules no one can explain, and the schedule changes. | How will you document what our current platform does, and is that work included? |
| Integrations beyond a named list | The quote says "CRM integration," but agents use three systems. | List each integration included by name. What rate applies to additional work? |
| Reporting rebuild | Your team goes live and leaders cannot find the reports they rely on. | Which reports are included, and who defines the metrics? |
| Number porting coordination | Carrier issues require extra coordination that may be billed separately. | Is porting project managed in this price, including carrier escalations? |
| User acceptance testing | Your team is left to plan and run testing on its own. | Who writes the test scripts, who runs them, and how much time is included? |
| Training beyond a few hours | The quote includes one admin session, leaving others to train themselves. | How many training hours are included, for which roles, and in what format? |
| Hypercare after go live | Support may move to a ticket queue soon after launch. | How long does hypercare last, who provides it, and will it be the implementation team? |
| Project management | An engineer is asked to manage the project while also doing the build. | Is a dedicated project manager included, and what certification do they hold? |
| Scope changes you request | New requests may become change orders. | What is the change order process, and what rates apply? |
| AI tuning after launch | Performance may drop if no one owns updates and tuning. | Who tunes the virtual agent after go live? Is that included in managed services or billed separately? |
| AI usage beyond the included allowance | Metered usage may appear on an invoice without being part of the original budget. | What AI usage is included, how is it measured, and what happens if we exceed it? |
| Outbound compliance configuration | A late compliance review may delay the campaign. | Who configures consent, do not call scrubbing, calling windows, and abandonment limits? |
| Outbound campaign and list strategy | The dialer is ready, but contact rates are low and no one owns pacing. | Is campaign design and pacing included, or only the configuration? |
| SMS registration and caller ID reputation | Messages may be blocked and calls may be flagged as spam. | Who handles 10DLC registration and caller ID reputation monitoring? |
| Post launch optimization | Follow up work may be quoted as a new project. | What support is available after go live, and what does it cost? |
It is reasonable for a partner to charge for work that falls outside the agreed scope. The problem is discovering that after you have signed.
Why the Lowest Quote Can Cost More
A lower quote is not always a problem. The key is understanding why it is lower. Often, it comes down to one of three things.
- The scope is narrower.The work still needs to happen, but it may be added later as a change order. By then, the project is underway and your old platform contract may be close to ending.
- The team costs less per hour.That may mean offshore subcontractors, part-time contractors, or engineers who are new to Genesys Cloud. The hourly rate is only part of the cost. Rework, extra handoffs, and missed requirements can add time and affect the design.
- The implementation is priced to win the account.That can work out, but ask who will do the work and what support will look like after the project. The senior people you met during sales may not be the ones who stay involved.
The question is not just which quote is lowest. It is what each quote includes and what you will need to pay for later.
Where Change Orders Come From and How to Reduce Them
Most change orders come from four areas:
- Discovery was skipped.If no one documents what the current platform does, the design starts with assumptions. When those assumptions are wrong, the team has to revisit the work.
- Scope was described in broad terms instead of specific work."CRM integration" does not say enough. "Salesforce Service Cloud, screen pop on ANI match, click to dial, and activity logging" gives both sides a clearer picture.
- The business changed during the project.A new department, channel, or acquisition can change the work. That is a valid reason for a scope change, so plan for it where you can.
- Decisions did not have an owner.When a design question sits unanswered, the schedule can slip and the team may need more time.
Three of these four causes can be reduced with good discovery, an itemized scope, and a project manager who keeps decisions moving. A Genesys Cloud assessment is where that discovery starts.
Get a Second Opinion on Your Genesys Cloud
Ninety minutes with a senior VDS Genesys engineer. No cost, no system access, no pitch.
AI Has Build Costs and Ongoing Costs
AI can be handled differently from one proposal to another. A partner may include a use case, plan it for a later phase, or leave it out. Ask what is included and what costs continue after launch.
There are three costs to plan for with each AI use case.
The license and usage. AI capabilities depend on your Genesys Cloud tier, and some usage is metered. Genesys includes a monthly AI allowance per organization, with additional allowance per named agent on the top tier. Usage beyond that allowance is billed. For budgeting, remember that a virtual agent that gets used can generate usage costs. Ask how those costs are measured and what allowance is included.
The build for each use case. An order status virtual agent is one use case. Appointment scheduling is another. Agent assist and automated quality scoring each need their own scope as well. There is also readiness work to consider: organizing the knowledge base, confirming data sources, and reviewing the routing for handoffs. AI depends on the information and processes around it, so gaps in those areas can affect the work and the results.
Ongoing tuning. AI needs regular review after launch. Intents can change, knowledge can become outdated, and customers may ask questions in new ways. If no one is watching performance, containment can drop. A system can work well at launch and lose effectiveness over time if no one owns the tuning. If a quote covers the build but says nothing about ongoing updates, ask what support will be available after go live.
- What AI usage is included and what is metered?
- Who tunes the AI after go live?
- Is that work part of managed services or a separate statement of work?
More on planning AI: AI strategy for Genesys Cloud.
Outbound Takes More Than Dialer Setup
Outbound can look like a configuration task. In practice, campaign design, compliance, and list management can add significant work. Make sure the quote explains what is included.
Dialing modes, pacing, and campaign structure all take planning. The work around the dialer, including compliance and data, can take just as much attention.
Compliance. Outbound has requirements that differ from inbound. These may include consent capture and storage, do not call scrubbing against federal, state, and internal lists, calling window rules, abandonment rate limits, and recording consent in some states. Your legal or compliance team should be involved early to review the requirements. Starting that review close to launch can delay the campaign.
List management and data hygiene. A dialer depends on the quality of the contact list. The team needs to plan the list structure, update schedule, suppression rules, and retry logic. If data comes from several systems, those connections need to be scoped too.
Reachability. Two areas are easy to miss in a quote and can affect whether customers can be reached:
- Caller ID reputation. Carriers may flag outbound numbers as spam. Monitoring and addressing those issues can continue after setup.
- SMS registration. Messaging campaigns may require 10DLC registration with carriers. It can take time and may be rejected, so decide early who will manage it.
Tuning after launch. Contact rates, right party connect rates, and pacing may need adjustments once campaigns are running. The initial configuration is only the starting point.
- Is outbound included or planned for a later phase?
- Who handles compliance configuration and approval?
- Is 10DLC registration included?
- Who reviews pacing after launch?
Who Does the Work Matters
Two projects with similar scope and pricing can go differently depending on the team doing the work. Here are four things to ask about.
US based or offshore. An offshore team may have a lower hourly rate, but consider how time zones affect decisions and handoffs. A question that takes ten minutes to resolve may wait until the next workday. In regulated industries, review the team's data access and handling as part of your evaluation. At VDS, our engineers, architects, and support specialists are based in the US and work your hours.
Full-time employees or contractors. A contractor may join for one project and move on when it ends. A full-time team can carry what it learned into the ongoing support relationship. That can matter months after go live, when someone asks why a queue or flow was built a certain way. Ask who will know the history and how that knowledge will be kept. VDS does not subcontract implementation or managed services delivery.
Current Genesys Cloud certifications. Genesys Cloud changes regularly. Ask which current certifications the people assigned to your project hold. A company wide count does not tell you who will be doing the work. Ask the partner to name the engineers on your project and list their current Genesys Cloud certifications. Every VDS employee is certified on Genesys Cloud. Our team holds Genesys Cloud Professional and Developer certifications, plus specialist certifications in Architect, Scripting, Workforce Management, and Outbound. Our engineers average more than 15 years of experience.
Dedicated project management. Project management is easy to cut from a proposal. It is also important to understand who will coordinate the work. Without a dedicated project manager, those tasks still need to happen. They may fall to an engineer who is also responsible for building the system. Decisions can stall, dependencies can be missed, and the schedule can slip. A project manager tracks the schedule, follows up on decisions, manages risks, and gives you a clear view of project status.
At VDS, our project managers are PMP certified. They coordinate the business and technical teams, keep decisions moving, and raise risks early. Ask whether a dedicated project manager is included in the quote, who will be assigned, and how much of their time is included.
Timeline Affects the Total Cost
When a Genesys Cloud implementation slips, the delay can add costs that are not obvious in the quote:
- Overlapping license costs while you pay for the old and new platforms
- Additional professional services hours
- Time from your internal team, even when it is not invoiced
- Delayed benefits, since each month of delay postpones the improvements you planned
- Lost momentum and added pressure on the project team
Ask each partner how many of their last ten implementations went live on the original date. For the projects that did not, ask what caused the delay and how it was handled.
How to Compare Genesys Cloud Implementation Quotes
Put the quotes side by side. Compare the scope and the people assigned to the project, not just the totals:
| Compare | What to look for |
|---|---|
| Scope based on complexity | The quote reflects your integrations, channels, and routing, not just agent count. |
| Itemized scope | Named integrations, channels, and reports rather than broad categories. |
| Discovery | Discovery is included as defined work, with time allocated. |
| Who does the work | Employment status, location, certifications, and who will be assigned. |
| Project management | A dedicated project manager is named and the hours are shown. |
| Training | Training time is listed by role and format. |
| Testing | The quote explains who writes and runs test scripts and how much time is allocated. |
| Hypercare | The duration, staffing, and team are clear. |
| AI scope | The quote names the use cases, included usage, and who tunes them after launch. |
| Outbound scope | It is clear whether outbound is included or planned for a later phase, and whether compliance work is included. |
| Change order terms | The process and rates are in writing before you sign. |
| Support after go live | The support model, response times, and line between support and project work are clear. |
If one quote is much lower, ask what work is included in the other quotes that is missing from this one.
Questions to Ask Before You Sign
- What did you use to scope this project besides our agent count?
- What is specifically out of scope in this quote?
- Which integrations are included by name, and what rate applies to work beyond that list?
- Who is assigned to my project, and what current Genesys Cloud certifications do they hold?
- Are the people on the project full-time employees based in the US?
- Is a dedicated project manager included, and what certification do they hold?
- How will you document our current platform before designing the new one?
- How many of your last ten implementations went live on the original date?
- Which AI use cases are included, what usage is metered, and who will tune them after go live?
- Is outbound included or planned for a later phase? Who handles compliance configuration?
- What is the change order process, and what rates apply?
- What support will we have after go live, and who do we contact?
- Can I speak with a customer whose implementation you completed more than a year ago?
That last conversation can help you understand what support looked like after the project was complete. If it was not good, read Your Genesys Partner Disappeared After Go Live.
Frequently Asked Questions
How much does a Genesys Cloud implementation cost?
There is no list price for implementation. Partners quote based on the work involved, including integrations, channels, routing, self-service, AI, outbound, reporting, training, and migration from a legacy platform. Quotes can differ because the partners scoped different work.
Does a bigger contact center mean a more expensive Genesys Cloud implementation?
Not necessarily. Agent count affects licensing, but implementation depends on complexity: integrations, channels, routing, regulatory requirements, and how much of the current environment needs to be discovered. A 60 agent contact center with four channels and two CRMs may take more work than a 500 agent voice only operation.
Is Genesys Cloud implementation included in the license cost?
No. Genesys Cloud licensing is priced per user, per month. Professional services for implementation are quoted separately by your partner.
Why are Genesys Cloud implementation quotes so different?
The scope may be different. A lower quote might leave out discovery, reporting, testing, training, or hypercare. Ask what is included and what would be billed separately.
What causes change orders in a Genesys Cloud implementation?
Common causes include skipped discovery, broad scope descriptions, changes in the business, or decisions without a clear owner. Good discovery, clear scope, and active project management can reduce avoidable changes.
Do I need a project manager for a Genesys Cloud implementation?
A project manager keeps decisions, dependencies, risks, and timing organized. Without one, that work may fall to an engineer who also needs to build the system. That can slow the project and add cost.
Does it matter if the implementation team is offshore?
It can. A lower hourly rate may come with time zone gaps and more handoffs. In regulated industries, you should also review how the team will access and handle data.
Is AI included in Genesys Cloud implementation cost?
AI may involve license usage, a separate build for each use case, and ongoing tuning. Ask what is included in the license, what the partner will build, and who will maintain it after launch.
Why does outbound add cost to a Genesys Cloud implementation?
The dialer is only one part of outbound. Consent, do not call lists, calling windows, abandonment limits, contact list management, caller ID reputation, and SMS registration may all need planning and ownership.
What should be included in a Genesys Cloud implementation quote?
Look for discovery, named integrations, routing and flow work, reporting, testing, training by role, go live support, hypercare, and project management. If AI or outbound are part of your plans, ask for those items to be scoped too.
Know What Is in the Quote Before You Sign
VDS is a Genesys Cloud Elite Partner in Grand Rapids, Michigan, and a back-to-back Genesys Mid-Market Partner of the Year. Our engineers, architects, and support specialists are US based, full-time, and certified, and we do not subcontract delivery. We spell out the scope, name the people assigned to your project, and explain what is outside the quote before you sign.
Nick Glimsdahl is a Senior Account Executive at VDS, a Genesys Elite Partner focused on Genesys Cloud.
Genesys Cloud is our focus, from implementation to managed services after go live.