elevate techConsulting Group

Wireless Infrastructure Services Company ยท Project-Based Services

The revenue lived in milestones. The systems did not know what one was.

A fast-growing wireless infrastructure company deployed small cells and fiber for carriers and building owners across the country. Its work arrived as master agreements that spawned statements of work, which spawned projects, built by up to a thousand subcontractors paid on milestones and billed to carriers on milestones. It ran all of that on a small-business accounting package and spreadsheets. David Day, as lead consultant, decided what the company would run on, picked who would build it, and stayed through go-live.

6 weeksfrom RFI issue to vendor demos, over the holidays
8 vendorsbid on three platforms; one partner selected
$43,500cut from the Phase 1 statement of work with scope unchanged
70%of a subsidiary's revenue ran through one carrier's system

What David walked into

The insight

When revenue is earned on milestones, project delivery and billing cannot live in separate systems, and the choice of platform matters less than the choice of who builds it. So David ran the selection as one decision, not two: three platforms, eight implementation partners, one request for information, judged on telecom references and certified staff rather than brand size.

The roadmap david built

Selection

Written requirements and one RFI to eight vendors across three platforms. Five written responses, three demos, one recommendation.

One platform

Accounts, contracts, projects, milestone billing and the general ledger on one platform, so a project stage and an invoice were the same record.

Identity

Company email, a website, cloud productivity and phones, run in parallel so the business had an identity of its own.

The telecom layer

Planned after go-live: network inventory, recurring billing for leased infrastructure, and site-system integration.

Selection, build and identity ran as parallel streams under one program.

Three decisions that mattered

Each one saved money or ended double work, and none of them was the default.

  1. He chose references over the biggest name

    A global accounting firm bid, replied within minutes, and never booked a demo. Another bidder proposed offshore junior developers. The recommendation went to a mid-size regional partner with three named telecom clients, every team member certified, and a rate card the business could afford.

  2. He trimmed the statement of work before signature

    Between the first draft and the signed version, the Phase 1 estimate dropped from 1,775 hours to 1,540, and from $328,500 to $285,000, with scope unchanged. The client took on standardizing its own project templates; the partner took on less.

  3. He recommended abandoning the custom build

    A custom project tool was working, but project managers still re-keyed every task into the carrier's own system, because that carrier was over 70% of the subsidiary's revenue. Finishing the custom tool was priced at $87,500. Licensing the carrier's system and connecting it was about $28,000 in year one and ended the double entry. David recommended the buy.

What was delivered

The engagement ran from kickoff in November 2016 through go-live; the planned telecom layer was not part of the delivered scope. Lead consultant: David Day, prior to founding Elevate Tech. Client, vendor and partner names withheld by policy.

What this means for your company

Related service: Independent ERP and system selection.

Not sure where to start?

Take a free three-minute score. If a conversation makes sense, it will offer one.