Web designers · Worked example

A website client workflow from brief to delivery

Fictional worked scenario: designer Avery and client Rowan plan a five-page website for an invented repair studio, Northline. Names, dates and amounts are illustrative. This is a practical walkthrough, not a customer story or measured result. Ordinary documents and delivered files use the parties’ existing tools.

The point where work gets scattered

Rowan wants a clearer website but has not separated the launch essentials from a later booking idea. Avery needs a specific first phase, a client input list and a way to handle changes without losing the conversation.

1. Turn the conversation into a concrete brief

Rowan’s opening request is ‘a modern website with easier enquiries.’ Avery asks which services matter, who supplies the content and what must be ready for launch. The first-phase list becomes Home, Services, About, Work and Contact. Rowan supplies approved copy and photographs, and is the contact who collects the team’s feedback.

The open booking idea remains a question, not a hidden commitment. A useful review message is: ‘This brief covers five pages and an enquiry form. Do you need online booking at launch, or should I price it as a separate option?’ Avery uses only the selected brief and relevant conversation when preparing a scope outline.

2. Review the scope and the initial payment separately

The ordinary proposal describes the five pages, two consolidated design review rounds, client content responsibilities and exclusions. In this scenario the reviewed price is $3,000 USD, with a $900 initial payment and later payments defined in the parties’ working terms. They inspect the exact document version through their existing agreement process.

Only then does Avery prepare the initial payment request: ‘Please review the $900 payment toward Northline website W-104. After confirmation and receipt of the approved copy, we can confirm kickoff.’ Rowan checks the recipient and amount in the payment experience. Avery inspects the confirmed result; a draft request or a funding step is not reported as a received payment.

3. Resolve a new request before building it

During design review, Rowan asks for a booking page. Avery compares it with the five-page scope and identifies it as additional work. The proposed change adds a booking page and setup of one appointment offer for $450, moving the delivery date by four days if Rowan supplies the offer details on time.

Avery offers two choices: keep the original launch scope or review change C-01 with the revised $3,450 total. Rowan’s choice is recorded through their existing scope and agreement process. The production checklist changes only after that decision. If Rowan does not accept the addition, the five-page scope remains the reference rather than a vague memory of the request.

4. Ask for feedback on the named version

Avery sends Homepage v2 with three questions: is the service description accurate, are the priorities in the right order and is any essential information missing? Rowan collects one team response. Avery distinguishes corrections to the promised work from suggestions for new pages, then summarizes the edits planned for v3.

When a live review is useful, they choose a real available time and inspect the confirmed appointment, including timezone and duration. The meeting is used to decide the remaining page-order question. It does not silently approve a new price or replace the review of the actual scope change.

5. Hand over what is actually ready

Avery checks the delivered site and files against the accepted scope plus C-01. The handover index names the pages, operating notes, access invitations and open issues. Rowan opens the site and accepts the account invitation through the approved process. Credentials are not pasted into a public message.

The closing record distinguishes delivered work, client inspection and confirmed payments. Missing items stay visible until resolved. A later maintenance request becomes a new discussion with its own scope rather than an assumed extension of the website project.

  • Current scope and accepted changes are identifiable.
  • Payment results match their project and purpose.
  • Actual deliverables and access are inspected.
  • The next support or maintenance decision is explicit.

Keep the context with the conversation

Messages can help prepare wording from chosen client context. Calendar supports a reviewed appointment, and the payment path supports payer approval and a confirmed result. Business and a configured Twin can help continue the relationship. Keep the ordinary documents and delivered files in your established process, with clear references in the conversation.

Understand your Twin · See Business access and metered AI usage

The next conversation starts with context.

Keep the messages and records you choose close to the next question. Prepare useful wording with your Twin, review it, and decide what happens next.

Try a client relationship in Messages ↗

Open your own Bankeiz Messages ↗

Messages remain available without Business. Twin assistance uses confirmed access and metered AI usage. Sending, booking and payment retain their own review.