Building Software: MVP, Mobile, Web and Migration
This hub is for the person who will be technically accountable for the thing that gets built — a CTO, a tech lead, an operations head who has become the de facto product owner.
The decisions covered here are the ones that are expensive to reverse: how much belongs in a first release, whether mobile means an app or a responsive web page for people wearing gloves on a shop floor, what to do with fifteen years of data in a system whose vendor no longer answers email, and where an integration will break at three in the morning.
The lens stays the same as everywhere else on this site: what changes for the business. A stack choice matters because of hiring, maintenance and how quickly a change request becomes a deployment — not because of what is fashionable. An architecture decision is a business decision with a technical vocabulary.
Where we hold an opinion, it comes from having built and maintained these systems for clients in manufacturing, distribution and services. Where the honest answer is "it depends", the posts say what it depends on, which is more useful than a recommendation that ignores your constraints.

How to Choose the Right ERP Integration Pattern
A technical framework for choosing between API-first, event-driven and batch sync when connecting ERP, CRM and shop floor systems.
Read the note →
Mobile App or Web Dashboard for Shop Floor Operations
Decide mobile vs web for shop floor tools by where the user physically stands, not by platform trends. A role-by-role way to choose.
Read the note →
Designing a Reporting Architecture for Multiple Sources
Decision criteria for technical leads: when direct database queries are still fine, and when you need a dedicated reporting layer instead.
Read the note →
Technical Debt in an Internal Tool: When to Pay It Down
Technical debt in an internal ops tool is decision-capability debt. Price it, prioritise it, and pay it down without stopping the business.
Read the note →
How to Choose a Tech Stack When the Business Has to Live With It
Stack choice isn't about frameworks. It's about who can maintain the system after the developer who built it leaves.
Read the note →
Role-Based Access Is Not a Feature, It's Your Org Chart
Generic admin/user roles cause permission sprawl at scale. Map access from real approval authority instead, before writing permission code.
Read the note →
How to Scope an MVP for an Internal Operations Tool
Internal MVPs succeed or fail on the decisions they remove from daily judgement, not the features they ship. Here's how to scope one properly.
Read the note →
Migrating Off a Legacy ERP Without Stopping the Shop Floor
A phased, parallel-run approach to ERP migration that keeps production running while the old system is retired in stages, not overnight.
Read the note →Rather see where you stand today?
Ten questions, about three minutes, no sign-up. You see your stage and your weakest area as you answer.