IMAXBELOV START A PROJECT

RESEARCH NOTE / 02 · AUGUST 2026

The unfinished brief: designing a better first website inquiry.

A client should not need a finished site map, budget model or technical vocabulary before they can ask a capable person for help.

The hidden work inside a generic form

“Tell us about your project” appears simple. For someone starting from zero, it can be the most difficult field on the site. It asks them to diagnose the problem, decide what details matter and translate uncertainty into professional language before they know who will read it.

The result is often silence, not because the visitor lacks a real need, but because the site has made formulation a prerequisite for conversation.

A first inquiry has one job

The goal is not to collect a complete specification. It is to gather enough information for a thoughtful human reply. A good first inquiry lets the client state the situation in plain language, then creates a clear route to the next conversation.

  • Who is asking?
  • What is the easiest reliable way to reply?
  • Is there an existing company or website to review?
  • What does the person want to create, change or solve?

Use choices as prompts, not gates

A small optional selector can reduce the pressure of an empty text field. It should help a visitor name a direction, not force them to select a product before they understand the problem.

  • Launch a website from scratch
  • Improve an existing website
  • Solve one specific problem
  • I am not sure yet; I would like to discuss it

None of these is a contract, a scope or a price tier. They simply give the client permission to begin where they are.

What not to ask too early

Budget, exact deadlines, page counts, platform preferences and a detailed feature list can become useful later. At the first contact, they can be misleading: a person may guess just to complete the form, and the resulting answer can distort the conversation.

Ask an early question only when the answer changes the immediate next action. Otherwise, let an actual conversation discover it.

Set a truthful expectation after submit

The confirmation should explain the next state without inventing a promise: the request is received, it will be reviewed personally and the response will suggest the appropriate next step. That is more credible than a countdown or a guaranteed result the studio cannot control.

Practical test

Before publishing a contact form, read it as a person who has no website and no technical language. Can they complete it in a few minutes using only what they already know? If not, the form is qualifying the client’s ability to write a brief—not the actual opportunity to help them.

RESEARCH BASIS

Related study

This note applies the “choice,” “context” and “handoff” layers from the public-interface study of 30 premium service journeys. It does not claim measured conversion results.

PROJECT START

Need a website that lets people begin without a perfect brief?

A useful first step can be a clear contact path, a focused page improvement or an audit of the current journey.

Start a conversation