Blog
Writing on ERP, LMS, CRM, custom software, automation, and the questions that come up before a build.
These notes are about operational software, not a catalogue of every technology. They sit next to how we take a brief from discovery to a system the team can own, and the ERP, LMS, CRM, and related work we actually take on.
17 September 2026
A generic ERP is the right starting point for many organisations. A custom system is worth it when the process itself is the product, and the package is already being bent around it.
17 September 2026
An LMS fails when courses, progress, and admin tools are hard to finish. Usable learning software is built around the people who teach, take, and run it.
17 September 2026
A CRM that nobody updates is not a customer system. Design the record and the flow so sales, support, and accounts can keep it current.
17 September 2026
An MVP is a first version with only the paths that matter. It should be enough to test with real users, and small enough that you have not already over-built.
17 September 2026
A useful brief names the people, the tasks, and the systems already in place. Feature lists without that picture lead to software nobody can own.
17 September 2026
Automation is useful when a step is stable, named, and repeated. It is a poor substitute for an unclear process, and it should not hide the work from the people who own it.
17 September 2026
AI is a fair question for operations software. It is not a substitute for a clear process, trustworthy records, and an interface people can finish work in.