Example
How a cleaning service can grow without breaking the Thursday crew
Imani can sell more work. Selling Thursday work into a full van is how a regular house gets a rushed hour and a cleaner quits.
Add work only on days the crew and van can actually support, while keeping Thursday residential stops honest
Crew hours, van, and the days that are already full
Keep van and crew hours beside the appetite for new accounts
Each day’s houses and travel
Show travel and hours that are already spoken for
Mark actual unused capacity
Cleaners’ real hours, including reduced ones
Keep a real constraint from being treated as a full headcount
New work not yet on a route
Compare decline, Tuesday offer, and drop-farthest-stop options
Hold the constraint the client named instead of wishing it were Tuesday
Imani is an explicitly fictional portrait, not a customer or testimonial.
The Crew and routes Board gives one mission a visible field; the Choose the commercial Thursday ask Room keeps its evidence, conversation, state, and decision together.
Current You.one provides the Superboard structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Why Crew and routes needs an operating picture
Imani is a fictional 41-year-old owner of a four-person residential cleaning service in Windsor, Ontario. Imani has a full Thursday route, a commercial inquiry that wants Thursdays, and one cleaner on reduced hours after a family change. Reviews are fine. The constraint is the van and the hours, not marketing.
A booking inbox, a paper route sheet, and a payroll notebook do not agree on Thursday hours.
The commercial inquiry would pay more per hour and still collide with five residential stops that already trust the team.
In You.one's Superboard view, Imani can give “Add work only on days the crew and van can actually support, while keeping Thursday residential stops honest” a Board of its own. That Board connects customer promises, operating evidence, capacity, and the owner's judgment; opening “Choose the commercial Thursday ask” creates a Room for its evidence, discussion, state, and decision.
A new account that lands on the full day is not growth
The mission is specific: Add work only on days the crew and van can actually support, while keeping Thursday residential stops honest.
The consequential choice is not something a board or an AI should quietly make: Whether to decline the Thursday commercial job, offer them Tuesday, or split Thursday by dropping the farthest residential stop.
You.one can keep the work, several kinds of evidence, and “Choose the commercial Thursday ask” decision visible through its Superboard view. The Owner boundary stays explicit: Imani chooses the account, talks to clients and crew, and owns scheduling and pay.
Available today
Crew and routes: one Board shape to adapt
The Crew and routes Board gives this mission one durable operating picture. Imani can use familiar language instead of translating the situation into project-management jargon. Its four Lists separate the kinds of attention this situation actually requires.
Its Cards deliberately distinguish actions, multiple kinds of evidence, and decisions. A Waiting List would be premature until a named request or outside condition is actually in motion. That separation makes the current choice, evidence, and next move easier to scan.
| List | What belongs here |
|---|---|
| Mission | Crew hours, van, and the days that are already full |
| Routes | Each day’s houses and travel |
| People | Cleaners’ real hours, including reduced ones |
| Inquiries | New work not yet on a route |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Imani's situation: “Choose the commercial Thursday ask” is the live choice, while “Thursday route: five houses” and “Commercial inquiry: Thursday only” hold different facts that can change it. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Grow into empty hours, not Thursday | Mission | Keep van and crew hours beside the appetite for new accounts |
| Choose the commercial Thursday ask | Inquiries | Compare decline, Tuesday offer, and drop-farthest-stop options |
| Thursday route: five houses | Routes | Show travel and hours that are already spoken for |
| Cleaner on reduced hours | People | Keep a real constraint from being treated as a full headcount |
| Commercial inquiry: Thursday only | Inquiries | Hold the constraint the client named instead of wishing it were Tuesday |
| Tuesday opening after noon | Routes | Mark actual unused capacity |
Available today
Available today: Choose the commercial Thursday ask becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Growth-path brief: Place Thursday hours, reduced crew, and decline / Tuesday / drop-stop options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Imani will choose whether Thursday can take new work.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Growth-path brief and this Card Room's visible notes and left “Choose the commercial Thursday ask” with Imani.”
A useful Card Chat request would be: “Using only the context visible in this Card Room, compare declining the Thursday job, offering Tuesday, and dropping the farthest stop. Do not contact the client or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. She does not gain authority over the decision merely because the context is organized.
Imani's call remains explicit: Imani chooses the account, talks to clients and crew, and owns scheduling and pay.
| Surface | Job in this example |
|---|---|
| Stage | Growth-path brief: Place Thursday hours, reduced crew, and decline / Tuesday / drop-stop options on one page |
| Chat | Keep Imani's request and Ava's attributed response with the work |
| Pulse | Open decision: Imani will choose whether Thursday can take new work |
| Activity | Ava compared the options in Card Chat using the Growth-path brief and this Card Room's visible notes and left “Choose the commercial Thursday ask” with Imani |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Choose the commercial Thursday ask” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Imani must provide the relevant facts and check the result.
Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Imani, watch other Lists, or act outside this Card Room.
Imani owns pricing, hiring, and client conversations. Ava does not schedule crew, message clients, or handle payroll.
Growth that fits hours: Thursday stays honest, Tuesday’s opening is visible, and the commercial ask is a chosen path.
- Request idea: using only the context visible in this Card Room, compare declining the Thursday job, offering Tuesday, and dropping the farthest stop. Do not contact the client or choose for me.
- Request idea: use only the Growth-path brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously
A paper route sheet plus an inbox may still be enough
A paper route sheet plus an inbox is enough when the crew is full-time and days are even.
It starts to break when a reduced-hour cleaner and a Thursday-only inquiry share a van.
The Crew and routes Board earns its place only when the familiar tool—a paper route sheet plus an inbox—can no longer keep the reason, Growth-path brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Imani should rename every List or Card that feels artificial. This recipe succeeds when “Choose the commercial Thursday ask” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. Mark full days | Thursday as a constraint, not a sales target |
| 2. Card real hours | Reduced hours are not a full person |
| 3. Keep inquiries off the route | Until a day is chosen |
| 4. Show empty capacity | Tuesday after noon as a fact |
| 5. Choose the commercial Thursday ask | Open a Room before a better rate overwrites regulars |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when an inquiry Card wants a day already marked full, still leaving every yes with Imani.
A future unified You.one experience could carry relevant context from “Choose the commercial Thursday ask” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action would still require the applicable capability, connection, grant, and human authority.
What this realistic example does not claim
- Imani is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not employment, tax, or insurance advice.
- It does not show Ava messaging clients or scheduling crew.
- It is not a measured growth result.