Start where you are. Grow when you need to.

Things buyers actually ask, answered straight.

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, full refund on Solo, prorated refund on Team.

Can I export the Role KB if I cancel?

Yes. The Role KB is your asset, not ours. Export as Markdown + JSON on demand, any tier. We're a processor; you're the controller.

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.