How we work.

Five rules you can see in every project we do, and a clear first step at a fixed price.

How we work.

  1. 01

    First, we understand how you work.

    Before we write any code, we go through how the work really happens with your people. They try the design before we build it.

    Example For Acta, we made four clickable prototypes with 155 screens, and a traffic law expert went through them too.

  2. 02

    The system keeps things in order.

    The system follows the process we agree on. Nobody has to check whether a step was skipped.

    Example In the SACMI system, a single big bag has 20 states and 8 decision points, all generated from diagrams.

  3. 03

    Careful with what's already running.

    When we change a system your work depends on, we do it without bringing your operations to a halt.

    Example At Sanindusa, we raised the number of tests from 20 to 3,400 before we touched production.

  4. 04

    Results you can check.

    We show you improvements in numbers from your own operations, not in promises.

    Example For Acta, we measured that a single CPU handles 24.9 fines per second, and we know where the headroom is.

  5. 05

    We stay after launch.

    We keep maintaining, fixing and developing the system as your needs change.

    Example The SACMI system has had 24 releases in 14 months in production.

A fixed-price first step.

  • Initial analysis1–2 weeks · fixed priceWe map out what you need and tell you what it will cost and how long it will take.
  • Performance audit2 weeks · fixed priceWe find out why your system is slow and suggest what to fix first.
  • Typical project3–9 monthsFrom the first meeting to a system your people work with every day.
  • SupportmonthlyWe look after the system after launch: fixes, changes and quick help when you need it.

How we get started

  1. 01

    A short call

    30 minutes, free. You tell us what's slowing you down, and we tell you how we'd approach it.

  2. 02

    Analysis or audit

    A fixed-price first step with a clear deliverable. After it, you know what, how much and when.

  3. 03

    Delivery in stages

    The system grows in working pieces. We regularly show you what's new, and we adjust priorities together.

  4. 04

    Operations and support

    Deployment, monitoring, fixes and further development, as agreed.

Ways to work together

  • Fixed-scope project

    When the brief is clear. We agree on scope, price and deadline.

  • Ongoing development

    When the system grows along with your company. You pay for the time worked and change priorities as you go.

  • Extra hands for your team

    For companies that develop their own software, or machines that run on software. We plug into your repository, processes and deadlines.

  • Support and operations

    Monthly: fixes, updates, monitoring and further development.

Frequently asked questions

Do you work with smaller companies too?

Yes. We start with a small fixed-price step, so even a smaller company knows what it's getting into before it commits to a bigger project. Often, connecting the tools you already have is enough.

Can you take over an existing system?

Yes. First we cover it with automated tests and measure where it loses time. That's how we handled the production system at Sanindusa, which runs around the clock.

Who will own the code?

We agree on code ownership and licensing in the contract, before any work starts.

Will you sign an NDA?

Yes, happily, even before our first detailed conversation.

Do you also work on site?

When the project needs it, we come to you. We do most of the work remotely.

What technologies do you use?

Most often .NET and C#, Angular, Kotlin Multiplatform, PostgreSQL and SQL Server, Docker and Kubernetes, and CI/CD in Azure DevOps and GitHub. We build websites with Next.js.

Do you use AI?

In development, yes, as a tool that helps write and review code. But every change is covered by automated tests and goes through our review. We only put AI into your system where it brings a clear benefit.

What if there are only two of you?

We build systems so that another team can take them over: automated tests, documentation and deployment are part of the delivery. For larger projects, we can team up with trusted partners.

Want this running at your company too?

Tell us what's slowing you down today. We'll get back to you within one business day and tell you how we'd approach it.