Planning and forecasting · Margo, FP&A

Plan the next twenty-four months on numbers that already posted.

A forecast is only as good as the actuals underneath it. Margo builds your operating model on the general ledger that is your system of record, so hiring plans, revenue assumptions, and expense drivers all sit on the same entries your statements come from. You set the assumptions. She keeps the arithmetic honest.

A two-year operating plan headed FY26 to 27, running August 2026 to January 2028 and marked active, with cash balance, net cash flow, expenses and revenue drawn as four lines against an axis topping out at $1.2 million. A small card sits over the lower left corner of the panel, labelled total fully loaded cost, reading $979,760, with an annualized run-rate for the full year underneath.

Your forecast should not bea spreadsheet nightmare.

Financial planning for a startup is the work of turning a set of assumptions, who you hire, what you charge, what you spend, into a cash number you can decide against. It breaks when the assumptions live in one place and the actuals live in another, because then nobody can say which half of the plan was wrong.

Spreadsheet models break

The model lives in a sheet with forty-seven tabs. One broken formula and the projection is wrong, and the evening goes into debugging a workbook instead of deciding anything with it.

Actuals never meet the forecast

The plan is refreshed by hand once a month, and by the time the refresh is finished the numbers have moved again. Nothing connects what was planned to what happened, so the plan quietly stops being used.

Board prep becomes archaeology

Investors expect clean actuals against forecast. Pulling the numbers from three places means the story on the slide and the data behind it were assembled by different people on different days.

Set the assumptions once.They meet reality monthly.

The model is not a separate artifact you maintain. It reads the ledger, so the actuals column fills itself and the only thing you own is the part that was always judgment.

01

Actuals flow in

Revenue, payroll, and operating costs reach the model from the ledger they were posted to. No export, no re-keying, no reconciliation between the plan and the books.

02

You set the drivers

Growth assumptions, expense categories, and a hiring plan with salaries and start dates. Margo prices each one and shows what it does to the cash line.

03

Scenarios compared

Run a conservative, a base, and an aggressive case side by side, or two hiring plans against each other, and read the cash impact of each without rebuilding anything.

04

You approve the plan

The version you approve is the one that feeds the board pack. Margo recalculates and flags variance; the plan that ships is the one you signed off.

Three decisions worth modeling.One place to model them.

Each answered on a surface you set yourself, so the number changes when the business does rather than when someone finds time to update a tab.

How far out can we plan?

A plan is scoped before a single driver is set: a name, a start date, the cash it opens with, and a term of one year, two years or three, at twelve, twenty-four or thirty-six months. The horizon is a choice you make rather than a template you inherit.

The create forecast panel, with a start date of September 13th, 2026, starting cash of $0, and a forecast duration of one year, two years or three years, with three years and thirty-six months selected.

Can we make these hires?

The hiring plan carries eight budgeted roles, five filled and three open, at $979,760 of fully loaded annual cost, with one of five approved roles filled. Roles enter the model as dated commitments with their own cost, not as a lump pasted into a row.

A hiring plan for fiscal 2026: eight budgeted roles with five filled and three open, $979,760 of total fully loaded annual cost, and one of five approved roles filled.

Which plan do we run?

Two budget cases set beside one another, an optimistic one against an aggressive one, compared line by line across research and development, general and administrative, sales and marketing, payroll and cost of revenue. The gap between the two columns is the decision.

Two budget cases compared category by category, an optimistic budget against an aggressive one, across research and development, general and administrative, sales and marketing, payroll and cost of revenue.

The plan has one author.The inputs have three.

MargoFP&A

The model and the scenarios

Margo builds the operating model on the ledger, prices every driver you set, compares scenarios against one another, and recalculates the cash line as actuals post.

VicBookkeeper

The actuals underneath it

Vic codes and reconciles the transactions the actuals column is made of, so plan against actual is a comparison between two things that were measured the same way.

NiaInvestor Manager

The pack that goes out

Nia assembles the board deck from the approved plan and the posted numbers, as a PDF or a slide deck. You read it and approve it before anyone else does.

The drivers, not just the chart.Every one is yours.

The loop first, then the grid the drivers live in and the plan that prices the people.

Where the plan closes

Five steps drawn as a circuit: actuals post, you set the drivers, scenarios are compared, a plan is approved, and variance comes back against the ledger it started on. A model that only runs forward has no fifth step, which is how it drifts.

The loop a plan has to close

  1. Actuals postCoded and reconciled on the ledger
  2. Drivers setHiring, pricing, and spend assumptions, yours
  3. Scenarios comparedConservative, base, and aggressive, side by side
  4. A plan approvedThe version that feeds the board pack
  5. Variance raisedPlan against actual, back on the ledger
The plan ends where it started, on the ledger. That is what keeps the variance visible while the quarter is still open.

The plan and its drivers

The chart sits over the grid it is drawn from. The plan is named across the top, an assumptions column runs beside a calculated metrics column, and the revenue group opens out to the driver underneath it, the pricing model. You fill the assumptions. The calculated metrics are what the model makes of them.

A crop of the forecast detail view headed FY26 to 27 Operating Plan, showing the monthly driver grid with an assumptions column beside a calculated metrics column, and a highlighted revenue group row opened out to a pricing model driver row beneath it. The driver cells are empty.

The hiring plan, by department

Under the summary tiles the plan charts monthly run-rate and cumulative spend across the fiscal year, and splits fully loaded annual cost by department, with research and development, sales and marketing, customer success, operations and general and administrative each carrying their own bar.

A headcount plan with tiles reading total headcount 8 with five filled and three open, total fully loaded cost $979,760, average cost per employee $122,470, and approved versus filled 1 of 5, above a cost and cash burn over time chart and a cost by department chart listing R and D, sales and marketing, customer success, operations and G and A.

The model in the sheet,and the forty-seven tabs under it.

What it replaces
A financial model spread across forty-seven tabs
Margo
FP&A
What it replaces
Re-keying last month's actuals into the plan
Vic
Bookkeeper
What it replaces
A board pack rebuilt by hand before every meeting
Nia
Investor Manager

What founders askbefore they plan on it.

The model sits on the general ledger your books live in. Revenue, payroll, and operating costs reach it as actuals post, and you set the drivers on top: growth assumptions, expense categories, and a hiring plan with salaries and start dates. Margo recalculates the cash line as the actuals change.

Yes. Build scenarios with different hiring plans, growth rates, and expense assumptions, then compare them side by side to see what each one does to your cash position. Roles can be priced together rather than one at a time, which is the version of the question most founders are actually asking.

A standalone tool imports your numbers and models them somewhere else, so the plan and the books drift apart between refreshes. Futureproof is the ledger the actuals post to, so the forecast reads them directly. There is no import step and no reconciliation between the model and the accounts.

That is your call, and the two are not the same job. Futureproof does the modeling and the data work a finance team would otherwise do by hand, which is most of what a fractional CFO spends billable hours rebuilding. The strategy conversation stays a human one, and it starts from a much better place.

Yes. Nia assembles a board pack from the approved plan and the posted numbers, with actuals against forecast, the cash projection, and the scenario comparison, as a PDF or a slide deck. You review and approve it before it goes anywhere.

Your numbers. Your answers. Smarter moves.

Stop guessing.Start planning.

Connect your accounts and the plan stops being a document you maintain. Set the assumptions, read the cash impact, and let the actuals meet the model on their own.

Starting at $1,000/month for all six agents, with a monthly review call with a human financial specialist included. No per-seat fees, no modules.

MRR Matters

The startup finance news, read for your MRR

Twice a month: the changes that touch your MRR and runway, the numbers behind each one, and one move to make. Three minutes, then back to work.

Twice a month. Unsubscribe anytime.