The right engagement model isn't a preference to state at the start of a conversation — it's a conclusion that follows from what's actually true about an organisation's situation right now: how defined the problem already is, how much of the work needs to live inside the organisation afterward, and how much senior judgement is needed on an ongoing basis rather than once.

A team that already knows exactly what needs to be built is usually better served by a project than by a standing team; a standing arrangement makes more sense once the roadmap itself keeps generating new judgement calls, not just execution. Neither is a better commercial arrangement than the other — they answer different situations, and the same organisation is often well served by different models at different points.

This isn't something an organisation is expected to work out alone against a matrix. It comes out of the same current-state assessment described on How We Work — the honest starting point determines which model fits, not the other way around.

Project Delivery fits a genuinely defined initiative — a system, a migration, a redesign — where the outcome can be stated and measured in advance. Therefore, the engagement has a start and an end, not an open-ended retainer dressed up as a project.

Revni owns delivery for the duration: shipping end-to-end, tested, with a rollback path, and the decision record for every consequential call made along the way. Governance is scoped to that one initiative — reviewed at the points the project itself defines, not folded into a wider cadence that outlives the work.

Dedicated Teams fits sustained, multi-quarter work where the roadmap itself keeps generating new decisions, not just new tickets — the constraint isn't one deliverable, it's ongoing capacity integrated into how the organisation already ships.

Responsibility shifts here: the team operates inside the client's own delivery cadence rather than around it, and governance becomes a shared discipline — joint review points, not a single project close-out. Continuity comes from the same named-owner and decision-record practice described on How We Work, applied continuously rather than once.

Fractional CTO fits an organisation that needs senior technology leadership on an ongoing basis but doesn't have — or isn't ready to hire — a full-time executive for it. Therefore, this model doesn't centre on shipping code; it centres on a standing decision register and a weekly leadership cadence.

Governance here looks different from a delivery engagement: vendor oversight, architecture and roadmap decisions, and the register itself are the primary output, not a production system. Responsibility for what gets decided sits with Revni in this capacity, but responsibility for what gets built, and when a build is warranted, stays a joint call with the client's own team.

Strategic Advisory fits a bounded question — a roadmap, a due-diligence review, a turnaround assessment, a pre-hire transition — where what's actually needed is a defensible answer, not an ongoing team. Therefore, this is the one model with no delivery component at all.

Revni's only responsibility here is the assessment and its documented rationale; nothing gets built, and nothing about the client's systems changes as a direct result of the engagement itself. Governance is a single review point: the assessment is checked against the evidence it used, not against a delivery outcome, because there isn't one.

The most common real pattern across Revni's practices starts small and deliberate — an assessment or a discovery sprint — and expands into a build or a standing team only once that first stage has actually proven the approach, not on a schedule set in advance.

The reverse happens too, and it's treated as a success rather than lost business: a Dedicated Team steps back down to Advisory, or ends altogether, once the client's own team can carry the work forward without it — consistent with the same no-dependency principle that governs every model, not an exception to it.