Presales & Solutioning
Presales solution engineering is the technical half of a sale: designing, demonstrating and pricing an answer to a customer's business problem before anyone has bought anything. It is engineering under commercial constraint, and the deliverable is being believed by the buyer and by your own delivery team.
Assumes you know: Enough engineering depth to design a system and be cross-examined on it, Willingness to speak, unrehearsed, in front of people who can say no
Overview
What this area actually covers
Presales — variously called solution engineering, sales engineering or presales consulting — is the technical work done before a contract exists. A prospective customer has a problem and, usually, a budget. Your job is to establish what the problem really is, decide what your product or your firm would build to solve it, prove the parts genuinely in doubt, write down what it costs and what it depends on, and defend all of that in front of the people who will pay for it and the people who will operate it afterwards.
The work divides into four modes that reward different skills, and interviews probe each separately. Discovery is investigative: you are diagnosing, and also deciding whether this is a real opportunity. Demonstration is performative and unforgiving — live software, live questions, no retakes. The proposal is written engineering, read by strangers including procurement and legal. A proof of concept is an experiment designed to remove one named reason not to buy.
| Mode | What it is for | The characteristic failure |
|---|---|---|
| Discovery | Find the funded problem and the decision process | Leaving with a feature list and no idea who signs |
| Demo | Make the answer credible in twenty minutes | Showing everything the product does |
| Proposal | Make it defensible without you in the room | Prose that quietly became a contractual promise |
| POC | Retire the doubts that block the deal | Free delivery work with no definition of done |
Treat it as a genuine engineering discipline, because the design decisions are real and the constraints are hard: an existing identity provider, data residency rules, the operating team's actual skills, a fixed-price contract model. Adjacent things get wrongly bundled in. Marketing and technical evangelism are one-to-many with no named deal attached. Post-sale solution architecture inherits your promise and is accountable for delivering it. And sales itself owns the number, the negotiation and the relationship, none of which are yours.
Now practise it
21 interview questions in Presales & Solutioning, each with the rubric the interviewer is scoring against.
- Your only contact is an architect who loves the product and cannot get you in front of anyone with a budget. What do you do next, and when do you stop?
- In the room, the customer tells you a competitor has committed to something you cannot match. How do you respond?
- The compliance matrix wants a yes or a no against a requirement you only partly meet, and there is nowhere to explain. What do you put in the box?
- Mid-demo, the prospect asks whether the product does something it does not. What do you say?