Perspectives/Case Study
Case Study · Telecom Services

The business they couldn't see clearly.

April 2026·4 min read·Telecom Services Consulting
$8M–$15M
Revenue-range firm
Established telecom services player
3–6 months
Engagement duration
All 5 pillars in parallel
5 pillars
Business areas transformed
Valuation, reporting, ops, BD, CRM

A telecom services consulting firm doing $8M–$15M in revenue had spent years building real technical capability — drive testing, network rollouts, RF design, optimization work for carriers and infrastructure clients. The expertise was genuine. The business around it wasn't keeping pace. No credible valuation. Reporting that didn't reflect what the firm was worth. Business development running on relationships and instinct rather than a system. Customer data scattered, not managed.

The technical work was winning projects. The business infrastructure wasn't capturing the value.

The situation

Telecom services firms operate in a demanding market. Carrier clients are sophisticated and demanding. Network rollout timelines are tight. RF optimization work requires specialized skill sets that take years to build. This firm had built all of that — a team that could do the work, a client base that trusted them, and a track record of delivered projects.

But the business itself — the entity behind the technical work — was undermanaged. The gap between the quality of the technical delivery and the quality of the business operations was significant. And in a market where contracts are large and clients evaluate vendors carefully, that gap starts to matter.

What was missing

Five things, each compounding the others:

Valuation.The owners had no clear view of what the business was worth. Without a credible valuation — grounded in normalized earnings, comparable transactions, and the firm's specific risk profile — major decisions about capital, partners, and eventual exit had no foundation.

Reporting. Financial reporting existed for tax purposes, not for management. There was no monthly view of which clients, projects, or service lines were generating margin — and which were consuming it. The business was operating without a dashboard.

Operations.Project delivery was strong. But the operational infrastructure supporting it — utilization tracking, capacity planning, project profitability visibility — wasn't there. Growth was creating complexity that informal processes couldn't absorb.

Business development. New work came in through existing relationships and word of mouth. There was no structured BD process — no pipeline tracking, no systematic outreach, no way to understand which efforts were producing revenue and which were not.

Customer relationship management.Client relationships were managed by the people who held them. Contacts, history, commitments, and opportunities lived in email threads and people's heads. That's fine when the firm is small. It becomes a liability as the business grows and people move.

What we did

Valuation
What the business is actually worth

Built a defensible valuation grounded in normalized EBITDA, market comparable transactions in the telecom services sector, and the firm's specific risk factors — client concentration, contract visibility, key-person exposure. For the first time, the owners had a number they could use.

Reporting
Monthly financial visibility

Rebuilt the reporting infrastructure to produce monthly P&L by service line and client. Margin visibility by project type. A management dashboard that distinguished between billable utilization and overhead. The owners could now see the business, not just the bank balance.

Operations
Infrastructure for scale

Designed the operational framework to support growth without proportional headcount increases — utilization tracking, capacity planning, project costing, and a reporting cadence that kept the management team aligned on what was happening and what was coming.

Business Development
From informal to structured

Designed and implemented a BD process: pipeline tracking, outreach cadence, proposal discipline, and win/loss visibility. Business development became a managed function with metrics — not a set of relationships that either produced or didn't.

CRM
Client relationships in a system

Stood up a CRM covering the full client base — contacts, project history, contract terms, renewal dates, and open opportunities. Relationship knowledge that had lived in inboxes and heads now lived in a system. That changes what's possible when the team grows or changes.

What changed

The firm now knows what it's worth — and why. The number is grounded in the actual performance of the business, not in a guess or a multiple applied to revenue without context. That matters when owners are making decisions about capital, partners, or the next chapter.

The reporting tells the truth about the business on a monthly basis. Service line margins are visible. Project profitability is tracked. The management team is looking at the same dashboard and making decisions from the same data.

Business development is now a process. The pipeline is visible. Outreach is systematic. The gap between the quality of the technical work and the quality of the business that surrounds it is closing.

The bigger point

Technical services firms — in telecom, in engineering, in any specialized discipline — tend to underinvest in the business of the business. The expertise is real and it takes years to build. The business infrastructure around it often lags by a decade.

That gap shows up slowly at first: in deals that don't close because financials aren't credible, in growth that creates chaos rather than returns, in client relationships that walk out the door when a key person leaves, in business development that depends entirely on who the founders happen to know.

The technical work is the product. The business infrastructure is what makes it possible to sell that product reliably, grow it intentionally, and eventually realize its value. Building one without the other is a bet against time.

Running a telecom services business — or thinking about acquiring one?

The technical capability is usually there. The business infrastructure usually isn't. Let's talk about what it takes to close that gap.

Book a 30-Minute Call