How do your software engagements work?

Why twelve months

Good software is a relationship, not a transaction. Twelve months is long enough for us to learn your systems deeply and for the compounding to show, and short enough that you are never trapped. It is a commitment on both sides: we invest in understanding your software, you get a partner who is actually responsible for it.

Scope, change budget and the edges

The monthly price buys a change budget to move your backlog and a maintained surface we keep healthy. When something falls outside that scope, we quote it separately and you accept it before we begin — so the monthly number stays the number you agreed to and nothing is done behind your back.

Renewal and leaving

At the end of the term, we renew only by explicit agreement. There is no automatic roll-over that carries you into another year by silence. If you choose to leave, you keep a running system and everything needed to operate it or hand it to another team, and we help with a clean handover.

Straight answers.

Does the engagement renew automatically?

No. Renewal is by agreement at the end of the twelve months. We never roll you into another term by default.

What counts as out of scope?

Work beyond the agreed change budget and maintained surface — a major new product line, say. We quote it separately and you accept it before it starts, so your monthly cost stays predictable.

What do we get if we decide not to renew?

Everything: a running system, the code and its history, the infrastructure in your name, and the documentation. We help hand it over cleanly, whether to your own team or another provider.

Keep reading.

Your software. Our responsibility.