Every month the finance team disappears into the close: pulling trial balances from each entity, re-mapping accounts by hand, hunting the one journal nobody booked, reconciling intercompany until it finally ties. Ten, fifteen working days later the numbers are "final" — and the month they describe is already old news.
The reflex is to add an accountant, or buy a consolidation tool and point it at the same manual feeds. Headcount grows; the calendar doesn't move, because the close was never short on people.
The pattern underneath
A long close isn't an effort problem; it's a dependency problem. The number can't be assembled until a chain of manual handoffs completes in order, and every link waits on a person, a spreadsheet, and a mapping that lives in someone's head. There's no slack to compress — just a relay where each runner waits for the last. And a number that lands two weeks late isn't a control, it's a postmortem: you can't steer a quarter on actuals that surface after the month you'd have steered is already over.
A close that lands two weeks late isn't reporting. It's a postmortem on a month you can no longer change.
The fix is to make the close continuous instead of a monthly event: source feeds that map themselves, reconciliations that run by rule rather than by hand, exceptions flagged the day they happen instead of discovered at quarter-end. The team stops assembling the number and starts reviewing one that's already mostly built — same controllers, half the calendar, and the days you win back are days you can still act inside.
The close will never be the work that makes the money. The point is to stop letting it eat the days that could.
The fastest way in is to point at the leak you feel — at whatmovesit. You'll get the honest read: what it is, whether software actually fixes it, and how far it moves.
Point at your leak