Pre-sales is the phase before contract signing — when the consulting firm is competing for or scoping the work.
Activities:
- Discovery calls with prospect — understand their needs.
- Scoping — what's in/out, rough effort, timeline.
- Demo — show the proposed solution working.
- Proposal writing — Statement of Work (SOW), pricing, timeline.
- RFP responses — formal answers to enterprise procurement questions.
- Proof of Concept (POC) — working prototype to demonstrate feasibility.
- Capability presentations — to executives evaluating the firm.
Role split:
- Account Executive (AE) owns the commercial relationship.
- Solution Engineer / Pre-Sales Engineer owns the technical demo.
- Consultant / Solution Architect is brought in for scoping, complex Discovery, or POC.
Skills consultants bring to pre-sales:
- Right-sizing the scope — credibly committing to deliverables.
- Identifying risk — flagging dealbreakers early.
- Calibrating estimates — bottom-up cost analysis.
- Demo design — what scenarios to show, what features to feature.
- Reference customer stories — evidence of past success.
Pitfalls:
- Over-promising in pre-sales to win the deal — bites in delivery.
- Under-scoping to look cheap — leads to scope creep + frustration.
- Junior consultant in pre-sales — credibility matters; senior engagement closes deals.
Successful pre-sales requires balance: aggressive enough to win, honest enough to deliver.
Senior consultants hate doing too much pre-sales (it's not billable), but the alternative is a salesperson promising things the team can't deliver — worse outcome.