Skip to content

Engagement models

Sized to the problem, not to a rate card.

We publish no consulting prices, because scope sets them. You get a written proposal with the model, deliverables and price before anything starts.

More hands on what you are already building

You know what to build but lack senior hands. We join your team for a set period; the work stays yours.

Shape.
Part- or full-time inside your process, or a scoped project with milestones you sign off.
Length.
Weeks to months, with an end date
Models.
Embedded engineering · Project-based
  • Senior engineers in your tools from the first week
  • A written plan with milestones, each signed off in the portal
  • Documentation and hand-over, so the work outlasts us

An audit, then a fix list you can act on

The cloud bill, reliability, a platform nobody owns. A fixed-scope assessment ranks the findings and plans the fix.

Shape.
A defined scope and named deliverables, agreed before it starts.
Length.
Weeks
Models.
Assessment · Advisory
  • Findings ranked by risk and effort, for engineers and budget holders
  • A remediation plan with owners and an order of work
  • An optional implementation phase, scoped from the findings

We run it with you

The platform needs to keep improving: an architect a few days a month, or a retainer, with the same engineers.

Shape.
A retained number of days per month, with an agreed backlog and a standing review.
Length.
Ongoing, month by month
Models.
Fractional platform / cloud architecture · Managed improvement retainer
  • A standing review and a backlog both sides can see
  • Continuity: the same people, with the context, each quarter
  • Reviews, upgrades and improvements done, not only recommended

The models

Six ways to work together.

Every model ends with documentation and knowledge transfer.

Advisory

Senior guidance, reviews, architecture decisions and design sessions.

Best for. Teams that have the hands but want a second, experienced opinion before committing.

Shape. Regular sessions and written reviews, scoped by the month.

Ongoing, month by month

Project-based

Defined scope, deliverables, milestones and implementation.

Best for. A known outcome, such as a platform, a migration or a pipeline framework, with a start and an end.

Shape. Fixed or milestone-priced, with the plan agreed up front.

Weeks to months, with an end date

Embedded engineering

Temporary infrastructure and platform engineering capacity inside your team.

Best for. Teams short of senior capacity for a period who want the work done inside their own process.

Shape. Part- or full-time for an agreed period, working in your tools and rituals.

Weeks to months, with an end date

Fractional platform / cloud architecture

Ongoing strategic and hands-on platform guidance, without a permanent senior hire.

Best for. Growing companies that need an architect's judgement a few days a month, not a full-time head.

Shape. A retained number of days per month, with continuity across quarters.

Ongoing, month by month

Managed improvement retainer

Recurring infrastructure optimization, platform improvements, reviews and engineering support.

Best for. Teams that want the platform to keep getting better after the project ends.

Shape. A monthly retainer with an agreed backlog and a standing review.

Ongoing, month by month

Assessment

A fixed-scope review of one area, with findings and a plan you can act on.

Best for. A decision that needs evidence first: a cost review, a platform review, a migration readiness check.

Shape. Defined scope, typical duration, named deliverables. It stands alone or leads into implementation.

Weeks