Use cases
Six kinds of week,one next step for every person.
Each one follows a remote team through its week, from the first prepped card to the fix that stops the problem coming back. People and numbers are examples.
Async teams · managers who run them without status meetings
Replace the status meeting
No hour works for everyone, so status comes from the work. The team view shows each card’s owner and status, and a recap lands every Friday.
RunYour weekly recap is ready.
BuildCut review turnaround from 3 days to 1.
See the use case
Managers of remote teams · and the people who need a hand
Spot stuck work early
Stuck work is quiet on a remote team. See how long each card has waited and how often it’s been skipped, and step in early.
RunSam has skipped the API migration card 3 times.
BuildSplit large cards into steps under 4 hours.
See the use case
Managers of remote teams · and the people they hand work to
Delegate without losing context
Delegate a card with its prep, a note and a due date. It lands ready to act on in any time zone, and the result comes back as a card.
RunSandpiper’s project plan is due Thursday.
BuildPut current estimates in the project template.
See the use case
Managers of remote teams · and everyone whose feed they shape
Know which fire matters
Set a few team priorities, and every feed ranks by urgency, impact and fit, so the right fire gets put out first.
RunHalden’s renewal is in 9 days, with 3 open escalations.
BuildGive every renewal-risk escalation a named owner.
See the use case
Client-service teams · account leads and the people who deliver
Keep client work moving
Client emails and scope changes land with the account lead who owns them, with the thread, the timeline and a reply drafted.
RunLarkin & Co. asked for 3 more landing pages.
BuildOffer retainers to repeat clients.
See the use case
Teams that bill by the hour · managers and the people who log time
Bill every hour to a task
People log time on the card they’re working, so every hour you bill traces to a specific card for a specific client.
RunBuild the Larkin pricing page.
BuildRe-estimate design tasks from logged time.
See the use case
The same loop, every time
Handle it now.Then fix what keeps causing it.
Every use case runs through the same four steps, whoever owns the work.
- A signal landsA client emails, a deadline moves, a card waits too long.
- A prepped cardRanked, routed to its owner, and prepped with a draft.
- A person actsAct, delegate with a note, or skip for now.
- Fix the sourceRepeat fires become a Build move with steps.
Pick the onethat sounds like your week.
Join the waitlist and we’ll email you the day it opens.
In pre-launch · Free plan planned for up to 3 people · Every integration included