Target: Agency
Risk: medium

Stop Writing Proposals for Clients Without a Budget — Here's Why

Agencies waste thousands of hours on detailed proposals for leads without real budgets. A hard truth about lead qualification and pre-sales efficiency.

Business essentials with calculator and coins

Charles Haggas, co-founder of design studio Brightscout, described a situation every agency owner recognizes 1:

A promising lead reached out. The discovery call went well. The project was interesting. Then Haggas asked the question most agencies are afraid to ask: “What’s your budget?”

The client refused to answer. They expected a detailed proposal anyway. When Haggas explained his policy — no detailed proposals without budget validation — the client said other agencies were more than willing to write proposals without any budget discussions.

He was right. They always are. And that’s precisely the problem.

The Cost of Proposals Without Budget Validation

Most agencies treat proposal writing as a cost of doing business. But the math doesn’t work in their favor:

  • 10-40 hours per detailed proposal
  • 20-40% close rate on qualified opportunities
  • $1,000-$4,000 in opportunity cost per proposal (billable hours lost)
  • Hundreds of proposals per year for a busy agency

When a significant portion of those proposals go to leads without real budgets, the waste is enormous.

Why Agencies Keep Writing Blind Proposals

Despite knowing the math, most agencies continue the practice. The reasons are rooted in fear:

  • Fear of losing the client — “If I ask about budget, they’ll think I’m only interested in money.”
  • Fear of competitors — “The other agencies will write a proposal, and I’ll lose the deal.”
  • Fear of appearing inflexible — “If I have strict rules, I’ll seem difficult to work with.”
  • Fear of missing out — “This project might be their big break, and I’ll miss it.”

These fears are understandable but irrational. A lead who won’t share their budget is almost never worth a detailed proposal.

The Signal in the Refusal

When a client refuses to share their budget, it signals one of three things:

  1. They don’t have a budget — they’re exploring options without any intention of buying soon
  2. Their budget is unrealistic — they know their number is too low for the project
  3. They don’t understand the value — they see software development as a commodity, not a partnership

In all three cases, sending a detailed proposal won’t help. The first case wastes your time. The second case leads to a negotiation where you’ll be pressured to cut scope or price. The third case means the client isn’t ready to choose a vendor intelligently.

How to Qualify Before You Write

The Budget Question

Asking for a budget isn’t rude — it’s professional. The right framing: “To prepare a proposal that matches your expectations, it helps to know your budget range. If the budget is far from the market rate for this type of project, we can discuss scope adjustments before I invest time in a detailed estimate.”

The Benchmark Alternative

If a client truly doesn’t know their budget, use market benchmarks: “For a project like this, the typical range is $50,000-$100,000 depending on scope and quality standards 2. Does that align with your expectations?”

This educates the client and filters out mismatched opportunities without requiring a full proposal.

The Triage System

Not all leads deserve the same level of effort:

Lead type Effort Approach
Budget confirmed, clear scope High Detailed proposal
Budget confirmed, unclear scope Medium Discovery workshop first
No budget, clear scope Low Share market benchmarks, ask for budget
No budget, unclear scope None Send them to a self-service tool

How Apropo.io Helps Agencies Qualify Better

Market Benchmarks: When a lead won’t share their budget, share market data instead. “For this project type, the median quote in your region is $60,000 2. Does that fit your expectations?” This educates the lead and filters out mismatches.

PPQL (Pay-Per-Qualified-Lead): Instead of paying for lead volume, pay for leads with verified budgets and genuine buying intent.

Readiness Check: A self-service tool that helps clients prepare before they contact you. Clients who complete it arrive with realistic expectations and a clearer brief.

Quote Sanity Check: Before sending any proposal, verify that your estimate aligns with market data. If it doesn’t, you’re either pricing yourself out or undervaluing your work.

Summary

Writing proposals for clients without budgets is the single biggest waste of time in agency pre-sales. The fear of losing deals keeps agencies trapped in a cycle of low-value proposal work.

Break the cycle: ask for the budget, share market benchmarks, and triage leads by readiness. The clients who can afford you will respect the process. The ones who can’t will self-select out — saving you weeks of wasted effort per year.

Footnotes

  1. Blog by Charles Haggas — “When a Client Asks for a Proposal Without a Budget: A Call to Action for Agencies.” Source

  2. Apropo Insights Benchmarks — market data from anonymized RFP and proposal logs. See methodology. 2

Want to stop preparing client proposals manually?

See how Apropo.io helps software houses create benchmark-backed estimations, qualify leads, and scale presales.

Book Apropo.io Demo

Recommended Reading

Vendor Selection

$30K or $300K? Why the Same Project Costs Completely Different Amounts — and How to Check

A non-technical founder receives quotes from $30K to $300K for the same project. Here's why the spread exists and how to compare offers intelligently.

Read Article arrow_forward
Vendor Selection

The Cheapest Software House Quote — Why a Smooth Launch Can Hide Costs That Surface 8 Months Later

A startup chooses the cheapest dev quote, launches smoothly, then hits a wall. The real cost isn't lower — it's just deferred.

Read Article arrow_forward
Project Management

The Fixed-Price Project That Almost Ruined Our Agency

A real story of how a fixed-cost web development project nearly destroyed a software house — and the lessons every agency owner should learn.

Read Article arrow_forward