Most of what's written about RFPs focuses on formatting and templates. We focus on the process problems underneath: how firms decide whether to bid at all, why answer libraries drift out of date, what actually breaks when a team scales from five RFPs a quarter to fifty, and where general-purpose AI tools like ChatGPT help versus where they quietly become the bottleneck. If you're building or running a proposal function at a B2B services or software company, this is the backlog of things we wish someone had told us first. New posts go up as we learn something worth sharing — check back, or browse the RFP glossary and tool comparisons for reference material alongside the writing.

Most Losing Bids Are Never Actually Read

Disqualification is quiet, common, and almost entirely preventable. Here is how bids die before evaluation, and the compliance matrix that stops it.

Read the article →

Your RFP Answer Library Is Probably Wrong

Reuse is the whole point of a content library. Stale reuse is how firms commit to things they can no longer deliver.

Read the article →

What Evaluators Actually Do With Your Proposal

Scoring is more mechanical, more rushed and far more literal than most bid teams write for — why coverage beats polish.

Read the article →

Why ChatGPT Works for Your First 5 RFPs and Fails at Your 50th

The chatbot solves the typing. It leaves the actual bottleneck untouched — and where a general-purpose AI stops being the right tool for a repeated team process.

Read the article →

Most RFPs Are Lost Before Anyone Writes a Word

What actually happens between an RFP landing in your inbox and a proposal going out, and how much of it your team should not be doing.

Read the article →