Work

Recent work

Selected projects, the constraints behind them and what changed

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 →

Engineering management

AUTODOC · 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
view case →