MANIFESTO

The principles this practice is built on.

Not values from a slide. Working principles that shape how we decline mandates, how we talk to owners, how we sign invoices. Living document — reviewed yearly.

00 Count everything.

Anything that changes a decision — on a number. Anything that doesn't — on faith. The game is played in the first category.

An owner who decides without a number is not deciding — they are placing a bet. Our job is to make sure the number exists.

01 One partner per client.

Not a team of consultants on rotation. One partner runs the client personally — from the first call to mandate close.

This caps practice size. We accept that cap as a quality condition.

02 No handoffs in chat.

The question is never «I'll send to the team — get back to you.» If we don't know the answer, we say so. And we go get it together.

A handoff through ten intermediaries isn't scaling. It's loss of context.

03 Numbers are an act of trust,

not a report. When an owner gives us access to their data, it's not a transaction, contract, or SLA. It's trust to be earned.

We don't publish client data. Cases on this site are anonymised with written consent. All internal documentation is on NDA.

04 Not an agency. A finance function.

We are not «finance help.» Not outsourcing. Not classical consulting. This is the finance function of the business — designed, built and run from outside.

The practical difference: an agency delivers a service. A function carries responsibility for outcomes beyond the current contract.

05 May decisions on May data.

If the owner makes May decisions on April data, they are not deciding — they are reacting to the past. T+5 isn't speed for speed's sake. It's giving the month back to the owner.

Every mandate closes the month on day 5 by month 6 of work. No exceptions.

06 An interface answers,

not a person. The «where are we now» question shouldn't require a call to the CFO. The dashboard opens on the phone. The answer is 10 seconds.

It's an engineering problem, not a finance one. So we solve it with engineering, not for the engineering team.

07 An owner doesn't need another report.

An owner needs an answer to «how much», «from where», and «what next» — in ten minutes, on a Tuesday at 9:14. A report is an archive. An answer is an interface.

The report cycle is always preserved. But it's not for the owner — it's for the auditor, regulator, history. For the owner we build an answer layer.

08 42 is the answer

to the owner's main question about the business: how much, from where, and what next. Not a number, not a metaphor, not marketing. A working principle: the answer must exist before it is asked.

The name is a promise.

09 Not reporting for reporting's sake.

Every line in a report that doesn't change a decision is a candidate for deletion. Not «we need to know everything.» We need to know what's required for the next decision.

A smaller report is a better report. Compressing 18 pages into 1 is work, not laziness.

10 Confidential. Always.

We don't discuss one client with another. We don't publish company names. We don't use client data in our marketing — even anonymised, without written permission.

A baseline condition, not a differentiator.