Written scope. Milestone billing. On time.

The method

We ship, refine, and ship again.

Most software shops promise perfection and deliver silence. We work the other way round: something real in your hands early, improved in the open, delivered on the date we wrote down.

1. 01

   Ship

   A working version of the most painful process in front of your staff on the date written into the scope — websites in 12 days.

2. 02

   Refine

   We watch it run, fix what the real work exposes, and extend it — with you, not for you.

3. 03

   Ship again

   Each milestone goes live on its date. Then the next one. The system grows while it earns.

Straight answers

What happens if you miss the date?

The date is in the scope you signed, and milestones are billed only after they are live. A late milestone is not an invoice you have to argue about — you have not paid for it yet.

Who owns the code?

You do, from day one. That includes the pilot, whether or not you continue with us afterwards.

What does a pilot cost?

A pilot is two weeks, fixed price, and covers one process. If you continue, it becomes milestone one rather than a sunk cost.

What happens after handover?

You get the code, the accounts and a walkthrough with the people who will use it. Support after that is agreed in writing rather than assumed.

Can we stop?

Yes. There is no long contract. You keep what has been delivered and paid for, and there is nothing further to settle.

Do we have to replace what we already use?

No. Most engagements start by connecting what is already in use rather than replacing it. Replacing something is a decision you make later, if it is worth it.