Before we quote a small business website, we send a short questionnaire rather than jumping straight to a call. It forces the client to think about content before design, which is usually where projects go sideways, and it's saved us from more scope surprises than any contract clause we've ever written.
Why we stopped starting with a call
Our early process was a phone call first, a proposal second. The problem was that most first calls with a prospective client are heavy on enthusiasm and light on specifics, "we want something modern, clean, professional" tells us almost nothing actionable, and by the time we'd built a proposal around vague impressions, half of it needed rewriting once actual content requirements surfaced.
Sending a written questionnaire first forces a different kind of thinking. Answering "how many pages, roughly" in writing makes a client actually count their services, their team members, their locations, in a way that a phone conversation rarely does. We get fewer proposals rejected for being wrong about scope, and the ones that do need revision need smaller revisions.
What we ask
- How many pages, roughly, and what's on each one? Not final copy, just a rough sketch: "About page with team bios," "Services page listing our four main offerings."
- Do you have a logo and brand colors already, or do we need to help with that? This alone changes the proposal significantly, brand work is a different scope of engagement than working from existing assets.
- Who is going to update the site after launch, and how comfortable are they with a browser-based editor? A client expecting to personally update a blog weekly needs a genuinely different setup than one who'll call us for every change.
- Any existing domain and hosting, or are we setting that up too? Surprisingly often the answer involves an old host nobody remembers the login for, which is its own can of worms worth surfacing early rather than during a launch week scramble.
- Do you have photos of your business, products, or team, or will we need stock photography? This one alone has changed several proposals' pricing meaningfully.
- Is there a competitor or similar business whose site you like the feel of? Not to copy, but as a fast way to calibrate what "modern and clean" actually means to this particular client, since it means something different to everyone.
Half the value isn't the answers
Filling it out makes the client realize how much content they still need to write, well before a contract is signed, which is exactly when you want that realization to happen rather than three weeks into a project when a homepage is designed and waiting on copy that doesn't exist yet.
We've had a couple of prospective clients go quiet after receiving the questionnaire, which initially felt like a bad sign, fewer leads converting. In retrospect, it's mostly filtered out the clients who weren't actually ready to commit to the project yet, which is a better outcome for both sides than starting a contract with someone who disappears for six weeks mid-project because they haven't sorted out their own content.
What it changed about our proposals
Proposals built off questionnaire answers are noticeably more specific than the ones we used to write off a single call. Instead of "5-page brochure website," we can write "5-page brochure website: Home, About with 3 team bios, Services listing 4 offerings with individual detail sections, Portfolio gallery with filterable categories, Contact page with embedded map," each line item tied to something the client actually told us they need.
That specificity cuts both ways, it's also made a few clients realize during the questionnaire stage that they wanted more than a basic brochure site, a blog section, an email signup, a simple product catalog, things that changed the proposal's scope before either side had invested time in a mismatched quote.
Tracking how well it's actually working
We started keeping a rough informal log this year of which projects came through the questionnaire process versus the handful that skipped it for one reason or another, a referral from an existing client who wanted to move fast, mostly. The pattern held up under a small sample: projects that went through the full questionnaire before a proposal was written needed noticeably fewer scope revisions once work started, and none of them hit the kind of "wait, I thought that page was included" conversation that used to happen a few times a year before we adopted this process.
That's not a rigorous study, we're talking about a handful of projects either way, but it's enough evidence for us to keep defaulting to the questionnaire even when a client seems eager to skip straight to a call, gently insisting on it rather than treating "the client seems busy" as a reason to shortcut our own process.
Sending it at the right moment
Timing matters more than we expected. Sending the questionnaire immediately after a first inquiry email, before any real conversation has happened, sometimes reads as impersonal, like we're trying to avoid talking to them. We've settled on a short reply first, acknowledging the inquiry and asking one or two clarifying questions in plain conversational language, then sending the full questionnaire once there's already a bit of rapport established. The content of the questionnaire hasn't changed, but leading with a human reply first instead of a form has noticeably improved how many prospective clients actually complete it rather than going quiet.
We're still tuning exactly how long to wait before that follow-up form goes out, somewhere between a day and three days seems to be the sweet spot from what we've seen so far, long enough to not feel automated, short enough that momentum from the initial inquiry hasn't faded.
Tailoring it by business type
We've started keeping two or three variants of the base questionnaire depending on the kind of business asking. A restaurant client gets extra questions about menu update frequency and whether they need online ordering or just a static menu PDF. A local service business, plumbers, contractors, the kind of client who mostly wants to be found and trusted, gets more questions about service area and reviews or testimonials they already have. A retail-adjacent client gets asked earlier and more directly about whether "a few products showcased" is actually code for "we want to sell online," since that's a fundamentally different project than a brochure site with photos.
This branching adds a bit of overhead to maintain, we're now keeping three documents instead of one, but it means the first round of answers is more relevant to the actual project rather than generic enough to apply to any small business, which was a real problem with our original one-size-fits-all version.
What we do with a blank or vague answer
Not every client answers thoroughly. Some questionnaires come back with one-word answers or a "not sure yet" on half the questions. We don't treat that as a red flag by itself, plenty of good clients are simply busy or genuinely haven't thought that far ahead yet. What we do instead is turn the vague answers into specific follow-up questions on the kickoff call rather than guessing at scope and hoping we guessed right.
The genuinely bad sign isn't a vague answer, it's silence entirely, no response after a reasonable follow-up. That's usually the client who wasn't actually ready to start a project, and we've learned to let those go rather than chasing them with reminder emails that rarely lead anywhere productive.
A caveat worth naming
The questionnaire isn't a substitute for the actual kickoff conversation, it's a better starting point for one. We still have a call after reviewing answers, but it's now a conversation about specifics, "you said four services, walk me through what makes each one different," rather than a conversation trying to extract basic scope information from scratch. The quality of that call has gone up noticeably since we stopped trying to do content discovery and rapport-building in the same thirty minutes.
We keep iterating on the questionnaire itself too, dropping questions that never produced useful answers, adding new ones when a project surprise reveals a gap. It's not a fixed document, more a living checklist of the things that have burned us before when we didn't ask up front.