How to Write a Winning Tender as a Small Contractor

I've priced tenders from both sides of the table. As a contractor putting bids together, and as a QS evaluating them for clients. That perspective has taught me something that most small contractors don't want to hear: the reason you're not winning work often has nothing to do with your price.

Let me be blunt. If your tender submission is a one-page quote on your company letterhead with a number at the bottom, you're not competing. You're just filling out someone's bid list to make up the numbers.

Why Small Contractors Lose Tenders They Should Win

The typical scenario goes like this. A small contractor — good team, solid track record, competitive pricing — gets invited to tender on a £1.2m office fit-out. They price the job carefully, maybe undercut the competition by five percent. And they lose.

Why? Because the client's QS or project manager looked at three submissions side by side, and two of them told a story about how the project would be delivered. One of them was just a number.

The firms that consistently win work at this level understand that a tender is a sales document. It's your chance to show the client that you understand their project, that you've thought about the risks and opportunities, that you have the team and the capability to deliver. Price matters — of course it does — but it's rarely the only factor.

What Makes a Strong Tender Return

After reviewing more bids than I can count, the pattern is clear:

An executive summary that shows you understand the project. Not a generic company profile — a one-page summary that demonstrates you've read the tender documents, you understand the scope, you've identified the key challenges, and you have a plan. Reference the specific building, the specific constraints, the specific programme requirements. Show you've done your homework.

A management organogram with real people. Not "Project Manager TBC" — actual names, actual CVs, actual relevant experience. Clients at this level are buying your team as much as your company. If your proposed project manager has just delivered a similar scheme, say so.

A programme that demonstrates you've thought about sequencing. A tender programme doesn't need to be a 500-line Primavera schedule, but it needs to show you understand the sequence of work, the key milestones, the critical path, and the interfaces between trades. A one-page bar chart that shows strip-out, first fix, second fix and completion dates tells the client nothing. Show them you understand the phasing, the lead-in times for key packages, and where the pinch points are.

A clear pricing document. Whether it's a bill of quantities, a schedule of works, or an activity schedule, your pricing needs to be transparent and easy to evaluate. Lump sums with no breakdown are a red flag to any competent QS.

A methodology or approach to works. How are you actually going to deliver this project? What's your approach to logistics, access, working hours, welfare, waste management? For refurbishment projects, how are you dealing with the existing building's constraints? This is where you differentiate yourself from the contractor who's just priced the same BOQ.

Health and safety and environmental credentials. Not a 50-page safety manual — a concise summary of your H&S management approach, your CDM competence, your recent safety record, and any relevant accreditations. SSIP, CHAS, Constructionline, CSCS — whatever's relevant.

Relevant experience and references. Case studies of similar projects, ideally with completion photos, final account values, and client references. Three to five projects that demonstrate you can deliver this type of work at this scale.

The Pricing Strategy

Let's talk about numbers. There's a misconception among small contractors that winning tenders is about being the cheapest. Sometimes it is — some clients will always take the lowest compliant bid. But in my experience, that's becoming less common, particularly in the commercial fit-out sector.

Most sophisticated clients use a quality-price evaluation. Typically 60/40 or 70/30 in favour of quality. That means your methodology, your team, your programme, and your track record count for more than your bottom line.

Even on price-only evaluations, the lowest tender doesn't always win. A QS evaluating bids will look for anomalies — packages that seem underpriced, provisional sums that are unrealistically low, prelims that don't add up. An unrealistically low price can be as concerning as a high one, because it suggests either the contractor hasn't understood the scope or they're planning to make their money on variations.

My approach has always been to price the job honestly, present the price clearly, and make sure the qualitative elements of the submission demonstrate value. You don't win on price alone — you win on confidence.

Common Mistakes

Submitting late. This should be obvious, but I've seen contractors disqualified from bid lists for late submissions more times than I can count. The deadline is the deadline.

Not reading the tender documents properly. If the tender asks for a specific format, specific information, or specific documents, provide them. If there's a tender query deadline, use it. If there's a site visit, attend it.

Generic submissions. I mentioned this already, but it's worth repeating. If your organogram looks the same on every tender, if your methodology could apply to any project, if your programme is clearly a template with dates changed — evaluators notice. Every time.

Ignoring the preliminaries. Your prelims are where the client sees how you'll actually run the project. Shared welfare vs dedicated welfare, site management team size, duration of temporary works, approach to security — these tell a story about how you operate. Price them honestly and present them clearly.

Not asking questions. The tender query process exists for a reason. If the documents are ambiguous, if the scope is unclear, if there's a discrepancy between the drawings and the specification — raise it. Not asking questions doesn't make you look easy to work with. It makes you look like you haven't read the documents.

Using Technology to Win More Work

One of the reasons we built Construction AI's tender management software the way we did is because I lived through the pain of managing tenders on spreadsheets. Tracking which packages have been sent, which subcontractors have responded, comparing returns like-for-like, pulling all of that into a coherent submission document — it's a massive time sink.

When construction bid management is handled by the system, you free up time for the things that actually win tenders: thinking about the project, developing your methodology, refining your programme, getting your pricing right. The fundamentals haven't changed — understand the project, present a credible delivery strategy, price it honestly, and treat every tender submission like what it is: your best opportunity to win the client's confidence before you've laid a single brick.