Where the Team Actually Sits
Two dotted lines, and the one most people crossing from engineering don't expect.
Pre‑sales in a managed service provider is aligned to sales — but that's only half the reporting picture. The second line runs into a solutions function: the group that productises what the company sells and owns the platforms it sells as its own, typically an infrastructure‑as‑a‑service offering, a managed voice platform, and managed network. That second line is the interesting one. It means part of the job is feeding what you learn in the field back into what the company offers, rather than only selling what already exists.
On the other side of the fence is service delivery and operations. You scope; they build. Which produces the adjustment that catches most people crossing from an engineering or delivery background:
A working MSP pre-sales person is not on the tools much any more. The technical depth is still essential, but it's spent on judgement — is this feasible, is it deliverable, what will it cost to serve — rather than on configuration. If what you love is the building, this role will quietly frustrate you. If what you love is the diagnosis and the shape of the answer, it won't.
| Function | Owns | Your relationship to it |
|---|---|---|
| Sales (AEs, BDMs) | The relationship, the commercials, the close | Primary alignment. You're usually paired with specific AEs by region |
| Solutions | Productised offerings, the platforms, the service catalogue, vendor tooling | Second dotted line. You sell from the catalogue and feed back what the catalogue is missing |
| Service delivery / projects | Implementation of what you scoped | Downstream. They review your scope before it goes out, and inherit whatever you left vague |
Regional pairing, national leverage
Most multi‑site MSPs pair each pre‑sales person with a business unit or region, then pull them across the whole country when a deal needs their particular depth. That's worth knowing when you're evaluating a role: your named patch is where the routine work comes from, but the interesting deals arrive because someone three states away needed a cloud‑transformation brain and yours was free. It's also the main way you build a reputation internally.
Most mid‑size MSPs grew by acquisition, and you can see it in the tooling
Above a certain size, the growth story is almost always the same: buy a regional business, leave it running substantially as it was, then migrate it onto shared platforms over the following years. Do that four or five times across a decade and the result is an operation running more than one PSA and RMM stack concurrently, sometimes split along jurisdictional lines, with a consolidation programme perpetually in progress behind it.
That sounds like an internal IT problem. For pre‑sales it is a daily tax, because scoping, estimating, hand‑over and the durable record of what was promised all run through the PSA. A fragmented tooling estate shows up as estimate history you can't compare, hand‑overs that lose detail at the boundary between business units, and reporting that can't be rolled up nationally. Knowing this exists — and asking about it — is one of the fastest ways to sound like someone who has worked inside an MSP rather than alongside one.
For a multinational, ask the adjacent question too: where is strategy actually set? A local operation with its own profit and loss and its own direction is a materially different job from a branch executing a playbook written elsewhere, because it determines whether the field feedback described above goes anywhere at all.