Set up a client project you can hand over

Agree what “finished” means

List the pages and formats you will deliver, who supplies copy and images, who approves the work and which accounts the client will own. Define the revision rounds and how a new request changes time or price. Put a named owner and acceptance check beside each deliverable.

For the example website, the home, service and contact pages must contain approved content, work on the agreed devices and pass the agreed form test. Design source files, deployment access and a handoff note are separate deliverables if the contract includes them. A payment milestone should point to a reviewable result.

Use a workspace the client can enter

Begin with one project folder, a short work list and a decision log. Give the approver one place to find the current version and one deadline for consolidated feedback. Record the decision and the resulting change so a chat comment does not silently become an agreed scope increase.

Google Drive documents Viewer, Commenter and Editor roles for My Drive files. Choose the role that fits the client’s job, then verify access from their account; organization and folder settings can affect sharing. See Google Drive: file sharing. Do not rely on a screenshot from the owner’s session.

Figma is a design candidate, Notion can be investigated for project documentation, and Linear for a work queue. A separate Slack workspace is optional when your existing communication and decision log already work. Compare the client’s access and export needs before adding seats.

Keep approval, invoicing and delivery connected

1. Collect: track missing copy, images, rights and access before production begins.
2. Review: share a labelled version with the acceptance checklist. Ask the named approver to resolve conflicting feedback.
3. Record: write down what was approved and which changes remain. Confirm new scope before starting it.
4. Invoice: use the agreed milestone and reconcile payment in the provider’s records rather than treating an email or screenshot as proof.
5. Handoff: deliver the promised files, account access, recovery instructions and any maintenance responsibilities.

Stripe’s hosted invoice page lets customers view the invoice, pay through enabled methods and download invoice or receipt PDFs. See Stripe: hosted invoice page. Check the fees, currency and payment methods for your business before choosing it.

Rehearse the handoff before launch

The client opens the review link

Their own account can see the correct version and leave the intended kind of feedback without gaining unnecessary edit access.

Two people request incompatible changes

The named approver chooses one decision, which is recorded against the deliverable.

The client asks for an extra page

The change has an agreed owner, acceptance check and scope adjustment before work begins.

You are unavailable next week

The client can access the agreed source files, domain and hosting records and follow the recovery note.

The project ends

Temporary collaborator access can be removed without taking away the client’s ownership or breaking the delivered site.

Keep the operating cost visible

Separate your delivery fee from recurring client costs such as domain, hosting, email and paid seats. Record who pays each bill, who receives renewal notices and what happens when a subscription ends. Use client-owned accounts where the handoff requires them.

Fewertools’ workflow test records show limited, documented exercises; they do not prove an entire agency stack. Run this delivery path with your actual permissions and exports before committing to a client.