Building our own products makes us better at building yours.

KHEL does something that sounds simple until you try to operate it. A player finds a game near them, joins it, and once enough players have committed, KHEL books the pitch and confirms the match. Find your game, book the pitch. If the roster never fills, the game does not run and nobody is charged.

Every clause in that description is a decision we have had to defend at nine on a Friday night with real people waiting.

What owning it teaches that a brief cannot

A client brief describes a system in its intended state. Operating a product teaches you about its actual state, which is messier and much more instructive.

• —A roster that fills to nine of ten players an hour before kickoff is not an edge case. It is Tuesday. The product has to have an opinion about it.
• —A refund guarantee is a one-line promise on a landing page and a genuinely hard problem in the payments layer, the notification layer, and the venue relationship.
• —Venue partners do not read your admin panel the way you designed it. They read it at speed, on a phone, between two bookings.
• —The support inbox is a product spec. It tells you, in order, exactly what is broken about the thing you thought was finished.

The consequences land on us

This is the part that changes behaviour. On a client build, a slightly awkward admin flow is a note in a backlog. On KHEL, it is a member of our own team doing something annoying forty times a week until we fix it.

You design software differently when you are the one who has to operate it at eleven at night.

It makes us suspicious of cleverness. It makes us spend more time than seems reasonable on the back office, because we have learned that the back office is where a product is actually run. And it makes us take monitoring seriously before launch rather than after the first bad weekend, because we have had the bad weekend.

What the client work gets from it

Three things, concretely. We estimate operational work honestly, because we have paid for underestimating it. We build the admin surface as a first-class product rather than an afterthought. And when we tell a client that the launch is the beginning rather than the end of the work, we are not selling a support contract — we are describing something we have lived.

It also keeps us from a particular kind of drift. A studio that only builds to order gradually optimises for what is easy to deliver and sign off. Running your own products means the market, not the invoice, tells you whether the work was good.

Where it goes next

KHEL was the first. There are now others in the house — a CRM for hotels, and an ERP for trekking and expedition companies built out of everything we learned mapping one of the hardest operations in that trade. Same discipline: we build it, we own it, and we are the ones who find out first when it is wrong.