No credentials required
Safe evidence paths
Documents, exports, screenshots, SOPs, walkthroughs and stakeholder input. You can run a full assessment on these alone — system credentials are not required on day one.
Generally available
Integrations · evidence paths
Bring evidence from the systems of record — honestly.
The point of an integration is better evidence, not a longer logo wall. A connector existing in the repository is not a public availability claim. Live connections pass authentication and data-quality gates before we rely on them.
Two ways evidence arrives
Start safe. Connect systems when it earns its place.
Behind auth & data-quality gates
Live system integrations
Direct connections to systems of record, provisioned after we validate authentication and the quality of the data they return.
Available by scope
Connector families in the platform
The systems we can draw evidence from.
Grouped by category. Each connection is provisioned by scope after validation — we confirm what a given connector can actually mine for your engagement.
ERP
Available by scope- NetSuite
- SAP S/4HANA
- Dynamics 365
- Oracle ERP
- Workday
- Odoo
- Infor
- ERPNext
CRM
Available by scope- Salesforce
- HubSpot
- Dynamics 365 CRM
- Zoho CRM
- Pipedrive
- SugarCRM
- Insightly
Accounting
Available by scope- QuickBooks Online
- Xero
- Sage Intacct
- Sage 50
- FreshBooks
- Acumatica
- Bill.com
Productivity
Available by scope- Google Workspace
- Microsoft 365
- Gmail
- Slack
- Teams
Work management
Available by scope- Jira
- GitHub
- Asana
- ServiceNow
Commerce & iPaaS
Available by scope- WooCommerce
- Zapier
- Power BI
- Data warehouse
How a connection becomes live
A connector earns “live” — it isn’t assumed.
01
Authentication
The connection authenticates with your system using scoped, user-controlled credentials — never blanket access.
02
Data-quality validation
We confirm the data returned is complete and reliable enough to draw evidence-backed conclusions from.
03
Scoped provisioning
Only then is the connection provisioned for your engagement — with the evidence it produces carrying the same lineage as any other source.
We will not publish integration status that has not passed production authentication and data-quality tests.