How an engagement runs, week by week.

One written scope, a steady weekly build, and a clean handover, applied the same way to every project.

Week 0

Brief

You write to us with a few sentences about the outcome you want. We read every message and reply within one working day.

You do not need a specification. A clear description of the situation is enough to start.

Week 1

We put objectives, boundaries, timeline, and price into one written scope, delivered within five working days of the brief.

Nothing is billable until both sides agree to it, and it becomes the document both sides point at for the rest of the project.

Weeks 2 to N

The people who wrote the scope build it, with a written check-in every week covering what is done, what is next, and any decision needed from you.

A scoped build reaches handover in six to ten weeks. Changes are written into the scope as they happen.

Final week

We walk through the finished work against the agreed scope and adjust where it does not fit the way you actually operate.

Done means it runs in your environment and is understood by the people who rely on it, not that it worked once in a demo.

After

You receive the working software, the source, and documentation written for a developer who was not in the room.

There is no lock-in and nothing further owed. Ongoing support is available on clear terms if you want it.

Working days from brief to written scope.

Written check-in every week during the build.

Lock-in after handover, and nothing further owed.

We reply within one working day, with a scope and a price or a straight answer that we are not the right fit.