Why You’re Losing Design Proposals

All that hard work for nothing! Here, 11 tips for winning proposals and securing lucrative contracts.


Losing proposals, and the potentially lucrative contracts that come with winning them, just plain sucks. You know you can do that job–knock it out of the park, even. But for some reason, the prospective client went in a different direction, leaving you, your proposal, and the hours that went into it in the reject pile.


We’ve been there. I write a ton of proposals at my design studio Paper Leaf; some we win, some we lose. Over the years, though, we’ve refined our proposals and learned a lot about why we win the ones we do–and conversely, why we lose. And guess what? The reasons we lose proposals are likely the same reasons you lose yours. Here are the reasons, and here’s how to fix them.

You didn’t pre-validate the client as a good match.


This one is simple. Some clients are a good match, and some aren’t. A proposal will never convince a client to spend $20,000 on something valued at $500, so don’t bother. Figure this out quickly, before writing a proposal, and save both parties a bunch of time.

You didn’t set expectations beforehand.

There’s a variety of steps that need to go into a proposal before you actually start writing–and a big one is setting expectations with the client. Let your prospective clients know, prior to sending your proposals:

  • How you work
  • What your baseline project budget floor is
  • Why your solution is unique and well-suited for their problem

If not, you’re setting yourself up for failure.

Use the initial meeting(s) to learn about the client, but also help them learn about you, what you do, and what to expect from your proposal.

You didn’t build a rapport.


Buyers hire people they trust and people they like. It is near-impossible to accurately portray your personality through a big written proposal. Instead, you need to start building a rapport with the client immediately, before the proposal. Learn about their business, but learn about them as people, too. I don’t know about you, but when I’m working on projects, I prefer to work with people I like.

You’re pitching a Lexus to someone on a Ford budget.

Too many people don’t like to talk about pricing or budget–on both ends of the client-provider spectrum. The simple truth, though, is that budget is a key matchmaker. If we aren’t asking our clients what their budget is, or if clients refuse to tell us, we’re swinging in the dark. Clients usually have a number in their head, and sometimes that budget places them in line for a Ford. If you don’t know that, you might be pitching them a Lexus, and that’s a waste of everyone’s time.


It can work in the other direction as well. If you pitch a Ford to someone wanting a Lexus, you’re probably losing. The solution? Talk about budget honestly and openly, set expectations, and then deliver a proposal.

You didn’t turn it around fast enough.

I know, you’re busy. So is everyone, though. Our internal rule at Paper Leaf is to turn around proposals in seven calendar days from the initial needs assessment meeting, and we tell the client exactly that.


I’d encourage you to do the same. Pick a turnaround time that is as efficient as possible–meaning as fast as possible while still allowing you to write a great proposal–communicate that to the client, and stick to it.

You talked too much about cost and not enough about value.

Cost and value are two different things, and the former is easier to understand than the latter. If your proposals are focused only on the cost of your service or product and not the value of it, you’re missing a big opportunity.


Home renovations provide a great analogy. Let’s say you renovate your house: exterior, floors, and kitchen to the tune of $35,000. That’s the cost, and it’s not cheap, and presenting it can make for a difficult decision. But if it adds $75,000 of value to the home? That decision just got a whole lot easier.

You didn’t take a unique angle.

We’re often in situations where we’re one of multiple agencies asked to submit proposals for the same project. You’ve likely been in a similar position. The key line of thinking, in situations like these, should be: What is every other shop going to say? What are their unique angles going to be? And how can we differentiate ourselves?


It will change from project to project, and sometimes your point of differentiation will be lost or misunderstood. Often, though, your unique angle will be what wins you the job.

Here’s a real-life example from our shop. In a proposal, we emphasized lightweight, mobile-first design and development for a client whose user base was in third-world countries where high-speed internet wasn’t always available–and the most popular mobile phones were cheaper, less powerful ones. That mobile-first angle, in part, won us the contract.

You didn’t practice price-bracketing.


Price bracketing is a simple concept to execute with real results. Here’s a quick ‘n’ dirty explanation: in the pricing section of your proposal, lay out a pricing table with three options for your services and product (as opposed to just one option). Give those options names like “premium,” “pro,” and, “standard.” Include deliverables and a price for each option.

Now your prospective client has a choice other than yes or no; they can see all ends of the spectrum.

You tried to upsell, instead of starting with everything, then removing features.


Keeping with the psychology of pricing, proposals, and bracketing, here’s a simple change you can make when laying out your three-option pricing table. Instead of starting at the lowest-cost option (“standard”) and adding on features, start at the highest-cost option (“premium”) and remove features down the line.

The result here is a shift in perception on the client end: their thinking goes from “These extra features cost more” to “I don’t get these features with the Standard package.” It’s a simple form of loss aversion.

You talked too much about what you’ll do, not what the client will get.


This is a simple syntax change that can reap benefits in your proposals: Make it about what the client will receive, not what you will do. Here’s a simple example. Talking about what you’ll do reads like this:

We will build you a new website that uses WordPress as a CMS.

Instead, rewrite it to focus on what the client will get:


Your new website will run on WordPress, allowing you to easily manage website content.

All of a sudden, you’re not talking about yourself. You’re letting the client know a tangible deliverable and a benefit associated with it.

You gave up too soon.

The purchasing cycle is a decision cycle, and dependent on the level of cost and risk involved, it varies greatly. If you’re buying a T-shirt online for $20, that’s a pretty low-cost, low-risk purchasing decision. However, if you’re a client looking to sign a custom web design and development contract worth $35,000, it’s a much bigger decision.

That understanding needs to factor in to your proposals–and the follow-up to your proposals.

You can’t meet clients, send them a proposal with a price tag worth tens (or hundreds) of thousands of dollars, and then just leave it. Sometimes the client will come back quickly with a decision, but often I’ve had to follow up two or three times. In fact, we’ve closed deals at Paper Leaf months and months after we sent the original proposal.

So don’t just send your proposal and then check out. Instead, check in and see if you can help answer questions and move the decision process along.

All in all, winning proposals is an inexact science at best. The points outlined here, though, are points we’ve learned from both winning and losing big contracts. Give them a shot–the results might surprise you.

About the author

Jeff Archibald is co-founder of a design agency in Edmonton called Paper Leaf, an award-winning shop focused on brand identities, websites, and interfaces. If he's not learning, creating, speaking or herding cats, he's partaking in one of his many other loves: coffee, typography, whisky, cycling and the mountains