Priced like the problem: a ramp, not a subscription trap.
A new person takes about three months to find their feet. Solo covers exactly that — the capture, then the successor chat through the ramp. Keep it after that for less than a coffee a day, or cancel and take your KB with you.
- · Passive observation of email/Slack (Team)
- · OAuth integrations (Team)
- · Custom retention or EU residency (Enterprise)
- · Microsoft 365 OAuth (Enterprise)
- · SSO / SAML (Enterprise)
- · EU data residency (Enterprise)
The graceful exit, in writing: cancel anytime after month 3, and your Role KB exports with you. No hostages.
Things buyers actually ask, answered straight.
Why monthly instead of a one-time fee?
Because the product isn't the interview — it's the three months your new person spends asking the predecessor questions. A one-time fee would end the relationship on the day the capture compiles, which is exactly when the successor starts needing it. $99/mo for the ramp, $49/mo after if you want the knowledge to stay on tap. Cancel after month 3 and export everything.
What happens after the three months?
Nothing dramatic. The plan continues at $49/mo — the KB stays hosted, the successor chat stays live, and anyone on your team can keep asking it questions. Most teams keep it because month 4 is when the weird edge cases start. If you cancel, you get the full Role KB as Markdown + JSON. It's your asset, not ours.
What's the real difference between Solo and Team in terms of output quality?
Solo's Role KB is built from interview transcripts only. Team adds passive observation (with consent) of email, calendar, and Slack — which catches the muscle-memory workflows the employee forgets to mention. In the demo, "Sarah" had Team-level capture. Solo will produce 60-75% of that depth. Good for many roles. Not enough for highly relational or interrupt-driven roles (sales ops, executive assistant) — start those at Team.
What happens if the AI's Role KB isn't good enough?
We run a Turing test before handover. The departing employee writes 20-25 hard role-specific questions, both they and the AI answer them, and they grade both. Target match rate: 85%+. If we don't hit it, we iterate the extraction at our cost. If we still don't hit it within 7 days, we refund everything you've paid on Solo, prorated on Team.
Do I need to involve IT?
Solo: no. The employee runs interviews through our web app, period. Team: yes for the OAuth setup (Gmail or Slack admin needs to approve our scoped read-only app). Takes 15 minutes. Enterprise: full security review, but we provide the pack.
How long does a capture actually take?
From signup to handover-ready: typically the employee's notice period. Two weeks works. Four weeks is ideal. We've completed captures in 7 days when notice was short.
What about the people I never want this on — confidential roles, departing under bad terms, etc.?
Voluntary on the employee side, always. They sign the consent or it doesn't run. You also can't legally force this in most jurisdictions, and we won't enable workflows that try to. For bad-departure cases, we recommend running the capture earlier — before the offboarding becomes adversarial.
Still deciding? Talk to Sarah first.
Sarah is a fictional finance manager we built to show what talking to a captured colleague feels like. Ask her anything. Then come back and pick a tier.
Open the demo