Copy a link to this pageThe canonical URL, on the clipboard↵ run
Copy this page as a Markdown linkTitle and URL, ready to paste into notes↵ run
Switch between the dark and paper themesFollows your system setting until you change it here↵ run
Clear what this palette remembersForgets which pages you open most. Stored only in this browser↵ run
Print this pageThe print stylesheet drops the navigation and expands links↵ run
Loading the indexIf this does not finish, the full index is a page.
↑ ↓ move↵ open> actions? helpAll shortcuts

Work with me

Five shapes. Most people start with the teardown, because it is the one that ends in a decision rather than a commitment.

I do not run general platform engineering, infrastructure, security or SRE.

  1. AI readiness teardown

    A three-week fixed-fee assessment of your data and AI stack that ends in a decision, with a written verdict you keep whatever you decide next.

    Duration
    3 weeks
    Commitment
    Roughly 8 days of my time, spread across three weeks
    Price
    On request

    Not for

    • Companies with no data team yet. There is nothing to assess and I would be an expensive way to buy a dashboard.
    • Anyone who needs a board deck by Friday. Three weeks is three weeks.
    • Organisations that have already decided and want the assessment to agree.
  2. Forward deployed engineer

    I join your engineering team, work in your repository, and ship the AI system myself. Six to twelve weeks, ending in something running in production.

    Duration
    6 to 12 weeks
    Commitment
    3 to 4 days a week, inside your engineering team
    Price
    On request

    Not for

    • Staff augmentation. I take one problem to production, and a body-shop brief is the wrong instrument for that.
    • Anyone who cannot give an outside engineer repository access. Without commit rights this becomes advisory work with a longer invoice.
    • Teams who need general platform engineering, infrastructure, security or SRE. I do not run those in any engagement.
    • Companies who want a permanent hire on a trial. I leave at the end, and the leaving is planned from week one.
  3. Interim CTO, or Chief Data & AI Officer

    I take the seat, own the layer AI runs on end to end, hire the person who replaces me, and spend the last month handing over.

    Duration
    6 to 12 months
    Commitment
    2 to 3 days a week, inside your leadership team
    Price
    On request

    Not for

    • Anyone who needs general platform engineering, infrastructure, security or SRE leadership. I do not run those, and "CTO" normally implies all of them.
    • Companies looking for a contract-to-hire route into a permanent role. I leave, and the leaving is the point.
    • Anyone who wants the executive seat and the building hands in one engagement. Pick the seat or the forward deployed work, because two days a week does not cover both.
    • Organisations where the real problem is that leadership does not want the answer the data gives.
  4. Data product management, installed

    Twelve to sixteen weeks to build the data product management function: the role, the hiring loop, the intake process, proven by shipping real products.

    Duration
    12 to 16 weeks
    Commitment
    2 days a week
    Price
    On request

    Not for

    • Teams under about ten people in data. You do not need a product layer yet, you need clearer ownership.
    • Companies that want the title without the authority. A data product manager who cannot decline a director is an expensive coordinator.
  5. Data governance and AI readiness

    Eight to twelve weeks to a written position that holds up in an audit, a data room, or a regulator conversation, with controls built into the pipelines.

    Duration
    8 to 12 weeks
    Commitment
    2 days a week
    Price
    On request

    Not for

    • Anyone who wants a compliance opinion. I am not a lawyer and this is an operating checklist, not legal advice.
    • Organisations looking for a policy document to file. If nobody changes what they do, you have bought paper.

Start

Thirty minutes, no deck. Tell me what is going wrong and I will tell you whether I am the right answer. Often I am not, and I will say so.

Start a conversation