Prerequisites
Before you roll FunnelStory out to a full revenue or success organization, confirm the items below. Confirming these items up front lets most teams finish onboarding in hours rather than weeks of back-and-forth.
People and access
Match people in your rollout to the FunnelStory roles they will use in the product (full detail in Roles and permissions):
| Role | What you need during onboarding |
|---|---|
| Super Admin | At least one person who can create the workspace, billing relationship, first admins, and IdP setup if you use SSO |
| Admin | Someone who can add connections, approve integrations, manage users under Admin Settings → Team permissions, and tune models and notifications |
| Data Admin | Optional split: owns Configure paths (connections, queries, model mappings, refresh) without full user administration—useful when IT owns OAuth apps and warehouse users but RevOps owns day-to-day config |
If you use single sign-on, involve whoever manages your IdP so SAML or OIDC metadata can be exchanged. See SSO.
Data you should have in mind
FunnelStory is built around B2B accounts rolling up users, usage, CRM, and support context. You do not need perfect data on day one, but you should know:
- Where the account list lives (CRM, warehouse table, or MDM) and which column is the stable account ID.
- Where renewal and revenue fields live if you want predictions and dashboards tuned to ARR and contract dates—usually on Account or Opportunity objects.
- Where product usage is stored (Segment, warehouse events table, or native product DB) if needle movers and journeys should reflect adoption.
If you are unsure, start from the Account model guide and map one source of truth first.
Supported connections
Any integration you plan to use must be available under Configure → Connections for your workspace edition. The catalog is documented in Data connections—databases, CRMs, support tools, chat, meetings, email, enrichment, and more.
Allowlisted egress applies to many warehouse and database setups. If your security team requires fixed IPs, share Allowed IP addresses before scheduling the first sync.
Model literacy inside your team
Someone on the customer side should be comfortable with queries or object pickers at the level your sources require (SQL for warehouses, SOQL for Salesforce, filters for HubSpot, and so on). FunnelStory accelerates authoring but does not remove the need for sensible joins and filters.
Browser and network
Use a current evergreen browser. Corporate proxies that terminate TLS can interfere with OAuth flows—test a connection from the same network your CSMs will use day to day.