Pre-Sales & Business Development

What happens here

Pre-Sales is the phase that runs from the moment a prospect makes contact to the moment a signed agreement converts them into a client. Nothing else in the delivery lifecycle happens without it — Pre-Sales is how the agency funds the work that follows.

The phase consists of four sequential activities — Lead Qualification & Scoping Calls, Proposal Writing, SOW & Contract Drafting, and Pricing & Estimation — plus a fifth cross-cutting reference, NDA / MSA / DPA — the legal stack, that documents the layered contracts running underneath every engagement. The four sequential activities narrow the funnel: qualification filters serious prospects from noise, the scoping call gathers enough information to price, the proposal sells the engagement, and the SOW makes it binding. The legal-stack page describes the five contracts in the stack (NDA, MSA, SOW, DPA, change orders) and when each is signed — the full picture senior engineers see on every engagement but rarely find documented in one place.

The actors are typically a sales lead or account manager (who owns the relationship), a technical lead (who validates feasibility and estimates), and sometimes a solutions architect or delivery manager on larger bids. On small agencies, one person often wears all four hats.

Cross-phase context: Pre-Sales hands off directly to Discovery, where the signed SOW becomes the mandate for detailed requirements work. Repeat clients re-enter Pre-Sales from Maintenance & Retainer when they want to expand scope or start a new engagement.

Best practices

Qualify before you invest. The scoping call is not a discovery session — it is a qualification gate. Before you spend time estimating or writing a proposal, confirm that the lead has budget, authority to sign, a real need, and a reasonable timeline (the classic BANT axes). A lead that fails two or more of those axes is a time sink.

Separate the proposal from the SOW. The proposal is a sales document: persuasive, outcome-oriented, and written for the buyer’s perspective. The SOW is a legal document: precise, scope-bounded, and written to prevent disputes. Merging them produces something that is neither effective at selling nor safe to sign. Draft them in sequence, not as a single file.

Price the unknown with a discovery phase, not a guess. When the scope is ambiguous, the correct answer is a fixed-price discovery engagement that produces a detailed spec, followed by a separately priced delivery. Agencies that skip discovery and quote delivery on ambiguous scope almost always under-price, over-commit, or both.

Tip

Write the desired outcomes section of your proposal before you write anything else. If you cannot articulate what “done” looks like for the client in two sentences, you do not yet understand the engagement well enough to price it.

Caution

Do not start any design, architecture, or development work before the SOW is signed. “We’ll get the paperwork sorted later” is how scope creep starts on day one.

Qualify the relationship, not just the brief. Agency work is delivered by small teams under pressure. A client who treats the pre-sales process as adversarial, who refuses to share their constraints, or who makes unreasonable demands on the proposal timeline is signalling how the engagement will feel at 11 PM on a Thursday before a Friday launch.

Document every commitment made during pre-sales. Verbal agreements on features, timelines, and pricing made during the sales process become client expectations. Record them in the proposal or SOW, or revisit them explicitly before signing. Surprises at kickoff destroy trust.

Desired outcomes

By the end of Pre-Sales, the engagement has the following in place:

• A signed Statement of Work with defined scope, deliverables, timeline, payment terms, and change-control provisions
• A client-countersigned proposal (or a proposal formally superseded by the SOW)
• A pricing commitment that the delivery team has validated as feasible
• A handoff package for Discovery: the signed SOW, meeting notes, any RFP or brief, and a list of named client stakeholders and their roles
• A shared understanding of what is in scope, what is explicitly out of scope, and the process for adding scope post-signature

What the industry does

Fixed-price vs. time-and-materials. The two dominant commercial models each demand a different pre-sales process. Fixed-price agencies invest heavily in scoping and risk-pricing upfront — the proposal includes a detailed work breakdown, a change-control clause, and a contingency buffer. T&M agencies write lighter proposals and shorter SOWs because risk stays with the client; their pre-sales effort goes into relationship-building and rate negotiation rather than estimation.

Discovery-included vs. paid-discovery. Some agencies bundle a lightweight discovery into the proposal as a free consultation in order to win the deal; others charge for discovery as a standalone phase. Paid discovery is the more defensible model: it produces a specification that justifies the delivery price, aligns the client’s expectations, and gives both parties an exit ramp if the engagement no longer makes sense. Agencies that give away discovery consistently find themselves anchored to the initial estimate even when requirements balloon.

RFP-driven vs. relationship-driven pipelines. Enterprise and public-sector clients often procure through formal RFPs with rigid response templates, scoring criteria, and procurement timelines. Boutique and startup clients typically prefer relationship-driven procurement: a referral introduction, a conversation, a short proposal. The pre-sales playbook differs significantly between these pipelines — RFP responses are document production exercises; relationship-driven bids are consultative sales.

Proposal review gates. Mature agencies run a bid/no-bid review before committing proposal effort: a 30-minute conversation between the sales lead and delivery leadership to decide whether the opportunity is worth pursuing. The gate considers win probability, client fit, margin, and strategic value. Agencies that skip bid/no-bid reviews find their senior engineers writing losing proposals instead of delivering client work.