From client message to estimate: a working AI workflow

Why a "simple website" is not yet a scope of work

Imagine a message: "Need a website for a bike shop: services, prices, photos, and booking." The word "booking" could mean a link to a messenger, a request form, or a calendar with available slots. These are three different scopes. Starting code generation before clarification is a risk of building something the person isn't willing to pay for.

Below is a training scenario that you can replicate in your own project. AI helps structure the request; you determine the time estimate, price, and promises to the client.

Step 1. Gather facts, and turn gaps into questions

Remove phone numbers, private correspondence, and unnecessary personal data from the input message. Pass only the job description. Ask to separate requirements from assumptions.

Turn the following client request into a draft scope of work in Ukrainian. 1. List only explicitly stated requirements. 2. Separately list assumptions and questions that affect the price. 3. For each task, suggest a verifiable acceptance criterion. 4. Separate one-time development from hosting, domain, and support. 5. Do not invent prices, hours, client consent, or functions they did not ask for. 6. End with an "out of scope" list for approval. Client request: [insert text cleared of personal data]

For a bike shop, it's worth clarifying: who provides photos and texts; how requests will be received; whether price editing is needed; how many languages; what constitutes a finished result. Confirm answers before estimating. Turn "mobile-friendly" into a check: the menu opens, the number is clickable, the form shows errors and confirmation.

Step 2. Estimate the work yourself

Open free Vibe Brief. Transfer the agreed list and replace demonstration hours with your own. Do not ask the AI to guess your hourly rate, and do not treat its estimate as a contractor's commitment.

This is an arithmetic example, not a recommended market price. Hosting, domains, taxes, and external services must be accounted for separately. Explain the buffer to the client: it does not mean unlimited revisions.

Step 3. Agree on the base and show the price of changes

Save the initial version. Suppose a new FAQ appears, which you estimate at an additional three hours. At the same rate and buffer, this is 2,070 UAH. The new total is 20,010 UAH. If 8,970 UAH has already been received, the remaining balance is 11,040 UAH. The down payment should not be reset when the scope changes.

Vibe-Brief calculates these amounts based on your data. Clicking "fix the base" does not itself mean the client has agreed to the price. Send a separate explanation of the changes and get their response through the usual channels.

Step 4. Transfer the agreed scope into AI tasks

Keep the result, criteria, and exclusions in one document. Break the implementation into short, verifiable steps. For example: first the page structure, then the form, then the mobile scenario. After each step, open the result yourself rather than relying on the agent's "all done" message.

What to give the client and what to keep for yourself

The client document should contain clear work items, the amount, timelines, and terms. Keep internal hours, rates, and service notes separate. The tool's JSON copy contains working estimates — do not send it instead of a proposal. Before sending, open the actual exported file and proofread it.

Check before the next step

• Every task has an acceptance criterion.
• It is noted what is not included and who provides the materials.
• Calculation verified manually, received payment saved.
• The client document does not contain internal notes.
• Additional work does not start based solely on an AI assumption.

This is an editorial original scenario using a demo example. For further work — checking AI responses and a guide about first services.