How to respond to an RFP without losing your weekend

Most lost tenders are not lost on price. They are lost on process: a missing tax clearance certificate, an unsigned declaration, an answer submitted in the wrong format, a reference that did not cover the required three years. The evaluation panel never even got to your pricing.

The fix is unglamorous and it works: treat the RFP as a checklist before you treat it as a writing exercise.

1. Read the document twice, for two different things

The first pass is for rules: what must be submitted, in what format, by when, signed by whom. The second pass is for substance: what the buyer is actually trying to achieve.

Teams that skip the first pass write beautiful proposals that get disqualified on page one of the evaluation sheet.

2. Build a compliance matrix

A compliance matrix is one row per requirement. Each row holds:

• the requirement, quoted from the source document
• where it came from (section and page)
• how severe non-compliance is
• who owns the answer
• your response, and whether it is finished

That is the whole method. It sounds bureaucratic until the first time it saves a bid.

3. Pay attention to the modal verbs

RFP language is precise, and the verbs carry the risk:

• shall / must — mandatory. Missing one usually costs you points and can cost you the bid.
• will be rejected / non-responsive / excluded — this is the disqualifying tier. If the document says an omission makes your bid non-responsive, that row is not negotiable and it is not a "nice to have".
• should / may / is desirable — scoring or optional. Answer them, but after the mandatory rows.

A useful discipline: nothing gets called disqualifying unless the document itself says non-compliance leads to rejection. Over-flagging is its own failure mode — when everything is critical, the team stops triaging and starts panicking.

4. Triage in severity order

Work the disqualifying rows to done first, then the mandatory ones, then everything else. Two practical benefits:

1. You find out early whether you are even eligible — before you have invested three days of writing.
2. If the deadline compresses, the work you sacrificed is the work that costs the fewest points.

5. Answer from evidence you already have

Almost every "demonstrate your experience" question has already been answered inside your own business. The client name, the contract value, the delivery dates and the outcome are sitting in your CRM. The question of whether you can staff the work by March is sitting in your resourcing plan.

Copying that evidence in beats inventing prose, twice over: it is faster, and it is true.

6. Audit before you submit

Before the final PDF, re-read your response against the matrix, not against itself. For every row: is there an answer, does it address what was asked, and is the required attachment actually attached? Weight the remaining gaps by severity so one unanswered disqualifying row does not hide behind twenty tidy optional ones.

How Kudu automates this

The RFP Assistant in Kudu PitchPro runs exactly this method:

• Import the tender document and Kudu AI extracts every requirement, deadline and mandatory attachment into a compliance matrix, with the source excerpt attached to each row.
• Each rule is assigned a severity using thresholds your workspace controls — so "shall" means High, and only explicit rejection language means Disqualifying. Filter the matrix to High and Disqualifying with one click.
• Matching past performance from your CRM and real availability from your resourcing plan appear beside the rule you are answering.
• The AI Compliance Audit scores the draft with disqualifying gaps weighted five times heavier than normal ones, sorts findings worst-first, and logs each run with the thresholds it used.

The judgement stays yours. The clerical work — the part that actually loses tenders, and the part that eats your weekend — does not have to be.

RFP Assistant is available in PitchPro. AI auto-draft is included from Pro; the Compliance Audit and severity tuning are Business plan capabilities.