Project-based delivery

When the outcome can be described clearly and you want one company to be responsible for reaching it: a defined application, an integration, a migration. If your priorities will keep changing, or the work has no natural end, a dedicated team usually fits better.

Against acceptance criteria we write and agree with you before the build starts. At each milestone we demonstrate the work and you test it against those criteria. If something does not meet them, we fix it. When everything in scope meets its criteria, you sign off the milestone or the project.

Requirements often change, and that is fine. Each change goes through change control: we describe the change, its effect on cost and on the plan, and you decide. Nothing changes the scope, the price or the dates without your written approval.

That depends on the scope, the number of systems and teams involved, how quickly decisions are made, and how ready third parties such as banks or vendors are. After discovery we give you a plan with milestones and their dependencies, and we report against it throughout the project.

A well-defined scope can be priced as a fixed price for that scope, with changes handled through change control. Where the scope is less certain, we price discovery separately and then the build, or work on time and materials with a budget we report against. You see the price and the timeline before we start.

Intellectual property in the work we build for you is yours from the first commit — no assignment step at the end. That covers the custom software, designs and documents delivered for you. Any existing tools or libraries of ours used in the project stay ours, are named in the contract and are licensed to you.

You choose. We can hand the system over to your own team with documentation and walkthroughs, or keep supporting and developing it under a support agreement or a dedicated team. We agree this before the project ends, so there is no gap.