Web Design Agency Project Pitch — 60-Min Training

The two roads out of a first call: quote now, or sell discovery

Every web design agency pitch forks at the same moment. A prospect says some version of "we need a redesign — roughly what does that cost?" and the rep has about four seconds to pick a road. Road one is the quote-on-the-call motion: give a range, follow with a capabilities deck, hope the range survives contact with reality. Road two is the discovery-first motion: refuse the number, sell a paid discovery engagement, and let discovery produce both the scope document and the build price. The entire training exists to make road two feel natural under pressure, because road one feels natural by default — it is friendly, it is fast, and it is how most agency principals were trained by their own first bad year.

The quote-now road has real advantages worth naming honestly in the room, because a training that pretends the alternative is worthless gets ignored the moment a rep hits a prospect who genuinely just wants a number. Quoting fast shortens the cycle. It filters out prospects with no budget in one call instead of three. For truly templated work — a marketing site on a known platform, five to twelve pages, no integrations, no content strategy — a fast number is often correct, and forcing a paid discovery onto a $12K brochure site is theater that costs you the job. The failure mode is not speed; it is speed applied to complexity. The moment a project involves stakeholder politics, a CMS migration, content that does not exist yet, or an integration list nobody has written down, the number given on the call is fiction, and every hour of the build spends the difference.

The discovery-first road trades cycle time for accuracy and for negotiating position. It reframes the agency from vendor to diagnostician. It generates revenue before the build contract exists, which matters enormously for cash flow at agencies running eight to thirty people. And it produces a written artifact — the scope document — that becomes the reference for every scope argument for the next six months. The cost is real: longer sales cycles, more prospects who walk when they hear "the first thing we sell you is a $12,000 research phase," and a sales team that has to be genuinely good at explaining why research is not overhead.

There is a third road most trainings skip, and it deserves ten seconds: refer out. Not every inbound lead belongs to you. An agency that positions on complex mid-market builds and takes a $9K brochure site because the pipeline looks thin has just bought itself a low-margin project that consumes a senior designer. Teaching reps to disqualify — warmly, with a referral to a smaller shop or a template partner — is part of the same discipline as refusing to quote. Both are the same muscle: the willingness to not have this deal.

Adjacent shops run identical forks. A marketing agency choosing between a project fee and a monthly retainer, an SEO shop deciding whether to audit before proposing, a brand studio pricing a positioning sprint before a visual identity build — same structure, different nouns. When you train this, say that out loud. Reps retain the pattern better when they see it is not a web-specific trick but the standard shape of selling expertise where the work cannot be specified before it is investigated.

The audit-first meeting, verbatim

Give the room the actual script, then make them run it on a live prospect from their own pipeline before anyone leaves. Reading a script is not learning a script.

The first call is sixty minutes and covers six things in order. First, the business decision behind the redesign — why is the website on the leadership agenda this year? A repositioning, a funding event, a new product line, acquisition costs that stopped working? Second, the named stakeholders: who owns the site internally, who can kill the project, and who has design opinions the team will have to manage. Third, the current site's measurable failures — ask for three numbers they are trying to move, whether that is conversion rate, time-to-publish, page speed, or inbound support tickets caused by the site. Fourth, the technical reality: current CMS, hosting, the integration list, and who maintains it today. Fifth, budget and timeline reality — all-in budget including content and third-party integrations, plus the hard launch date and the reason behind it. Sixth, the process statement: "We do not quote the build on a first call. We propose a fixed-fee discovery within three business days. Discovery produces the build scope and the build quote. Are you good with that?"

The stakeholder question is the one reps skip and the one that predicts the project. A build with one decision-maker runs on schedule. A build with a marketing owner, an IT gatekeeper, and a founder with strong opinions about typography runs 40% over on revision cycles unless the scope document names all three and defines who signs off on what. Ask it early, write the names down, and put those names in the discovery proposal.

When the prospect pushes for a number anyway — and roughly half will — the scripted answer is short: "I respect the question. A real number requires real discovery. Discovery is fixed-fee, and I can have the proposal in your inbox by Friday." Do not soften it with a range. A range is a price. "Most projects like this land around fifty to eighty" is not a helpful gesture; it is an anchor the prospect will hold against you in month four when the number is $118K because the content migration turned out to involve nine thousand legacy URLs.

Drill the phrases that should never appear in a first call. Committing to a platform before the audit — "we can definitely build that in Webflow" — is solving before diagnosing, and it forecloses the finding that their real problem is a publishing workflow, not a template. "We've done a hundred sites like this" turns you into a commodity; specificity about their situation outperforms volume claims. "We can have mockups next week" is the single most reliable scope-creep accelerant in agency work, because mockups produced before scope become the scope in the client's mind, permanently. And any talk of page counts, sprint counts, or launch dates belongs in the discovery deliverable, not the diagnostic call.

Give the room one more move: the summary email. Within two hours of the call, the rep sends a five-bullet playback — the business decision, the named stakeholders, the three numbers, the technical reality, and the discovery proposal date. It costs ten minutes and it does two things. It proves you listened, which is most of what differentiates you from the other three agencies they called. And it puts your framing of the project in writing before anyone else's.

Choosing the road: a decision path reps can run in real time

The decision is not philosophical. It is a short sequence of observable facts about the prospect, and a rep can run it during the call.

Walk the diagram once, then stress it. The interesting branch is the one where the client declines discovery. Reps read that as a loss; train them to read it as information. A prospect who will not fund three weeks of research on a six-figure project is telling you either that the budget is not real, or that they have already picked a vendor and you are the price check, or that they intend to direct the project themselves and want hands, not judgment. All three are things you want to know in week one rather than month three. The clean exit is a win with a smaller number attached.

The second interesting branch is the refer-out. Build the referral relationship before you need it. Two or three smaller shops or freelancers who do good template work, who know you send real leads, and who send back the complex ones they cannot staff. That reciprocal flow is one of the cheapest pipeline sources an agency has, and it costs nothing but the discipline to say "this isn't our shape, but I know exactly who it is."

One nuance for the room: the decision path changes by lead source. A referral from a past client arrives pre-sold on your process and rarely fights the discovery fee. A cold inbound from a directory listing arrives comparing four agencies on price and fights everything. An RFP arrives with the scope already written by someone who is not you — read it, then propose discovery anyway, because the RFP describes what they think they want rather than what the build requires. If they refuse to move, decline the RFP. Blind RFP responses are among the lowest-converting activities in agency business development, and they consume senior time that produces nothing reusable.

The numbers behind each option

Put real ranges on the whiteboard, framed as ranges the agency will defend rather than industry claims. Reps need arithmetic they can do in front of a client without looking anything up.

Discovery pricing scales with build size, and the usable heuristic is roughly 10 to 20 percent of the anticipated build. For a build expected to land between $50K and $150K, a discovery of $8K to $15K covering three to four weeks is defensible: stakeholder interviews, analytics review, content inventory, technical audit, sitemap, and a phased build estimate. For builds in the $150K to $500K range, discovery grows to five or eight weeks and prices accordingly, because the content inventory alone may run into thousands of URLs and the integration audit involves other people's engineering teams. Below $25K, the discovery compresses into a paid strategy session — a day or two, priced in the low thousands — because a three-week research phase on a $20K project is a larger percentage than any client will accept.

The build itself gets quoted per phase, not as a range. Two phases is the usual shape: design and prototype as one fixed fee, build plus content migration plus launch as another, with the total stated plainly. Ranges signal negotiability and invite the client to treat the bottom of the range as the price. A phase number invites a conversation about what is in the phase, which is the conversation you want.

Billing structure is where margin actually lives. A defensible schedule on a $90K project: 40% at signature invoiced day one, so $36K arrives before design starts; 30% at design sign-off, so $27K lands as you exit the most senior-labor-heavy phase; 20% at beta launch, $18K, which funds QA and migration; and the final 10%, $9K, at go-live plus thirty days. That thirty-day tail is not a courtesy — it is what stops the final invoice from becoming a hostage in the two weeks after launch when the client is busiest and least motivated to pay. Terms of net 15 rather than net 30 on a project business is normal and worth holding.

Compare that to the 50/50 net-30 structure most agencies drift into. Half up front, half at launch, thirty days to pay, means the agency finances the middle of the project out of its own working capital, and the entire back half of the fee is exposed to a launch dispute. The gap between disciplined milestone billing and 50/50 is not primarily a revenue difference — it is a collections and cash-cycle difference, and on a shop doing $2M a year it is the difference between funding growth from operations and living on a line of credit.

Change orders need a floor. Set a minimum — $2,500 is a common and workable number — and state it in the proposal meeting rather than discovering it during month two. The minimum exists to kill the four-hundred-dollar nuisance request. Those requests do not lose money on their face; they lose money because each one costs a context switch for a designer, a Slack thread, a scope conversation, and a small erosion of the principle that scope is written. Ten of them across a project quietly consume a week of senior time nobody billed.

Post-launch support is a separate retainer with its own number, and the rep should say out loud in the proposal meeting that they are not selling it today. Bundling maintenance into a build fee is how agencies end up doing unbounded free work for eighteen months on a project that closed at a decent margin. Quote it, park it, revisit at go-live plus thirty when the client has felt the need.

For adjacent revenue lines, the arithmetic rhymes. A marketing agency retainer converts the same discovery muscle into a scoped monthly engagement with a defined deliverable count. An SEO shop sells a technical audit that plays the exact role discovery plays here: a paid diagnostic that produces the scope of the work that follows. A brand studio sells positioning before identity. If your agency runs more than one of these lines, standardize the paid-diagnostic price ladder across all of them so reps are not inventing a structure per service.

Sequencing the build, and the discipline that protects the margin

Structure is easy to agree with in a training room and hard to hold at 4pm on a Thursday when a client asks for "one small thing." Make the sequence visible.

The rule underneath the diagram is three words: no signed change order, no work. Reps and project managers both break this one, usually out of goodwill. The problem is precedent. The first unbilled favor teaches the client that scope is a suggestion, and every subsequent request arrives with the assumption that it is also free. Holding the line in week two is cheap; holding it in week nine, after eleven favors, requires a difficult conversation that damages a relationship you were trying to protect by being flexible in the first place.

Sequence the change-order conversation so it is never adversarial. The move is to say yes to the request and no to the timing: "Absolutely, that's a good idea. It's outside the scope doc, so let me price it and send it over — probably a day. Do you want it in this phase or after launch?" You have agreed with them, priced the work, and handed them the choice. Nobody has been told no.

The proposal meeting itself has a shape worth rehearsing. Open with a playback of discovery findings — the three measurable failures, the business decision, the stakeholder map — and ask whether it is right. Let the client correct you and update the document live; that single move does more for trust than any slide. Then present the phased proposal in a handful of pages, not forty. Then state the change-order minimum and the billing schedule in the same breath as the price, so they arrive as part of how you work rather than as fine print discovered later. Then name the support retainer as separate and explicitly not part of today. Then stop talking and ask what questions you can answer. The silence after the number is the hardest thirty seconds in agency sales, and it is the one thing worth drilling in pairs before anyone leaves the room.

Rehearse the four objections that show up in nearly every deal. "Can you just give me a ballpark?" — discovery produces the ballpark and the scope together; without it the ballpark is fiction. "Your competitor quoted forty." — ask whether they ran a paid discovery, and if not, the difference will arrive later as change orders. "Can we skip discovery, we know what we want?" — what you want and what the build requires are two different documents, and discovery is what protects the build budget. "Can we do time and materials instead?" — yes for discovery and for post-launch optimization, no for a defined build, because T&M on defined work destroys client trust and agency margin simultaneously.

Close the sixty minutes with three written commitments per rep, taped somewhere they will see them. One: the discovery script runs on the next three prospect calls without exception. Two: no build number on a first call this quarter, with a small social penalty attached if it happens — the penalty matters less than the fact that the team is now watching. Three: every build contract ships with the change-order minimum, the milestone schedule, and the support retainer as a separate line item, all pre-approved so no rep is negotiating contract language alone on a Friday afternoon.

Then make the training recur. A single sixty-minute session decays inside a month. The version that sticks is a standing weekly working session where one rep walks a live deal through the decision path in front of the room and the group pressure-tests the scope document. That is also how the script improves — the objections that actually show up in your market are not the ones in any playbook, including this one.

Related questions

How long should paid discovery run before the build quote?

Three to four weeks for a mid-size build; five to eight for large or migration-heavy projects. Shorter than three weeks and you are guessing about content volume and integrations, which are the two variables that blow up build estimates most often.

Should the discovery deliverable belong to the client if they walk?

Yes. It was paid work. Hand over the scope document, sitemap, and stakeholder map. Retaining it as hostage sours referrals and rarely wins the build back. A clean, generous exit converts to future work more often than agencies expect.

Does this motion work for retainer-based agency services?

Directly. Marketing, SEO, and PR retainers use the same shape: sell a paid diagnostic, let it define the engagement, then price the ongoing work against a written scope. Only the deliverable names change.

What if the prospect insists on responding to their existing RFP?

Read it, then propose discovery alongside your response. If they refuse any diagnostic, decline. RFPs written without you convert poorly and consume senior time that produces nothing reusable for the next deal.

How do you keep a 60-minute training from decaying?

Convert it into a recurring weekly working session where reps walk live deals through the decision path. One-time trainings fade within a month; a standing session compounds because the objections discussed are the real ones from your market.

FAQ

What if the prospect refuses paid discovery and demands a free proposal?

Treat it as a qualification signal rather than an insult. Prospects who will not fund a diagnostic on a six-figure project generally either lack a real budget, have already selected a vendor, or intend to direct the work themselves. Decline politely, send a one-page relevant case study, and keep the door open. Some of them come back in a quarter having been burned by the agency that did quote on the call.

Is fixed-fee always better than time and materials?

No. Fixed-fee works when discovery has defined the scope; it is dishonest when scope is unknown, because the agency either pads heavily or change-orders the client to death. T&M is the correct structure for genuinely open-ended work: research engagements, prototype sprints, and ongoing optimization after launch. The failure is mismatching the structure to the certainty of the scope.

How should small projects under $25K be handled?

Compress the motion rather than abandoning it. Discovery becomes a paid strategy session of a day or two, the build stays fixed-fee, and billing collapses to a simpler two-payment split. The principles — no first-call quote, written scope, a change-order floor — still hold. Only the price tags and the calendar shrink.

Should we discount if the client signs discovery and the build together?

No. Discounting teaches prospects that your prices are opening positions, and the discount they receive on this project becomes the baseline expectation on the next one. Price discovery and the build independently, at full rate. If you want to reward commitment, offer scheduling priority or an extra strategy session rather than money off.

How do we handle a client who ghosts between beta launch and go-live?

The milestone schedule already handles most of it, because only the final ten percent is exposed. Add a written clause defining what happens if client-side review stalls past a set number of business days — typically the phase is deemed accepted and the milestone invoices. Say it in the proposal meeting so it never feels like a trap later.

Who from the agency should attend the first call?

One business development lead and one senior practitioner — a design or technical director. Two people is enough to run a real diagnostic without turning the call into a panel. Sending a rep alone produces surface answers on the technical reality question; sending four people signals that your overhead is about to be in the price.

Sources

1. A Book Apart — *Design Is a Job* by Mike Monteiro: https://abookapart.com/products/design-is-a-job
2. A Book Apart — *Just Enough Research* by Erika Hall: https://abookapart.com/products/just-enough-research
3. Stuff & Nonsense — Andy Clarke's "Contract Killer" template: https://stuffandnonsense.co.uk/projects/contract-killer/
4. A List Apart — design, contracts, and business articles archive: https://alistapart.com/blog/topic/business/
5. Smashing Magazine — client and business practice articles: https://www.smashingmagazine.com/category/business/
6. Interaction Design Foundation — UX design process and design sprint curriculum: https://www.interaction-design.org/literature/topics/design-thinking
7. Bureau of Digital — Owner Camp and agency leadership peer groups: https://bureauofdigital.com/
8. Mule Design Studio: https://muledesign.com/
9. Nielsen Norman Group — UX research and design process guidance: https://www.nngroup.com/articles/

Related on PULSE

• [Marketing Agency Retainer Pitch — 60-Min Training](/knowledge/st369)
• [SEO Agency Retainer Selling — 60-Min Training](/knowledge/st371)
• [PR and Communications Agency Retainer Selling — 60-Min Training](/knowledge/st372)
• [60-Min Sales Training: Slide Deck Design for Sales](/knowledge/st0451)
• [Commercial Electrical Project Selling — 60-Min Training](/knowledge/st328)
• [Luxury Travel Agency Concierge Booking Selling — 60-Min Training](/knowledge/st375)