Six connectors
Six systems the company already runs.
No new tooling on the company’s side and no questionnaire. You drop the deck, the company 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 company, independently. Once the systems connect, the deck’s claims are checked against them.
- Finance
QuickBooks
- Reads
- Profit and loss, balance sheet and cash-flow totals, revenue by customer, AR aging buckets, open bills, expense category totals
- Never stored
- Individual transactions, invoice and bill line items, customer details beyond the company name, payroll records, bank credentials
- Scope
- com.intuit.quickbooks.accounting
- CRM
HubSpot
- Reads
- Deal-stage transitions, pipeline timestamps, deal owner changes
- Never stored
- Contact records, company records, email bodies, call recordings, notes
- Scope
- crm.objects.deals.read
- CRM
Salesforce
- Reads
- Account concentration, renewal dates, owner history
- Never stored
- Opportunity notes, attachments, contact records
- Scope
- api refresh_token read-only pending
- Engineering
GitHub
- Reads
- Commit and PR cadence, review latency, deploy frequency
- Never stored
- Source code, diffs, commit message bodies
- Scope
- metadata:read contents:read pull_requests:read read-only pending
- Engineering
Jira
- Reads
- Cycle time, reopen rate, work-in-progress age
- Never stored
- Ticket descriptions, comments, attachments
- Scope
- read:jira-work
- Communications
Slack
- Reads
- Channel graph, response latency, cross-team edges, message text in public and private channels, scored and then dropped
- Never stored
- Message bodies, DMs, file contents
- Scope
- channels:read channels:history groups:read groups:history users:read
What the connections unlock
The deck says one thing. The books say another. Zoe shows both.
Once the systems connect, Zoe checks the deck’s claims against them automatically: Said vs True. Gaps in the Claim Ledger become the questions for the Company Call, and the transcript is scored as answered, dodged or contradicted. Every finding in the Deal Package 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
- Coming Q4 2026
Google WorkspaceCommunications
Gmail and Calendar metadata: a deeper read on decision-making velocity across the leadership group.
- Coming Q4 2026
Microsoft OutlookCommunications
The same read for Microsoft-first companies: mail and calendar cadence.
Plannedcoverage for other setups
- Coming Q4 2026
Microsoft TeamsCommunications
Communication topology where Slack isn’t the workplace.
- Coming Q4 2026
Xero · FreshBooks · NetSuiteFinance
A second finance system, for companies that don’t run QuickBooks.
- Coming Q4 2026
StripeFinance
Billing-side coverage where neither finance system is in use.
- Coming Q4 2026
Additional delivery systemEngineering
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 in the Deal Package, 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.
52%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 company had granted or revoked it. The Deal Package restates itself. The Zoe Score carries a confidence percentage and a coverage tier.
The grant
Every scope is on screen before the company grants it.
It starts with a signed link from Zoe. Whoever at the company 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 through OAuth, in the company’s own session. Zoe only reads, though the permission a provider grants can be broader than what Zoe reads. You never see a credential. This is what the company contact sees. No hidden scopes, no bundled permissions, no “and related data”.
- channels:readChannel names and membership graph
- groups:readNames and membership of the private channels the person granting access is in
- users:readMember list and team membership
- channels:historyMessage text, scored and then dropped. Message bodies are never stored.
- groups:historyMessage text in those private channels, scored and then dropped. Message bodies are never stored.
Disconnecting stops future reads, and Zoe also asks Slack to revoke its access. Records already synced stay until the workspace is deleted.
Why it’s built this way
The person granting access usually isn’t the buyer. It’s someone at the company, 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 diagnostic shows the status of each source as it connects.
Prepare for diligence →Six systems. One afternoon. No passwords.
The company connects what it already runs, in its own login, and Zoe only reads. You never hold a credential, and the Deal Package that follows is built on what the systems actually recorded.
Rather not wait? Start a diagnostic, add the company’s deck, invite the company to connect, and receive the Deal Package inside 24 hours.