Blog

Notes on building software that has to last.

Architecture, APIs, automation, and the unglamorous decisions that keep a business system maintainable after launch.

Mar 12, 2026

Decisions

When custom software is the right call — and when it is not

Buying a tool is often the cheaper path. Custom software earns its keep when the process is the business, the data model is specific, or the workarounds are already costing more than a build.

8 min read

Feb 3, 2026

Architecture

Designing APIs that other systems can actually use

A usable API is a product contract: stable resources, boring errors, and failure modes that operators can see. Cleverness is optional. Predictability is not.

7 min read

Jan 16, 2026

SaaS

SaaS architecture that you can still change in year three

Multi-tenancy, billing, and permissions are not features you sprinkle on later. They are the load-bearing walls. Keep them simple, explicit, and boring.

9 min read

Nov 21, 2025

Operations

Automating operations without creating a brittle mess

Useful automation makes the happy path faster and the exception path visible. Hidden scripts that email “success” are how operations lose a day.

6 min read

Oct 8, 2025

Technology

Choosing a stack for a business web application

The right stack is the one a small team can operate in two years. For a lot of business software, that still looks like Laravel, a relational database, and as little client-side complexity as the interface requires.

8 min read

Aug 19, 2025

Delivery

What software maintenance actually looks like after launch

Launch is the start of ownership. Maintenance is not a vague retainer for “tweaks.” It is monitoring, small changes, dependency hygiene, and a way to decide what not to build.

6 min read

Next step

Building something that needs this kind of thinking?

Tell us about the workflow, the constraint, and the people who will use the software. We will tell you whether a build is the right next step.

Start a project See selected work