Build
Multi-tenant business platforms and bespoke line-of-business systems, modelled on your rules rather than a vendor’s idea of your industry.
01The problem
Most operational software fails in one of two ways. Off-the-shelf products force your process into someone else’s model, and the gap gets filled with spreadsheets. Bespoke builds solve that but calcify — every new client or site needs a fork, and within three years nobody can safely change anything.
02How we approach it
We model the business rules explicitly, in the database, before any interface exists. Client-specific behaviour is handled by configuration and extension on a shared codebase rather than by forking the product. That is the discipline that decides whether a platform is still maintainable at its fifth customer.
03What you get
04How it runs
Sit with the people doing the work. Document the rules that actually govern decisions, including the exceptions nobody wrote down.
Schema, keys, constraints and transaction boundaries. Get this right and the application layer becomes straightforward.
One working module at a time, in production use, rather than a big-bang release eighteen months out.
Test against real data, train the users, document the runbook, stay available when it meets reality.
DOTERP — our own multi-tenant ERP, ten modules on a shared schema, in production build for a heavy-civil contractor.
05Where we have done this
Tell us what the system has to do and where it currently breaks. You will get a reply from the engineer who would do the work.