The work, written down
Every entry starts from a real decision we made.
Why we rebuilt a variant grid already running in production
Merlin's admin variant grid had passed development and was running in production, until one complaint from real use got it completely rebuilt within hours.
Why Merlin changed from single-tenant to multi-tenant
An architecture decision that felt final turned out to rest on a business assumption. Once the assumption changed, the decision deserved a second look.
Why Merlin's storefront was built with Astro
An online store is only useful if people can find it. That constraint decided the tool I used to build Merlin's storefront.
Why we left Laravel for Go
An overloaded server is what made us start looking for an alternative. But what kept us with Go ever since turned out to have nothing to do with that.
Identity → Transaction → Control: the thinking framework that shaped Merlin
Before Merlin settled on an architecture or a stack, we first found a thinking framework. Identity → Transaction → Control became how we understand a problem before translating it into a system.
Why we built Merlin
How Merlin began — from the operational patterns we found while talking with business owners, to the decision to build one system connecting every business process.
When does a business need a web-based operations system?
There are specific signs that a business has outgrown a manual spreadsheet's capacity. Recognize them before operational chaos becomes routine.
A guide to building a digital operations system for local businesses
A comprehensive guide to building a structured digital system foundation. Not about the latest features, but about the flow a team actually uses every day.
Professional website vs. digital system: what's the difference?
Having a website doesn't mean having a system. Learn the fundamental difference between a digital presence and the operational engine that actually runs a business.