QuickBooks
Finance- Reads
- Invoice and ledger metadata, AR aging, close cadence
- Never
- Line-item descriptions, customer PII, bank credentials
- Scope
- accounting.read
Feeds Financial Vitality
Six connectors
Six systems the company already runs.
No new tooling on the target’s side and no questionnaire. You drop the deck, the target connects the systems it already runs, and Zoe reads the metadata from up to six sources. Each one is granted, scoped, and revoked by the target, independently. Once the system(s) connect, the deck’s claims are checked against them.
Six connectors live
HubSpot
CRM- Reads
- Deal-stage transitions, pipeline timestamps, owner changes
- Never
- Email bodies, call recordings, contact notes
- Scope
- crm.objects.deals.read
Feeds Go-to-Market
Salesforce
CRM- Reads
- Account concentration, renewal dates, owner history
- Never
- Opportunity notes, attachments, contact records
- Scope
- api refresh_tokenread-only pending
Feeds Product & Customer
GitHub
Engineering- Reads
- Commit and PR cadence, review latency, deploy frequency
- Never
- Source code, diffs, commit message bodies
- Scope
- repo:status read:orgread-only pending
Feeds Delivery & Execution
Jira
Engineering- Reads
- Cycle time, reopen rate, work-in-progress age
- Never
- Ticket descriptions, comments, attachments
- Scope
- read:jira-work
Feeds Delivery & Execution
Slack
Communications- Reads
- Channel graph, response latency, cross-team edges
- Never
- Message bodies, DMs, file contents
- Scope
- channels:read users:read
Feeds Culture & People
What the connections unlock
The deck says one thing. The books say another. Zoe shows both.
Once the system(s) connect, Zoe checks the deck’s claims against them automatically: Said vs True. Gaps in the Claim Ledger become the questions for the Founder Call, and the transcript is scored as answered, dodged or contradicted. Every finding in the readout links back to the source it came from.
Not live yet
The next sources on the list.
Six are live today. These are the sources being built next. Some deepen dimensions Zoe already scores; others open coverage to companies set up differently. Coming in Q4 2026, landing in the order they read cleanly.
Nextdeeper reads on what Zoe already scores
Google WorkspaceCommunicationsComing Q4 2026
Gmail and Calendar metadata: a deeper read on decision-making velocity across the leadership group.
Microsoft OutlookCommunicationsComing Q4 2026
The same read for Microsoft-first companies: mail and calendar cadence, never content.
Plannedcoverage for other setups
Microsoft TeamsCommunicationsComing Q4 2026
Communication topology where Slack isn’t the workplace.
Xero · FreshBooks · NetSuiteFinanceComing Q4 2026
A second finance system, for companies that don’t run QuickBooks.
StripeFinanceComing Q4 2026
Billing-side coverage where neither finance system is in use.
Additional delivery systemEngineeringComing Q4 2026
Delivery and velocity signal beyond GitHub and Jira.
Tell me when a source goes live.
One line when a connector ships. Nothing else. Unsubscribe from any of them in one click.
If a source is missing
Coverage is reported, not assumed.
Not every company runs all six. When a source is absent, the dimensions that depend on it are marked as reduced coverage on the readout, and the score carries a confidence percentage and a coverage tier, rather than being scored on thinner evidence and presented as equal. Pending renders as pending.
Example · four of six granted52%coverage
- Financial VitalityFull coverage
- Delivery & ExecutionFull coverage
- Culture & PeopleNo coverage · no Slack
- C-SuiteNo coverage · no Slack
- Market & CompetitionFull coverage
- Go-to-MarketReduced · no Salesforce
- Vision & StrategyReduced · no Slack
- Product & CustomerNo coverage · no Salesforce
- RiskReduced · no Salesforce, Slack
Toggle a source above, as if the target had granted or revoked it. The readout re-reports itself. The Zoe Score is reported with a confidence percentage and a coverage tier.
The grant
Every scope is on screen before the target grants it.
It starts with a signed link from Zoe. Whoever at the target holds the keys (often the CEO, CFO or an admin) opens it, reads the DPA, and accepts; the acceptance is logged as a consent event. Then each system is connected read-only through OAuth, in the target’s own session. You never see a credential. This is what the target sees. No hidden scopes, no bundled permissions, no “and related data”.
Zoe is requesting read-only access
- channels:readChannel names and membership graph
- users:readMember list and team membership
- messages:readNot requested. Message bodies are never stored.
Revocable at any time from your Slack admin. Destroyed 30 days after the case is sealed, with certificate.
Why it’s built this way
The person granting access usually isn’t the buyer. It’s someone at the target, often the CEO, CFO or head of IT, mid-deal, being asked to connect systems to a company they met last week. They buy nothing and they carry all the perceived risk. So they see the DPA first, and they grant from their own session.
So the scope that isn’t requested is shown alongside the ones that are. The strongest thing on this screen is the permission Zoe deliberately doesn’t ask for.
The case shows the status of each source as it connects.
Prepare for diligence →
Six systems. One afternoon. No passwords.
The target connects what it already runs, read-only, in its own login. You never hold a credential, and the readout that follows is built on what the systems actually recorded.