Inference Public

Engagements

A delivery model
that fits your team.

Agree what needs to be delivered, who owns the decisions and how we work together.

Architect presenting a target architecture to senior leaders in a government meeting room.

Defined delivery projects

An agreed piece of engineering, from design through implementation and acceptance.

When it fits
The outcome can be described in advance: a landing zone, a migration wave, a deployment path, a recovery capability.
What we take on
Delivering the agreed scope, the engineering decisions within it, and the evidence that it works.
What you provide
A service owner who can accept the work, access to the environments and people involved, and timely decisions.
How it starts
A statement of work: scope, deliverables, dependencies, milestones, acceptance criteria and how changes are agreed.
Working rhythm
Regular demonstrations of working increments, a short written progress report and a shared risk and decision log.
Ending
Acceptance against the agreed criteria, documentation and runbooks, and a handover session with the team who will run it.

Embedded specialists

An architect or engineer working inside your team, on your backlog.

When it fits
Your team owns the work but needs a particular skill, or more capacity in one area, for a defined period.
What we take on
The agreed role and objectives, working to your team’s practices and priorities.
What you provide
A clear mandate, a reporting line, access, a backlog and the authority the role needs to be effective.
How it starts
Agreed role, objectives, onboarding steps and duration. The first week is spent on access, context and a first small change.
Working rhythm
Your team’s ceremonies, plus a regular check on objectives with the person the specialist reports to.
Ending
Handover of work in progress, documentation of anything only the specialist knew, and pairing on it before leaving.

Technical leadership

Architecture and engineering direction for a programme or platform.

When it fits
Several teams or suppliers need consistent technical direction, or decisions are stalling.
What we take on
Architecture decisions, design review, technical standards and hands-on contribution where it unblocks delivery.
What you provide
Agreed decision authority, access to the people who set priorities, and an escalation route.
How it starts
Agreeing which decisions this role makes, which it recommends and which it escalates, and how they are recorded.
Working rhythm
A regular design review, a visible decision record, and time spent with the teams doing the work.
When people disagree
Options and trade-offs are written down, a decision is made by whoever holds the authority, and the record shows why. Disagreements that cannot be resolved are escalated, not left open.

Contingency and transition

Time-limited engineering continuity through a capacity gap, a departure or a supplier change.

When it fits
A key engineer is leaving or unavailable, a supplier contract is ending, or delivery has stalled and needs steadying.
What we take on
Keeping agreed engineering work moving within a defined service boundary, and capturing knowledge as we go.
What you provide
The service boundary, the critical knowledge holders while they are available, access, and the changes we may make.
How it starts
Agreeing priorities, permitted changes, working hours, escalation and the exit criteria.
Working rhythm
Short, frequent check-ins on priorities and risks, with knowledge written down as it is learned.
Ending
An agreed exit or handover to a permanent team or new supplier. The supplier transition checklist covers what to secure.

Availability, staffing and working hours are agreed for each engagement. We do not offer emergency call-out or round-the-clock incident response. Knowledge transfer and a clear handover form part of every engagement.

Comparing the models

Which one fits?

Comparison of engagement models
ModelWho directs the workDefined byEnds with
Defined projectWe do, within the agreed scopeDeliverables and acceptance criteriaAcceptance and handover
Embedded specialistYour teamRole, objectives and durationHandover of work and knowledge
Technical leadershipShared, by agreed decision authorityDecision rights and review cadenceDecision record and successor
Contingency and transitionYour service owner, within a boundaryPriorities, permitted changes, exit criteriaAgreed exit or handover

An illustrative example

The first fortnight.

How an embedded or contingency engagement typically begins. This is an example of the shape, not a promise of availability or timing.

  1. Days 1–3: access and scope. Accounts, repositories and tools; the service boundary; who decides what.
  2. Days 3–5: current risks. What could go wrong with the service now, and what nobody else knows how to do.
  3. Week 2: backlog and decisions. Agree priorities and the first decisions that need making.
  4. Week 2: a first reviewable change. Something small, shipped through the normal process, to prove the path works.
  5. Throughout: knowledge transfer. Pairing and short written notes as things are learned, not saved for the end.

Start a conversation

Let’s talk about what you need to build.

Bring the service, the constraint or the engineering question. We’ll work through a sensible starting point.

Discuss specialist capacity