# How we work

A steady rhythm, short lines and something you can look at or use after every step.

## 1. Discovery

We map your goal, your users, your existing systems and your data. For AI questions we immediately test whether the problem suits AI, or whether ordinary software is cheaper and more reliable.

You get: a scope, the risks and a proposal with planning and price.

## 2. Design

We design the architecture and, where there is a screen, the user experience. Decisions about hosting, data residency, models and security are written down with the reason.

You get: an architecture sketch, wireframes and a decision log.

## 3. Build

We build in short iterations. Every change goes through a pull request, automated checks and a preview environment, so you follow along with working software instead of status reports.

You get: working software you can test every iteration.

## 4. Handover and operations

After go-live we stay involved: updates, monitoring, security patches and further development. If you prefer to run it yourself, we hand over with documentation and runbooks.

You get: documentation, runbooks and a team that knows your system.

## Principles we do not deviate from

- **Change additively.** We do not break a live system. New fields and routes are added; existing ones keep working until nobody uses them.
- **AI with a human at the wheel.** We use AI agents to build faster. An agent does not merge on its own and does not change production data; a human approves every change.
- **Decisions on paper.** Every architecture choice has a recorded reason, so the next team, or you, can later understand why things are the way they are.
- **Fail closed.** If a security or privacy rule cannot be guaranteed, the request stops. It does not silently fall through to a less safe route.

---
Source: https://mg-devs.nl/en/approach/
