Services

How I can help

Four ways to work together, from a two-week audit to a long-term architecture partnership. Each one has a defined scope, clear deliverables and a price agreed before the work starts.

01

Architecture & cost audit

Fixed scope · 2–3 weeks

An independent review of your cloud platform: where the money goes, where the risk is, and what to fix first.

Talk about this

When it makes sense

  • The cloud bill grows faster than the business
  • Incidents or slow releases point to structural problems nobody has time to map
  • A second opinion is needed before a large investment, a migration or a due diligence

What you get

  • Architecture, cost and risk findings, ranked by business impact
  • A prioritised roadmap with effort and expected savings per item
  • An executive readout for decision-makers and a working session with the team
02

Cloud modernisation

Project · multi-month

Legacy systems moved to a modern, cloud-native platform in increments, with the business running.

Talk about this

When it makes sense

  • A legacy monolith holds back releases, hiring and scaling
  • A move to the cloud, or between clouds, has been decided and needs someone to lead it
  • A previous migration stalled halfway and has to be finished

What you get

  • Target architecture and a migration plan cut into releasable steps
  • Hands-on technical leadership of the team that executes it
  • Automated infrastructure, delivery pipelines and monitoring left in place, owned by your team
03

Fractional architect

Retainer · monthly

Senior architecture judgement on call, for companies that need it every week but not full time.

Talk about this

When it makes sense

  • The team is strong at delivery but has no one accountable for architecture
  • Key technical decisions are made under pressure, without a second pair of eyes
  • Leadership needs a technical counterpart for vendors, partners and investors

What you get

  • A fixed number of days per month, with agreed response times
  • Design reviews and architecture decision records for every relevant choice
  • Technical input for hiring, vendor selection and roadmap planning
04

AI adoption for engineering teams

Assessment · pilot · rollout

AI brought into how your team builds software, with guardrails and measured results.

Talk about this

When it makes sense

  • Developers use AI tools on their own, with no shared practice or policy
  • Leadership expects productivity gains and needs evidence, not anecdotes
  • A product feature based on AI has to reach production safely

What you get

  • An assessment of where AI pays off in your delivery process, and where it does not
  • A pilot with one team, measured against a baseline
  • Working agreements, security guardrails and a rollout plan for the rest of the organisation

How it works

From first call to delivery

  1. 01

    Conversation

    A 30-minute call about your situation and what a good outcome looks like. No preparation needed.

  2. 02

    Proposal

    A written proposal within days: scope, deliverables, timeline and a fixed price or monthly fee.

  3. 03

    Delivery

    Work in short cycles with visible results, and a single point of contact from start to finish.

Not sure which one fits?

Tell me where you are and where you need to be. The first conversation is free and commits you to nothing.

Let’s talk