How We Work Together

Engagement Models

Three shapes of engagement depending on what you need. Each starts with a conversation, not a contract.

Smallest commitment

Advisory

A specific engineering question, thoroughly answered.

Bring a defined problem: an architecture review, a technical audit, a design decision that needs an expert second opinion. We analyse it, document it, and give you a clear path forward. No ongoing obligation.

  • Architecture review & risk assessment
  • Technical due diligence for acquisitions or vendor evaluation
  • Codebase audit with written findings
  • Pre-project design session
1–3 days
Start with a question
End-to-end delivery

Project

A scoped piece of work, delivered from start to production.

Scope is defined together before anything begins. Both sides agree on what is being built, what done looks like, and what the timeline is. Then we build it. No ambiguity about what was agreed.

  • New system or application build
  • Legacy modernisation or .NET Framework migration
  • Integration or automation project
  • Architecture-first design, delivered to production
Typically 4–16 weeks
Discuss your project

How an engagement begins

No lengthy intake forms or sales sequences. Three steps from first contact to work underway.

01

A conversation

We talk through the problem in enough detail to actually understand it — the system, the constraints, the history, and what you are trying to achieve. Most of the conversation is us asking questions. By the end, both sides have a clear picture of the situation and whether working together makes sense.

02

A written proposal

Scope, approach, timeline, and pricing in one document. No verbal commitments, no surprises later. You have a clear picture of exactly what you are agreeing to before anything starts. Questions at this stage are expected and encouraged.

03

Work begins

Once both sides are aligned, work starts on the agreed date. For retainers, capacity is reserved from day one. For projects, the first milestone is set before the first line of code. You will know what is happening and when throughout.

What every engagement includes

  • Direct communication with the engineer doing the work
  • Written documentation of decisions, architecture, and findings
  • Code built to be maintained without a dependency on us
  • Honest assessment of risks and trade-offs throughout

What is out of scope

  • Third-party licence fees and hosting costs
  • Ongoing maintenance beyond the agreed engagement (unless renewed)
  • Work that falls outside the agreed scope without a change discussion first

Before you reach out

Do you work with fixed-price projects?

Yes, for clearly scoped work. Scope is defined together before anything is agreed, so both sides know exactly what is being built and what done looks like.

Can you work alongside an existing in-house team?

Yes. Most engagements involve collaboration with in-house developers, product owners, or other consultants. The model adapts to how your team is structured.

What does a typical engagement look like end to end?

A short discovery conversation to understand the problem. A written proposal with scope and approach. Work begins once both sides are aligned. For projects, milestones are agreed upfront.

Do you take on multiple clients at the same time?

Retainer clients get reserved capacity that is not available to other engagements. Advisory and project work is scheduled to avoid conflicts. You will know in advance what the arrangement looks like.

Not sure which model fits?

Describe what you are working on. We will tell you what makes sense.

Start a Conversation