Voice is the one system everybody notices the moment it breaks.
Modernizing it means changing the platform without changing the day for the people using it.
How it works
Most organizations are not shopping for a phone system. They are responding to something: a carrier retiring copper, a contract that renewed itself, a contact center that outgrew what the current platform was built to do. The work starts at that forcing event rather than at a feature comparison.
From there it covers platform evaluation, POTS replacement, contact center design, and provider negotiation, and it stays through porting and cutover. That last part matters more than it sounds. Most voice projects are not lost during selection. They are lost during the switch.
There is no product to sell. Compensation comes from the vendors through the TSD model, so the engagement carries no cost to you and the recommendation follows the requirements rather than a quota.
Start where it applies
Your platform cannot do what the business now needs
Your carrier is retiring copper, or already repriced it
Contact center routing exists only in someone's head
The contract renews itself within two quarters
Platform Evaluation
UCaaS platforms look nearly identical in a feature matrix and behave differently in practice. Evaluation concentrates on the handful of things that actually vary.
What gets compared
- Call handling depth, and admin tooling a non-specialist can actually run
- Native contact center versus a bolt-on
- Teams or Webex integration path, if one is already in place
- Uptime history, and how outages get communicated
Seat rate is the smallest part of the number once usage, E911, toll-free, and hardware are in. Normalizing quotes onto one basis is where two proposals that looked close stop looking close.
POTS Line Replacement
Carriers are retiring copper and repricing what remains, in some cases at several times the previous rate. The first problem is almost never technical. It is that no current inventory exists.
What the work covers
- Full line inventory pulled from billing, matched to what each line actually serves
- Accounts consolidated, including lines still billed after the equipment came out
- A disposition per line: cellular replacement device, SIP, or retire
- Elevator and fire panel lines scoped against code, not bulk-migrated
That last one is where projects go sideways. Code requirements limit which replacement options are acceptable, and a wrong assumption becomes an inspection problem rather than a phone problem.
Contact Center Design
Routing usually lives in one person's memory rather than a document. That is the real constraint on any platform change, and underneath it sits the question that decides most of the budget: a full CCaaS platform, or the features already bundled into the UCaaS license.
What gets designed
- Queue and routing design, written down rather than inherited
- IVR structure, and where callers actually abandon
- Every report the operation runs on today, confirmed to exist in the new platform
- CRM integration and screen pop behavior
That question gets answered before demos start, not during them. Contact center demos are built to make the larger platform feel necessary, and without a written definition of what the operation requires there is no honest way to judge one.
Sourcing, Negotiation, and Cutover
Providers get compared on total cost across the full term, not seat price at signature.
What gets negotiated
- Term length and rate lock
- Seat count flexibility in both directions
- SLA, and the remedies actually attached to it
- Exit and porting language for the next change, not just this one
Exit language gets almost no attention at signing and decides a great deal three years later. Cutover stays in scope, with the porting sequence and rollback conditions set before the switch rather than during it.
How the engagement runs
Understand your environment
Current inventory, contract dates, sites, and what the business actually needs the technology to do.
Define where you want to go
Target state, growth requirements, and success criteria, all agreed before a single vendor is contacted.
Evaluate solutions
The requirement goes to every provider that can meet it, and the responses come back on terms that can be read side by side.
Define a solution and negotiate terms
Pricing, term length, service levels, and exit language are settled before signature rather than discovered on the first invoice.
Oversee activation
We stay in the project through installation, porting, and acceptance, and we escalate on the client's behalf when dates slip.
What you walk away with
A line-by-line inventory with a replacement path and disposition for each
A platform short list scored on feature fit, reliability, and total cost across the term
A cutover and porting plan with rollback conditions defined in advance
Negotiated pricing, term, SLA, and exit language
Questions we get
- Do you handle the porting, or does the provider?
- The provider executes the port. Elk Run builds the port plan, sets the cutover sequence and rollback conditions, and holds the provider to the schedule.
- What happens to our existing phones?
- It depends on the models and whether they can be unlocked and re-provisioned. Hardware is evaluated during platform selection rather than after, because a full device refresh can move the first-year number substantially.
- Can this be handled alongside a network change?
- Usually it should be. Voice quality depends on the connectivity underneath it, and sequencing a circuit change and a platform cutover in the wrong order creates problems that are hard to diagnose afterward.
- How are you paid if the engagement costs us nothing?
- Compensation comes from the provider through the TSD model, which stands for technology services distributor. When a contract is signed, the provider pays a distribution fee that would otherwise go to its own direct sales team. Your pricing comes off the same rate card either way.
- What if the right answer is staying where we are?
- That gets recommended when it is correct. A renegotiated contract with the incumbent, or leaving a working system alone, counts as a finished engagement and gets the same work as a migration.
- When should we start relative to our contract end date?
- Roughly six months out. Auto-renewal notice windows commonly close 60 to 90 days before term end, and starting inside that window removes most of the leverage. Check your specific renewal clause, since the window is the constraint rather than the end date.
The market we compare for you.
The first conversation is a scoping call, not a pitch.
Bring your current contract end date, a recent invoice, and a rough site and seat count. That is enough to say whether there is anything worth pursuing.
The first conversation is a scoping call, not a pitch.
We ask what you have, what is expiring, and what is not working, then tell you whether there is work here worth doing. If Elk Run is not the right fit for the decision in front of you, we will say so.