Building software for decades, not quarters.
Most software companies are organised around the next eighteen months. What changes when you organise around the next thirty years?
There is a particular discipline that emerges when a team commits to running a product for a very long time. Short-term thinking quietly exits the room. The conversation stops being about what to ship this quarter and starts being about what you are willing to be accountable for, every quarter, for the foreseeable future.
This is the posture Ally Group takes. We are a privately-held Dutch company, deliberately small, and we expect the products we build to outlive the funding cycles, political weather, and technology fashions that were in vogue when we started them. That expectation is not ambition. It is constraint.
It constrains what we build: we avoid software that depends on market momentum we cannot generate, or on customer behaviours we do not believe are stable. It constrains how we build: we prefer boring technology, documented well, owned by people who are still around to answer questions about it five years later. And it constrains how we measure ourselves: the only metric that matters, ultimately, is whether the thing still works, still serves its users, and still earns its keep.
The rest of this essay is about what that looks like in practice — in the commercial SaaS side of the group, and in the youth-software side, which operates under the same discipline but with a very different customer.