FAQ
Pricing
How much does Handoff Wizard cost?
A single handover is $15,000 (Tier 1). For organizations forecasting 5+ departures a year, Tier 2 is $50,000/year for up to 10 handovers. Enterprise / PE-portfolio pricing is $150-300k/year for unlimited coverage. Pricing is per-departure-event, not per-seat.
The full pricing rationale lives at handoffwiz.com/pricing.
What does the $15k include?
The full two-week wizard engagement, the 16-doc synthesis pipeline, the 35-question gold validation gate, NotebookLM Enterprise delivery into your GCP, a 30-min walkthrough call with the successor, and 30 days of post-delivery Q&A access.
Do you offer refunds?
Yes — the standard contract has a 50% refund clause if the gold validation gate doesn’t pass after extended work and both sides agree to abandon. We’d rather keep working at no extra cost until pass; the refund is a backstop, not a strategy. Full terms are in the MSA.
Data handling
What happens to my source data?
Source files stay on your laptop. AI calls go to your Anthropic API key. Synthesis lands in your employer’s GCP NotebookLM Enterprise tenant. Handoff’s infrastructure stores only licensing metadata, anonymized telemetry, and crash reports — no content.
Full architecture writeup at handoffwiz.com/security.
Is Handoff SOC 2 / GDPR / CCPA compliant?
- SOC 2: Type I targeted Q2 2027, Type II Q4 2027 / Q1 2028. For 2026, the BYO-key architecture means we hold no customer content; most enterprise buyers accept this for departure-event scope.
- GDPR + CCPA: Yes. Customer data is customer-controlled (BYO architecture); Handoff is a Processor for licensing metadata only. EU customers get a Standard Contractual Clauses addendum.
- HIPAA / PHI: Not the horizontal product. PHI requires Handoff Wizard MD — a separate product on a separate HIPAA-eligible deployment.
Will Handoff sign a DPA?
Yes. Email legal@handoffwiz.com. The DPA is also a downloadable PDF at handoffwiz.com/security.
BYO API keys
Why do I need my own Anthropic key?
So that your Anthropic account is billed for the inference, your account holds the conversation logs (per Anthropic’s data retention policy), and Handoff never sees your prompts or outputs. This is a deliberate architectural choice — not a cost-shifting move. (Per-handover Anthropic spend is roughly $40-80, well under our $15k handover price.)
What if my employer doesn’t have an Anthropic account?
Either you create one with your personal email (then expense the $40-80 spend), or your employer creates a workspace-scoped key. The Anthropic console at console.anthropic.com is straightforward — provisioning takes <10 minutes. If your employer hits an enterprise-procurement wall, email support@handoffwiz.com for an alternate path.
Can I use OpenAI / Gemini / a self-hosted model instead?
Not in v1. Claude was chosen because synthesis quality at the 16-doc / 35-question scale is reliable starting with Claude 3.5 Sonnet. OpenAI Assistants and Gemini support are on the v1.5 roadmap.
GCP + NotebookLM
Why NotebookLM Enterprise specifically?
It’s where your successor will read the knowledge base. NotebookLM Enterprise gives them grounded, citation-backed Q&A out of the box — no separate vector DB, no separate UI build, no separate authentication. It’s roughly $9/user/month (Google Cloud listing), much cheaper than Glean.
What if my employer doesn’t have NotebookLM Enterprise?
Your employer’s IT person provisions it during kickoff. With an existing GCP account, it takes under a day. Without one, budget 2-3 days for GCP account setup + NotebookLM enrollment.
We help with this in the kickoff call. If your employer is M365-shop and balks at “we have to use Google?”, they typically provision a thin GCP project specifically for the post-handover KB — that’s the most common pattern. Most enterprise IT teams accept it.
What about NotebookLM (free tier) — same thing?
No. The free tier doesn’t support service-account authentication, has lower content limits, and lacks the Enterprise admin controls (audit logs, IAM, retention). We only ship to NotebookLM Enterprise in v1.
After the handover
Who has access to the published knowledge base?
Whoever your employer’s GCP admin grants access to. Typically: the successor, the successor’s manager, and 1-2 cross-functional teammates. Handoff doesn’t gate access — the published notebook lives in your employer’s GCP, governed by their IAM. Most employers grant read access for ≥1 year.
How long do I (the departing employee) have access?
The desktop app stays installed for 30 days post-publish to support clarifying-question pings from your successor through the in-app chat. After 30 days the app self-uninstalls and your access ends.
What if I leave the project mid-handover?
You’ll have completed onboarding, some interviews, and possibly some files. Your employer’s admin can resume the handover from where you left off — usually by reassigning the project code to a co-worker who shadows your role. The app preserves all approved sessions and ingested files.
If the handover can’t be completed (e.g. abrupt termination), the 50% refund clause in the MSA applies.
How long does a typical handover take?
Calendar: two weeks. Active work: about 6 hours of your time spread across 30-45 minute interview blocks plus 30 minutes of file intake plus an hour of draft review and validation. Most departing operators do their work in the last hour of each day during their notice period.
Roadmap
Multi-employee handovers — when?
Deferred to v1.5. v1 is one departing employee → one notebook. Multi-employee (e.g. an entire team turning over) is on the v1.5 roadmap once we’ve shipped enough single-employee handovers to validate the synthesis pipeline at scale.
Mobile / web / Linux versions {#linux}
Deferred. v1 is Windows + macOS desktop only. Web is on the roadmap (v1.5+), mobile is unlikely (the work is keyboard-heavy), Linux is targeted for v1.5.
Custom archetypes {#archetypes}
v1.5+. v1 ships only the Operations archetype. v1.5 adds Sales, Customer Success, and Engineering / Tech. v2 ships a YAML-template authoring SDK so customers can define custom archetypes (industry-specific, function-specific). If you have a unique role and need to ship sooner, email support@handoffwiz.com — we may be able to accommodate as a paid customization.
Customer support SLA
During the 2-week engagement: same-day response during US business hours, often within an hour. Post-delivery (during the 30-day Q&A window): next-business-day response. After the 30-day window expires, support is out of scope — your employer’s admin can re-engage us via the admin dashboard.
Anything else?
If you have a question that isn’t here, email support@handoffwiz.com or check the Troubleshooting page. We update this FAQ monthly based on what customers ask.