How BidLab works
Why tendering feels so complicated — and how to make it manageable
By Ross Watson, Founder of BidLab
Talk to enough SME owners who’ve been through a tender process and you’ll hear some version of the same complaint: the work itself, the thing they’d actually be doing if they won, isn’t the hard part. It’s everything around it.
That’s because a tender is almost never one question. It’s a stack of documents, mandatory requirements, certificates, policies, financial thresholds, commercial schedules, pricing assumptions, case studies, method statements, and a set of submission instructions that will disqualify you if you get them wrong. The business is often perfectly capable of doing the work. What trips people up is proving it, in the right format, against everything the buyer happened to ask for.
The complexity is usually hiding in the detail
A tender can look manageable on first read. Then you actually start going through it properly.
One requirement sits in the main specification. Another turns up in an appendix nobody opened first. A mandatory certificate gets mentioned almost in passing, in a schedule three-quarters of the way through. Insurance levels are somewhere else entirely. The pricing workbook comes with its own separate set of instructions, usually written by someone different to whoever wrote the narrative questions. And the questions themselves ask for evidence, examples, mobilisation plans, service levels, performance measures — often several of these at once, inside a single question.
Some of what you’re being asked for isn’t even phrased as a question. It’s just a statement, buried somewhere in the pack, that still needs addressing or evidencing even though nobody asked you directly.
This is usually where things start to go wrong. Not because the business can’t do the work — because the information they need is scattered across a hundred pages and nobody’s had time to pull it together properly.
There’s more than one problem happening at once, which is part of why it feels so exhausting. A decent response requires you to hold several things in your head at the same time.
First, what’s actually mandatory. Some requirements are simply pass or fail — insurance levels, certifications, financial thresholds, policies, licences, the right forms filled in correctly, deadlines met to the minute. Get the narrative brilliant and miss one of these, and none of that quality matters.
Second, what the buyer is actually trying to find out. A lot of tender questions are deliberately broad — “describe your approach to service delivery,” that sort of thing — and a polished answer on its own won’t cut it. You need the right facts and the right examples from your own business sitting underneath the words.
Third, what you already have sitting around that could help. Most businesses hold more useful evidence than they realise — certificates, policies, old case studies, client references, performance numbers, team CVs. The problem usually isn’t a lack of material. It’s knowing which bit of it is relevant to which requirement, three tenders and eighteen months later.
And fourth — this is the one that actually matters most — what’s genuinely still missing. Not “what should we write,” which is a horrible, open-ended question to sit down with a blank page and answer. More like: what does the business still need to tell us, specifically, that we don’t already know?
That second framing is a much easier place to start.
Capable businesses still struggle with this
This is one of the more frustrating things about the process, honestly. You’ll meet businesses with years of relevant delivery experience, glowing references, a genuinely strong operational setup, all the right accreditations, a good team — and they’ll still turn in a weak submission, or miss a deadline entirely.
It’s rarely a capability problem. It’s a structure problem. Tendering asks you to translate everything you already know about your own business into the exact shape the buyer’s evidence and scoring criteria expect — and that translation work is where the hours disappear.
So the answer isn’t more complexity — it’s breaking it down
The most workable way through a tender is to stop treating it as one enormous task and split it into a handful of smaller, more honest questions. That’s the thinking behind BidLab.
Start with your own organisation, before you even look at a specific opportunity. What do you actually offer? Which sectors have you worked in? What certifications and insurance do you hold, and are they current? What case studies or past evidence could genuinely be reused? Where are the obvious gaps? Do that groundwork once properly, and you shouldn’t need to start from a blank page every single time a new tender lands.
Then look at the tender itself. What’s mandatory here? What is this particular buyer actually asking for? Where does your organisation already meet it, based on what you just worked out about yourself? Where are the real gaps, and is this even one worth bidding? That’s what a Tender Health Check is for.
Once you’ve compared the tender against what’s already known about the business, the remaining work gets a lot smaller and a lot more specific. Instead of being told to “write a tender response” — genuinely one of the more paralysing instructions in business — you end up with practical, answerable questions. How would you actually mobilise this service? What happens the moment something goes wrong? Which past project best demonstrates this particular requirement? Could your current insurance be increased if needed? How will performance get measured and reported back?
You don’t need to be a tender writer to answer any of that. You need to know your own business, which — reasonably — you already do.
From there, building the submission becomes something closer to structured assembly than a blank-page writing exercise: company facts, existing evidence, certificates, case studies, commercial information, the answers you’ve just given, all pulled together against what this specific tender required. That’s the Draft Submission piece.
None of this makes the tender itself less complicated. Buyers are going to keep producing dense procurement packs with schedules and appendices and evidence requirements scattered through them, and that isn’t going to change.
The aim was never to pretend the complexity isn’t there. It’s to stop it landing entirely on you to sort out — understand your organisation, understand the tender, work out what’s actually missing, answer the specific questions that remain, then build the submission — because the person running the business shouldn’t have to become a professional tender writer on top of everything else. They just need to know their business.
Bid with Confidence. Win more contracts.