About us
We build software for the people who use it every day
Not for the person who signs the contract. That difference decides whether a system gets used, or gets abandoned after three months.
Our story
It started with a system nobody would use
Cluvix started from an uncomfortable observation: a lot of businesses had already paid for software, and a lot of that software still sat unused while people worked from spreadsheets. It had a license, an account, and nobody logging in.
The reason was almost always the same. The system was designed from a manager's description, and nobody had asked the person entering data every day. To them, the new software took more steps than the old habit — so they went back to the old habit.
From then on we set one rule for every project: discovery has to include sitting with the person who actually does the work, not just the meeting room. That rule makes a project a few days slower at the start, and saves months at the end.
We moved from taking on one-off custom projects to packaging a product, then from an installed product to SaaS running on our own platform — each shift meant relearning what real users actually needed, not what we assumed they needed.
- 2018FoundedCluvix started with its first project for a distribution company — the place where the "sit with the real user" rule was born.
- 2020First packaged productFrom one-off custom projects, we packaged the work into a product that could be sold to multiple customers at once.
- 2022Moved to SaaSThe product left the on-premise install model and moved fully to a SaaS platform for faster rollout and centralized maintenance.
- 2025Completed & brought to marketThe product lineup reached its finished shape and was formally brought to the broader market, not just customers we already knew.
How we work
Four principles, and we're measured by them
We say so when you don't need to buy anything
Some problems are cheaper to fix by changing a process than by buying a system. Saying that is the advisor's job, even when it costs a contract.
Estimates can be wrong. Silence can't
Projects run late — that happens. We flag it the moment we see it, not in the final week.
We deliver something that runs, not a report
Every two weeks you get a build you can try, not a progress chart.
We don't keep clients by locking the source code
The source code is yours. We keep clients by doing good work, not by holding the door shut.
How we work
Four steps, none of them skipped
Every step produces something you can see and approve before the next one starts.
Discovery
We sit with the people doing the work every day, not just with management.
Design
A written spec and sample screens for you to approve before anyone writes the first line of code.
Build
Delivered in two-week batches. You see real progress, not a report about it.
Handover & support
User training, data migration, and staying on once the system is live.
Operating commitments
Four things we put in writing so you never have to ask
Buying a management system means handing part of your operation to someone else. These four commitments exist so that decision does not depend on how large or small Cluvix is.
- The source code and the data are yours
- When the project ends you receive the complete source code with unrestricted rights to use it. You can export your data to a spreadsheet at any time, on your own, without notice and at no cost.
- Documentation good enough for another team to take over
- Setup instructions, the data model, and the reasoning behind the significant design decisions are all part of the handover. That work is priced into the quote — it is not a line item added later.
- Incidents come with response times in numbers
- System down: a response within 4 working hours. Everything else: within 1 working day. A response means we confirm receipt, assess severity and commit to a fix window — we do not promise a fix time before we have seen the fault.
- If we part ways, handover takes 30 days
- Should you move to another vendor, we hand over source code, data and documentation within 30 days, along with a working session for the incoming team. We hold nothing back as leverage.
Want to know what we can do for your problem?
A 30-minute conversation is usually enough to know whether to buy off the shelf or build custom.
We'll reply within one business day.