
BONX just raised $8.6M.
It’s a milestone — but more than that, it’s a story of risk, resilience, and rewriting the rules of what software for operations can be.
This post is not about numbers. It’s about the decisions behind the metrics, the architecture behind the product, the trust behind the rewrite. And the lesson that speed without clarity is not progress — and clarity without courage is just analysis.
From market to validation, everything up and to the right
From day one, BONX was a different kind of ERP bet.
Not another top-down suite for financial control. Not another one-size-fits-all product with mandatory training sessions and rigid workflows.
Instead, BONX started with a radically simple idea: what if the operational part of the ERP — production, supply chain, quality, logistics — could be built bottom-up, process by process, by the people who actually run operations?
We teamed up with Rémi and Alexandre, two founders with strong convictions and sharp technical thinking.
Together, we started building a no-code, composable ERP core — where SMEs could create and manage their own operational logic, without compromising on control or scale.
It resonated instantly.
Initial deployments lit up with engagement. The “aha” moments were clear. Customers started building their own flows, tweaking their own systems, seeing value in days, not quarters.
The no-code interface combined with graph-based architecture made BONX feel like a product years ahead of its time.
AI integrations made configuration and iteration dramatically faster. It wasn’t just software; it was infrastructure for builders.
We moved fast, and the market moved with us.
That’s when Dynamo joined the journey, co-leading the first funding round and helping frame the ambition in bigger terms. The goal was now clear: build the operating core of modern SMEs in Europe and beyond.
Building too fast on the wrong foundation
But startups don’t fail for lack of demand. They fail when demand hides fragility.
As more factories joined and product usage increased, we saw a strange trend. Some sites showed healthy usage curves — others stalled. Some feature requests made sense — others pointed to fundamental tension. The pipeline was strong — but customer teams were hesitating pre-sale. And internally, shipping was slowing.
We started asking questions. A lot of them.
We dug into telemetry, sat in on onboarding calls, walked through admin views, rebuilt customer setups by hand. But no single metric explained it.
And then it became painfully clear.
The product was flexible on the surface, but brittle at its core.
The data structure — which governs how processes, fields, entities, and automations relate to one another — was not composable enough. As users layered workflows, the whole system started to resist.
Every edge case multiplied the complexity. Every workaround added weight.
We weren’t iterating anymore — we were patching.
The founders felt it. OSS felt it. Dynamo felt it.
And in a rare alignment, we reached the same conclusion: you can’t build a revolution on a fragile foundation.
Rewriting. From scratch. In four weeks.
We did something that felt irrational and necessary.
The team paused all new feature development. Four OSS engineers joined full time. BONX went into full rewrite mode.
In just four weeks, using AI tooling and a complete re-architecture of the graph engine and process designer, the product was rebuilt from scratch.
No legacy. No safe bets. Just shipping — fast and clean.
This wasn’t a v2 in name only.
It was a fundamental reboot: same vision, same thesis, but now with the data model and modularity to actually support scale.
And the results? They came fast.
BONX turned into a rocketship
Usage surged. Retention climbed.
More clients started signing — not just more, but faster, with clearer onboarding paths and stronger adoption from day one.
BONX became the answer to stalled ERP projects and legacy replacements.
And the value prop matured: not just “faster ERP deployments” but own your own system. Build it. Change it. Scale it. No consultants required.
The addition of AI unlocked something powerful — not end-user gimmicks, but upstream value.
The AI helped create processes 10x faster. Think: auto-generated flows, semantic entity linking, smart validation, internal copilots for workflow creation.
It wasn’t “ERP + ChatGPT.” It was “process engineering at the speed of thought.”
In real-world tenders, BONX started winning 7 out of 10 times. 70% win rate — in competitive, multi-vendor RFPs.
That number alone tells the story: BONX wasn’t an underdog anymore. It was becoming the standard.
Deployments launched in Italy, new geographies opened up, and the team was focused on one thing: keeping up with demand.
Fundraising plans are just plans
The original plan was to raise again late 2025 or early 2026.
The metrics were strong. The team was executing. The timeline made sense. Cash in the bank.
And then 9900 came forward with a term sheet to pre-empt the round.
It wasn’t just about valuation — it was the partner fit, the timing, and the opportunity to stay focused on growth instead of managing a long fundraising cycle.
So the founders said yes. The board trusted the founders.
And now BONX is fully funded, focused, and scaling hard. With a new partner on board and the market pull accelerating.
And now, BONX scales
This round is not the finish line — it’s fuel.
BONX is now helping factories, logistics operators, and growing SMEs take control of their systems and scale with software that fits them.
Not the other way around.
It’s a big vision. But it’s also a simple one.
- No-code, so anyone can build.
- Composable, so nothing breaks.
- AI-native, so creation moves at light speed.
- Operational-first, so the people who run the business actually run the software.
To Rémi and Alexandre: thank you for the courage to do the hard things.
To the early adopters: thank you for the trust.
To Dynamo and now 9900: thank you for the partnership.
And to everyone in the ecosystem building the future of operations — you’re not alone. Let’s keep pushing.