Most Financial Problems Aren't Financial at All
I spent seven years doing restructuring work for small businesses before I stopped taking cases that didn't have a clear problem statement. The reason is simple: I've watched more companies burn through cash trying to fix the wrong thing than I can count. You don't get to skip the definition stage and still call yourself a consultant. There's a particular client of mine from two years ago that still sits in my head. A logistics company in the north of France, roughly forty employees, revenue around 3.2 million euros. They came to me saying their margins were collapsing and they needed a pricing overhaul. I looked at the books for three days before I told them the truth: their problem wasn't pricing. Their problem was that they were running twenty-three different vehicles on mismatched maintenance contracts, and the idle time between jobs was eating forty percent of their gross profit. Pricing had nothing to do with it. We restructured the fleet management software, consolidated three vendors into one, and renegotiated the primary contract based on actual utilization data. Margins went from 8.3 percent to 21.1 percent over six months. Not because we changed a single price point.
What Is A Financial Problem Definition Solutions That Deliver Real Change
It's the process of identifying what is actually broken in a financial system before you touch any models, dashboards, or automation tools. Most people skip straight to solutions because defining the problem is boring and uncomfortable. It forces you to admit you don't understand your own numbers. That's why half the "digital transformation" projects I see fail within twelve months. They automated a broken process instead of fixing the process first. The framework I use has four layers and it takes most businesses anywhere from two to six weeks to complete properly, depending on data availability. Layer one is the symptom map. You write down every financial complaint as a factual statement with a number attached. "Cash is late" is not a symptom. "Accounts receivable days increased from 41 to 67 over the last eight months, and three customers now hold over 120 days outstanding" is a symptom. The difference matters because it determines whether you're solving a behavioral problem or a structural one. Layer two is the causal chain. You take each verified symptom and trace it backward through the operational workflow until you hit a decision point or a system boundary. Where the chain stops being traceable by human actions and starts requiring external factors, that's usually your root cause. In the logistics case above, the chain went: delayed cash collection (symptom) lower margin per job (symptom) higher vehicle operating cost per job (root observation) fragmented maintenance contracts creating scheduling gaps (root cause). The pricing question was a red herring the owner kept insisting on because it was the only thing he understood how to change.
Layer three is the constraint identification. Every financial problem has one binding constraint at a time. There's always exactly one bottleneck that, if removed, makes three other problems vanish automatically. Finding it requires you to be willing to ignore the noisy complaints and focus only on the metrics that move when you tweak the right lever. I use a simple method here: change one variable at a time in a spreadsheet model and watch which downstream metric actually responds. If nothing moves, you're looking at the wrong variable. Layer four is the solution fit assessment. This is where most frameworks collapse because consultants sell tools, not outcomes. You take your root cause and ask whether the fix requires behavioral change, process redesign, technology investment, or capital reallocation. Each category has dramatically different time horizons and success rates. Behavioral fixes take six to eighteen months and have the highest long-term retention. Process redesigns take three to nine months. Technology solutions over thirty thousand euros have a failure rate of roughly sixty percent in small business environments because they assume infrastructure that doesn't exist yet. Capital reallocation is the only category I've seen consistently deliver results in under ninety days, and it's also the one business owners resist the most because it requires admitting some parts of the business shouldn't be funded at all. The counter-intuitive part that nobody writes about is that your best financial data is usually the stuff you're ignoring. Inbound payment patterns, vendor negotiation leverage points, employee expense categorization errors, inventory turnover by warehouse zone. The standard P&L tells you nothing about these because they don't appear as line items. They appear as variance between what you thought would happen and what actually happened. If you've never pulled a monthly variance report with sub-ten-thousand euro thresholds, start there. It will reveal problems your accounting software is actively hiding from you.
Get the Full Details
There's a serious limitation to this approach that I want to be straight about: it does not work for businesses with fewer than fifty thousand euros in monthly revenue, and it breaks down entirely for founder-owned operations where the owner refuses to separate personal and business transactions. In those cases the causal chain is deliberately obscured and no amount of framework application will surface it. The workaround for that situation is usually to install a mandatory three-month clean accounting period where all transactions are categorized with professional help, then start the four-layer process from scratch with actual data. It costs money and it feels pointless until you see what the numbers were actually doing while you were pretending they didn't exist. Another thing that catches people off guard is the temptation to solve multiple symptoms simultaneously. When you finish layer two and you've identified six root causes across three departments, the instinct is to build a six-month transformation roadmap. That almost never works. You'll get partial adoption on five of the six initiatives and total failure on the one that mattered. Pick the binding constraint from layer three and ignore everything else until it shows measurable improvement for at least two full quarters. I've watched too many competent business owners lose momentum by spreading focus across too many fronts at once. If you want to actually use this, start with a single month of transaction-level data and map three financial complaints using the symptom format I described. Not vague ones. The ones you hear in every leadership meeting. Write them down with exact numbers and dates. Then trace each one backward through your operational workflow on paper, not in software. The act of drawing the chain by hand forces you to confront the parts of the process you've been avoiding because they're messy or politically uncomfortable. The numbers won't lie to you about that the way a dashboard will.
