In six months, from manually stamped paper invoices and unmanageable spreadsheets to fully integrated, data-driven financial controlling with current KPIs. That was the starting point. As CFO and Managing Director, I built this from scratch while the company was simultaneously on its way to the FT 200 Fastest Growing Companies in Europe 2024. The most important lesson: you can't automate your way out of chaos. You have to fix the processes first.

The Starting Point: Chaos That Felt Normal

It wasn't a poorly run company. Quite the opposite. The team was motivated, the growth real, the customers satisfied. But like most fast-growing companies, the finance organization hadn't kept pace with the business.

  • Invoices were manually stamped each evening. That delayed all downstream reporting.
  • Reports were built from spreadsheets assembled manually each week.
  • Data from accounting, sales, and project management lived in separate, disconnected systems.
  • Supposedly current metrics were factually one to two weeks old, too old for operational decisions.
  • The finance team spent sixty to seventy percent of its time assembling data rather than analyzing it.

The question that triggered the transformation: if an investor asks tomorrow how much runway we have, how many hours would it take to give a reliable answer?

— Philipp Siegert

The Six-Month Transformation Plan

The transformation followed a structured plan in four phases, each building on the previous one. The guiding principle throughout: fix broken processes before introducing technology.

Months 1–2: Build a Reliable Financial Foundation

No software fixes a structural problem. We started with the foundation.

  • Standardized chart of accounts for consistent, comparable reports.
  • Automated invoice processing: manual work reduced by more than eighty percent.
  • Clear, documented approval processes with defined authorization limits.
  • GoBD-compliant document archiving from day one as due diligence preparation.

Months 2–3: System Integration with Odoo ERP

Siloed departments created enormous friction. Rolling out Odoo ERP as the central operating system unified the key functions:

  • Accounting and controlling
  • Sales with CRM, quotes, and orders
  • Project management and time tracking
  • HR and personnel cost planning
  • Supply chain and procurement

The result was a fully digital workflow from first customer contact to outgoing invoice, with no manual data transfers between systems.

Months 4–5: Data Warehouse on Microsoft Azure

ERPs thrive on centralized data, but operational analysis requires more flexibility. On Microsoft Azure, we built a central data warehouse consolidating all relevant sources.

  • Odoo data merged with external sources including weather data for solar yield forecasts and market data.
  • One consistent data foundation across all departments.
  • Automated data processes without manual exports.
  • Historical data accessible for trend analysis.

Months 5–6: Automated Dashboards in Power BI

Data is only valuable when it accelerates decisions. Power BI handled the presentation layer.

  • Current KPI tracking for all core metrics: cash runway, contribution margin per project, overdue receivables.
  • Automatic alerts on threshold breaches.
  • Auto-generated monthly reports as the basis for the board pack, replacing manual slide creation.
  • Predictive models for revenue forecasting and resource planning.

The Results After Six Months

MetricBeforeAfter
Reporting effort60–70% of finance time on data assemblyUnder 20%, remainder for analysis and strategy
Data freshness1–2 week delayUnder 24 hours
Invoice processingManual, error-proneOver 80% automated
Investor readinessAd-hoc reports on requestStructured board pack, available at any time
Overall efficiencyBaseline+60% efficiency gain

What Other Companies Can Learn From This

  1. 1Process before technology: No software solves a structural problem. Clarify what your process should look like first, then choose the tool.
  2. 2Integration beats optimization: A moderately integrated system beats five excellent siloed systems without data flow.
  3. 3Early wins build confidence: Automated invoice processing in the first weeks delivered immediate value and created buy-in for the bigger steps.
  4. 4Develop the team alongside the system: Reporting automation only works if the team understands what the systems do. Investment in training pays off.
  5. 5Investor-readiness as a byproduct: A well-built finance system is automatically investor-ready. No separate project required.

FAQ

Which ERP systems are suitable for scale-ups in Germany?+
For scale-ups up to around two hundred employees, Odoo has proven particularly flexible and cost-effective, with native integration of accounting, CRM, project management, and HR. For larger companies with more complex requirements, SAP Business One or Microsoft Dynamics 365 Business Central are relevant alternatives. What matters is not the tool but the consistency of implementation and willingness to adapt existing processes.
How long does a finance transformation take?+
A complete build, from chaotic processes to integrated, data-driven controlling, typically takes six to twelve months. Early improvements like clean bookkeeping and automated invoice processing are achievable in four to six weeks. The full BI system with current dashboards requires four to six months. The transformation must work in parallel with ongoing operations.
What does an ERP implementation cost?+
Costs vary significantly. Odoo for a fifty-person company typically runs fifteen thousand to fifty thousand euros for license, implementation, and training in year one. SAP Business One starts considerably higher. Critically, include internal costs for process analysis, data migration, and change management. They are often higher than the software costs.
Can this process be run during strong growth?+
Yes, and that's often the only realistic option. The transformation happened during peak growth. The key is phasing: don't change everything at once, but sequentially, first the accounting foundation, then ERP, then BI. Each phase must be stable before the next begins.