Example
How to run a sales territory plan without confusing a long list with a week
Brett's problem is not a lack of effort. It is that Give this week a true route: renewals that bill, travel that fits, and logo work that does not silently cancel paying accounts has outgrown scattered reminders, tabs, and memory. This fictional playbook shows a concrete Board, the Cards inside it, one consequential Room, and the line Ava does not cross.
This fictional example was created with AI assistance from a structured editorial brief and reviewed by the You.one Editorial Team for usefulness, distinctness, and product truth.
Brett is an explicitly fictional portrait, not a customer or testimonial.
The Territory week Board gives one mission a visible field; the Choose Thursday’s job Room keeps its evidence, conversation, state, and decision together.
Current Superboard provides the durable structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Brett's pressure is ordinary—and still heavy
Brett is a fictional 35-year-old account executive covering a regional territory in Houston, Texas. Brett has a CRM full of accounts, a week of driving, and a strategic logo that wants a custom demo. Two existing customers need renewal conversations. The CRM says the week is full because everything is marked next.
Brett can talk to people. If the custom demo and two renewals all sit on Thursday in different cities, the CRM will still look busy while the week fails.
CRM stages, a maps list, and a product-team demo request do not share a Thursday.
A logo chase is exciting and would postpone a renewal that actually bills this quarter.
Next is not a plan; miles are a constraint
The mission is specific: Give this week a true route: renewals that bill, travel that fits, and logo work that does not silently cancel paying accounts
The consequential choice is not something a board or an AI should quietly make: Whether to protect Thursday for renewals, split the week and delay the custom demo, or pause one renewal to chase the logo
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Brett still owns the purpose, tradeoff, and final call.
Available today
Territory week: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Brett does not have to convert life into project-management jargon or decide the perfect taxonomy first. Lists separate kinds of attention; Cards keep each meaningful item visible and movable.
The Cards are deliberately mixed. Some are tasks, some are decisions, some hold a person or promise, and some are reference points. Current Superboard supports that flexibility without flattening the mission into one long to-do list.
| List | What belongs here |
|---|---|
| Mission | This week’s miles and the paying-account rule |
| Paying accounts | Renewals and live customers |
| Pursuits | Logos and demos that are not yet revenue |
| Route | Days, cities, and drive time |
| Waiting | Demo support and customer replies |
Available today
The Cards make the operating picture concrete
A Board becomes useful when the Card titles sound like the actual situation. These are not generic placeholders; they show what Brett would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Miles and paying accounts first | Mission | Keep travel and billing accounts beside the exciting logo |
| Choose Thursday’s job | Route | Compare renewals-first, split-week, and pause-renewal-for-logo options |
| Renewal: Gulf Coast fabricator | Paying accounts | Hold a conversation that actually bills this quarter |
| Logo chase: custom demo ask | Pursuits | Keep a strategic maybe from occupying the only Thursday |
| Thursday cannot be two cities | Route | Show a geography fact the CRM stage cannot see |
| Product team demo support | Waiting | Park an unconfirmed helper so the demo is not assumed ready |
Available today
Available today: Choose Thursday’s job becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Week-route brief: Place miles, billing renewals, and renewals / split / logo options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Brett to choose what Thursday is for. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare protecting Thursday for renewals, splitting the week, and pausing a renewal for the logo. Do not email customers or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported context and can make limited reversible product changes. She does not deeply reason over the whole Board by default, and she does not gain authority over the decision merely because the context is organized.
Brett's call remains explicit: Brett chooses the week, talks to customers, and owns every promise and discount
| Surface | Job in this example |
|---|---|
| Stage | Week-route brief: Place miles, billing renewals, and renewals / split / logo options on one page |
| Chat | Keep Brett's request and Ava's attributed response with the work |
| Pulse | Waiting for Brett to choose what Thursday is for |
| Activity | Preserve attributed Card changes and the supported record around the request |
What to ask Ava—and what not to assume
These are useful requests to adapt, not claims that current Ava automatically surveys the whole Board, prepares every comparison, or follows up on her own. The relevant facts must be present in supported Board/Card context, and the human still checks the result.
Brett owns customer conversations, pricing, and travel. Ava does not email accounts, book travel, or forecast a number.
The modest outcome is not that Ava lives Brett's life. The modest outcome is a week that can be driven: Thursday has a job, a billing renewal is not hiding under a logo, and next is no longer a pile.
- Request idea: summarize paying accounts, pursuits, and route constraints already on the Board
- Request idea: compare Thursday options using miles and billing dates Brett captured
- Request idea: help keep unconfirmed demo support in Waiting
A CRM where everything is next may still be enough
A CRM where everything is next is enough when the week is in one city
It starts to break when two renewals, a custom demo, and two cities all claim Thursday
Superboard earns a place only when the responsibility needs a durable picture around the list: the reason, artifact, conversation, current state, decision, and history.
A starter recipe to adapt, not obey
Use the names that already make sense in Brett's world. The recipe is successful when the Board reduces remembering and exposes the real decision—not when every Card is perfectly categorized.
| Step | Action |
|---|---|
| 1. Write the week’s miles | Geography is a constraint |
| 2. Lift paying accounts | Renewals that bill this quarter |
| 3. Keep pursuits separate | Logos are not yet revenue |
| 4. Park unconfirmed help | Demo support in Waiting |
| 5. Choose Thursday | Open a Room before the CRM fills the car |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when two Route Cards share a day in different cities, still leaving every trip with Brett.
The unified You.one and Superboard runtime, cross-product personalized Memory Spine, broad proactive coordination, realtime shared editing, and general external execution are not available today. Future actions would still require the applicable capability, connection, grant, and human authority.
What this realistic example does not claim
- Brett is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not a sales-forecast or quota claim.
- It does not show Ava emailing customers or booking travel.
- It is not a measured revenue result.