"Hi, we need a new website, what would it cost?"
The enquiry form asks for name, email and a message. The message says the business needs a new website, the current one is dated, and could the studio give a rough price. The owner books a call, asks the usual questions, takes notes on a pad, and writes a proposal.
Halfway through the project it emerges that the current site has hundreds of blog posts that need moving, the booking system is a bespoke tool with no API, and the final approver is a board that meets monthly. None of this came up on the call because the owner did not think to ask and the client did not think it mattered.
Why the scope arrives late
- Clients describe what they want, not what they have, so the current site's complexity is invisible.
- Discovery calls follow the conversation, and important questions get skipped.
- Notes are handwritten or in the owner's head, so they cannot be reviewed later.
- Budget and deadline are awkward to ask, so they are left vague.
- Decision makers and approval processes only become clear once the project starts.
Proposals are only as good as what the studio knew when writing them. Most of what matters is simply never asked in a structured way.
What late scope costs
Projects are underquoted because major work was unknown. The studio spends time on calls and proposals for prospects who were never going to fit the budget. Disputes start early when the client assumes something was included that was never discussed. The owner's time, which is usually the scarcest in a small studio, goes on repeating the same questions.
The discovery questionnaire we build
- The enquiry form leads to a short questionnaire that adapts to the answers, so an e-commerce business sees questions about products and payments, and a service firm sees questions about bookings and lead forms.
- Questions cover what the business does, the current site and platform, pages and content to keep, integrations such as CRM, booking or payments, who writes content, who approves, deadline and budget range.
- The prospect's current site is crawled automatically: number of pages and posts, platform, forms, third-party tools detected and obvious technical issues.
- The answers and the crawl are combined into a one-page summary for the owner, with gaps and risks highlighted, such as a large blog to migrate or a system with no known API.
- The summary feeds your estimator and proposal template, so components are pre-selected.
- Prospects who are clearly outside your range, by budget or type of work, can be sent a polite, honest reply rather than booked in for a call.
| Question area | Why it matters for scope |
|---|---|
| Current site size and platform | Migration and redirects effort |
| Integrations | Often the biggest unknown |
| Who writes content | Content entry and chasing time |
| Approvers | Number of revision rounds |
| Deadline | Whether it is realistic at all |
| Budget range | Whether to propose at all |
The questionnaire informs the call. It does not replace talking to the client, which is still where you judge the fit.
A discovery call that starts informed
The prospect completes the questionnaire. Before the call, the owner sees that the current site has a large blog, uses a booking provider with an API, and that approval sits with a board. The call is spent on the questions that matter and on building rapport, not on basic facts. The proposal includes migration and a realistic approval schedule from the start.
Do your proposals start from too little?
- Enquiries arrive with very little information.
- Important scope often emerges after the project starts.
- Discovery calls cover different ground each time.
- Budget and deadline are left vague until the proposal.
- The owner spends a lot of time on prospects who do not fit.