# Clarity before code. Accountability through delivery.

> AI should make delivery more capable, not more mysterious. Our approach makes the decisions, tradeoffs, constraints and proof visible from the first engagement through handover.

Canonical URL: https://marmation.com/approach/

## The decision

What is the next decision worth funding?

Start with the smallest piece of work that resolves a material uncertainty or delivers a useful capability. Give it an artifact, an acceptance boundary and someone with authority to decide what follows.

## The situation behind the request

When a client already has systems, data, users and procurement requirements, an exciting model demo is only one input. A strong project needs a boundary around the first problem and a shared understanding of what is included.

## Where the obvious solution falls short

Rushing into a fixed-price build before requirements are settled increases scope change and technical risk. At the other extreme, indefinite strategy workshops can consume budget without bringing the organization closer to working software.

## How we would approach the work

We begin with the business job and its operating conditions; compare buy, build, extend and integrate; validate the hardest assumption; engineer a tested vertical slice; then transfer the agreed knowledge, source and operational control.

## What the engagement may include

- Frame the business job and measurable success.
- Architect the data, product experience, model and system choices.
- Validate with representative cases, including failure.
- Engineer, test, deploy and document the system.

## The choices worth making explicitly

Each project can enter at the right stage. An established product team with a clear specification should not be forced into an unnecessary workshop. A vague transformation concept should not skip decisions essential to responsible delivery.

## What we would test before calling it ready

Every funded milestone should have deliverables, scope, dependencies, acceptance criteria and a client-side decision owner. Human review and security controls are planned, not retrofitted.

## A sensible first step

The first useful engagement is the smallest one that resolves a material uncertainty or delivers a working capability.

## Related reading

- [Build the capability. Keep control of what belongs to you.](https://marmation.com/approach/client-ownership/)
- [Resolve the question before funding the build.](https://marmation.com/engagements/decision-and-architecture-sprint/)
- [Built for the decisions that turn technology into working software.](https://marmation.com/about/)