Services

Three ways of working together — usually they overlap.

Tech modernisation

Most businesses are running on tech that's grown by accident — a mix of tools bolted on over the years, none of them quite talking to each other. Either as a set project or starting with a review of what you've got, I work out what's actually holding you back and update or replace it, sequenced so it doesn't disrupt the business while it happens.

  • Fixed-scope project, or a review-then-build engagement
  • Updating or replacing outdated systems and tools
  • Modernisation roadmap, sequenced to avoid disruption

Best for: businesses whose tooling hasn't kept pace with how they've grown.

Process digitalisation

If a process still lives in someone's head, a spreadsheet, or an inbox, it doesn't scale. I map how your business actually operates, then design and build digital processes that remove the manual steps, reduce errors, and give you visibility over what's happening and when.

  • Workflow mapping and bottleneck analysis
  • Digitalisation of manual/spreadsheet-based processes
  • Visibility and reporting built in from the start

Best for: teams whose critical processes depend on one person remembering the steps.

Bespoke software

Off-the-shelf software makes you adapt to it. I build software the other way around — tools designed specifically for how your business works, so your team spends less time working around the system and more time using it.

  • Requirements scoping around real workflows
  • Staged delivery, with working software at every checkpoint
  • Handover and support once it's live

Best for: businesses where the right tool for the job simply doesn't exist yet.

How I work

The same four stages, whether it's a set project or a review-then-build engagement — a tech update, a new process, or a piece of software.

  1. 1. Discover

    Understand the business problem, the systems already in place, and the constraints around them — before proposing anything.

  2. 2. Align

    Agree scope, priorities, and what success looks like with the people who'll actually use the result, not just whoever signs it off.

  3. 3. Build

    Design and deliver in stages, with something working at every checkpoint — not one big reveal at the end.

  4. 4. Embed

    Support the rollout, train the team using it, and hand over something that keeps working without me.

Not sure which one you need?

That's fine — most projects start as a conversation, not a fixed brief.

Get in touch