Not one more vendor.
Someone on your side.
Always the same person, always reachable.
There are technical decisions worth years that get made in half an hour, usually with the wrong information. Someone who knows your systems and picks up when you call, without opening a ticket and without buying six months up front.
Fifteen years on the same problems.
- 15
- Years of experience
- 60+
- Projects delivered
- 7 years
- Average partnership
- 100%
- Clients by referral
We don't do everything: system integration and automation. The number that counts is the last one - none of these projects came from a tender.
Every choice stays written down. Including the one not to do it with us.
On every project we keep a decision log: what was chosen, when, why and what was ruled out. This is a real extract, with the names changed.
The data layer runs on PostgreSQL, not MySQL.
The data layer needed a database. The in-house team knew MySQL and was already running it on two applications.
The questions the client wanted to be able to ask were all about deep relations and time windows: on Postgres they take a tenth of the time to write and hold up better as the data grows. The learning curve for the team was two days, and we went through it together.
MySQL. More familiar, but we would have written three times the code to compensate - and that code would have been theirs to maintain.
Shipping is bought, not built.
The client had asked us to quote for handling couriers, labels and tracking inside the management system. It was the biggest piece of the project.
A third-party product does exactly that, with every courier already in it and kept up to date by someone else. Building it would have cost forty days and been worse the day after. We only did the integration: two days.
Our own quote. We take no commission on that product and we don't resell it: it was simply the right thing.
The data refreshes overnight.
The initial request was "the data always up to date". It's the request everyone makes, and almost never what's needed.
We went to look at who actually opens the reports: nobody before nine. Real time cost three times as much and would have loaded the management system during working hours, slowing down the people entering orders.
Continuous sync. It can still be added later on single tables: the data model doesn't change.
AI waits until the data is ready.
There was budget and there was an appetite to start straight away with an assistant answering questions about company figures.
The data wasn't normalised yet. An agent would have answered badly, and inside the company the blame would have gone to AI rather than to the foundations. Data layer first, the rest six months later - it shipped and it works.
Starting immediately. Easier to sell and much worse to use.
We stay on the management system that's there.
The ERP vendor was proposing migration to the new version as a condition for fixing some open issues.
We read the specification together with the client and asked the vendor the questions on their behalf. The migration fixed two problems out of nine and opened three more. That money went into the data layer, which fixed seven.
The migration. It wasn't a sale of ours in either scenario - which is exactly why we could say so.
We don't resell licences. When we recommend something, we make nothing on it.
Bespoke means we have nothing to place with you.
- 01
Listening comes first
The first meeting isn't a demo: we look at how you work now and what already works.
- 02
Bespoke, not off the catalogue
Every proposal starts from what you have: we only add the piece that's genuinely missing.
- 03
Including solutions that aren't ours
We don't resell licences and take no commission: that's why the advice can be taken at face value.
- 04
Counterpart to your vendors
We speak their language but we're on your side - quotes and deadlines included.
- 05
Always the same person
Whoever takes the first call does the work, and a year later remembers why you chose that way.
- 06
We know how to say it isn't needed
Sometimes we close a meeting saying the problem can be solved with far less.
No tickets. A direct contact, and an answer the same day.
Support doesn't go through a portal and has no case number: there's a direct contact with the person who knows the project, and the answer arrives within the day.
trace "the report stopped updating"
- open a ticket on the portal10 min
- first line asks you to rephrase+ 1 d
- escalation to second line+ 2 d
- they call back to understand the context+ 3 d
- whoever did the work has left+ 5 d
- answer8 d
- you call, or write an email2 min
- answer from whoever knows the projectsame day
no case number
Bought in pieces. Not in months.
By the hour
Small packs of hours, used when they're needed and not expiring at the end of the month. It's the right way when the need is intermittent: a few questions, an intervention now and then.
→ no expiry
Light retainer
A few guaranteed hours a month, the rest as used. It works when you want someone who knows the systems to be around anyway, including the months when nothing happens.
→ pause it whenever
By intervention
You agree on one thing to solve and a spending cap, not a period. If it closes early, it closes early: there are no hours to fill.
→ ends when it works
No minimum contract and no annual package to burn before it expires. Nobody has stayed because of a contractual lock: the average collaboration lasts seven years.
The projects completed over the yearsGo to the case studies