The 4–8 Week Pilot Project

Fixed price. Defined scope. Working software at week 1.

Week 1

Discovery and architecture

Stakeholder interviews. Data model. Technical architecture. First deployable spike on real data.

Weeks 2–4

Core build

Daily commits. Weekly demos. Stakeholder review at week 3. Iterative feedback loops.

Weeks 5–6

Refinement

Performance optimisation. Security audit. User acceptance testing. Documentation drafts.

Weeks 7–8

Production deploy and handover

Production cutover with monitoring. Training session. Documentation handover. Decision point.

What you own at the end

The codebase — Git repository under your organisation

The data — exported in standard formats, no lock-in

Infrastructure access — EU-hosted, on Hetzner by default

Operational runbook and incident playbook

Test suite and CI configuration

Decision point at the end

At week 8 we run a mutual decision call. Two outcomes only: continue into a managed engagement, or wrap cleanly with handover.

There is no auto-renewal, no surprise invoice, no quarterly commitment baked in. The pilot ends when the pilot ends — what comes next is a separate, written agreement.

The 4–8 Week Pilot Project

What you own at the end

Decision point at the end

Discuss a pilot