Example
How to leave a freelance client cleanly when the work no longer fits
A good relationship can still occupy the wrong future. Noah must complete a dated handoff, offer a shorter transition, or end at the current term after inventorying what is owed and what the actual agreement permits.
End the retainer with honest notice, complete artifacts, and no invented emergency
Purpose, boundaries, and the definition of enough
Hold the mission and boundary: end the retainer with honest notice, complete artifacts, and no invented emergency
The decision and preparation that deserve attention next
Hold the live choice—whether to offer a shorter transition retainer, name a final date, or refer the client immediately—so Noah can decide from the evidence in this Room
Draft a notice that names the chosen handoff path, final responsibility, and date
Draft one question about homepage approval and a separate question about the final invoice
Mark each source package ready, incomplete, or needing a client question before promising a handoff
The visible proof behind the plan—not a vague feeling of readiness
Inventory the logo source, page layouts, design-system files, and invoice state without assuming client approval
Name the source package Noah must transfer
Separate approved layouts from work that may require a client question
Record the reusable component source included in the handoff
Determine the current state before treating payment or acceptance as Replies and outside conditions
Record the actual notice period and deliverables promised in the agreement
Name what Noah wants to preserve without letting goodwill choose the exit path
Show which higher-value work the recurring requests interrupt
In You.one’s Superboard view, the Clean client exit Board separates the closing promise, handoff packages, approval and invoice evidence, client replies only after sending, and work genuinely transferred.
Open Full handoff, short transition, or term end as the consequential Card Room. Start by inventorying source files, open approvals, access, and invoice state without assuming client acceptance.
After an explicit request, Ava can organize the visible inventory or draft language Noah reviews. Ava cannot interpret the contract, contact the client, transfer access, invoice, or accept terms; Noah and the client retain authority.
Clean client exit has one live choice: Transition, final date, or referral
The mission is specific: End the retainer with honest notice, complete artifacts, and no invented emergency.
The consequential choice is not something a board or an AI should quietly make: Whether to offer a shorter transition retainer, name a final date, or refer the client immediately.
You.one can keep the work, evidence, and “Transition, final date, or referral” decision visible through its Superboard view. Authority does not move to the software: Noah chooses transition, a final date, or referral and owns the notice, source-file map, and deliverables he promised. The client owns whether a transition, final date, referral, homepage copy, or final invoice is accepted.
Available today
Clean client exit: the working map
The Clean client exit Board gives this mission one durable operating picture. Noah can use familiar language instead of translating the situation into project-management jargon. Its three Lists separate the kinds of attention this situation actually requires.
The Lists separate what Noah can move now, what is evidence, what is already waiting on a named person or event, and what still needs a decision.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Exit promise | Purpose, boundaries, and the definition of enough |
| Handoff work | The decision and preparation that deserve attention next |
| Account evidence | The visible proof behind the plan—not a vague feeling of readiness |
Available today
Open one decision: Transition, final date, or referral
Opening the Card gives the visible item durable depth. Stage can hold Exit-path brief: Place contract terms, logo source, page layouts, design-system files, homepage-copy approval, final invoice, relationship value, and capacity cost together. Live choice: Whether to offer a shorter transition retainer, name a final date, or refer the client immediately. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Noah will decide whether to offer a shorter transition retainer, name a final date, or refer the client immediately.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Transition, final date, or referral” from the visible evidence. Ava can work from the context Noah deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Noah's call remains explicit: Noah chooses transition, a final date, or referral and owns the notice, source-file map, and deliverables he promised. The client owns whether a transition, final date, referral, homepage copy, or final invoice is accepted.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Exit-path brief: Place contract terms, logo source, page layouts, design-system files, homepage-copy approval, final invoice, relationship value, and capacity cost together. Live choice: Whether to offer a shorter transition retainer, name a final date, or refer the client immediately |
| Chat | Keep Noah's request and Ava's attributed response with the work |
| Pulse | Open decision: Noah will decide whether to offer a shorter transition retainer, name a final date, or refer the client immediately |
Useful Ava requests, with the boundary intact
These requests stay with the facts Noah has made visible around “Transition, final date, or referral.” Noah supplies the evidence, checks Ava's work, and decides what belongs in the Room.
Current Ava can prepare help after an explicit request. She cannot make the choice, represent Noah, watch other work on her own, or contact anyone.
Noah chooses transition, a final date, or referral and owns the notice, source-file map, and deliverables he promised. The client owns whether a transition, final date, referral, homepage copy, or final invoice is accepted. Ava compares only evidence in the choice Card Room and does not contact anyone or decide.
Noah finishes “Mark each source package ready, incomplete, or requiring a client question,” keeps “Logo source, page layouts, design-system files, and final invoice” beside “Transition, final date, or referral,” and does not treat “Draft separate homepage-approval and final-invoice questions” as completed or sent before doing the work.
- Request idea: using only this Card Room and the Exit-path brief, compare a short transition, a final date, and a referral. Treat homepage approval and final-invoice state as unknown until Noah verifies them. Do not send a notice, message the client, invent urgency, or choose.
- Request idea: use only the Exit-path brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Transition, final date, or referral,” show which visible fact could reverse the current choice
The limit of an offboarding email draft
An offboarding email draft can be enough while the situation stays simple: “Draft the notice” and “Draft separate homepage-approval and final-invoice questions” no longer change the “Transition, final date, or referral” choice.
It starts to break when “Logo source, page layouts, design-system files, and final invoice” and “Draft separate homepage-approval and final-invoice questions” must inform the same choice.
The Clean client exit Board earns its place only when the familiar tool—an offboarding email draft—can no longer keep the reason, Exit-path brief, conversation, current state, decision, and history connected.
A practical way to start the Clean client exit Board
Noah should rename every List or Card that feels artificial. This recipe succeeds when “Transition, final date, or referral” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
Swipe or scroll sideways to see every column.
| Step | Action |
|---|---|
| 1. Inventory the handoff | Mark logo, layouts, design-system source, and invoice ready, incomplete, or unknown |
| 2. Read the real agreement | Put notice terms and promised deliverables beside the source-file map |
| 3. Choose the exit path | Compare transition, final date, and referral before writing the notice |
| 4. Draft separate client questions | Do not collapse homepage approval and invoice state into one ask |
| 5. Transition, final date, or referral | Name the selected path, final responsibility, artifacts, and date |
Where this example stops
- This is a fictional example, not a customer story.
- This fictional example is not legal, contractual, tax, or client-relationship advice; the freelancer reviews the actual agreement and owns every communication.
- It does not show Ava completing external actions or contacting anyone for Noah.
- It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.