Skip to content

Products we built while working with clients

Both came out of a need that kept recurring in implementation projects, not from a decision that we ought to have a product. Today they run in client production environments.

Why an implementation company builds its own software

We never planned to become a software vendor. Both tools started as answers to specific problems in client projects - and only when the same problem kept returning at other organisations did we turn the proven method into code that can be deployed again. That is the reverse of a typical software company: practice came first, the product second.

How a product differs from a project

In a custom project the scope is designed from scratch and priced from scratch. A product inverts that: the core is ready and proven in production, so implementation work covers configuration, integrations and data - not building foundations. In practice this means a shorter path to first results, a predictable scope, and a roadmap funded by all users of the platform rather than a single client.

How the engagement works

Implementation, integrations and support are handled by the same team that writes the code - there is no seam between vendor and integrator, so a ticket never travels between companies. Where security policy requires it, we work inside the client's own environment.

Who this is for - and who it is not for

We build our products for mid-size and large organisations that want to solve a specific problem without replacing their system landscape. If you are looking for a global enterprise platform with an ecosystem of hundreds of partners, we will say so honestly - that is a different shelf and a different budget. Our edge is fit, pace and direct access to the team that knows every line of the code.

Get in touch