Withose for chiefs of staff
You are the institutional memory. That should worry you.
A chief of staff's unwritten job description: remember what was decided, who agreed to it, and why, across every leadership conversation in the company. When the CEO asks in October what was agreed in March, you are the search engine. When two VPs relitigate a settled question, you are the referee with no written ruling to point at.
Withose turns that memory into a system. When a decision surfaces in Slack or Microsoft Teams, capture it in place: AI drafts the decision record from the actual conversation, the stakeholders you name are asked to state their position, and the finalized record lands in a searchable archive that new decisions are automatically checked against for contradictions.
Decisions relitigated because nobody wrote them down
The question was settled in a thread four months ago, but the thread is unfindable and half the people in the new debate were not in it. A finalized Withose record ends the rematch: here is what was decided, when, by whom, and what each stakeholder said.
"Who actually agreed to this?"
Silence in a channel is not agreement, but it gets treated as agreement until something breaks. Withose asks each named stakeholder to record support, opposition, or a neutral stance with their reasoning, so the record shows who weighed in and who never did.
Exec asks, you excavate
Instead of scrolling Slack history at 11pm reconstructing a rationale, you search the archive. Each record carries the question, options considered, positions, the AI synthesis, and the outcome, plus a ready-to-paste announcement when it is time to tell everyone.
New leaders inherit no context
A new VP's first months are spent asking why things are the way they are. An archive of finalized decisions with reasoning is the onboarding document you never had time to write.
A week in practice
- 1Monday: leadership debates moving the London office in a Slack thread. You type /withose and the draft decision record appears, built from the thread.
- 2Tuesday: the CFO and Head of People get weigh-in links by email. Neither needs a Withose account, and neither needs to be in the Slack channel.
- 3Wednesday: positions are in. The AI synthesis lays out the agreement, the one open risk, and a recommendation.
- 4Thursday: you finalize. Withose flags that this contradicts a decision from February about lease renewal, so you resolve that on the record instead of discovering it in Q4.
- 5Friday: you paste the auto-drafted announcement into #general and set a 90-day revisit reminder. Total added process: minutes.
Common questions
Do executives need accounts for me to use this?
No. Stakeholders weigh in through an email link with no account and no seat cost. You can run Withose usefully as a small number of seats plus account-free stakeholders around them.
Does Withose read all of our Slack or Teams messages?
No. It has no access to your message history and no event stream. Messages reach Withose only when someone explicitly captures a specific conversation, and captured content is encrypted at rest with your workspace's own key.
How is this different from keeping a decision log in Notion?
A Notion log depends on someone re-typing the decision after the fact, which is exactly the step that gets skipped. Withose drafts the record from the conversation itself, chases the stakeholders for you, and checks new decisions against the archive for contradictions.
Also see Withose for operations leaders and product teams, how it works in Slack and in Microsoft Teams, or pricing.
See it work before you sign up for anything.
The playground runs the whole flow on sample data: capture, stakeholder positions, AI synthesis, and a finalized record. No account needed.
Every new workspace starts with a free 7-day Team trial. No card required.