Skip to content

A company behind one product

I co-founded companies that each made one thing, Infowijs among them. What that teaches a company that makes one thing for care: the people who build Inora also bring it into the teams, what goes wrong on the floor is changed in the product, and each implementation takes fewer hours than the last.

Written by

Essay6 min read

Since October 2025 I have advised Axiomatic on how it sells and implements, from the first conversation to the signed proposal. I do not build Inora myself. I watch from London, drawing on what I did before: I co-founded five companies, the first at sixteen. Scholica and Infowijs made software for Dutch schools, NearSt for shops, Examplary for teachers.

Some of those years ran side by side. From 2017 to 2019 Ahsan, Bart and I built working prototypes in one-week sprints, for clients including NS and Google. In the same years I co-founded Infowijs and led its technology: communication software for nearly 200 Dutch schools. So I have done both: work that starts again with every client, and a company behind one product. This piece is about the difference.

Work that starts again with every client

A one-week sprint delivers something that works. Then the next sprint starts, with another client and another problem. You carry what you learned in your head. That is not a criticism. It is how project work goes, and for a prototype it is exactly right.

A company behind one product has to work differently. It puts what it learns from one customer into the product, and the next customer gets it without anyone having to explain it. That is the only reason to make one thing instead of ten. If you do not, you get the drawbacks of both: a product you have to maintain, and customers who each start from zero again.

What Infowijs taught me

On 5 December 2025 I had an advisory call with Ahsan about selling and implementing.

I told him how it went at Infowijs. We started selling to schools without much experience of it. The first implementations were literally a matter of seeing what was needed. With every customer the plan got better, until it was a fixed set of steps. Now it is a checklist a school works through online on its own. “That is a position you have to end up in,” I told Ahsan.

I still think so. But a checklist like that does not come from someone writing a better manual. It gets shorter because, with every customer, the product takes over something a person had to do before. A step that comes back at every school and that the software can do does not belong on the checklist. It belongs in the software.

Why the builders also implement

In care, only the floor shows whether software works. Not the demonstration and not the launch, but the middle of the night, a handover, the moment nobody remembers the link. What goes wrong there has to reach someone who can change it in the product.

When building and implementing sit with different people, a finding like that travels through a ticket, a meeting and a priority list. Along the way the cheapest answer nearly always wins: explaining to the team how it should be done. That explanation works, for that team, for a while. The next team runs into the same thing, and someone explains it again. That way you keep implementing the way you build prototypes: from zero every time.

So at Axiomatic the people who build Inora bring it into the teams themselves, team by team, and answer for whether it is used. They change what recurs in one team in Inora itself, not by explaining it to that team, and every team after it has the change. An explanation is forgotten. A change to the product stays.

Two examples. Nobody remembered a link, so Inora is now where staff already look: in the start menu of every workstation and one tap away on the phone. And the stroke-care chain handover, asked for by name, came back in the structure the handbook prescribes 0 times out of 7. After Axiomatic fixed it at its cause in August 2026, it was 40 times out of 42. The headings now come from the organisation’s own formats; the code sets them, never the language model. No team has to remember anything for that.

One product, set up for each organisation

A software company gets a request every week that applies to one customer only. Saying yes feels like good service. But every yes that exists only for that one customer is a branch you maintain forever. After ten customers you have ten products, and not one product.

So every request comes with one question: does this also make things better for the next customer? If it does, it belongs in the product. If it does not, it belongs in the set-up, or nowhere.

In Inora that line sits in the right place. Each organisation has an environment to itself, with its own sources, users and conversations. Its report formats are kept with their headings in a register its own quality team maintains. That is set-up. The product beneath it is one product. What one team teaches us becomes the product for the next.

Implementation is not a line you can strike out

In the same call I named a trade-off that every company with a product and an implementation faces. You can offer a light version, without the implementation sessions. The offer gets cheaper, and the chance that the product works for that customer gets smaller.

For a company behind one product that is no real trade-off. A customer where the product goes unused teaches you nothing, but it does tell the next customer. So at Axiomatic implementation is part of Inora; it is not a separate service sold by the hour. Axiomatic does not bill hours either, so it never earns more when a team is served worse. This piece is about what that choice does to the company. For Axiomatic, the hours of an implementation are a cost, not revenue. That gives you every reason to make them fewer, and none to let them grow.

The number I look at

As an adviser I look at a lot of numbers. One of them tells you whether a product is growing here: how many of its own hours an implementation takes, per organisation, set out in order. Axiomatic holds itself to fewer hours per implementation, never more; each organisation must need less of us than the one before. If that line goes up, no product is growing. What is growing is a consultancy with software attached.

Care is not a school. A care team works day and night, in changing shifts, and the people who use the software mostly did not choose it. I do not know whether an implementation in care will ever become a checklist an organisation works through online on its own. The end point here is somewhere else, too: with a team that works with Inora without Axiomatic. Until then Axiomatic stays, and it makes no team depend on it.

But the direction is the same as at Infowijs. Every implementation makes the next one smaller, because what a team taught us is already in the product when the next team starts.

In a company behind one product, the expertise of implementing does not end up in the heads of a few people. It ends up in a product that does a little more itself after every implementation, and in a line of hours that falls.

Postscript, 2 November 2026

Implementation has a fixed price, beside the annual licence per location or team, and is never billed by the hour (Implementation).

Do you work in care and use Inora? Sign-in and help go through your own organisation: your team’s project lead and ambassadors can help you.

Talk through what your team needs next.