Custom development
- 9 to 18 months before first value.
- High upfront cost and maintenance forever.
- Project risk carried by an SME with no IT team.
This food distribution company, a fast-growing wholesaler, was juggling spreadsheets, emails and paper purchase orders. The temptation: commission custom software. Our recommendation: don’t. After a build-vs-buy analysis, we selected a proven off-the-shelf ERP, then focused our effort where it really counts — adoption by the teams.

In five years, the company had doubled in size, yet still ran operations like a small business. Order errors were multiplying, inventory was imprecise and information lived in the heads of a few key people.
Not everyone needs custom software. We objectively compared both paths against the company’s real needs, budget and timeline.
A great tool poorly adopted is worth nothing. We ran adoption as a project in its own right, with internal champions and hands-on support.
Technology almost never fails for technical reasons — it fails for human ones. We treated adoption as the real work of the project.

Identifying and training ambassadors in each team to carry the change from the inside.
Short, concrete sessions tailored to each job rather than generic training.
On-site presence in the first weeks to clear blockers in real time.
Gathering friction points and adjusting quickly to sustain buy-in.
Success isn’t measured at go-live, but in usage. Three months after launch, the new ERP was part of the daily routine.
I wanted custom software built for us. Codally convinced me otherwise — and they were right. We paid a fraction of the price, it was in place in weeks, and above all, my teams use it every day.
Sometimes the best software is the one that already exists. Let’s talk about your real need.