Example
How to run a sales territory plan without confusing a long list with a week
Brett’s CRM marks everything next, but Thursday cannot hold two cities and a custom demo. He must lead with the Gulf Coast renewal, the Bayou renewal, or the strategic demo, then place the other conversations on days the route can actually reach.
Give this week a true route: renewals that bill, travel that fits, and logo work that does not silently cancel paying accounts
This week’s miles and the paying-account rule
Keep travel and billing accounts beside the exciting logo
Renewals and live customers
Hold a conversation that actually bills this quarter
Show the second billing conversation competing for Thursday
Logos and demos that are not yet revenue
Keep a strategic maybe from occupying the only Thursday
Days, cities, and drive time
Compare one-city Thursday routes led by the Gulf Coast renewal, the Bayou renewal, or the custom demo
Show a geography fact the CRM stage cannot see
The sent product-team demo-support request
Keep Brett’s sent support request from counting as confirmed help
The Territory week Board separates paying accounts, pursuits, the route, and the product-team reply that remains outside Brett’s control.
Open Choose Thursday’s job as a Room with a Week-route brief for three one-city paths.
Ava can compare visible route and account facts. Brett owns customer and product-team conversations, pricing, discounts, forecasting, and travel; Ava does not email, book, promise, or forecast.
Next is not a plan; miles are a constraint
The work has a clear center: Give this week a true route: renewals that bill, travel that fits, and logo work that does not silently cancel paying accounts.
Organizing the evidence does not authorize the software to decide: Whether Thursday goes to the Gulf Coast renewal, the Bayou renewal, or the custom demo while the other two conversations move to days and cities the route can actually reach.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Choose Thursday’s job” decision visible through its Superboard view. Brett still owns the call: Brett chooses the week, talks to customers, and owns every promise and discount.
Available today
Name the work in plain language
These Card titles come directly from Brett's situation: “Choose Thursday’s job” is the live choice, “Renewal: Gulf Coast fabricator” holds evidence, and “Product team demo-support reply” names something genuinely in motion outside Brett's control. The point is recognition, not a perfect taxonomy.
Swipe or scroll sideways to see every column.
| Card | List | Job |
|---|---|---|
| Miles and paying accounts first | Mission | Keep travel and billing accounts beside the exciting logo |
| Choose Thursday’s job | Route | Compare one-city Thursday routes led by the Gulf Coast renewal, the Bayou renewal, or the custom demo |
| Renewal: Gulf Coast fabricator | Paying accounts | Hold a conversation that actually bills this quarter |
| Renewal: Bayou packaging group | Paying accounts | Show the second billing conversation competing for Thursday |
| 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 reply | Replies and outside conditions | Keep Brett’s sent support request from counting as confirmed help |
Available today
Territory week: separate the kinds of attention
The Territory week Board gives this mission one durable operating picture. Brett can use familiar language instead of translating the situation into project-management jargon. Its five Lists separate the kinds of attention this situation actually requires.
The Lists use Brett's own language so actions, evidence, open questions, and decisions do not collapse into one queue. A separate place for replies is useful only after Brett has asked someone or a real outside event must happen first.
Swipe or scroll sideways to see every column.
| 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 |
| Replies and outside conditions | The sent product-team demo-support request |
Ask Ava to prepare the judgment—not make it
These requests stay with the facts Brett has made visible around “Choose Thursday’s job.” Brett 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 Brett, watch other work on her own, or contact anyone.
Brett owns customer conversations, product-team follow-up, pricing, and travel. Ava does not email accounts or the product team, treat demo support as confirmed, book travel, or forecast a number.
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: using only the context visible in this Card Room, compare a one-city Thursday led by the Gulf Coast renewal, the Bayou renewal, or the custom demo, and name where the other two conversations move. Do not email customers or the product team, treat demo support as confirmed, or choose for me.
- Request idea: use only the Week-route brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Choose Thursday’s job,” group the visible evidence by option and leave the decision open
Available today
One Card Room for the consequential choice
Opening the Card gives the visible item durable depth. Stage can hold Week-route brief: Place miles, both billing renewals, the custom demo, and three one-city Thursday routes on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Brett will choose what Thursday is for.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose Thursday’s job” from the visible evidence. Ava can work from the context Brett deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Brett's call remains explicit: Brett chooses the week, talks to customers, and owns every promise and discount.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Week-route brief: Place miles, both billing renewals, the custom demo, and three one-city Thursday routes on one page |
| Chat | Keep Brett's request and Ava's attributed response with the work |
| Pulse | Open decision: Brett will choose what Thursday is for |
Build only enough Board to make the next decision
Brett should rename every List or Card that feels artificial. This recipe succeeds when “Choose Thursday’s job” 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. 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 Replies and outside conditions |
| 5. Choose one city for Thursday | Open “Choose Thursday’s job” and record the Owner's city choice before placing the other conversations |
Where this example stops
- This is a fictional example, not a customer story.
- 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.