Insights

Practical thinking about the systems underneath the business.

Short, useful guidance on deciding what to automate, when to integrate, when to build, and how to recognize operational problems before they become expensive.

Operations6 min read
01

When a spreadsheet becomes an operational risk

How to tell when a useful spreadsheet has quietly become critical business infrastructure — and what to do next.

Read article →
Systems6 min read
02

You probably do not need another SaaS product

Why the missing piece in many businesses is the operating layer between software products, not another subscription.

Read article →
Automation7 min read
03

What should a business automate first?

A practical way to prioritize automation opportunities without starting with the flashiest technology.

Read article →
Buying software7 min read
04

How to know if you actually need custom software

A decision framework for choosing between process changes, off-the-shelf software, integration, and a custom build.

Read article →
Integration6 min read
05

The hidden cost of employees copying data between systems

Manual re-entry looks inexpensive because it is distributed across the day. In aggregate, it can become a major source of waste and operational risk.

Read article →
Strategy8 min read
06

Build vs. buy: when custom software earns its cost

A practical comparison of buying software, integrating existing tools, and building a custom operational system.

Read article →
Operations7 min read
07

Who owns a business system after launch?

Why maintenance, onboarding, training, documentation, and roadmap ownership matter after custom software goes live.

Read article →
Delivery7 min read
08

How to phase a custom software project without building half a product

A practical way to divide a larger systems roadmap into useful releases that create value before the entire platform is finished.

Read article →

Start with the problem

What is the business doing manually that it should not be?

Technology experience

Tools I use to build.

Languages, frameworks, databases, cloud platforms, and development tools I use to design and build business systems.

Next.js
React
TypeScript
JavaScript
Python
HTML5
CSS
PostgreSQL
Supabase
Google Cloud
BigQuery
GitHub
Vercel
WordPress
Security & data practices

The stack matters. How it is configured matters more.

Business systems can contain sensitive operational and customer information. I design around practical controls such as least-privilege access, secure credential handling, authorization boundaries, environment separation, logging, and recovery planning appropriate to the project.

Read Security Practices →
01

Least-privilege access

Users and services are given only the access their role or workflow requires.

02

Secure credentials

API keys, service credentials, and environment secrets are kept out of public source and client-side code.

03

Protected data flows

Encrypted connections and appropriate authorization controls are used for production data paths where supported.

04

Environment separation

Development, staging, and production concerns are separated when the project risk and scope call for it.

05

Validation & auditability

Business rules, permissions, input boundaries, logging, and failure handling are treated as part of the system design.

06

Recovery planning

Backup, retention, and recovery responsibilities are defined according to the system and the agreed scope.

Security controls are scoped to the needs of each engagement. Formal compliance or certification requirements should be identified during discovery and documented in the applicable statement of work.