Week 1: connect, read-only
We start with read-only access to the ERP, the CRM and the spreadsheets that matter. For SAP, our team sets up the VPN tunnel, the SAP NW RFC SDK and a read-only user, then reads your tables, custom Z tables included. Nothing in your source systems changes.
Weeks 2 and 3: model and reconcile
We build one data model with your finance team and reconcile it line by line to your own books. We don’t share a single dashboard until the numbers match.
We don’t share a dashboard until the numbers match the books.
Week 4: go live
Dashboards, alerts and answers go live on the model, and every team learns to ask, build and act in CIRO. Our standard plan targets four weeks; larger ERP landscapes can take longer, and we say so on day one.
- 1Week 1Connect
Read-only access to the ERP, CRM and spreadsheets.
- 2Weeks 2–3Model and reconcile
One data model, matched to your own books.
- 3Week 4Go live
Dashboards, alerts and answers; your team trained.
- +ThenExpand
Add RevOps, Marketing, Supply chain and Finance.
Then: every space on the same model
RevOps, Marketing Studio, Supply chain and Finance plug into the same model. One customer, an agro-industrial group with 10 companies in SAP, now closes with a consolidated P&L that matches SAP to the cent.
Key takeaways
- Read-only from day one.
- Reconciled to your books before anyone sees a dashboard.
- Four weeks is the target for a standard plan.
- Then every space runs on the same model.