Finance excluded from operating data

This reveals that finance is still treated as a closed back office system, not as part of the company’s shared operating data layer. In practice, product, sales, and marketing data flows into Snowflake or another warehouse where teams can query it, chart it, and combine it, while general ledger data stays trapped in QuickBooks, Xero, or NetSuite. That split is exactly the workflow gap tools like Causal are trying to close.

• Once startups reach roughly 100 employees, finance teams start pulling both accounting data and warehouse data into planning. Causal described customers importing cohort behavior, usage, CRM, and accounting data together because revenue forecasts depend on all of them, not just booked transactions.
  1 sacra 2 sacra
• This is a broader pattern across modern FP&A. Equals argues the important finance work sits across Stripe, Salesforce, HubSpot, databases, and accounting systems. Runway makes the same point from the planning side, that every department already has its own future facing model, but those models are disconnected from the official forecast.
  3 sacra 4 sacra
• Incumbent planning systems solve workflow and approvals better than modeling. Larger companies often use Adaptive or Anaplan for headcount and expense planning, then still build custom revenue models in spreadsheets and paste outputs back in. That leaves financial truth fragmented even after buying enterprise software.
  2 sacra 4 sacra 5 sacra

The direction of travel is toward one numbers workspace where financial actuals, operating metrics, and planning models live together. As more companies push ledger data into the warehouse and expect finance tools to sit on top of that combined dataset, FP&A products that can unify reporting, modeling, and collaboration will replace point tools built only for budgeting.