RFP to PowerPoint: A Controlled Proposal Workflow for Consulting Firms

An RFP to PowerPoint workflow is the controlled path from receiving a request for proposal to submitting the deck. Intake and version control. A compliance matrix. An agreed bid thesis. Retrieval from approved credentials. Drafting into your template. Three separate reviews. A recorded release.

Nine steps. The order matters more than any single one of them, and the most common failure is starting at step six.

I have watched enough bids to know the shape of a bad one. It starts with somebody opening a blank deck on day one, because building feels like progress and reading the tender document does not. Four days later the storyline is beautiful and question 3.2b, the one requiring three comparable projects from the last five years, has not been answered at all.

Here is the sequence that avoids that.

Step 1: create a clean RFP record

Before anything else, capture the request as a record rather than as an email thread.

Store the original request, all attachments, the clarification correspondence, the submission channel, the deadline including time zone, the client entity, the language, the confidentiality level and the version. Assign a bid identifier.

Somewhere in your firm there is a file called Final_v7.pdf. It is a filename, not version control. When the client issues an addendum four days before submission, and they will, you need to know which version each answer was written against.

For public procurement this matters more than usual. Formal requirements can determine whether a bid is admissible before anyone reads your argument. The procedures differ across frameworks, but the operational rule is constant: mandatory conditions are a different object from persuasive content, and they need to be captured separately.

Step 2: build the compliance matrix

Extract every question, required statement, attachment, format rule, page limit, declaration, signature and deadline into one structured table.

Let AI populate the first draft of this table. It is genuinely good at extraction and the work is tedious enough that people rush it. Then have the proposal manager confirm completeness before any creative work starts.

This is the highest leverage half day in the entire bid. A missed mandatory question found on day two costs nothing. Found on submission day, it costs the bid, and no amount of storyline quality compensates.

Step 3: agree the bid thesis

Before a single slide exists, write the central argument in one paragraph.

The client needs to deliver X despite Y. We recommend Z because our team combines A, B and C. The first measurable outcome will be D within E, subject to the assumptions listed.

Teams skip this step because it feels like an unnecessary meeting. It is the step that decides whether the proposal is any good.

Without a thesis, the deck becomes a catalogue of everything the firm can do. With one, every subsequent decision has a test: does this slide advance the argument, or is it here because we have it. That test alone removes about a fifth of the pages from most first drafts.

The thesis also gives the automation a stable decision context. A generation instruction that includes the thesis produces material that argues. One without it produces material that describes.

Step 4: plan the response structure against the matrix

Now map the compliance matrix onto a page structure. Two rules.

The RFP's structure wins. If the tender specifies a response format, section order or page limits, that overrides your house storyline. Compliance outranks style, always, and evaluators frequently score against their own structure.

Every requirement has a destination before drafting starts. Each row in the matrix points at a specific slide or appendix. Requirements with no destination are the ones that go missing.

Where the RFP leaves the structure open, a sequence that works:

1. Our understanding of the situation and the decision you face.
2. What success should look like.
3. Recommended approach and workplan.
4. Why this approach fits your constraints.
5. Team and governance.
6. Relevant experience and proof.
7. Deliverables, timeline, assumptions and commercials.
8. Compliance appendix.

Step 5: review the storyline as text

Take the page titles, in order, as plain text. Read them as a single argument. Does the sequence make a case, or is it a list of topics?

Twenty minutes here saves an afternoon later. Challenging ten page titles is cheap. Challenging ten fully formatted slides is expensive, and the person who built them will defend the layout as though you criticised the argument.

Step 6: draft with sources and constraints

Only now does anyone build slides. And the drafting instruction needs to carry more than a topic.

Draft slides 4 to 9 for requirement IDs RFP 2.1 to RFP 2.4. Use only project records PR104 and PR221 and methodology version M12. Preserve the approved client wording where quoted. Each slide needs an action title, evidence and a source footer. Mark missing evidence as [OPEN]. Do not create pricing, staffing availability, client names or outcome metrics.

Five things are specified: scope, permitted sources, protected content, output rules, and an explicit list of what may not be invented. That last element is the one that separates a reviewable draft from a plausible one.

The prohibition list is not paranoia. Pricing, availability, client names and outcome metrics are exactly the four categories where a confident invention costs you a client relationship rather than an edit.

Step 7: generate into the approved template

Master, layouts, typography, colours, icons, legal pages, appendix conventions. Native text, shapes, tables and charts that stay editable.

The first draft is never the deliverable. Partners rewrite action titles. The team changes. Assumptions move. Pricing gets updated two hours before submission, which it always does. If the output is flattened or lives in a web viewer, every one of those completely normal edits becomes rework in a tool nobody wants to fight at eleven at night.

Step 8: run three separate reviews

These are three different jobs. One tired reviewer will silently collapse them into a visual proofread.

Compliance review. Is every requirement answered, in the specified location and format? Declarations, attachments, signatures, page limits, filenames, deadline. This review reads the matrix, not the story.

Evidence review. Is each credential accurate, current, permitted and relevant? Is team availability confirmed by the person who controls it? Are outcomes, client names and qualifications real? Can every material claim be traced to a record?

Persuasion review. Does the proposal make a choice? Does it show understanding, or recite the RFP back to the client? Is the approach feasible with the team proposed? Are differentiators supported? Would an executive understand why this team is the lower risk option?

Assign them to different people wherever you can. The compliance reviewer should ideally not have written any of it.

Step 9: freeze, submit, and learn

Lock the submitted version. Record the approver by name. Archive the compliance matrix together with the exact evidence records used and their effective dates.

Keep updating the live source library as facts change. Never overwrite the records that went into a submitted bid. If a client challenges a claim eight months later, you need to know what you actually said and what it rested on.

After the decision, capture structured feedback: shortlisted or not, strengths, weaknesses, price position, missing evidence, client objections, and which content needed heavy rework. Feed that into the workflow and the source library. Do not feed it into an uncontrolled training process built on client material.

The bid submission checklist

What to measure

Most firms measure win rate and drafting time. Both matter and neither tells you where the process is failing.

• Hours from RFP receipt to a review ready first draft.
• Time spent searching for people and project evidence.
• Mandatory requirements missed, caught internally versus caught by the client.
• Claims that turned out to be unsupported or needed correction.
• Partner review cycles and material rewrites.
• Format and submission defects.
• Share of content drawn from approved records versus rebuilt.
• Time spent maintaining the source records.
• Shortlist rate, win rate and client feedback by proposal type.

Watch the relationship between drafting time and review cycles. If drafting halves while review cycles rise, you have moved work to your partners rather than removing it, and partners are the most expensive place to move work to.

Where offgen fits

The Company Brain holds CVs and project references, approved slides, methodologies and protected wording as structured records with permission metadata. A proposal skill built in the Structured Skill Builder defines which sections vary, which sources are permitted, which elements stay locked and which reviews apply. Output is native PowerPoint, because partner review happens in PowerPoint and the pricing always changes at the last minute.

More on how this fits practice workflows is on our consulting page.

Start with one proposal type and one evidence set you are genuinely willing to maintain. Get retrieval, sources, template behaviour and approval to a point partners trust. Then add sectors, languages and response formats. Firms that try to do all of it in one quarter end up trusting none of it.