Engagements

Three ways to engage us, all under contract.

Every engagement runs on written scope, milestone acceptance, and formal IP transfer. capped at four active engagements per quarter, so a confirmed start date is capacity that has already been reserved for you.

Model 01

Fixed-Scope Delivery

A defined outcome delivered against a signed statement of work: fixed deliverables, milestone schedule, acceptance criteria, and change-control terms.

Best for
A discrete build, integration, or platform migration with a known end state.
Commercial model
Fixed fee, invoiced against milestone acceptance
Governance
Named delivery lead, weekly demo and written delivery note
Model 02

Dedicated Capacity

Reserved senior engineering capacity working to your roadmap in sprint cycles, with scope agreed sprint by sprint rather than fixed upfront.

Best for
Continuous product development where priorities move faster than a fixed SOW allows.
Commercial model
Monthly capacity fee, minimum three-month term
Governance
Sprint planning, demo, and retrospective on a fixed cadence
Model 03

Managed Support & Advisory

Ongoing ownership of a live system: defect resolution, patching, monitoring, and periodic advisory on architecture and roadmap decisions.

Best for
Live systems that need guaranteed continuity without a permanent in-house team.
Commercial model
Tiered monthly agreement, 30-day notice
Governance
Contracted response targets by severity, monthly service report
Contracting

How an engagement is put in place

Four steps from first conversation to signed statement of work. We work under your paper where your legal function requires it.

Contracting terms agreed before work starts
01

Mutual NDA

Signed before any technical detail is exchanged. Ours or yours — we sign your paper where legal requires it.

02

Scoping engagement

A structured technical discovery producing a written scope, architecture direction, risk register, and cost band.

03

MSA and statement of work

Commercial terms, IP assignment, confidentiality, and liability agreed once in a master agreement; each project runs as a SOW beneath it.

04

Delivery and acceptance

Sprint-based delivery with milestone acceptance, then a documented handover of code, credentials, and infrastructure.

Security & data handling

Commitments we make on every engagement

These are operating commitments, not certifications. Where your organisation requires a security schedule or supplier assessment, we complete it as part of contracting.

Access, secrets and data handling under guard

Confidentiality

Mutual NDA before technical discovery. Client material is never used as a public reference without written approval.

Least-privilege access

We request the narrowest access needed, scoped per environment, revocable by you at any time, and removed at handover.

Credential handling

Secrets are held in managed secret stores, never in source control, tickets, or chat. Production credentials remain in accounts you own.

Code and IP ownership

All work product and IP transfer to you on payment. Repositories, documentation, and pipelines are delivered under your organisation.

Change control

Reviewed pull requests, protected main branches, and versioned releases so every production change is attributable and reversible.

Continuity

Automated backups with tested restores, documented runbooks, and a handover pack written so another team could take over.

Sectors

Where our work concentrates

  • Financial operations & fintech
  • Professional services
  • Healthcare operations
  • Logistics & field services
  • B2B SaaS
  • Retail & e-commerce

Discuss an engagement

Send the outline and we will respond within one business day with a scoping proposal or a straight answer on fit.

Request a scoping call