Responding to new agency RFPs inside 4 hours (without burning a day on it)

The economics of agency new business are unforgiving. A typical inbound RFP goes to four to eight agencies. The shortlist is usually two or three. The buyer's first cut happens in the first 24-48 hours, and the criteria are almost never about creative quality at that stage — they're about whether you proved you read the brief, whether you asked the right questions, and whether you replied promptly enough to feel like a serious shop.

This article is the playbook for the first response — the one that gets you into the shortlist conversation, without burning a partner-day on a speculative pitch.

What the first reply is for

The first reply is not the pitch. It is not the SOW. It is not the case studies deck. The first reply has three jobs:

1. Prove you read the brief. One specific reference to something they actually asked for, not a templated "we love this kind of work."
2. Ask 3-4 qualifying questions that you genuinely need answered before you could build a credible proposal.
3. Propose a 30-minute discovery call as the next step.

A first reply that does all three lands inside 4 hours, with under 250 words. Anything longer is overinvestment in a deal you have not yet been shortlisted for.

The first-reply template

Hi [name],

Thanks for the brief on [their specific project — pull a phrase from the RFP, e.g., "the rebrand + marketing site for the Series B raise"]. The piece I'd want to dig into first is [one specific question their brief raises — a target audience ambiguity, a timeline question, a scope edge].

A few questions before I can put a credible response together:

1. Decision-makers and process. Who on your side is signing off, and what does your shortlist process look like — written proposals only, or are you doing chemistry calls?
2. Budget range. Is there a working range you'd share, even if it's "we're not sure yet"? Saves us both from a mismatch we'd have caught in week 3.
3. Timeline driver. Is there a hard date driving the [launch / event / fiscal-year cut]? Helps me scope feasibility honestly.
4. Incumbent or last vendor. Who did this work before, and what worked / didn't?

If it's easier, we can cover all of these in a 30-minute call. Three times that work on my end this week: [Tuesday 2pm], [Wednesday 10am], [Thursday 4pm] (Pacific). Or send a few that work for you.

One small thing: I won't quote a number, scope, or timeline in writing before we talk — that's not me being cagey, it's because any number I put in writing now would be wrong, and bad numbers anchor harder than good ones.

Talk soon, [Your name]

The structure is doing a lot of work in 200 words. Three things to notice:

The specific-reference line. This is the single most important sentence in the reply. It's the proof that you read the brief, not a templated "thanks for the inquiry." Pick one thing from the RFP — a concrete asset, a target audience, a tension — and reference it precisely.

The four qualifying questions. Decision process, budget, timeline driver, incumbent. These are the four things you actually need to know before you can scope. Asking them up-front does two things: it filters out the prospects who weren't serious (they won't bother answering), and it educates the serious prospects that you're not the agency that pretends $20k and $200k are the same job.

The no-numbers-in-writing line. Specifically calls out that you won't quote yet, and explains why. This works because it's professional, not evasive. Buyers who have done RFPs before know that early numbers are usually wrong and that quoting blind protects nobody.

When to skip the call and just write the response

Sometimes the RFP is detailed enough that you don't need a discovery call before responding. Three signals it's safe to write the response without a call:

1. Budget range is stated explicitly in the RFP (e.g., "$30-60k for the website + content").
2. Timeline is firm with a clear driver ("must launch before our Series B announcement on October 14").
3. Scope is well-defined with deliverables enumerated, not just goals.

If all three are present, you can write a tight response without the qualifying call. Still keep the first reply — but make it shorter, acknowledging the RFP and confirming you'll respond by a specific date.

Hi [name],

Thanks for the brief on [project]. We've got what we need to put together a credible response — I'll have a 4-5 page write-up to you by [Friday EOD Pacific].

One quick clarifier: [a single specific question that genuinely matters — usually about decision process or a scope edge].

Talk soon, [Your name]

Four sentences. The commitment to a specific delivery date is what carries you into the shortlist conversation.

The actual response — what goes in 5 pages, not 25

Once you've done the discovery call (or have enough from the RFP), the response itself should be tight. Most agencies overinvest at this stage; the buyer doesn't read 25 pages, they skim for signals.

The structure that works:

Page 1: How we read the problem. One paragraph restating the brief in your own words. This is the "did they actually get it?" test. If you misread the problem here, no amount of creative recovery will save you.

Page 2: Approach and process. How you'd structure the engagement. Phases, deliverables, what's collaborative vs. agency-led. No timeline numbers yet — those go on page 4.

Page 3: Why us — the one or two case studies that match. Don't include five case studies. Pick the one or two that closely match the buyer's situation. For each: the brief, what you did, the outcome. One paragraph each, max.

Page 4: Timeline, scope, and price. A single page. Phases mapped to weeks. Scope deliverables enumerated. Price as a range with a single line on what would move it up or down. Be specific about what's not included — scope ambiguity at this stage is what kills proposals later.

Page 5: Working agreement basics. Payment terms, how scope-change is handled, who the day-to-day contact will be, intellectual property terms in one sentence. Nothing should be a surprise here.

That's it. Five pages, clearly structured, scannable in 8 minutes. The buyer's first read of your proposal is going to be a skim regardless. Make the skim work for you.

What kills proposals at the response stage

Three things, in order of frequency:

Over-creating "for free." Some agencies, trying to differentiate, do unprompted strategy work, mocked-up designs, or detailed plans inside the proposal. This often works — but it just as often signals desperation and locks you into a high effort-to-revenue ratio if you win.

Quoting a price as a single number. A range with explicit drivers ("$45-60k depending on scope of content production and number of stakeholder rounds") gives the buyer room to engage with the trade-offs. A single number forces them to either accept or reject before they've understood the levers.

Skipping the "what's not included" section. This is the section that protects you and signals professionalism. Buyers respect explicitness; vague proposals invite scope creep that you'll fight later.

The internal cost of doing this well

A clean RFP response on this template — first reply + discovery call + 5-page proposal — should take a partner about 4-6 hours total, spread across 3-7 days. That's roughly 1/3 of what most agencies actually spend on RFPs, because most agencies overinvest in the proposal stage.

The math: if you respond to 20 RFPs a year and you win 25% of them (industry average for shortlist-stage), you'll spend roughly 100 partner-hours on new business. At a partner's effective hourly cost of $300+, that's $30k in opportunity cost. Cut response time in half (which this template does) and you save $15k of partner time, or you can pursue 40 RFPs at the same cost.

The wins compound. Better filtering up front (the qualifying questions in the first reply) means fewer of the 20 are deeply unqualified. Tighter responses mean less wasted work. Faster turnaround means a higher shortlist rate.

What changes in a quarter

If you run this template on the next 10-15 RFPs:

• First few: Mild discomfort. The first reply feels short. The proposal feels brief. Push through — the buyer's experience is dramatically better than yours.
• By RFP 5-7: Your shortlist rate visibly improves. Buyers tell you in the discovery call that your first reply stood out from the others.
• By RFP 10+: Win rate at the shortlist stage holds steady or improves, but the time-per-pursuit drops 40-50%. You can pursue more deals at lower cost.

The competitive advantage in agency new business isn't being the most creative agency in the inbox. It's being the most operationally serious one. The first reply is where that signal gets sent.