Before technique, the ground truth: what the job is, where it sits, how far it can take you, and why the humans on the other side of the table decide the way they do. Skip this level and every framework in Level 1 becomes a trick instead of a discipline.
What Pre‑Sales Actually Is
The function whose job is to remove risk and prove value before a signature exists.
Pre‑sales is the technical and business-value partner to a sales cycle. Where an Account Executive owns the relationship, the commercial terms, and the "yes," pre‑sales owns the answer to a harder question: will this actually work, for this customer, and is it worth what they're being asked to pay? Everything in the role — discovery, demos, proofs of concept, RFP responses, ROI models — exists to answer that question credibly, for an audience that doesn't trust a salesperson's word for it.
That makes pre‑sales a translation function. It sits between four groups who each speak a different language about the same deal:
| Function | Owns | Cares most about |
|---|---|---|
| Sales / Account Exec | Relationship, commercials, the close | Will this deal happen, and when |
| Pre‑Sales | Technical fit, solution design, proof of value | Will this work, and can we prove it |
| Customer Success | Post‑sale adoption and renewal | Will the customer actually get value after go‑live |
| Product | What gets built next | Is this a one‑off ask or a real market signal |
| Delivery / Professional Services | Implementation | Can we actually deliver what pre‑sales promised |
The last row is the one juniors underestimate and architects live by: a pre‑sales person who wins the deal by promising something delivery can't build hasn't won anything — they've deferred the loss to renewal. "Winnable and deliverable" is the actual job, not "winnable."
Where it sits
Structurally, pre‑sales almost always reports into the sales organisation (VP Pre‑Sales, under a CRO or Chief Revenue Officer), not into product or engineering — even though the daily work is deeply technical. That reporting line matters: it means pre‑sales is measured on deal outcomes, not on shipping features, and it means the skill that gets you promoted is influence without authority, not technical depth alone.
What it's called elsewhere
The function goes by different names depending on industry and how technical the product is: Sales Engineer (SaaS, infrastructure), Solutions Consultant (enterprise software, CRM), Solutions Architect or Pre‑Sales Architect (complex/platform deals — your target), Value Engineer (when the ROI/business-case work is split out as its own specialism), and Technical Account Manager (a role that overlaps at the edges but is usually post‑sale). Titles are covered in full in Module 02.