Index

I build products,
systems and occasionally
unnecessary things

Work, side projects and the occasional detour

What I do

I build software and lead engineering teams. A lot of my work starts with figuring out why something is stuck. Sometimes a team is waiting for another team’s API. Sometimes people are copying the same information between spreadsheets and tools because nothing connects.

I help work out what needs to happen and stay involved through implementation. I’ve done this as an engineering manager and working directly with businesses. I also build tools for myself, some of which you’ll find here.

Recent work

BUSINESS SYSTEMS · 2025—NOW

Building the digital operating layer of a small insurance broker

I’m helping a small insurance broker connect its systems and build software for its customers and partners. My work runs from figuring out what people need to making technical decisions and coordinating delivery.

The website, CRM, communication tools and management reporting are running. The customer and partner products are still at different stages of development.

Inside the project

BEFORE / MANUAL HANDOFFS

  • CRM
  • Spreadsheets
  • Messaging
  • Email
  • Telephony
  • Legacy website
  • Manual commissions

CURRENT LAYER

Customers · Partners · Internal team

  • New website
  • CRM
  • Team communication
  • Telephony
  • B2B
  • Admin
  • B2C
  • Commission tool
  • Reporting / automation

Marketing · Sales · Operations · Management.

FIG 01 / FROM FRAGMENTED TOOLS TO CONNECTED OPERATIONS
view case →

AUTODOC / ENGINEERING MANAGEMENT · 2024—2026

Four engineers, a PHP monolith, and APIs that didn’t exist yet

I managed four frontend engineers working on a migration out of a PHP monolith. Some APIs were still being built; one had no owning team. I worked on those dependencies, the team’s delivery practices and people development.

Two direct reports progressed to the next grade. The new frontend did not reach production during my tenure.

Inside the project

My team

Four direct reports.

  • Three on modules and pages
  • One with the Principal Engineer on the core platform

The Principal Engineer led platform architecture.

What a page needed

Data
An API owner and an agreed contract, or a feasible path through the monolith.
Existing behaviour
The details in PHP, old tickets and people’s heads.
Review
Time from QA and SEO, planned with the implementation.
FRONTEND WORK AND THE DEPENDENCIES AROUND IT

Before committing to a page, I checked who owned its data and when QA and SEO could review it. Where feasible, we agreed an early contract, used fixtures or planned a legacy data path. Some dependencies stayed unresolved.

view case →

Current experiments

Working together

I’m open to engineering management or hands-on technical roles. I also take on selected independent projects and would like to meet people interested in building something together.

  • With a team

    I can join as an engineering manager or in a hands-on technical role. My experience includes helping a team ship when its work depends on other teams, unfinished APIs and an existing system that still needs to run.

    Talk about a role →
  • On a project

    If your business runs on tools that barely talk to each other, I can help work out what needs to change and build the software to connect them. That includes understanding how people do the work today.

    Discuss a project →
  • On something new

    If you know a problem well and want to build a product around it, I’d be interested in talking. We could work out what a first version needs to do and build from there.

    Build something →

about