MOD 02+
How Pre‑Sales Pay Actually Works
Not the numbers — those vary by country, currency and employer far too much to print in a global manual without going stale or misleading someone in a market this hasn't been checked against. The mechanics of how a package is assembled, and the questions that matter more than the headline figure you're quoted.
Why there are no bands on this pageA number that's generous in one country's market is under‑market in another, currencies and cost of living move independently of each other, and a printed figure ages the moment a market reprices. What travels everywhere is the structure: how a package is assembled, what the base/variable split signals about the role, and the handful of questions that expose more than the headline figure ever will. Take the structure below and run it against your own market's own current data — Glassdoor, LinkedIn Salary, levels.fyi, a recruiter's regional salary guide, or your local job board, per the sourcing note at the end of this sheet.
Five components, not one
A pre‑sales offer is assembled from up to five parts, and two offers with identical base salaries can differ by a large fraction of that base once the rest is counted.
| Component | What it is | What to check |
|---|---|---|
| Base | The guaranteed annual salary | Whether the number quoted is base alone or a fuller "package" figure — employers everywhere use both terms and rarely say which they mean |
| Variable / commission | The at‑risk portion, expressed with base as On‑Target Earnings (OTE) | What it is calculated on, whether anyone can show you last year's actual attainment, and whether it is guaranteed during ramp |
| Retirement / pension contribution | Employer contribution to a retirement scheme — superannuation, a 401(k) match, a workplace pension, or the equivalent. The name, the rate and whether it's compulsory all vary by country | Whether it's paid on the variable component as well as the base, and whether a quoted "package" figure already includes it |
| Tool of trade / allowances | Vehicle or car allowance, phone and plan, home internet, laptop, home‑office allowance | Whether a vehicle benefit is a taxable cash allowance or a tax‑advantaged scheme (structures vary by country — a novated lease in Australia, a company car scheme in the UK, a straight allowance in the US) — the after‑tax difference is large either way |
| Equity | RSUs or options | Common at software vendors, essentially absent at MSPs, resellers and integrators. Vesting schedule and whether refreshers are granted annually |
The split, and what it tells you about the role
How the base/variable ratio is set says more about what the organisation expects from you than the job description does — this pattern holds across markets, even where the absolute numbers don't.
| Split (base/variable) | Typically found in | What it implies |
|---|---|---|
| 80 / 20 | Support‑heavy technical roles, hardware, infrastructure, many MSPs | You are valued for coverage and reliability more than for influencing the close |
| 70 / 30 | Enterprise software and SaaS, the most common arrangement | Consultative selling is genuinely part of the job |
| 65 / 35 | Senior Sales Engineers | More upside as deal influence grows |
| 60 / 40 | Where pre‑sales owns the technical evaluation outright | Real ownership, real exposure — check the attainment history carefully |
| 50 / 50 | Account executives, not pre‑sales | If you are offered this in a pre‑sales title, find out why |
The variable itself is usually built from one of: a flat commission on each supported closed‑won deal; tiered commission with accelerators past a threshold; a shared quota with the account executive, often split 50/50 and weighted by contribution; or MBOs — management objectives covering non‑revenue work such as POCs delivered, enablement built, or demo environments maintained. Many MSPs run no formal scheme at all and pay a discretionary annual bonus instead.
The valuation ruleIf nobody in the interview process can explain how the variable is calculated, or nobody will tell you what the team actually achieved against it last year, value it at zero and negotiate the base. A plan that cannot be explained is a plan that has not been paying out.
Two different jobs, two different bands
The titles get used loosely, and someone deciding which direction to aim at deserves the distinction stated plainly. These are not seniority levels of one job so much as two overlapping jobs with different centres of gravity — and the pay follows the difference, in every market this manual has been checked against.
| Pre‑Sales / Sales Engineer | Pre‑Sales Solutions Architect | |
|---|---|---|
| What you're paid for | Running the technical half of a sales cycle well and repeatedly — discovery, demo, POC, technical objections | Judgement on whether something should be done at all, how it fits an existing estate, and whether it can be delivered as sold |
| Scope | A product or a defined stack; assigned accounts | A customer's whole environment, often multi‑year, often several products at once |
| Who you're in front of | Practitioners, team leads, sometimes a department head | CIO, CTO, CFO and their direct reports, regularly |
| Owns commercials? | Rarely — supports the AE's numbers | Frequently owns the scope, and with it the margin (MSP 04) |
| Where it sits in your market's range | Junior through senior individual‑contributor bands | Principal through Field CTO bands — consistently the upper tier of the ladder, wherever you are |
| Variable | Usually a larger share of the package — 70/30 or 80/20 is normal | Often a smaller share, sometimes none, because more of the value is base‑rated judgement |
| What moves you across | Breadth across a stack rather than depth in one product, evidence of executive‑level communication, and a track record of scoping things that were actually deliverable. It's a material step up in every market this has been checked against, and consistently the single largest jump in the ladder | |
On title inflationSome employers call a senior Sales Engineer an "architect" and pay accordingly — at the SE band with an architect's business card. Others give an architect an SE title because that's what the HR framework has. Read the scope in the job description, not the noun: if the role owns the scope document and the margin on it, it is an architect role whatever it is called, and it should be paid in the architect band.
Why published salary data disagrees with itself
Whichever market you're checking, the same three source types exist and they routinely disagree by a wide margin for the same title in the same city — that disagreement is a finding, not a flaw in the data:
| Source type | What it actually measures | Where it skews |
|---|---|---|
| Self‑reported data (Glassdoor, Payscale, levels.fyi) | What people currently in the seat report being paid | Downward — includes everyone who's been in the role for years without a market adjustment |
| Recruiter salary guides (Robert Half, Hays, Michael Page and similar) | What employers are paying to hire right now | Upward — reflects current hiring pressure, and the recruiter has a commercial interest in pitching it high |
| Job‑board data (your local board — SEEK, Indeed, Naukri, LinkedIn Jobs) | Only the postings that state a range at all | Toward the middle — employers advertising a range tend not to advertise the extremes |
The useful read is the shape, not any single number: if the incumbent average and the current hiring band differ sharply, that market is repricing — and the people being underpaid are the ones who stayed put.
The rest of the package
Ask about every line. None of it is unusual to ask, and the ones that are absent tell you something about the employer.
Commonly included
- Phone and plan, or a phone allowance
- Laptop and peripherals; sometimes a home‑office allowance
- Home internet contribution — common in field roles, less so in office‑based ones
- Vehicle allowance or tool‑of‑trade vehicle where the role includes regular client site visits
- Vendor certification costs, exam vouchers, and paid study or exam leave
- Vendor training and at least one conference a year
- A tax‑advantaged vehicle or benefits scheme where your country's tax code offers one
Worth asking about specifically
- Whether the variable is guaranteed during ramp — commonly the first one or two quarters
- Whether the retirement contribution is paid on the variable as well as the base
- Whether commission is paid on renewals and expansions or only on new business
- A certification budget with a stated figure rather than "we support certifications"
- Professional memberships and, if relevant, security clearance sponsorship
- Income protection and life cover
- Purchased or additional annual leave
- Parking, tolls or travel reimbursement if the role is site‑heavy
- Equity, refresher grants and vesting — at vendors; assume none at an MSP
Three questions that change the number more than negotiating the base
"Is that figure base, or base plus everything else?" Ask it in the first conversation. "Base" and "package" cover materially different numbers depending on what's bundled in, and the assumption is rarely corrected until the contract arrives.
"What did the team actually earn against the variable last year?" Not the plan — the outcome. If attainment ran well under target, the OTE you were quoted is a number nobody on that team has actually seen.
"Is the vehicle benefit a taxable cash allowance or a structured scheme?" A straight cash allowance is taxed as ordinary income. The same money run through your country's tax‑advantaged vehicle structure — where one exists — is worth materially more in the hand, at no extra cost to the employer.
How to actually benchmark yourselfCheck your own market directly rather than importing a figure from somewhere else: your local Glassdoor/levels.fyi/LinkedIn Salary data, a recruiter's current regional guide, and your local job board's advertised ranges — triangulated the way the table above describes, not taken individually. Base/variable split conventions and package‑structure norms in this sheet are drawn from published sales‑engineer compensation practice generally rather than any single country's data, and are stated as this manual's judgement, not as a market finding for any specific place. If you're working the Australian market specifically, AU 01 has actual current bands with sources.