← All workflows
Workflow · tenders, RFPs and bids
You didn't lose the bid.
You lost the week before it.
The tender lands. Nobody has three clear days. So it goes in the folder, the deadline passes, and the no-bid gets made by default — not on merit, not on price, not on capability. On time you never had.
The bids you never submitted cost more than the ones you lost.
Book a Bid Audit →
Where it actually goes wrong
Four failures, same root.
›The default no-bid. Not a decision. An expiry.
›The 11pm assembly. Last year's response, re-dated, with one section that still names the wrong client.
›The compliance kill. Disqualified on a missing certificate, a wrong form, an unsigned page — never on the work.
›The evidence hunt. Three hours finding the CVs, certificates and project references you already own, every single time.
None of it is a capability problem. It is a process that repeats, sits in nobody's job description, and therefore never gets built.
What the workflow does
An hour to decide. Days back on every response.
Day it lands
Qualified in or out against a written standard — in under an hour.
Immediately
Compliance matrix built from the document itself. Every mandatory item, listed.
First draft
Assembled from what you have already written and already won with.
Before submission
Checked back against the matrix. Nothing missing, nothing unsigned.
The AI does not write your bid from nothing — generic text is what an evaluator discounts first. It assembles from your own past responses, capability statements, CVs, certificates and references. The judgement, the pricing and the win themes stay yours. The three hours of hunting and re-typing do not.
The next step
The Bid Audit. Twenty minutes.
Not a pitch. Bring your last twelve months of tenders — even a rough count. I bring six questions.
How many tenders or RFPs crossed your desk in the last 12 months?
How many did you actually submit?
Of the ones you skipped — how many were fit, and how many were time?
How long does one response take, start to finish, and who does it?
When did you last lose one on a compliance item rather than on price?
What is your average contract value, and roughly what is your win rate?
Tenders skipped for time × your win rate × your average contract value
That is not a projection. It is your own arithmetic, on your own numbers — and it is the figure the workflow is built against.
Within 24 hours you get one page: what your bid process costs in hours, what the default no-bids cost in revenue, and what week one would change. It ends with one of two lines — this is worth building, or it isn't, and here's why. The second line is what makes the first one worth anything.
Book a Bid Audit →
This workflow is built with you, not run for you. It goes as deep as you choose — the three rungs →
Who this is for
Firms that bid for their work.
›You sell to government, state enterprises, energy, utilities, financial institutions or large corporates — anywhere procurement runs a formal process.
›Tenders and RFPs are a real share of your pipeline, not a once-a-year event.
›The response is written by the owner or a senior manager on top of a full job.
›You have won before. The evidence exists — it is just scattered.
Not for you if you bid once a year, you have a dedicated proposals team already running a system, or you have never won one — in that case the problem is positioning, not process, and the Quickscan is the better first move.
Questions people ask
Straight answers.
Why do small firms lose tenders they were qualified to win?
Usually they never submit. Nobody has three clear days, so the no-bid gets made by default. The ones that do go in are assembled late from a recycled document — which is also how firms lose on a compliance or formatting item rather than on price or capability.
How should you decide whether to bid?
With a written standard applied the day it lands, not a feeling applied the week it is due. Can we meet every mandatory requirement, do we have the past-performance evidence, is the contract value worth the response cost, is the timeline real. Under an hour, every time, so your no-bids are decisions.
Can AI write a tender response?
Not from nothing — that produces generic text an evaluator discounts immediately. It should assemble from what you have already written and already won with. Judgement, pricing and win themes stay with the people who know the work.
Who runs the tender process in a small firm?
Usually nobody, formally. It falls to the owner or a senior manager on top of a full job, which is why it happens at night and close to deadline. That is the defining feature of a workflow nobody owns: real work, repeated, in no one's job description.
A no-bid should be a decision.
Not an expiry date.