Skip to content

Consulting

Start a project, or borrow the judgement to scope one.

I work on enterprise data platforms and the AI built on top of them. Most of the value is not in picking a model — it is in the architecture around it: where the data comes from, who is allowed to see it, what breaks the build when it drifts, and whether anyone can reconstruct why a number is what it is six months later.

Eight years across engineering, consulting and enterprise architecture — PwC, CANCOM, ORBIS — plus my own practice run alongside them. Austria-based, remote or on-site.

Engagements

Four ways in.

  1. 01

    Hourly

    Advisory

    Pressure-test a decision before it becomes an architecture.

    Working sessions on a specific decision — build versus buy, platform selection, how to structure a migration. You get a written summary with the alternatives named and the trade-offs stated, plus async follow-up. Usually a handful of sessions rather than an ongoing engagement.

    • · Written summary per session
    • · Named alternatives and trade-offs
    • · Async follow-up
    Placeholder Rate for advisory Priced per engagement — ask

  2. 02

    Fixed scope

    Technical diagnostic

    A bounded review of a platform that is not behaving.

    Three to five days looking at an existing data or AI platform: architecture, data flow, governance, evaluation and the failure modes nobody has written down. Ends in a ranked findings document and a walkthrough with the engineers who have to act on it.

    • · Ranked findings document
    • · Engineer walkthrough
    • · Fixed scope, fixed price
    Placeholder Rate for technical diagnostic Priced per engagement — ask

  3. 03

    Per engagement

    Project delivery

    Design and build the platform, not just the diagram.

    End-to-end delivery of a data or AI platform — requirements, architecture, pipelines, governance and handover. Azure, Microsoft Fabric, Databricks, AWS. Specification first, fixed price against it, working software and documentation at the end.

    • · Written specification up front
    • · Working software
    • · Handover documentation
    Placeholder Rate for project delivery Priced per engagement — ask

  4. 04

    Monthly retainer

    Fractional architect

    Senior data and AI architecture without the headcount.

    Technical direction for teams that need architectural judgement more often than they need another full-time architect: platform strategy, vendor evaluation, reviewing what the team is building, and translating between engineering and the people funding it.

    • · Technical direction
    • · Vendor and build-versus-buy strategy
    • · Stakeholder translation
    Placeholder Rate for fractional architect Priced per engagement — ask

Process

Three steps, and you can stop after any of them.

  1. 01 A short call Thirty minutes to work out whether this is a problem I can actually help with. Free, and I will say so if the answer is no.
  2. 02 A written specification Scope, approach and price in writing before anything is built. Charged, and credited against delivery if we go ahead.
  3. 03 Visible progress Work lands in your repository as it happens, not in a status deck at the end of the month.
Placeholder Current availability Add earliest start date and capacity

Start here

Tell me the problem before the solution you had in mind.

An email with the shape of the problem, the stack you are on and roughly when you need it is enough to work out whether a call is worth either of our time.

[email protected] LinkedIn ↗