The layer on top

Your books stay where they are. The insight comes here.

A diagnostic and prescriptive layer that reads your ledger via OAuth and never writes back. Connect QuickBooks, Intacct, NetSuite, or Xero in an afternoon — then let the AI tell you what went wrong and what to do about it.

The architecture

Your ledger of record stays put. The decision layer is new.

We don't replace your accounting software. We sit on top, read-only by default, and add the diagnostic and prescriptive layer that finance leadership has been doing in Sheets for the last decade.

Your ledger of record

  • QBO QuickBooks Online
  • SI Sage Intacct
  • NS NetSuite
  • XR Xero
  • PL Plaid bank feeds

Rollupbooks · the layer above

  • DX Anomaly + variance + root-cause
  • GS Goal Seek — targets to lever paths
  • WI What-If — live lever sliders
  • EB EBITDA bridge — period & plan
  • MC Multi-entity consolidation
The thesis

From what happened — to why — to what's next.

Close-automation tools answer the first question, faster. We answer two more.

Diagnostic

Why did EBITDA miss?

  • Anomaly detection — every journal entry watched, 2σ from trailing 24 months gets flagged
  • Variance attribution — each miss decomposed to the operational lever that drove it
  • Root-cause walk — descend from a $120k EBITDA miss to the specific entries that caused it
  • EBITDA bridge (period) — last period to this period, waterfall by lever and location
  • Forecast accuracy tracking — measure how well past plans held up, feed it back into calibration
Prescriptive

What should I do about it?

  • Scenarios — named plans (Commit / Stretch / Bear) with full P&L, BS, CF at consolidated level
  • What-If Calculator — drag any lever, watch EBITDA recompute in under 400ms
  • Sensitivity Analysis — tornado charts and elasticity readouts: which lever matters most
  • Goal Seek — state the target, get three to five ranked lever combinations that hit it
  • EBITDA bridge (plan) — baseline to target, waterfall by lever, drillable to projection entries
The four modes are not four products. They are four ways of asking the same engine the same question. Pick the mode that matches the question; the math is the same.
One engine · WhatIfProjector
The AI Planning Layer

Calibrated on your history. Not a generic model.

What makes the suite prescriptive rather than a glorified spreadsheet is the AI Planning Layer — seven distinct AI surfaces, all calibrated by your operational driver framework. The model can see what your business has actually done before, and it's bounded to propose only what's plausible inside that envelope.

A 5% price increase your team has held three times before scores very differently from a 25% increase you've never attempted. The calibration is the moat — the more the platform sees, the more credible its proposed paths become.

  • Scenario generation from natural language ("get me to $2M EBITDA without cutting headcount")
  • Lever magnitude calibration bounded by historical_min / max envelopes
  • CFO-style narratives on every scenario, solution, bridge, and anomaly
  • Feasibility scoring and honest infeasibility flags — we tell you when no realistic path exists
  • Anomaly-aware baselining — one-time gains don't propagate forward as if recurring
  • Audit log of every AI call — see exactly what the model was told and why it proposed what it did
Trustworthy intelligence

Every AI call is audited.

"Why did the AI propose this scenario?" is a question we expected, so we made it answerable. Every Prism call lands in ai_planning_calls: the surface, the model, the prompt payload, the response payload, the triggering user, the timestamp. Operators can see exactly what the AI was told and why it returned what it returned.

The "AI-in" parts — generation, narration, NL parsing — are AI-driven. The "AI-out" parts — the feasibility scoring, the envelope clamping, the simulator itself — are deterministic. The boundary is explicit. The score is reproducible even when the model is not.

  • Lever values are clamped to historical envelopes; values outside the envelope are dropped, not silently coerced
  • Schema-validated structured output; malformed responses retry once, then surface as an error
  • Honest infeasibility flags — the AI is required to say "no realistic path reaches this" when that's true
  • Read-only on your ledger — planning lives in its own tables; journal_entries is sacrosanct
Platform questions

What buyers ask when they get past the demo.

How is this different from a close-automation product? +
Close-automation tools (Campfire, Rillet) answer what happened, faster. We answer two more: why did it happen, and what should I do about it. Diagnostic + prescriptive on top of the close, not the close itself.
How do you keep the AI honest? +
Every lever value the AI proposes must fall inside your business's historical envelope. A 5% price increase your team has done three times before scores very differently from a 25% increase you've never attempted. When no realistic path reaches a target, the AI says so explicitly. Prescriptive does not mean overconfident.
What if we already have FP&A in a spreadsheet? +
Most of our customers do, day one. Goal Seek and Sensitivity Analysis read the same data sources your spreadsheet does — they're just calibrated by the platform, attributed by lever, and tied back to the journal entries automatically. Most operators keep the spreadsheet for one or two cycles, then stop opening it.

Stop signing contracts before you've seen your own numbers.

Connect your books in an afternoon. See the diagnostics and the first scenarios on your real data, the same week. No implementation fees, no six-month rollout, no SOW.

app.rollupbooks.ai Start free
Already a user? Sign in ↗