08/19/2026
A company sends out a website redesign RFP. It's 18 pages long. It requires a multi-page competitor teardown, a detailed sitemap, and fully itemized pricing just to be considered. The underlying project is actually a good one.
The strongest agencies on the shortlist pass.
This is happening more often, and AI-generated RFPs are part of the reason. Ask a chatbot to write a website RFP from a few bullet points and it will produce a complete-looking document modeled on the most exhaustive examples it can find. You end up with 18 pages where two carry your actual priorities and the rest is scaffolding the tool assumed you needed.
The agencies you most want to work with are choosing between projects. A document that reads like a procurement contract and demands unpaid strategy work up front will not win that competition.
A good website RFP communicates your goals, your challenges, your stakeholders, your technical requirements, your budget, and your timeline. Then it stops.
We put together a practical guide on how to get that balance right: https://hubs.li/Q04txgNr0
How to write a website RFP that gets strong agencies to respond—what to include, what to leave out, plus a lightweight template and the mistakes to avoid.