Skip to content
Manifesto · est. 2026

Building software means taking
responsibility
for the people who use it.

Work desk with manifesto pages, governance notes and responsibility checklist
manifesto as practice, not slogan

Security, clarity and maintenance need to show up in decisions and deliveries.

A portal should help a customer complete a task. An app should fit the team’s routine. A new system needs a reason to exist. We believe engineering starts there, before choosing a tool.

We work with small and medium businesses, including owners who follow a project without an in-house IT team. Our role is to turn an idea into understandable decisions and deliveries that can be reviewed.

The software we aim to build:

  • Solves a concrete problem. We start with its users, the task and what needs to work better.
  • Protects the information it needs. Access, data use and risks belong in the project, not in a review left until the end.
  • Can be maintained. Tests, documentation and recorded decisions help the people who will operate and improve the solution.
  • Respects people. We involve users and pay attention to clarity, accessibility and error situations.

Artificial intelligence is one of the available tools. When it fits, we define sources, boundaries and review proportionate to risk. When an application or a simple rule works better, we do not add AI to justify the project.

Delivery is more than the appearance of a screen. We need to agree on how the software enters use, who looks after it and what maintenance includes. We prefer clear scope to a promise no one can verify.

We want to build technology that makes sense in the work of the people using it.