Every few weeks I see a small business put out a formal Request for Proposal for a five-page website. Ten pages of requirements, a submission deadline, a scoring rubric, sometimes a mandatory bidders' call. For a project that should cost somewhere between $500 and a few thousand dollars.
I understand the instinct. An RFP feels rigorous. It feels like what a responsible buyer does. Somebody on the board suggested it, or the owner came from a corporate or government background where RFPs are simply how purchasing works, and for big purchases in those worlds, they are.
But for a small website project, an RFP is the wrong tool, and not in a mildly inefficient way. It actively selects for the wrong vendors, costs you weeks, and produces a decision based on who writes the best proposal rather than who builds the best website. Those are very different skills.
Here is why, what to do instead, and, because the answer is not never, when an RFP genuinely makes sense.
Why RFPs Backfire on Small Website Projects
The Best Small Shops Will Not Bid
A serious response to an RFP takes a competent shop somewhere between several hours and a couple of days: reading the requirements, writing the proposal, building the estimate, formatting it to your template. For a $50,000 project, that investment makes sense. For a $2,000 website with five bidders and a 20 percent chance of winning, the expected return is far below what those hours earn doing actual client work.
So the busy shops with full pipelines, which is to say the ones whose work you actually want, quietly pass. Who does respond? Shops with empty pipelines, shops with a salesperson whose whole job is proposal volume, and offshore mills that fire a templated response at every RFP on the internet. Your rigorous process just filtered out the people you were hoping to find.
You Are Scoring the Wrong Skill
An RFP evaluates writing, formatting, and promise-making. A website project needs design judgment, technical execution, and follow-through. The overlap between "writes a beautiful 12-page proposal" and "ships a fast site on schedule and answers the phone in month eight" is much smaller than the RFP process assumes. Some of the best builders I know write mediocre proposals. Some of the slickest proposals I have seen came from shops that subcontract everything the moment the contract is signed.
You Probably Cannot Spec It Yet, and That Is Normal
An RFP assumes the buyer can fully specify the requirements up front. But if you are buying your first or second website, you genuinely do not know yet what matters: whether you need separate pages per service, what should happen when a form is submitted after hours, whether online booking is worth the complexity. That is not a knock on you; discovering those answers is what a good vendor conversation is for. An RFP freezes your guesses into requirements, then incentivizes vendors to bid exactly to those guesses and change-order you for everything you learn later.
The Process Costs More Than the Project
Write the RFP, field clarifying questions, wait out the deadline, read five proposals, score them, hold finalist calls, negotiate. Realistically that is four to eight weeks and a couple dozen hours of your time before any work begins. Meanwhile the actual build, done well, can take a week. When the procurement process is five times longer than the project, the tool does not fit the job.
The SBA's guidance on hiring contractors and vendors is sensible reading for small purchases generally, and the consistent theme is proportionality: match the diligence to the size and risk of the buy. A small website is a small buy. It deserves real diligence, just not the ceremonial kind.
What to Do Instead: Three Conversations and Fifteen Questions
Here is a process that takes about a week of calendar time and maybe three hours of your attention, and reliably produces a better decision than an RFP.
First, Write One Page, Not Ten
Before talking to anyone, write a single page: what your business does, who your customers are, the main thing you want the website to make happen (calls, bookings, quote requests), three or four sites you like and why, and your rough budget range. Yes, state your budget. Hiding it does not get you a better price; it gets you a week of mutual guessing. This one-pager replaces the entire RFP document.
Then, Have Three Conversations
Pick three vendors. Find them the way you would find a good electrician: ask other business owners whose sites you admire who built them, check whose own portfolio includes businesses your size, look local first. Get on a 30-minute call with each, send your one-pager ahead, and use the fifteen questions below.
Three is the right number. One gives you no comparison. Five gives you diminishing returns and scheduling fatigue. Three gives you contrast on price, communication style, and approach, which is everything you need.
The Fifteen Questions
Ownership and control:
- Will the domain be registered in my name, with me as the owner?
- Do I get owner access to my own Google accounts, like Search Console and my Business Profile?
- If we part ways in two years, what exactly do I walk away with, and what does leaving cost?
- Is the site built on a platform I could have someone else maintain, or is it proprietary to you?
The work itself:
- Can you show me two or three sites you built for businesses like mine, and can I call one of those owners?
- Who actually does the work, you, your team, or subcontractors?
- What do you need from me, and what happens if I am slow getting it to you?
- How do you handle the writing? Do I draft it, do you, or do we do it together?
Money and timeline:
- What is the total first-year cost, build plus hosting plus everything, with no category left out?
- What does month 13 cost? What is the ongoing monthly number once the build is paid?
- How long from kickoff to live, and what is your track record of hitting that?
- What is included afterward, and what is billed extra? Updates, fixes, content changes?
Aftercare:
- What does your monthly reporting look like? Can I see a real (redacted) example?
- How do content updates work after launch, and how fast do they happen?
- When something breaks on a Saturday, what is the actual process and response time?
You will notice none of these ask the vendor to make promises about rankings. Be suspicious of anyone who volunteers guarantees there; we covered why in our post on reading your monthly SEO report, and the ownership questions echo our piece on firing your web company cleanly, because the time to prevent a hostage situation is before you sign, not after.
Then Decide on Three Signals
After three calls, the decision usually makes itself. Weight these:
- Clarity of answers. Did they answer question 9 and 10 with actual numbers, or with "it depends" followed by fog? Vendors communicate during the sale the way they will communicate during the project, except slightly better.
- Proof over promises. Real sites, for real businesses your size, with owners you can call.
- Ownership posture. Anyone who hedged on questions 1 through 4 is disqualified, regardless of price. That hedge is the expensive part of a cheap quote.
Sleep on it once, pick one, and start. Total elapsed time: about a week.
When an RFP Does Make Sense
The answer is not never. A formal RFP earns its overhead when:
- The budget is large. Once a web project crosses into the tens of thousands, like a custom web application, e-commerce with complex integrations, or a multi-site rebuild, vendor proposal effort is justified by the prize, and the comparison genuinely requires written technical detail.
- You are required to. Government entities, many nonprofits, and grant-funded organizations have procurement rules. If your funding or bylaws mandate competitive bids, run the RFP, and use the fifteen questions above as your evaluation criteria so the rubric measures the right things.
- Requirements are genuinely complex and known. If you can specify integrations, compliance needs, and data migrations precisely, because you have done this before, an RFP communicates that efficiently to qualified bidders.
- Multiple stakeholders must sign off. When a board needs a documented, defensible process, paper has political value beyond its information value.
Notice what all four have in common: scale, obligation, or genuine complexity. A five-page site for a service business has none of the three. When in doubt, the proportionality test settles it: if writing the RFP would take longer than building the website, skip the RFP.
The Bottom Line
Rigor is good. Ceremony is not rigor. For a small website project, three structured conversations with the fifteen questions above will tell you more than five proposals ever could, in a fifth of the time, while keeping the good shops in your candidate pool instead of filtering them out.
Or Skip the Search Entirely
Here is how we answer our own fifteen questions: we build done-with-you websites live on a call with you, first draft in 24 hours, live in 7 days, guaranteed. Your domain and accounts are yours from day one. Quarterly content refreshes and a monthly plain-English report are built into every tier, so questions 13 through 15 are already handled.
Tiers start at $500, with pay-in-4 and Klarna available. Veteran-owned, based in Wilmington, NC, with 1,500+ small business sites built in the last 90 days, including portfolio clients like Air Support HVAC, Sano Steam, and Ramar Transportation whose owners can tell you how it went.
Book a call, bring the fifteen questions, and see pricing before you do.