Confidence
A draft you can’t ship
“Claude in Excel is awesome for a first draft. But the moment I shape it around how we actually operate, rows shift and a formula lands on the wrong cell. Not something I’d ship.”
Modeler, finance consultancy
MCP plugin — Claude Code · Claude Desktop · Codex
Give Claude a finance workspace.
You use Claude on spreadsheets. You know the limits — it drifts on formulas, forgets between sessions, burns tokens on grids. Layerz holds the structure so Claude doesn't have to.
1-click setup
Your data stays yours · Use your own Claude · Export to .xlsx
Bump churn to 4% on DistribSaaS. What changes for Q1?
I ran it as a dry-run, so the saved model is untouched. Here's the Q1 impact:
Net revenue
€428K
−3.0% from €441K
Gross margin
€176K
−7.1% from €189K
Runway
13.4 mo
−1.6 from 15 mo
Save as scenario_churn_4% and stress a downside?
Yes, and add a downside at −15% revenue
Scenario saved. The downside cuts deeper:
EBITDA Y1
€212K
−51.9% from €441K
Runway
8 months
−5.2 from 13.4 mo
Covenant DSCR
0.88×
breach
Covenant breaks at month 9. Want me to surface a debt restructuring option, or just flag it on the board pack?
Plot quarterly EBITDA, base vs downside
Quarterly EBITDA, both scenarios:
Base caseDownside −15%EBITDA · €k
Covenant floor
Q1Q2Q3Q4
The downside sits under the covenant floor from Q1 onward.
Flag it. Then export both scenarios for the board.
Done. Board pack ready:
DistribSaaS_Q1_board.xlsx
Export Layerz · 92 KB · 2 sheets
Standard Excel, no Layerz account needed on their end.
Write a message…
Opus 4.8
Bring your agent · connect your data
Where Claude breaks
Finance pros who hit the same wall.
Business context
Re-explaining the model every time
“Every session I open, I’m re-explaining the same model — the assumptions, the structure, where we left off. I feel like I never finish onboarding it.”
CFO, PE-backed SME
Time & tokens
The context window runs out
“A few rounds into a real spreadsheet and the conversation is already too long. I cut it into pieces, lose half the context, and track what changed in my head.”
Associate, transaction advisory
What the model looks like
The missing layer for working safely with AI in finance.
Every item is named. Every formula is traceable. Claude navigates the dependency graph instead of scanning cells.
SaaS Plan 2026 – 2028P&L202620272028
Revenue1 200 0001 900 0002 800 000
MRR900 0001 500 0002 200 000
Expansion300 000400 000600 000
COGS300 000500 000600 000
Gross margin900 0001 400 0002 200 000
% of revenue75%74%79%
Operating expenses700 0001 000 0001 400 000
EBITDA235 000441 000523 000
% margin20%23%19%
Your existing workflow
Same deliverables. Your agent does the work.
Monthly close, board pack, cash forecast — unchanged for your colleagues. Standard .xlsx, no Layerz account on their end. Your agent stops drifting on the way there.
Revenue
€252K
▲ +5% vs budget
EBITDA
€68K
▲ +13%
Gross margin
77%
▲ +2 pts
March close · actual vs budget · €k
| Budget | Actual | Δ% | |
|---|---|---|---|
| Revenue | 240 | 252 | +5% |
| COGS | (60) | (58) | −3% |
| Gross margin | 180 | 194 | +8% |
| Operating expenses | (120) | (126) | +5% |
| EBITDA | 60 | 68 | +13% |
| Net income | 42 | 48 | +14% |
What you hand to your agent
How to connect
Pick your agent. Paste. Go.
How it fits your stack
Built for financial logic, not generic data.
| Feature | Layerz | Excel | Claude alone |
|---|---|---|---|
| Dynamic calculations (formulas, dependencies) | ✗ raw figures | ||
| Structured for AI navigation | ✗ cells only | ✗ no persistence | |
| Variables with type + timeline | ✗ | ✗ | |
| Persists context across sessions | ✓ data only | ✗ | |
| Native financial logic (dependencies, patterns) | ✗ manual | ✗ raw figures | |
| Versioning — every edit logged, auditable, revertable | ✗ file copies | ✗ | |
| Export to standard .xlsx | native | ✗ |
Keep using Claude. Now with financial framework.
1-click setup
Your data stays yours · Use your own Claude · Export to .xlsx