Trend · 01
Maturity of no-code platforms
Notion, ClickUp, Monday and Airtable already support relational data models, complex automations and granular permissions. What was a promise a few years ago is now in production.
● Digital work systems
ERPs and custom systems.
We build the operational backbone of a company, a system that adapts to the business, not the other way around. Without the scars of a traditional ERP.
The context
Why it matters today more than ever.
For decades, mid-sized companies faced a binary choice: invest hundreds of thousands of euros in a traditional ERP, or keep stretching spreadsheets. Neither option works well. Today, no-code platforms have made a third way viable: build the system your business needs in weeks, not months, and at a fraction of the cost.
Trend · 02
Mature integration layer
Make, Zapier, n8n and Relay connect practically any API to any other without programming. The old argument of «you need an ERP for the integrations» no longer applies.
Trend · 03
AI applied to the operational stack
The new systems are no longer passive repositories: they read, decide and act. This only works if your operational system is flexible enough to be instrumented, the opposite of a closed ERP.
The problem
Where your system always breaks.
Symptoms vary from company to company, but the patterns repeat. These are the four structural pains we find in practically every operational audit we run.
01
Data fragmented across 5-10 tools
CRM in HubSpot, invoicing in Holded, projects in Trello, HR in Factorial, finance in Excel, contracts in Drive. Each area has its system, none really talk to the others.
Impact
No consolidated picture of the real state of the business.
02
Impossible or outdated reporting
Generating a consolidated report of margin by client, utilization by person or pipeline by quarter requires downloading CSVs, crossing them in Excel and praying. By the time it arrives, it's already obsolete.
Impact
No real-time business view or reliable KPIs.
03
Traditional ERPs: expensive, rigid, and they fail
SAP Business One, Dynamics 365, NetSuite. Implementations of 6 to 18 months, cost overruns of 3x to 4x, and between 50% and 75% miss the objectives. And in the end, only a quarter of the team uses it.
Impact
Large investments that don't produce the promised ROI (26% average adoption, RubinBrown).
04
Critical spreadsheets that no longer scale
The CFO's Excel, the COO's capacity sheet, the salesperson's commission sheet. Million-dollar decisions are made on files that only one person understands and that any change could break.
Impact
High operational risk, dependence on specific people.
We tried a big ERP and it was a disaster, we left it half-implemented. Meanwhile, the master Excel is run by a single person and every month-end close is a nightmare of crossing data.
, What we hear in discovery calls
The cost
What it costs to leave it unfixed.
215%
average cost overrun on initial budget for ERP implementations in discrete manufacturing.
Source · Panorama 2025 ERP Report
An uncomfortable conclusion
For most companies under 200 people, the right question isn't «which ERP do we pick?». It's «do we need an ERP, or do we need a system of our own?». The answer changes the order of magnitude of the project.
The solution
A system, not a tool.
The alternative to the false ERP-vs-Excel dilemma is to build your own operational system: a coordinated set of databases, views, automations and integrations, designed around your real processes and supported by mature no-code platforms. Six pillars sustain it.
01
Unified data model
An explicit relational schema that connects clients, projects, people, products and operations. The backbone of the system: if this is well designed, everything else falls into place.
02
Design around the real process
The system is built around how the company works, not the other way around. The peculiarities of the business stop being exceptions, they're first-class features of the design.
03
Integrations that eliminate rekeying
Make, Zapier, Relay and n8n connect the system with the rest of the stack (mail, accounting, banking, e-signature, e-commerce). Data enters once and propagates on its own.
04
Layered architecture, not monolith
Data layer + logic + interface + integration. Each can be evolved (or even swapped to a different tool) without rewriting the whole system.
05
Capacity to evolve without rewriting
When the business changes, the system adjusts in hours or days, not months. The company becomes faster at pivoting, the system stops being a brake and becomes an accelerator.
06
Reasonable total cost of ownership
Per-user licenses on no-code platforms, no expensive consultants for every change, no dependence on a single enterprise vendor. TCO stays proportional to the size of the business.
The tools
4 platforms, one technical decision.
«We don't sell tools or ERPs, we design systems. The platform choice is made in phase 1 based on objective criteria, not preference.»
Notion
Relational databases + docs + integrated AI in a single workspace. Maximum modeling flexibility.
Ideal for
Systems where docs and data go together: consultancies, agencies, product teams, startups in definition phase.
ClickUp
Structured hierarchy (Spaces · Folders · Lists · Tasks) + custom fields + powerful native automations. Operational all-in-one.
Ideal for
Mid-sized companies with clear processes and digital discipline. When processes matter as much or more than data.
Asana
Clear structure, strong accountability, well-resolved portfolio. Gentle learning curve for the end user.
Ideal for
Systems where delivery and cross-team coordination is the dominant domain. It's worth combining with external databases for more relational domains.
Monday
Highly configurable visual boards + powerful dashboards + cross-board automations. Excellent for non-technical users.
Ideal for
Cross-departmental organizations where several non-technical teams (sales, marketing, customer service, operations) operate on the same system.
03—Our methodology
The process.
A sequence proven in 200+ companies. Each phase has deliverables before moving to the next, and is developed in collaboration with your internal team.
01→
Diagnostic
We audit existing processes and the current stack. We map bottlenecks and optimization opportunities to ensure the success of the following phases.
02→
Planning
We define target architecture, rollout plan, roles, and metrics before getting into the weeds.
03→
Build
We execute in short iterations with your team. We create, adapt, and integrate with your existing tools.
04→
Rollout
We start with a test and expand after validation. We train your team so adoption feels natural.
05✓
Follow-through
We measure and listen to feedback throughout so the result truly becomes yours.
Results
What changes when it works.
The results of a well-built custom operational system are tangible and fast: the first impacts show up in weeks, not years.
−90%
Implementation time vs. traditional ERP
From 9-18 months to 6-12 weeks. And with phased go-live instead of big-bang: less risk, more real adoption.
−80%
Investment vs. traditional ERP
One-tenth of the cost of an equivalent ERP implementation. No enterprise licenses, no expensive consultants, no surprises.
+70%
Real team adoption
Compared to the 26% average usage of a traditional ERP. When the system is designed around the team's process, the team uses it.
Days
Time to evolve the system
When the business changes, the system adjusts in hours or days, not months. The company pivots fast, the system stops being a brake.
This is what we wanted from the ERP we tried three years ago, and we have it at a fraction of the cost.
, Managing Director, mid-market industrial company
Let's talk.
Book a free intro session so we can understand where you stand and how we can help. No strings attached.
Contact →
or write to us at info@theoptimalflow.com