What I Learned From Three Tenders I Was Relieved to Lose
Photo: U.S. Army Corps of Engineers Savannah District, Public domain, via Wikimedia Commons
Every consultant has a case-study page. Fewer have an anti-portfolio. I keep a short one: a list of projects I didn’t win, didn’t pursue, or quietly stepped away from, along with a note on why I’m glad. It isn’t a wall of shame. It’s a record of the deals that looked like revenue and would have cost me something harder to replace.
I should say I’m not against turning down work. I’m against pretending every near-miss was bad luck. Some tenders are a lucky escape. Here are three.
The anti-portfolio is not a failure list
A case study says ‘here is what we can do’. An anti-portfolio says ‘here is what we shouldn’t do together’. That’s useful. It keeps me honest about the kind of client I serve well, and it gives me a language for walking away without making it personal.
It also protects margin. A project that looks profitable on the quote can turn sour fast if the scope is vague, the decision-making is broken, or the client is buying a rescue rather than a result. The money isn’t real until the work is done and the invoice is paid. Sometimes the best commercial decision is to leave the table.
The retainer with no edges
The first near-miss was a retainer. A prospect wanted ‘ongoing support’ for a fixed monthly fee, but couldn’t say how many hours, what kind of work, or who would be asking. The brief used phrases like ‘as and when’ and ‘we’ll grow into it’. They mentioned a budget that was roughly a third of what the scope implied, then said they were flexible.
I didn’t win it. I also didn’t really chase it. The warning signs were all there: no scope, no priority, no named owner, and a fee that only worked if the work stayed small. If I’d taken it, I’d have spent every month negotiating what counted. The client would have felt nickel-and-dimed, and I’d have felt like a helpdesk with a consultancy invoice.
Now I have a rule. If a retainer has no edges, it isn’t a retainer; it’s an open tab. I’ll offer a small, fixed diagnostic instead, or a defined block of days with a review at the end. If the client wants truly unlimited access, they need a different supplier and a much bigger budget. Saying that early is kinder than resenting it later.
The project with twelve owners
The second was a website replatform. It had a steering group, a sub-group, a digital working party and a procurement contact who described himself as ‘just the messenger’. There were twelve people in the first call. Nobody could say who could approve the final design. The phrase ‘we’ll need to socialise that’ came up four times in twenty minutes.
I was relieved when they went elsewhere. Not because the project was too big, but because it had no centre of gravity. Every decision would have been a committee decision, and every committee decision would have taken a fortnight. The scope would have drifted while everyone waited for permission. I’d have spent more time managing the client’s internal politics than doing the work.
The warning sign wasn’t the number of people. It was the absence of one person who could say yes. A committee can advise; it can’t make a decision. If nobody owns the outcome, the consultant becomes the lightning rod for every unresolved argument. That’s not a delivery role. It’s a therapy role with a project plan.
The rescue mission with no map
The third was a rescue. A client had a broken system, a hard deadline and a firm view that discovery was a luxury. They wanted a fixed price to ‘get it live in six weeks’. They couldn’t give me access to the existing setup until after the contract was signed. They also couldn’t say who had built it, or what had gone wrong.
I offered a two-week paid discovery instead. They declined. I was disappointed for about an hour, then I remembered what a rescue with no map usually looks like. You inherit someone else’s decisions, you discover the data is worse than described, and you spend the first month explaining why the original estimate was fiction. The client is already stressed. You become the next person who let them down.
The warning sign was the refusal to let me look before I quoted. I understand why clients do it. They want certainty. But certainty on unknown work isn’t confidence; it’s a guess with a deadline attached. If I can’t see the mess, I can’t price the clean-up.
How I walk away without burning the bridge
Walking away well is a skill. I try to do it quickly, clearly and without a lecture. I say what I can’t do, why, and what I can offer instead. If I know someone better suited, I make an introduction. I don’t badmouth the prospect to anyone, and I don’t write a passive-aggressive email that makes me feel clever for ten minutes.
The aim is to leave the door open. A client who wasn’t right this year might be right in eighteen months, or might refer someone who is. A short, honest ‘this isn’t my shape’ is better than a slow fade or a quote designed to lose.
What the anti-portfolio does for the next client
The anti-portfolio isn’t a monument to my good taste. It’s a practical tool. It reminds me to ask about decision-makers, scope and access before I get excited about the fee. It gives me the confidence to say no when the warning signs are flashing, and it makes the yeses cleaner.
If you’re a consultant, try writing yours. Three projects you’re glad you didn’t win. Three warning signs you now recognise. Three polite exits you can use next time. You don’t have to publish it. You just have to read it before the next shiny brief lands in your inbox.
A case-study page tells clients what you’ve done. A short anti-portfolio tells them what you’ve learned. Mine has saved me more margin than any pitch deck.