Live
Module 01
Client & Engagement Core
Holds clients, engagements, charters, contacts, and the operating context around the advisory relationship.
PLATFORM
One operating layer for the Financial Readiness Pathway.
FourX CFO Platform is the financial operating system that runs the FourX Financial Readiness Pathway.
FIVE-MODULE ARCHITECTURE
01Engagement Core
02Data Layer
03Operating WorkflowOperating loop
04Report Generator
05Client Portal
The platform does not replace the FourX methodology. It runs it. Built for owner-operated businesses with $5M-$100M in revenue.
WHO THIS IS FOR
For owners, controllers, and advisors evaluating the platform.
This page is for owners, controllers, and advisors evaluating whether the platform can replace the current mix of Excel, Word, OneDrive, email, and meeting memory.
Read it top-down for the system view. If you already know the high-level pitch, jump to the operating loop section and see how the monthly cycle moves.
SYSTEM MAP
The five-module architecture.
The platform is built around five modules. The Client & Engagement Core holds the relationships. The Financial Data Layer holds the numbers. The Operating Workflow holds the rhythm. The Report Generator turns the work into output. The Client Portal is the owner-facing layer for access, archive, and review.
FourX CFO Platform is the financial operating system that runs the FourX Financial Readiness Pathway.
In Build
Module 02
Financial Data Layer
Holds KPIs, observations, forecasts, actuals, and audit history.
Per-client KPI configuration with monthly observations.
In Build
Module 03
Operating Workflow
Connects the Working Brief, Action Register, Decision Log, forecast versions, and period rollover.
Run the monthly CFO cycle in one place. The Pack is generated from the same operating workflow.
In Build
Module 04
Report Generator
Turns reviewed operating work into the Monthly CFO Pack and future report outputs.
The Pack is generated from the Working Brief, KPIs, Action Register, and Forecast Version.
Planned
Module 05
Client Portal
The owner-facing layer for review, archive, and stakeholder access.
Owners log in to see what changed, what it means, and what they need to decide. (Client Portal is on the roadmap.)
BEFORE / AFTER
What the platform replaces.
Today
With the platform
Pack assembly depends on Excel, Word, and manual document assembly.
The Pack is generated from the Working Brief, KPIs, Action Register, and Forecast Version.
KPI tracking lives in a control workbook or scattered notes.
Per-client KPI configuration with monthly observations.
Actions are followed up through email or meeting memory.
Action Register captures the owner, due date, source meeting, and status of every commitment.
Decisions are hard to reconstruct later.
Decisions captured time-stamped in the Decision Log, linked to actions and forecast versions.
Forecast versions can get overwritten by the latest view.
Forecasts are versioned and locked. Each version preserves the assumptions from when it was sent.
Report status is managed manually.
Every deliverable moves through draft, ready for review, and final states. Final is immutable.
Owners wait for PDFs and email threads.
Owners log in to see what changed, what it means, and what they need to decide. (Client Portal is on the roadmap.)
Today
Pack assembly depends on Excel, Word, and manual document assembly.
With the platform
The Pack is generated from the Working Brief, KPIs, Action Register, and Forecast Version.
Today
KPI tracking lives in a control workbook or scattered notes.
With the platform
Per-client KPI configuration with monthly observations.
Today
Actions are followed up through email or meeting memory.
With the platform
Action Register captures the owner, due date, source meeting, and status of every commitment.
Today
Decisions are hard to reconstruct later.
With the platform
Decisions captured time-stamped in the Decision Log, linked to actions and forecast versions.
Today
Forecast versions can get overwritten by the latest view.
With the platform
Forecasts are versioned and locked. Each version preserves the assumptions from when it was sent.
Today
Report status is managed manually.
With the platform
Every deliverable moves through draft, ready for review, and final states. Final is immutable.
Today
Owners wait for PDFs and email threads.
With the platform
Owners log in to see what changed, what it means, and what they need to decide. (Client Portal is on the roadmap.)
OPERATING LOOP
How a month moves through the platform.
Run the monthly CFO cycle in one place.
Seven stops: close data reviewed, KPI observations updated, Working Brief drafted, forecast version locked, actions and decisions captured, Pack generated and reviewed, next month rolled forward.
See the full Phase 03 OS- 01Close data reviewed
- 02KPI observations updated
- 03Working Brief drafted
- 04Forecast version locked
- 05Actions and decisions captured
- 06Pack generated and reviewed
- 07Next month rolled forward
METHODOLOGY
The platform runs the FourX Financial Readiness Pathway.
The platform does not replace the FourX methodology. It runs it.
The Financial Readiness Pathway gives the platform its structure: assessment, build, and recurring monthly CFO cadence. The software is not a generic dashboard. It is an operating layer for how FourX already delivers advisory work.
See the methodologyHONEST SCOPE
What ships when.
The platform is being built in phases. This is what is in production today, what is in active build, and what sits on the roadmap.
Live today
FourX CFO Platform is the financial operating system that runs the FourX Financial Readiness Pathway.
The platform does not replace the FourX methodology. It runs it.
Every edit captured in audit_log with actor, timestamp, before/after.
Firm-scoped data isolation enforced at the database layer.
Financial data hosted on Supabase Postgres in Canadian region (ca-central-1).
Active build
Run the monthly CFO cycle in one place. The Pack is generated from the Working Brief, KPIs, Action Register, and Forecast Version.
Author the Working Brief in the platform. Markdown editor with KPI-substitution syntax.
Action Register captures owner, due date, source meeting, and status. Editable by the FourX team today; client read access on the roadmap.
Decisions captured time-stamped in the Decision Log, linked to actions and forecast versions.
Forecasts are versioned and locked. Each version preserves the assumptions from when it was sent.
The Pack is generated from the Working Brief, KPIs, Action Register, and Forecast Version.
Planned / roadmap
Owners log in to see what changed, what it means, and what they need to decide. (Client Portal is on the roadmap.)
Direct accounting integrations are on the roadmap. Today, data is uploaded manually.
Direct bank connections are on the roadmap.
Standing reports include Executive Snapshot, Monthly Pack, MFCF, Lender Package, Board Pack, Cash Flash, 13-Week. Pack is in-platform today. Others are on the roadmap.
WHERE THE DATA SITS
Built for finance work, not generic SaaS.
Firm-scoped isolation
Firm-scoped data isolation enforced at the database layer.
Audit trail
Every edit captured in audit_log with actor, timestamp, before/after.
Canadian data residency
Financial data hosted on Supabase Postgres in Canadian region (ca-central-1).
AI assists, humans approve
AI is used for drafting (Working Brief skeleton, Pack section drafts). Every output is human-reviewed before publish.
See it in motion.
Walk through the operating loop, the Monthly CFO Pack, and the roadmap honestly, with your business as the example.