For new hires
Ask the question you'd feel
silly asking twice.
In your first month everything is new: the acronyms, who owns which system, where the real docs are, why things work the way they do. Asking the same teammate a fifth time feels bad, so you guess.
Sound familiar?
The docs are out of date
The onboarding doc says to use a tool the team stopped using last year.
You don't know who to ask
There's a person who owns billing, a person who owns the release process, and nobody told you who.
The “why” is missing
You can see what the team does, but not why, so every decision looks arbitrary.
Questions you can ask
In plain English, in Slack or in the web app. Every answer links to where it came from.
- “What does “QBR” mean here and who runs them?”
- “Who owns the release process, and how do I get something into the next release?”
- “Why do we use two different ticket systems?”
- “What should I read first to understand our biggest customer?”
What it reads
SlackNotion or ConfluenceGoogle Drive & DocsJira or LinearGitHub (engineers)Google Calendar
How to start
- Your team connects its sources once; you just log in.
- Ask in Slack or in the web app, any time, as often as you like.
- Click the source on every answer to read the real doc, not a summary of a summary.
Also for: Sales · Support · HR & ops · Founders.
Want this for your team?
We are letting teams in from the waitlist in small batches. One email when your invite is ready, nothing else.