Where they started
The systems in use, who kept the books, and what the owner could not see. Described plainly, without making the client look foolish for it.
Case Studies
We publish what a client has signed off, and nothing else
A case study is a claim about somebody else's business. So ours will be written with the client, approved by the client, and carry no figure the client has not checked.
The numbers we can stand behind
Counted, not rounded — the same standard we hold a client's books to.
- Clients
- 43
- Live implementations
- 37
- Odoo modules implemented
- 94
Clients who let us name them
These companies agreed to have their names on this site.
Trusted by businesses across the region
What goes into one of our case studies
The same four parts every time, so you can compare one with another.
What we changed
The processes we mapped, the modules we configured, the data we migrated and what we chose to leave alone.
What it took
The real timeline, including the part that slipped and why. A case study with no difficulty in it is an advertisement.
What is different now
In the client's own words, with figures only where the client has checked them and agreed to publish them.
Illustrative example
What an engagement looks like, start to finish
Illustrative example. This is not a client. It is an invented example of how an engagement of ours typically runs, written in the four parts above so you can see the shape of one. No company, person or figure in it is real.
A distributor with three branches
Where they started
Sales were invoiced in one program, stock was counted in spreadsheets kept separately by each branch, and the accounts were brought up to date by an outside bookkeeper once a quarter. The owner knew the business was selling; what he could not say was which branch was making money, or how much stock he really had on any given day.
What we changed
We mapped how an order actually travelled — from the phone call to the delivery note to the payment — before configuring anything. Then one Odoo system: sales, purchasing, inventory with a warehouse per branch, and accounting, with an analytic account for each branch. Opening stock was counted once, properly, and loaded. The old invoicing program was kept readable for history and nothing new was entered in it.
What it took
Configuration went to plan. The data did not: the three branches had been naming the same products three different ways, and merging the item lists took longer than everything else put together. We said so as soon as we saw it, and the go-live moved rather than the clean-up being skipped. Training was done branch by branch, on their own orders.
What is different now
The stock figure on screen is the stock on the shelf, because every movement goes through one system. The month is closed in its second week rather than at the end of the quarter, and the owner reads profit by branch from a report instead of asking for it. The decisions are still his; he now makes them on this month's numbers.
Real client stories come with the client's signature
The example above is here to show the method, not to claim a result. A real case study carries a client's name and numbers, so each one is published only after that client has read it and agreed. Until the first is signed off, the fastest way to find out whether we have solved a problem like yours is to ask.
Ask us about a business like yoursTell us where it hurts
A first conversation costs nothing and usually makes the problem clearer even if you never hire us.