Signals specific to web design

Look for launch deadlines, requests for design partners, outdated information architecture, unusable mobile flows or a website that cannot support a new offer. These signals differ from technical incident repair and traffic acquisition.

A complaint about low conversions may concern pricing, demand or copy rather than design. Ask what users are expected to do and where the current journey fails.

Scope the inputs

InputQualification question
Business outcomeWhat decision or action should the site support?
Pages and contentWho supplies and approves the copy?
Brand assetsIs identity established or part of the work?
PlatformWhat must remain connected?
Review processWho approves and how many stakeholders participate?
LaunchWhat date is real and what depends on it?

These questions reduce the risk of quoting a visual task that actually includes strategy, content and integrations.

A useful first response

Hypothetical request: a consultancy needs a booking-focused site before an event. Ask whether its offer, copy and booking tool are ready. Explain how these inputs affect the scope and timeline.

If service replies are permitted, offer a bounded scope review. Do not promise delivery before reviewing dependencies.

Evaluate lead quality

Track whether the buyer has a coherent outcome, compatible scope and a feasible approval process. Record rejected leads such as unsupported platforms, impossible deadlines or requests for unpaid speculative design.

Use those reasons to refine discovery language. A request containing “website” is not automatically a design project.