Collect
Extracts on the agreed morning. Late feeds are declared in the pack. We do not move the date to wait for a tidy file.
Process
Sprint the first pack. Name the release day. Repeat. No theatre, no six-month transformation programme.
The sprint
You give us extracts, a named owner, and two hours in week one. We give you a dictionary, a first pack, and a walkthrough on day 14.
Interviews with whoever currently compiles the month. Sample extracts from ledger, bank, billing and ads. A short note on what can be recovered this sprint and what must wait.
Write the definitions. Revenue recognition in ordinary language. Margin at the grain you will actually use. Cut-off rules that do not change because someone is late.
Wire the feeds. Build the pack and, if scoped, the 13-week cash view or unit model. Two working reviews, not an endless comment thread.
A full month in the agreed format, with gaps named in the movement note. If a figure cannot be rebuilt in the room, it stays out.
Walkthrough, refresh instruction, and a decision: stop here, or keep a monthly cycle. Files sit in a location you control.
After the sprint
A retainer is a calendar, not a standing invitation to “do finance”. Named working days. A three-month minimum so the rhythm has time to exist.
Extracts on the agreed morning. Late feeds are declared in the pack. We do not move the date to wait for a tidy file.
Draft inside the working week. Release on the published day. Movement note goes with the file, not after the meeting.
A short call on the figures, not a redesign of the tabs. New cuts from the existing model are in scope. New models are quoted.
What we need from you
Success fees. “Make revenue look stronger.” Packs that invent a KPI the data cannot support. If the extract cannot carry the claim, the pack says “not yet”. See how this lands in a scenario