Custom software built around your process, with AI doing the heavy lifting.

Systems, web applications and integrations built from the ground up, for when off-the-shelf software makes you change how you work instead of supporting it.

Some processes cannot be served by an off-the-shelf product without twisting the process itself. When that adaptation effort exceeds the cost of building, building is the sensible option — and the cheaper one over time.

How we decide between buying and building

We add up the licences, the cost of adapting the product and the cost of adapting your process to it. Where an existing product covers the essentials, we integrate it and build what is missing around it. Building from scratch is justified when the process is the competitive advantage or when no product keeps up with it — and that is where most of our work happens.

How we build

• Stack. Angular on the client, .NET on the server, Oracle or PostgreSQL for data, containers on Kubernetes. Mature technology with a real hiring market — not the newest thing.
• Continuous delivery. Usable versions early, so feedback arrives while changing is still cheap.
• Multi-entity and permissions from day one. Adding these later means rewriting half the system.
• AI where it adds something. Search, suggestion, classification — when it solves a real problem. Not as a sales argument.

What you get

• The application in production, with a documented and reproducible installation.
• The source code and the database, yours, with no closed components stopping another team from carrying on.
• An operations manual: how to deploy, how to recover from a failure, where to find the logs.
• Training for the team that will use it and the team that will maintain it.

We also rebuild legacy systems

Migrations of Delphi or Access applications, and of spreadsheets that grew until they became critical. The rule we follow is to preserve known behaviour first, including the quirks the team already relies on, and only then improve. Changing everything at once is the most reliable way to lose the trust of the people who use it.

Frequently asked questions

Do you work on fixed-scope projects or time and materials?

Both. A stable, well-defined scope works well as a fixed project; an evolving product works better in iterations with priorities reviewed as you go.

Do you maintain the system after delivery?

Yes, under a maintenance agreement. But the system is delivered in a state where another team could maintain it — that is the proof it was built well.

Do you build corporate websites?

Yes, including multilingual, search-optimised sites. This site is an example: static HTML, one page per language, with no third-party dependencies slowing the load.

← All services