Finance
The close that eats the next month
Every month finance pulls trial balances from each entity, re-maps accounts by hand, hunts the journal nobody booked and reconciles intercompany until it ties. By the time the numbers are final, the month they describe is over.
Another accountant, or a consolidation tool pointed at the same manual feeds, rarely moves the calendar. The close was never short on people. It is a chain of handoffs, and each one waits on the last.
What it costs
- Decisions made on actuals that arrive after the month they could have changed.
- Controllers' days spent assembling the number instead of reviewing it.
- A mapping that lives in one person's head, and a close that stalls when they are out.
What gets built
01
Source feeds that map accounts by rule, with every mapping written down.
02
Reconciliations that run by rule, with exceptions flagged the day they happen.
03
A review step where the team checks a number that is already mostly built.
How the outcome is proven
The number: Days to close
The sprint runs the slice on one entity's real exports for one period. It is judged on the number your finance team already tracks: working days from period end to a closed book, against the last close.
Ten days
Frame · days 1–2
We map the process and name the one doubt that keeps the project from being funded. You get a written go or no-go, and it can be an honest no.
Prove · days 3–10
A working slice that answers that doubt on real inputs. You leave with the prototype, the number, the full project map and a priced plan for the build, whoever does it.
Start with the decision that’s stuck
Tell us where this shows up in your business. We will tell you whether ten days can answer it.