Small teams don’t need more process so they can look terribly grown up in meetings. They need something that stops them wasting time on work that was never a good idea in the first place.
That’s why qualification matters so much more than people think, especially in smaller businesses. A big company can survive quite a lot of bid nonsense. It can throw more people at the problem, soak up the wasted effort, and keep lumbering forward. A small team doesn’t usually get that luxury. One bad bid decision can swallow a week of leadership time, drag good people away from live work, annoy finance, clog the diary of the poor soul writing most of the response, and generally leave everybody asking how they got so tired for so little return.
So if you’re going to have a qualification framework, it has to be simple enough to use when people are busy, because that’s exactly when you need it. If it needs a workshop, a slide deck, and a committee, it’ll be ignored until the bid has already started. At that point, the conversation isn’t really “should we do this?” any more. It’s “how do we justify the fact that we’ve already half started?”
That’s the trap small teams fall into all the time. Not ignorance, exactly. Drift. A tender appears, looks vaguely relevant, and starts gathering momentum before anybody has made a proper decision. Somebody spots it on a portal. Somebody else says the value looks decent. Someone senior says it’s worth a look. And because there aren’t many people in the business, that sequence of events somehow becomes a decision by osmosis. Really, it’s just enthusiasm left unsupervised.
The fix doesn’t need to be complicated. In my view, a small-team qualification framework only needs to answer four things. Does the work fit? Are we well positioned? Is it worth winning? And can we actually respond properly without setting fire to everything else?
That’s it. Fit, Position, Value, and Practicality. Nothing fancy. Plain is good.
Fit comes first because it saves the most grief. Strip away the shiny bits for a minute and look at the work itself. Is this actually the sort of thing we do? Is the sector familiar enough that we can speak with proof instead of hand-waving? Is the size sensible for the way we operate? Can we meet the technical and compliance bits with the business we’ve actually got? Small teams are often used to stretching, and sometimes that’s a genuine strength. But there’s a big difference between stretching a bit and quietly inventing a fantasy version of your company that only exists inside the bid.
Position matters next, because being able to do the work isn’t the same as having a believable chance of winning it. Did you know the opportunity was coming, or has it landed completely cold? Do you know the client, the market, or the incumbent well enough to avoid guessing your way through the response? Do you understand what the buyer actually needs, or are you just reacting to the wording on the page? Have you got any real angle beyond turning up and hoping to write something half decent? Small teams pay a high price for ignoring this. Cold bids can be won, yes, but they eat time and energy for breakfast.
Then comes Value, which is where people often get a bit silly. The contract value looks good, so everyone starts acting as though the opportunity must be worthwhile. Those two things are not the same. For a small team, value means margin, bidding cost, mobilisation effort, reporting burden, delivery risk, cash flow, contract length, and whether the work actually takes the business in a useful direction. Big contract doesn’t automatically mean good contract. Sometimes a smaller piece of work is much better for you because it fits, pays properly, and doesn’t require internal warfare every month.
And then there’s Practicality, which is where even good opportunities can go bad. You might have a strong fit. You might have decent position. You might think the contract would be worth winning. Fine. Can the team actually respond properly? Have you got the right contributors available? Do you have the evidence you need? Is the pricing exercise manageable, or is it about to consume days you haven’t really got? What else is already going on? Small teams don’t only lose by chasing the wrong opportunities. They also lose by trying to do too many good ones at once. There’s a world of difference between having enough capacity to submit something and having enough capacity to bid well.
If you want to make those four tests repeatable, a simple scorecard works perfectly well. Score each area from one to five, then write a sentence on the biggest risk. That sentence matters because numbers on their own can make people feel much more confident than they should. A tidy score with one rotten commercial problem hidden inside it is still a bad bid. The scorecard isn’t there to replace judgement. It’s there to force people to use some.
I’d also keep a middle ground in the decision, because not every tender is a clean yes or no. “Bid with conditions” is often the most honest answer in the room. Maybe the opportunity is fine, but only if a delivery partner is confirmed, or finance signs off the pricing, or a key person can make time, or the clarification comes back the right way. That’s a much healthier position than pretending everything is green when half the team can already see the shelf wobbling.
There are a few warning signs that deserve immediate suspicion. If the bid is completely cold and you know almost nothing about the buyer, slow down. If the spec looks oddly tailored to someone else, slow down. If the work is much larger or more complex than your normal delivery model, slow down. If the return looks weak compared with the effort of bidding, slow down. If the timetable is daft, slow down. And if the strongest internal argument in favour is “we should have a go”, slow right down, because that phrase has caused a tremendous amount of pointless suffering over the years.
One good thing about small teams is that you don’t need a cast of thousands to make a sensible decision. Usually the right people are obvious: whoever owns the commercial call, whoever understands delivery risk, whoever will own the bid, and whoever has to live with the pricing. Sometimes that’s four people. Sometimes it’s two. Sometimes it’s one overworked human wearing three hats and asking somebody else for a sanity check. That’s fine. Informal is fine. Careless isn’t.
And if you want the framework to get better over time, don’t just record yes or no. Record why. Keep the score, the strengths, the risks, the conditions, and what happened in the end. After a while, patterns start showing up. You may find that bids with weak Position almost never convert however much energy goes into them. You may find that modest contracts with strong Fit and Practicality are much better business than glamorous monsters that eat the team alive. You may find that senior overrides create lots of motion and not much else. Without those records, you’re left with anecdotes and hunches. With them, you can actually learn something.
That’s really what a small-team qualification framework is for. Not to make the business sound mature. Not to create paperwork. Just to protect time, energy, and judgement from being wasted on work that doesn’t stack up. Used properly, it gives people permission to pause, think, challenge the excitement, and say no without feeling awkward. In a small team, that’s not bureaucracy. It’s survival.