Industries
Permute for Fractional CFOs
Run all your clients data from one application. Connect QuickBooks, Xero, Stripe, HubSpot, FileMaker, Supabase, and whatever else each client uses, then answer CFO-level questions live instead of two days later.
How it works
Bring it in. Unify it. Report on it.
01
Connect every client stack.
Use native connectors for supported systems and scope custom connectors for legacy or specialized tools. Each client keeps the stack it already uses.
02
One reportable layer per client.
Stitch QuickBooks, Stripe, HubSpot, and every other system into a single layer per client, the work you do today in Excel, done once and kept live.
03
Live FP&A and dashboards.
Daily-refreshed P&L, cash, AR/AP, and KPI dashboards. Ask "what's our runway?" in plain English and get an answer in seconds, across one entity, fifteen, or your whole portfolio.
Dashboards
Build anything. In plain English.
Start from finance-grade templates (P&L, cash, AR/AP, GTM) or describe what you want and Permute builds it. Unlike legacy BI tools, you’re never locked into a fixed schema or template library.
Why it works
Scale the portfolio without scaling headcount.
Every client stack, one workspace
Use native connectors for supported systems and scoped custom connectors where a client has a legacy or specialized stack.
Multi-client, multi-entity by default
Workspace-isolated data per client. One pane of glass across the portfolio for you. Ideal for 15-entity holdcos, restructurings, and growth-stage groups.
Reporting layer that actually scales
Skip the Power BI rebuild for every client. Daily-refreshed P&L, cash, AR/AP, and KPI dashboards reusable across the practice.
Higher effective hourly rate
Every hour Permute saves is an hour you bill elsewhere. Take on the 10th client without dropping quality on the other nine.
At a glance
Permute gives every fractional CFO the leverage of a full data and analytics team, so you can take on more clients and deliver sharper answers without adding headcount.
Start with one workflow
Pilot it on one client
Start with two systems and one recurring reporting workflow, then expand after the delivery model is proven.