Method

How we commit

Each page below maps to an actual clause in our contracts. It is verifiable in due diligence — and it is what separates us from a time-and-materials sale.

Fixed-price development: what the model actually puts on each side

A billing model is not an administrative detail: it decides who loses money when a project slips. Fixed price moves that risk to the supplier, time and materials leaves it with the client. Both are defensible — provided you know which situation you are in before signing.

Phased delivery with formal acceptance: how a project actually runs

A software project is not judged on its opening schedule but on what happens in month four, when a forgotten rule surfaces and the switchover date is closing in. Batch delivery and formal acceptance exist to make that moment manageable rather than adversarial.

Reversibility and source code ownership: what the clause has to say

"The source code is yours" is the most repeated and least verified sentence in software proposals. The gap between an enforceable assignment of rights and a carefully worded licence only becomes visible when you try to leave — which is to say, too late.