The Go/No-Go Decision Framework for Architecture RFPs

The Cost of Saying Yes to Everything

Most architecture firms say yes to every RFP that lands in their inbox. Not strategically. Not deliberately. Just yes, because saying no feels like leaving money on the table.

Here's what actually happens: your team burns through 2 weeks of billable time on a proposal for a client who's already chosen someone else. Your best designer gets pulled off paid work to chase a lead that dies in committee. You win the project but lose 3 junior staff to burnout before the schematic phase even starts.

This isn't a feeling. The numbers prove it.

The AIA found that architecture firms spend $5,000 to $50,000 per RFP submission. That's real money. And the Dezeen 2024 burnout survey found that over 60% of architects report burnout. Exhaustion isn't a personal failing; it's a symptom of chasing projects you should've declined months earlier.

A go/no-go decision framework flips this. Instead of asking "Can we win this?" you ask "Should we win this?" It's the difference between growth and grind.

Why Firms Skip the Hard Decision

Rejecting an RFP feels irresponsible. What if this is the one? What if the client gets offended?

That anxiety is real, but it's based on scarcity thinking. Most practices operate as if the next project is the last project they'll ever see. So they pursue everything.

Actually pursuing selectively does 3 things:

• It improves your win rate (you're competing on projects you're actually suited for)
• It reduces proposal costs (fewer submissions, better quality)
• It keeps your team from burning out (you're not bleeding resources on long shots)

The math works like this. Let's say your firm chases 20 RFPs a year and wins 3 (15% win rate). You spend roughly $30,000 per submission. That's $600,000 for $900,000 in revenue (if your average project is $300,000). You're not making money; you're just replacing your proposal costs with barely better cash flow.

Now say you apply a go/no-go framework and only pursue 10 RFPs. You win 4 (40% win rate). You spend $15,000 per submission. That's $150,000 for $1.2M in revenue. You just tripled your efficiency and still grew revenue.

That's not theoretical. That's what happens when you stop treating every lead like a survival situation.

The 6-Criteria Scoring Framework

A go/no-go framework needs teeth. It can't be a vague checklist. Each criterion should be weighted, scored, and defensible. Here's one that works:

1. Strategic Fit (Weight: 25%)

Does this project align with your practice's direction, experience, and positioning?

If you're a healthcare specialist and this is a retail center, it's a bad fit. Your team doesn't know retail codes. You're competing against firms who've built 30 of them. You're not the expert; you're the expensive learning curve.

Score it:

• Strong fit (9-10): Project type matches your portfolio and goals.
• Moderate fit (5-8): Related to your practice but not a core competency.
• Poor fit (1-4): Outside your wheelhouse or conflicts with positioning.

2. Client Quality (Weight: 20%)

Who is this client? Are they known for scope creep, slow decisions, or playing agencies against each other?

Talk to firms who've worked with them. Check references (yes, actually call them). Find out: Do they value design or just want low fees? Do they respect the design process or micromanage every detail? Will they pay on time?

A "good" client offsets a dozen project problems. A "bad" client makes a great project feel like punishment.

Score it:

• Strong (9-10): Established client, known for collaborative relationships, healthy budget.
• Moderate (5-8): New to you but appears stable; mixed intel on process.
• Weak (1-4): Reputation for adversarial relationships or chronic underfunding.

3. Budget Realism (Weight: 15%)

Does the fee make sense for the scope?

If they're asking for a master plan, SD, DD, and CA for $50,000, they're not serious. They're fishing for cheap explorations. Walk away.

Calculate your estimated effort in hours. Divide by the fee. If it lands below your minimums (usually $150-$200/hour depending on market), it's not a project; it's volunteer work.

Score it:

• Strong (9-10): Fee supports full-service delivery with proper margins.
• Moderate (5-8): Tight but possible with efficiency; some risk.
• Weak (1-4): Requires cutting corners or absorbing significant loss.

4. Timeline and Resources (Weight: 15%)

Can you actually do this without cannibalizing other work?

If the RFP deadline is in 3 weeks and your team is slammed with construction admin for another 4 weeks, you're setting yourself up to deliver a mediocre proposal. That's an immediate no.

Real timeline pressure doesn't just kill proposal quality. It kills project quality, team morale, and your reputation.

Score it:

• Strong (9-10): Timeline allows dedicated, focused effort.
• Moderate (5-8): Tight but manageable without impacting other commitments.
• Weak (1-4): Requires pulling staff from billable work or working nights.

5. Differentiation and Competition (Weight: 15%)

Can you honestly compete here?

Look at who else is chasing it. Are you the obvious choice or the longshot? If 8 firms of your caliber (or better) are bidding, your odds are rough. If only 2 or 3, you're in better position.

Also: can you say something meaningfully different? If your approach mirrors every other firm, design won't be a tiebreaker. Price will be.

Score it:

• Strong (9-10): You have a clear differentiator; limited competition.
• Moderate (5-8): You're competitive but not the obvious first choice.
• Weak (1-4): Crowded field or you can't articulate a unique position.

6. Long-term Relationship Value (Weight: 10%)

Beyond this project, is there potential?

Some clients are platforms. One renovation leads to an expansion, then a new facility, then an entire portfolio of work. Others are one-offs. Both are fine, but you should know which you're chasing.

A 1-time project with a difficult process and mediocre fee might still be worth it if the client is a developer who builds 5 projects a year. It's not worth it if they're a nonprofit doing their first renovation and probably won't build again.

Score it:

• Strong (9-10): High likelihood of repeat work; strategic partnership potential.
• Moderate (5-8): Possible future work; unclear repeat business.
• Weak (1-4): Likely one-off; no clear path to additional projects.

The Decision Matrix

Use this to score every RFP:

Scoring guide:

• 8.0 and above: Go. Pursue this project.
• 6.5 to 7.9: Proceed with caution. This is your decision call based on firm capacity.
• Below 6.5: No-go. Decline respectfully and move on.

When to Say No (Real Examples)

Here's where theory meets practice. These are the RFPs you should decline:

The Commodity Race

A retail developer sends you an RFP for 3 identical tenant improvement packages across 12 strip centers. Fee is $75,000 total. 8 firms are bidding. Winner gets chosen on lowest price, not design.

No-go. You'll lose this on price to someone with lower overhead. Even if you win, the margin evaporates.

The Underwritten Client

A nonprofit issued an RFP but their board already approved funds to hire their board member's cousin's architecture firm. The RFP is a formality for procurement.

No-go. You can't compete against predetermined decisions. Your proposal effort is free work for their process theater.

The Scope Creep Omen

During RFP clarifications, the client keeps adding questions. "Can you also explore a mixed-use addition? What about a parking study? And here's a list of 15 stakeholders who need to be interviewed in the process."

No-go. This signals a client who hasn't scoped their own project. They'll keep adding during the execution phase, the budget won't stretch, and your team gets squeezed.

The Opportunistic Lowball

A client calls with an RFP for a project they love your work for (you checked their references; they're solid). But the fee is 30% below market and the deadline is 2 weeks.

Maybe no-go. This feels like they want a quick exploration at discount pricing. If you win, they'll shop your design to cheaper firms for the actual delivery. Push back on the timeline or fee before submitting.

The Distressed Handoff

A project goes sideways under another architect and the client (correctly) blames bad design. Now they're putting it out for bid, hoping to fix it. Fee is for SD and DD only.

No-go (usually). You're being asked to fix someone else's mistake while the client is frustrated and angry. You inherit their problems, their timeline pressure, and their distrust. The only exception: the client is a repeat relationship you trust, they're realistic about what you can fix, and the fee reflects the reality of fixing legacy work.

The Math: Why Selectivity Wins

Let's model this for a 20-person firm that bills $200/hour as a blended rate.

Scenario A: Shotgun Approach (Current state)

• RFPs pursued per year: 20
• Proposal cost per RFP: $30,000 (150 hours at blended rate)
• Total proposal spend: $600,000
• Average win rate: 15%
• Projects won: 3
• Average project size: $300,000
• Annual revenue from won projects: $900,000
• Net after proposal costs: $300,000
• Burnout status: High (team stretched across bad pursuits)

Scenario B: Go/No-Go Approach

• RFPs pursued per year: 8 (applying framework)
• Proposal cost per RFP: $20,000 (100 hours, higher quality focus)
• Total proposal spend: $160,000
• Average win rate: 40% (better fit = better odds)
• Projects won: 3.2 (round to 3)
• Average project size: $350,000 (higher caliber clients)
• Annual revenue from won projects: $1,050,000
• Net after proposal costs: $890,000
• Burnout status: Manageable (team focused on winnable pursuits)

You didn't sacrifice revenue. You nearly tripled profitability and got your team's life back.

That's the real win.

Implementing the Framework (Practically)

Step 1: Build consensus on criteria

Get your leadership team in a room. Agree on the 6 criteria. Agree on what "weak" vs. "moderate" vs. "strong" looks like for each. Document it. This isn't subjective if you're specific.

Step 2: Create the decision moment

Designate someone as the gatekeeper. When an RFP lands, they run it through the matrix within 48 hours. This person has authority to say no without requiring full team debate.

That speed matters. Slow decisions become slow yeses, and slow yeses become resource drains.

Step 3: Make declining normal

Your first few no-gos will feel risky. They won't be. After you've declined 3 bad-fit pursuits and still hit your revenue targets, the anxiety dissolves.

Step 4: Track what you decline

Keep a simple log of rejected RFPs and the reasons. After a year, look back. Were your rejects actually bad opportunities? Did any of them become known disasters for the firms that pursued them? This data hardens your conviction.

FAQ

Q: Won't clients be offended if we decline their RFP?

A: Most won't care. If you respond quickly and respectfully ("We appreciate the opportunity, but we don't think we're the right fit for this particular project scope"), they move on. The ones who get offended are usually the difficult clients you'd regret working with anyway. You've self-selected out of a bad relationship.

Q: What if we decline something and regret it later?

A: You might. Once. That's your learning moment. What changed? Was it a criterion you weighted wrong? A misread on the client? Adjust and move forward. One regret against dozens of avoided bad pursuits is a solid trade.

Q: How do we handle partner disagreement on a decision?

A: Your scoring matrix is the tiebreaker. If two partners disagree and it scores 6.8, you're in the caution zone. Whoever feels stronger can make the call, but the decision should be informed by the data, not just gut feel.

Q: Can we adjust the weightings for different project types?

A: Yes. A healthcare facility might weight "strategic fit" at 30% instead of 25%. A renovation might weight "client quality" higher because scope ambiguity is more dangerous. Build variants if you need them, but don't build new variants every time. That defeats the purpose (making decisions faster).

Q: What if our pipeline is empty and we really need the work?

A: You take a project you'd normally decline. But be honest about it. Score it, see it's a 5.2, and make the choice deliberately. You're accepting a known risk for survival reasons. Once the pipeline is healthier, you return to your standards. Desperation-driven decisions should be conscious, not accidental.

The Shift

This isn't about becoming picky. It's about being strategic.

You're not rejecting projects because you're arrogant. You're rejecting them because pursuing the wrong project costs more than not pursuing it. You're optimizing for the projects you can actually do best work on, with clients who'll respect that work, at fees that justify the effort.

That's not gatekeeping. That's professionalism.

Your team will feel it first. No more 2 AM proposal scrambles for leads that were dead on arrival. No more designing into a wall because the scope was never real. No more staying at the office because you're underwater on a project you never should've chased.

Then your metrics improve. Win rate climbs. Project profitability climbs. Your reputation improves because you're doing better work for better clients.

It's not magic. It's just stopping the bleeding.

---

Related Reading

• Architecture Proposal Best Practices
• How Architecture Firms Win More Proposals
• AEC Win Rate: What Top Architecture Firms Know
• Why Architecture Firms Lose Proposals (And How to Fix It)