The Web Design RFP.

Most Tucson business owners approach hiring a web designer the same way they'd approach buying a car: they describe what they want, collect quotes, and pick the number in the middle. That process selects for the best salesperson, not the best web designer. It also routinely produces the outcome people complain about most: a site that looks different from what was discussed, delivered late, with no explanation of what's missing and no clear answer about who's responsible for what comes next.

A well-constructed RFP — request for proposal — changes that. It forces you to define what you actually need before you start talking to vendors. It creates a structured basis for comparison. And it reveals, through how firms respond, more about their process and communication style than any sales call will. This guide is useful to anyone shopping for a web design firm, including people not hiring us. The framework is honest, and if you use it, you'll make a better hiring decision regardless of who you choose.

01What an RFP is and when to use one.

1.1What is a web design RFP and is it worth the effort for a small Tucson business?

An RFP (Request for Proposal) is a structured document you send to prospective vendors that describes your project, asks specific questions, and requests a formal response with pricing, methodology, and timeline. In the enterprise context, RFPs are lengthy formal documents. For a small Tucson business, a useful web design RFP is 2–4 pages — concise enough that serious firms will engage with it, thorough enough that lazy firms will respond with a generic quote that doesn't answer the questions.

The question of whether it's worth the effort depends on your budget and stakes. If you're investing $3,000 or more in a website, an RFP process pays for itself in the first bad proposal it helps you avoid. If you're doing a quick $500 portfolio site update, a phone call is sufficient. For anything representing meaningful investment in your business's primary marketing channel, the discipline of an RFP is worth it.

1.2Is an RFP different from just getting multiple quotes?

Yes — and the difference is important. Getting multiple quotes means calling three firms and describing your project verbally. Each firm will interpret what you said differently, propose different scopes, price entirely different things, and produce proposals that are impossible to compare apples-to-apples. An RFP gives all three firms the same document — the same project description, the same questions to answer, the same evaluation criteria. When you compare responses to a written RFP, you're comparing responses to the same stimulus. You can see, directly, who answered your actual questions and who sent a template.

1.3How many firms should I send an RFP to?

Three to five is the practical range for a small business web project. Fewer than three and you don't have enough comparison points. More than five and the evaluation effort exceeds the value — and serious firms sometimes decline to respond to large RFP distributions because the odds of winning are low. If you have a rough sense of which type of firm you want (local and boutique, vs. regional with a larger team, vs. national), narrow the list to firms that fit that profile and send to three in each category you're considering. Quality of the shortlist matters more than its length.

1.4Should I tell firms what my budget is?

Yes. This is counterintuitive for a lot of buyers — the instinct is to withhold the budget so firms don't just "fill up" to the maximum. But withholding the budget produces three problems: (1) firms scope very differently without a number, making proposals impossible to compare; (2) you waste time evaluating elaborate $15K proposals when your budget is $5K; (3) good firms that could serve you well may submit budgets outside your range because they don't know what you're working with. The better approach: give a realistic budget range and ask firms to show you what they'd deliver within it. Then evaluate whether the delivered scope matches your needs. A firm that's honest about what's not included at your budget is more valuable than one that overpromises.

02Defining your project scope before you send anything.

2.1What do I need to define before writing the RFP?

Before the document is written, you need clear answers to six questions:

• What is the primary purpose of the site? Lead generation, e-commerce, appointment booking, credibility/portfolio, information resource — or a combination. The answer shapes every design and technical decision.
• Who is the target visitor and what action do you want them to take? A HVAC company website wants a visitor to call or fill out a form. A law firm wants them to schedule a consultation. The primary conversion action determines the site's information architecture.
• What does success look like, and how will you measure it? More leads, lower bounce rate, better Google rankings, faster load time — name the metrics you'll use to evaluate whether the site is doing its job.
• What is your content situation? Do you have existing copy and images, or will the firm be expected to produce them? This is a major cost driver that many buyers don't realize until they get the first invoice.
• What is your real timeline? Not "as soon as possible," but an actual date by which the site needs to be live — and why that date matters.
• What is your actual budget? Not the number you're willing to tell vendors, but the number you can actually spend, including post-launch maintenance and hosting.

2.2How do I figure out how many pages my site actually needs?

Start with function, not aesthetics. Every service you offer should have its own page — not because of SEO (though that helps), but because a visitor looking for one specific service shouldn't have to read about all your other services to find what they need. Your homepage, about page, and contact page are table stakes. Any service with enough complexity to warrant explanation gets its own page. If you have service areas (Tucson, Marana, Oro Valley), each area gets a page. If you have a blog or resource section planned, count it as a content type, not individual pages. A Tucson home services business with five services and three service areas is looking at roughly 15–20 pages for a complete site. A dental practice might be 10–12. A web design firm might be 30+ if they're building topical content depth.

2.3Should I specify a platform (WordPress, Webflow, Squarespace) in the RFP?

If you have strong reasons for a preference, state it. If you don't, leave it open and ask each firm to justify their platform recommendation. Platform choice affects: editing experience (who manages the site long-term and how technically capable are they?), portability (can you move the site if you change firms?), extensibility (what do you want to add in two years — e-commerce, booking, automation?), and total cost of ownership (hosting, maintenance, updates). A firm that recommends Squarespace for a service business that needs strong local SEO is telling you something about their SEO knowledge. A firm that recommends a custom-coded static site for a client who needs to add blog posts weekly is telling you something about their understanding of your content workflow.

2.4What existing assets should I inventory before writing the RFP?

Domain name (do you own it and control the registrar login?), current hosting (who hosts your site and do you have access?), current site files and content (do you have a backup?), existing brand assets (logo files in vector format, brand guidelines if they exist), content (existing copywritten pages, product descriptions, photos), and integrations (CRM, booking system, payment processor, email marketing platform). Knowing what you have changes what the firm needs to produce — and catches the common scenario where a business owner doesn't control their own domain or hosting and has to negotiate to get it back from a previous vendor.

2.5How do I write a project description that's specific without locking in a wrong solution?

Describe the problem you need solved, not the solution you assume you need. "I need a five-page website" is a solution assumption. "I'm a Tucson HVAC company that gets most leads from Google but can't tell if our website is helping or hurting — we need a site that converts searchers into phone calls and loads fast on mobile" is a problem description. The second version gives a competent firm the information to propose the right solution. It also filters out firms that will just build the five pages without asking whether that's actually the right scope. Invite each firm to push back on your assumptions in their proposal — the ones that do are telling you they read it carefully and think about the problem, not just the deliverable.

03What to include in your RFP document.

3.1What are the essential sections of a web design RFP?

A functional web design RFP for a Tucson small business has six sections:

• Project overview — 1 paragraph describing your business, the purpose of the project, and the problem you're solving
• Scope and requirements — page count estimate, functionality requirements (forms, e-commerce, booking, blog), platform preferences if any, content situation
• Goals and success metrics — what does a successful site look like 90 days after launch
• Timeline — launch target date and any hard deadlines (trade shows, seasonal peaks, funding announcements)
• Budget — your range, and whether it includes content creation, photography, SEO, hosting, or post-launch maintenance
• Questions for the firm — specific questions each respondent must answer (see 3.2)

3.2What questions should the RFP require every firm to answer?

These are the questions that separate serious firms from order-takers. Ask every respondent to answer all of them:

• Show us two or three client sites similar to ours — walk us through what you built, what the client's goal was, and what happened after launch.
• What platform will you build on and why is it the right choice for this project specifically?
• What's your approval process? At what stages do we review and sign off before the next phase begins?
• How do you handle schema markup, page speed, and on-page SEO? What does your technical SEO deliverable look like at launch?
• What does post-launch support look like? What's included and for how long? What's the billing model after the maintenance period ends?
• Who specifically will be working on this project — designer, developer, copywriter — and can we talk to them before signing?
• What's your communication cadence during a project? How do we reach you if something is wrong?
• What happens if the project goes over timeline? Over budget? What's the escalation path?

3.3Should I include wireframes or design direction in the RFP?

If you have strong brand guidelines or visual direction, include them — it helps firms scope accurately and respond with relevant portfolio work. If you don't, describe the feeling you're going for and three or four website examples you admire — not "I want a site like this," but "I like the editorial restraint of this site's typography, and the way this site organizes its services." This gives firms creative direction without pre-determining a solution. What you should not do is include a wireframe of what you think the homepage should look like. That immediately makes every firm try to design what you drew, rather than what your visitors need — and it prevents you from learning anything from their design thinking.

3.4What response format should I ask for?

Ask for: a written response to each of your listed questions (not a sales deck with generic bullet points), a project proposal that describes what they will deliver, in what phases, with what client responsibilities at each phase, a detailed timeline with milestones, a pricing breakdown that separates design, development, content, and post-launch maintenance, and one or two portfolio examples with a brief explanation of relevance to your project. Set a maximum length — five to eight pages of written content is more than sufficient. A firm that sends a 40-page PDF of case studies and logos without answering your specific questions is telling you something about how carefully they'll read your project brief during the actual work.

3.5How should I evaluate firms that ask clarifying questions before responding?

This is a green flag. A firm that asks three or four specific, intelligent questions before submitting a proposal has read your RFP carefully and is trying to scope accurately. A firm that asks "what's your budget?" (after you've already included it) hasn't read it carefully. A firm that asks "what CRM do you use and do you need the contact form to integrate with it?" is thinking about your actual workflow. The quality of a firm's clarifying questions is one of the most reliable signals of the quality of their discovery process — which is the first and most important phase of any web project.

04Evaluating proposals — what to look for and what to ignore.

4.1How do I compare proposals that have very different scopes and pricing?

First, normalize them. Build a comparison matrix: list each RFP requirement down the left column (homepage, X service pages, contact form, SEO setup, mobile optimization, schema markup, accessibility, post-launch support), and put each firm in a column to the right. Mark what's included, excluded, and optional at an add-on cost. This normalizes proposals that look very different at first glance — often because one firm included content writing and another assumed you'd provide it, or one included three months of maintenance and another stopped at launch day. Once the comparison matrix is built, you can evaluate on a like-for-like basis: price per included deliverable, not total price tag.

4.2What makes a portfolio worth looking at versus one that's just pretty?

Look for three things in a portfolio. First, relevance: have they built sites for businesses similar to yours in industry, size, and complexity? Second, depth: can they explain what problem each site solved, what metrics improved, and what the client outcome was — or do they just show you the homepage? Third, current quality: when did they build each portfolio site? Technology changes fast; a portfolio of sites from 2020 built on Elementor doesn't demonstrate current capability. Ask specifically about load times, accessibility scores, and schema implementation on their portfolio sites. A firm that knows their own portfolio work's Core Web Vitals scores is a firm that cares about performance, not just appearance.

4.3How should I think about price when comparing proposals?

Price is not a quality signal in either direction. We've seen $15,000 sites that perform worse than $4,000 sites, and $4,000 sites that look like $15,000 sites because the firm was efficient. The honest pricing framework: what is the project-specific cost of production (the hours and skill required to build what you need), plus what is the firm's market position (boutique premium, mid-market efficiency, offshore discount). A higher price isn't evidence of quality. A lower price isn't evidence of a deal. The relevant question is: does this firm's process and portfolio suggest they can deliver what they've scoped, at the quality level this project requires, for the price they're quoting? If all three are yes, the price is reasonable. If any one is uncertain, the price is irrelevant until you clarify it.

4.4What should I pay attention to in a discovery call with a shortlisted firm?

Three things. First, how many questions do they ask about your business versus how much time they spend pitching their services? A firm that spends the first 20 minutes of a discovery call describing their portfolio is a firm that leads with selling, not listening. The best discovery calls are mostly them asking you questions. Second, do they push back on any of your assumptions? If you say "I want a five-page site" and they say "that might not be enough for your SEO goals — let me explain why," they're thinking about your outcome. If they just nod and scope five pages, they're filling the order. Third, what happens at the end of the call — do they propose a clear next step, or does it fade into "we'll send something over"? Process and communication during the sales cycle predict process and communication during the project.

4.5Should I hire someone local to Tucson or does location not matter?

For most projects, location matters less than it used to — the work is digital, collaboration happens via Zoom and shared tools, and there's no meaningful advantage to a firm that's geographically close if they don't communicate well. That said, there are real advantages to working with a Tucson firm: they understand the local market, local search landscape, and local business context; they can meet in person if the project needs it; and their reputation in the local market creates accountability that national firms don't have. A national firm that treats you as a small account has no incentive to invest in your success. A local firm whose reputation depends on your satisfaction is structurally more aligned with your goals.

05Contract terms — what protects you.

5.1What contract terms protect the client on a web design project?

The terms that matter most, and what each should say:

• Scope of work — every deliverable should be named specifically. Vague language ("a website with a professional design") gives the firm latitude to deliver the minimum; specific language ("a homepage, five service pages with individual meta titles and descriptions, a contact page with form integration to [specified CRM], and a blog template") is a commitment.
• Intellectual property — upon final payment, all design files, custom code, and content produced for this project become your property. Not licensed to you — owned by you. This is important if you ever change firms.
• Approval gates — explicit language that no phase advances without your written sign-off. Protects you from a firm that delivers the site and then invoices for it before you've approved anything.
• Revision policy — how many rounds of revisions are included at each phase, and what's the cost structure for revisions beyond the included rounds. Protects both parties from scope creep.
• Timeline and penalties — if the firm misses a milestone, what happens? Most contracts don't address this; the better ones have a clear escalation path (written notice, cure period, termination with partial refund).
• Payment schedule — milestone-based payment tied to deliverables (not calendar-based) protects you from paying in full before the work is done.

5.2What payment structure is reasonable for a Tucson web design project?

A fair payment structure for a fixed-scope project: 25–33% at contract signing, 33–40% at design approval (before development begins), and the remainder at project completion. Some firms request 50% up front, which is reasonable for smaller projects where the design and development phases overlap. What you should not agree to: 100% upfront payment for a project over $2,000 from a firm you've never worked with. And what you should not propose: holding all payment until launch — the firm has legitimate production costs that precede launch, and a payment structure that doesn't compensate them during the project creates perverse incentives to rush or cut corners to close the invoice.

5.3What should I know about domain and hosting ownership in the contract?

Your domain and your hosting account must be in your name, controlled by credentials only you have. Not the firm's name. Not the firm's account. Yours. This should be explicit in the contract. The reason: every year, Tucson businesses discover they can't update their website, switch firms, or even access their site because their web designer owns the domain or controls the hosting account. When the relationship ends — for any reason — those businesses are held hostage. A legitimate firm should have no objection to this term. A firm that insists on controlling your domain and hosting is either running a lock-in model by design or hasn't thought through the ownership implications. Either way: it's a problem you should identify before signing.

5.4What is a maintenance agreement and do I need one?

A maintenance agreement is a recurring service contract (usually monthly) that covers WordPress core, theme, and plugin updates; security monitoring and response; uptime monitoring; regular backups; and a set number of hours per month for content updates or minor changes. Whether you need one depends on your capacity. A WordPress site without maintenance is a security liability — plugins go out of date, vulnerabilities get exploited, and an unmaintained site that gets hacked or breaks on a WordPress update can be expensive to recover. If you don't have someone in-house who will actively maintain the site, a maintenance agreement from your web designer is significantly cheaper than emergency recovery work. For a Tucson small business, expect to pay $75–$200 per month for a legitimate maintenance plan.

5.5What recourse do I have if the delivered site doesn't match what was proposed?

Your recourse depends entirely on what's in the contract. A contract with a specific scope of work and explicit approval gates gives you clear grounds to withhold final payment if the deliverable doesn't match the agreed scope. A contract with vague language ("professional website design") gives the firm enormous latitude to define what they delivered as compliant. Before signing: read the scope section carefully, and if anything is described vaguely, ask for specific language. "Mobile responsive design" means something; "looks good on phone" means nothing legally. After signing: document every approval and every change request in writing. Email is sufficient. If a dispute arises, the paper trail of approvals and requests is the most important evidence you have.

06Red flags, due diligence, and making the call.

6.1What are the most reliable red flags in a web design proposal or discovery call?

In order of seriousness:

• No approval process described. A firm that doesn't mention client review and approval at any stage is planning to build the site, then show it to you when it's done. That's the origin story of every "they built something I didn't ask for" complaint.
• Vague deliverables with specific price tags. If the contract says "a beautiful, conversion-focused website" without page count, features, or technical requirements, you're buying ambiguity at a defined price.
• The portfolio looks suspiciously similar to the demo they're showing you. Some firms show a polished demo site and imply they'll build something like it — then deliver a lightly-customized template.
• They can't explain what's not included. A confident, honest firm can tell you exactly what's out of scope and what it would cost to add. A firm that deflects this question doesn't know their own scope.
• They'll own your domain or hosting. Covered above. Non-negotiable.
• Guarantees of specific Google rankings. No firm can guarantee a position. An agency that makes this claim is either using tactics that will eventually hurt you, or planning to collect the retainer without delivering.

6.2How should I check references, and what questions should I ask?

Ask the firm for three client references from projects in the last two years. Contact all three. The questions that matter: Did the project come in on time, and if not, why? Did the final price match the quoted price? Describe a moment when something went wrong during the project — how did the firm handle it? Did the firm communicate proactively or did you have to chase them? Would you hire them again, and has the site performed as expected since launch? The answer to "would you hire them again" is less telling than how they talk about specific problems. A firm that never has problems either has no references telling the truth, or has never done complex work. A firm that had problems and handled them well is the firm you want.

6.3How do I make the final hiring decision when two firms are close?

When scope, price, and portfolio are approximately equal, the decision comes down to communication fit. Which firm communicated more clearly throughout the proposal process? Which one asked better questions? Which one's written responses were more specific, more direct, and better-organized? Communication style during a proposal process is strongly predictive of communication style during a project — because the proposal process is the firm's best behavior. If a firm's best behavior is "getting back to you in five business days with a generic response," their project behavior will be worse. The firm that communicates like a craftsman during the proposal will communicate like a craftsman during the build.

6.4What should the handoff look like at the end of a project?

A complete project handoff includes: access credentials for all accounts (domain registrar, hosting, WordPress admin, Google Analytics, Google Search Console), a brief written documentation of what was built and why key decisions were made, training on the CMS for whoever will manage content, and a clear statement of what's included in any post-launch support period. Some firms also provide a maintenance guide — how to update plugins, how to add a blog post, how to change contact information. A firm that disappears after launch without transferring knowledge or access has delivered a product that may soon become a liability. The handoff is part of the project. It should be in the scope and in the contract.