Systems for businesses that have outgrown their tools.

Where the problem shows up

Growing businesses add tools and processes faster than they add an understanding of how those tools and processes fit together. A spreadsheet answers one question, a subscription solves one problem, and an export connects two systems, and each addition is reasonable when it is made. For a long time the arrangement works, because a few people remember how everything fits.

The difficulty arrives as the business grows. Reports disagree, repeated work fills the week, the platform depends on one person's memory, and nobody can say with confidence what the business knows about itself. What does it cost a team to spend its time reconciling and repairing instead of deciding? And how long can a business grow on arrangements that only a few people understand?

The better principle is to trace how the work and the information move, to find the smallest structural change that removes the cause, and to build it so that others can maintain it. My background in accounting shapes this: every number should have a history, every difference should be explainable, and every process should leave enough evidence for someone else to follow.

What I have changed for others

HIPAA-regulated platform: 70% less operational workload

I led a nationwide treatment platform end to end, with modular CMS workflows, automation and Dockerised infrastructure. Operational workload fell by 70%, outdated content by 80% and facility publishing time by 50%, with page loads under 2 seconds and a 100% uptime SLA. Read the case study.

500+ microsites: new site delivery in under a week

I designed a reusable publishing system with block-based pages and serverless deployment. It supports more than 500 microsites, and new website development takes less than one week. Read the case study.

6.4 million records: one reproducible research environment

I designed a PostgreSQL architecture that holds more than 6.4 million historical price records with 21 native timeframes kept as recorded. Research now runs in one environment instead of in separate files. Read the case study.