Supported CRM providers
Salesforce and HubSpot
Orchestri Overlay · Available through guided configuration
Keep Salesforce or HubSpot. Add Orchestri intelligence.
Orchestri adds a clearer operating experience above supported CRM records while Salesforce or HubSpot remains official. Current Overlay access is read-only and preserves the original source.
Clear system ownership
Existing CRM records stay official.
01
Connect CRM
02
Normalize records
03
Analyze intelligence
04
Show original CRM sources
Current coverage
What is available, configured, and scoped.
Coverage depends on the connected CRM, supported records, permissions, refresh behavior, and configured workflow. The boundaries below reflect current Orchestri Overlay support.
Supported records
Accounts, contacts, and opportunities or deals
Connected-system behavior
Read-only; no source CRM writeback
Authentication and permissions
Secure connection and configured access determine what Orchestri can read and who can use it.
Refresh and synchronization
Connection-specific refresh health and last-sync status are shown in Orchestri.
Additional objects or systems
Coverage beyond the listed records requires technical and product review.
What Orchestri Overlay does
A clearer operating and intelligence experience above supported CRM data.
With guided connection, Orchestri reads supported Salesforce or HubSpot records, organizes them into consistent views, and uses them across Forecasting, Revenue Intelligence, weekly revenue review through Operating Rhythm, Reporting, Search, and Maestro while keeping the original CRM source visible.
Connect existing CRM
Start with the customer and pipeline system your team already uses.
Normalize into Orchestri
Map supported records into consistent intelligence views with source context attached.
Analyze across surfaces
Use the same connected data for forecasting, reporting, search, rhythm, and Maestro guidance.
Supported objects
Accounts, Contacts, and Opportunities/Deals first.
Orchestri Overlay is intentionally clear about what is supported now and what is not part of current overlay intelligence.
Supported now
Used for
Salesforce Accounts
Views, answers, risks, recommendations, and supported product workflows
Salesforce Contacts
Views, answers, risks, recommendations, and supported product workflows
Salesforce Opportunities
Views, answers, risks, recommendations, and supported product workflows
HubSpot Companies
Views, answers, risks, recommendations, and supported product workflows
HubSpot Contacts
Views, answers, risks, recommendations, and supported product workflows
HubSpot Deals
Views, answers, risks, recommendations, and supported product workflows
Not included today
Contract Intelligence
Product Intelligence
Price Book Intelligence
Source CRM writeback
These areas are strategic direction, not current Overlay capability. Any additional coverage must be confirmed before it is treated as part of an engagement.
Read-only by design
Your system of record remains protected because Orchestri does not write changes back to it.
Overlay records are read-only intelligence inputs. Orchestri does not update Salesforce or HubSpot records, change stages, modify owners, or write back forecast changes.
Read supported source records
Keep Orchestri-native information separate
Prepare recommendations
Run supported Orchestri actions
No external CRM writeback
Read-only lowers the risk of source-record corruption and preserves clear system ownership. It does not eliminate access, privacy, integration, data-quality, or governance risk.
Overlay Data Policy
What gets analyzed, and why.
The default policy keeps forecast logic practical while still surfacing useful operating and trust signals from connected CRM data.
Open opportunities are included by default.
Closed Won opportunities can be included within a lookback window.
Closed Lost opportunities can support loss and risk context, but are excluded from forecast calculations.
Forecast eligibility requires amount, stage, and close date.
Owner gaps are treated as operating and trust signals, not automatic forecast blockers.
Health and coverage
Every intelligence surface shows inclusion, exclusion, and coverage.
Teams can see which records were used, which records were excluded, and what needs cleanup before a record becomes forecast-eligible.
Included opportunities
Excluded opportunities
Missing amount
Missing close date
Mapping incomplete
Source breakdown
Last sync
Read-only active
Where it helps
A weekly revenue review, powered by connected data.
Operating Rhythm helps teams use the customer and deal context already sitting in Salesforce or HubSpot for a more useful weekly review.
Forecasting
See pipeline status and weighted views from connected CRM opportunities.
Weekly revenue review
Use connected CRM, activity, and customer data to power Operating Rhythm.
Revenue Intelligence
Identify risk, movement, and coverage gaps from connected records.
Maestro
Ask questions across connected customer and opportunity context.
Reporting
Create blended reports with provenance and eligibility.
Ideal fit
A practical starting point for teams that need visibility before migration.
Orchestri Overlay is usually strongest when the team already has CRM records in place and needs operating clarity before changing core workflows.
Use Salesforce or HubSpot today
Want better visibility without a migration
Need forecasting and operating cadence
Have data spread across teams or systems
Want to evaluate Orchestri before replacing their CRM
Start with visibility. Keep migration as a separate decision.
Orchestri Overlay gives teams a practical way to improve operating clarity while keeping supported Salesforce or HubSpot records read-only and official.