About

KAIHITO combines two Japanese words: 開 (kai) — to open, to unlock, to begin — and 人 (hito) — human being. Opening and people. Together they describe what we do: open up systems so people can actually work with them.

Technology alone opens nothing. A system only becomes effective once people understand it, trust it and let it into their day. That is why people are not at the end of a project, but at its centre.

The red seal is our mark of quality. In Japan, the hanko stands for a personal commitment: whoever seals, stands behind the result. We place it where we take responsibility — not as decoration.

KAIHITO grows out of running an IT company: responsible for delivery, sales, marketing and team at the same time — with a daily view of what actually makes initiatives fail.

That is where the focus on leadership, organisation and a way of working that enables performance without consuming people comes from. Async collaboration, clear decision paths and psychological safety are not ideals here; they are the conditions under which complex projects work.

KAIHITO FlexCo will be founded in September. Until then, this site is mainly one thing: a place where the position can be read.

We are not a full-service agency offering everything at once, and not a pure code supplier that disappears after go-live.

Independence is not a side effect for us, it is part of how we build: data, identity and business logic stay with the client. We favour open source and self-hostable building blocks so nobody ends up dependent on a vendor whose pricing, data location and exit risk they cannot steer.

And we say what an initiative will not solve. We prefer one core slice into production over a concept phase — and afterwards someone inside the organisation should be able to answer for it, not us indefinitely.

We work in bounded cuts with a fixed window: a tenant and permission model, an audit-proof history for one process, provability ahead of an audit. Complexity gets cut until something workable stands — not until everything has been considered.

Foundational work without a fixed point drifts. So we tie it to an initiative someone inside the company actually wants: a deal, an audit finding with a deadline, a customer with security requirements. And we only work as a business-and-tech tandem. If nobody from the business carries the decisions with us, we say so early.

What we are not the right answer for: general contracting for your entire IT, business-critical core systems that require references at a comparable scale, pure capacity at an hourly rate, and “modernisation” without a concrete trigger. We would rather say that upfront than in month three.