How to scope an AI-assisted website project
Define what an AI-assisted website quote includes, price the review work, and handle new requests with a practical scope and approval example.
A client sees a website draft appear quickly and asks why the project still needs a meaningful budget. The useful answer is a clear description of the finished work: what you will deliver, what you will check, and who will approve it. An AI-assisted draft changes part of the production process. It does not, by itself, define the scope of the finished website.
Describe a finished result the client can recognize
Start with the same question you would ask on any fixed-fee project: what evidence will show that the work is complete? “Build an AI website” leaves almost everything open. “Deliver a five-page marketing site using the approved page list, with one contact form and two consolidated review rounds” gives both parties something they can inspect.
Name the inputs too. Will the client supply approved copy, product claims and images, or are you researching and editing them? A tool-generated first draft can still require subject-matter review. Make that ownership visible before presenting a timeline. The baseline guide walks through how to turn a broad promise into a defined starting point.
Keep methods separate from acceptance. If a client is buying an agreed result, explain the result and the review process. If they are buying your time, explain how time will be recorded. Do not quietly switch between those two arrangements when a task becomes faster or harder.
- List pages, reusable layouts and supported screen sizes.
- Name the person who approves factual claims and final copy.
- Specify the number of review rounds and what a round contains.
Make verification an explicit work package
Separate initial production from the checks that make the work usable. Your checklist might include keyboard navigation, form delivery, mobile layout, content accuracy and link testing. Choose checks that fit the actual project; a short brochure site and a customer portal do not need identical acceptance criteria.
For an illustrative landing-page addition, assume two hours to assemble a first version, two to integrate approved content, three to test and revise it, and one to prepare the handoff. The total is eight hours. The fact that the first version took only two hours is useful production information, but it is not the total delivery estimate.
Show the client the work categories without turning the quote into a defense of every minute. The goal is a shared understanding of what will be checked and what remains their responsibility. If a requested claim cannot be verified, record that as an unresolved input rather than polishing it into apparent certainty.
Scroll sideways to see all columns.
| Work | Hours | Completion evidence |
|---|---|---|
| First version | 2 | Layout ready for review |
| Content integration | 2 | Approved copy placed |
| Checks and revisions | 3 | Agreed checks completed |
| Handoff | 1 | Owner receives final instructions |
Separate corrections from new decisions
Suppose the approved scope includes a contact form, but the delivered form does not submit. Fixing that is different from a new request to add a customer qualification flow, conditional questions and a CRM connection. Write the distinction in plain language: a correction makes the agreed work function as specified; a change adds or replaces an agreed requirement.
AI-assisted production can produce many options quickly. That makes it tempting to keep exploring after a direction has already been approved. Define when exploration ends and implementation begins. A new visual direction after approval may reopen layout, content and testing work even when generating the initial concept is quick.
Use a change record with the original requirement, the new request and the impact on delivery. If the boundary is ambiguous, discuss it before quoting. A scope document is a conversation aid, not a reason to charge for work you already promised.
- Correction: the delivered behavior fails the agreed acceptance check.
- Change: the client requests an additional behavior or approved direction changes.
- Unclear: pause and compare the request with the written baseline.
Quote the whole addition, including its dependencies
Continuing the illustrative eight-hour example, assume a planning cost of $60 per hour. The estimated delivery cost is $480. A $800 fee would leave $320 before other business expenses, a 40% margin on that fee. These are example inputs, not a suggested market rate. Your costs, uncertainty and commercial arrangement may be different.
Also check whether the addition moves the launch date or waits on someone else. An extra page may require photography, a stakeholder decision or a new navigation item. State the proposed sequence and the assumptions behind it. The scope change calculator can help you inspect the arithmetic before you write the client-facing explanation.
Give the quote an explicit decision: approve the addition, keep the original plan, or exchange a named piece of work for it. Avoid beginning work while the client is still choosing. That is how a helpful exploration turns into an unapproved commitment.
Keep a record that survives the next conversation
Once a choice is made, save the request, the agreed version, the fee and the revised delivery assumption together. A chat message saying “looks good” can be hard to interpret later if several options were discussed. Restate the selected option in one short confirmation and ask the client to acknowledge that version.
Clearcut helps you keep the baseline and additional-work quote together. Its paid account supports client review links tied to a saved quote version; review the recorded response before applying it. It is not a substitute for your contract or an identity-verified signature service. Start with the change order template if you need a clear structure for the next request.
At project close, compare estimated review time with actual review time. That is the useful lesson for the next AI-assisted project: which checks were necessary, where the inputs were incomplete, and which assumptions deserve a clearer line in the next scope.
