Like a physical for
your company.
Walk in, get checked, walk out with a diagnosis. One read-only login. Nine dimensions. 24 hours from connect to IC-ready report.
Five steps. Twenty-four hours.
Zero surveys.
The same end-to-end flow that powers every Zoe diagnostic, in the same order, every time.
Connect
Sign in with Google. One click. We read email metadata and calendar patterns — never message content.
Discover
Zoe detects your tech stack, maps your org structure, and identifies which tools to analyze for the deepest signal.
Diagnose
Nine health dimensions computed from behavioral and financial data. Benchmarked against companies your size, stage, and industry.
Prescribe
Specific findings with root cause analysis. Not "improve communication" — but "Engineering and Product stopped talking directly on December 15."
Monitor
Pulse monitoring tracks changes over time. Know when a dimension drops before it becomes a crisis.
Connect your workspace
Eight weeks of work, in a day.
Traditional operational diligence takes weeks of consultant interviews, internal politics, and a 200-page deck nobody reads. Zoe replaces all of it with one OAuth and 24 hours of background processing.
What happens at each stage.
For every step in the process: what data we collect, what we analyze, what you get back.
Connect
- Google Workspace OAuth (read-only)
- Calendar metadata
- Email metadata (sender/recipient/timestamp only — no content)
- Tech-stack discovery from inferred integrations
- Organizational topology from communication graph
A scoped, isolated workspace with the target’s metadata ready for analysis. ~10 minutes of customer time, then 0.
Discover
- CRM activity (Hubspot, Salesforce)
- Code/deploy signals (GitHub, Linear)
- Finance signals (Stripe, NetSuite, QBO)
- HR signals (Rippling, Gusto)
- Stage classification
- Peer-set selection for benchmarking
- Org structure inference
A baseline picture of how the company is wired — what tools, what roles, what cadence. Establishes the comparison set for scoring.
Diagnose
- Behavioral signals across all integrated systems
- Nine-dimension scoring against the Zoe model
- Stage-weighted composite Zoe Score
- Peer benchmarking
- Trend detection over the lookback window
A composite Zoe Score (0–100) with sub-scores per dimension and confidence intervals. The headline number that goes in the IC memo.
Prescribe
- Findings from each dimension’s scoring engine
- Root-cause attribution per finding
- Impact estimation
- Owner suggestion based on org graph
A ranked list of findings with specific root causes (not "improve culture" — "engineering and product stopped talking directly on Dec 15") plus a 100-day action plan.
Monitor
- Continuous metadata refresh on a schedule
- Drift detection across all nine dimensions
- Threshold alerting for declining metrics
Pulse monitoring — know when a dimension drops before it becomes a crisis. Optional weekly digest, optional Slack alerts.
The questions teams ask before they connect.
What if some integrations fail or aren’t available?+
Zoe runs on partial data — it requires only one core system (typically Google Workspace) to produce a meaningful diagnostic. Additional integrations sharpen specific dimensions; missing integrations widen the confidence interval on those dimensions but don’t block the report.
How is the data secured during the diagnostic?+
Each engagement runs in an isolated workspace with its own encryption key. Data is encrypted in transit (TLS 1.3) and at rest (AES-256). Raw metadata is processed and discarded after the report ships — only scores, findings, and aggregated patterns are retained. See /security for the full spec.
Can the diagnostic run without management knowing?+
No — Zoe requires authorized OAuth access into the company’s systems, so an admin must approve the integration. Most engagements run as a condition of moving to LOI, similar to a QofE.
Does Zoe read message content, code, or documents?+
Never. Zoe reads metadata only — who communicates with whom, how often, across which channels, and at what cadence. We don’t parse message bodies, code commits, document text, or financial line items.
How long does the company need to be operating before Zoe is meaningful?+
About 90 days. We need a meaningful behavioral history to compute reliable signals — anything younger and the confidence intervals get too wide to be actionable.
Can I re-run the diagnostic and track progress?+
Yes — Zoe is built for repeat use. Many founders run it quarterly to track whether their fixes are working. Investors typically run it pre-LOI, again at close, and quarterly post-close.
Ready to run your first diagnostic?
One login. 24 hours. No surveys, no interviews, no team disruption.
Join 200+ firms on the waitlist