Why generic systems get abandoned
The failure is rarely technical. A system asks for data the business has never recorded, in a sequence that does not match the working day, and reports in a format the owner does not read. Within a quarter, staff are back to the old spreadsheet and the system becomes a compliance exercise.
- Data entry demanded at a point where nobody has the information yet.
- Reports built for an accountant, while the owner wants a single number.
- Approval steps that formalise a decision already made in person.
Designing around how the business runs
We start with what the owner looks at each morning, then work backwards to what has to be captured to produce it. Anything that cannot be captured at the moment it happens is either automated or left out of the first phase.
- One page showing the numbers the owner actually checks.
- Data captured at the point of the transaction, not reconstructed later.
- Approval limited to the cases that genuinely need it.
Succession and continuity
A family business that has run on memory has a continuity risk that is not usually written down: if the person who knows the customer relationships and the informal credit terms is unavailable, the business slows down. Recording that knowledge is often the real reason to build a system.
- Customer credit terms and history recorded against the customer.
- Supplier and pricing relationships documented, not held by one person.
- Operating procedures stored where staff can find them.
Delivery scope
Most family business engagements start with one module and expand. Ordering or receivables first, then inventory, then reporting. The scope document states what will be live in which quarter.
- Order and receivables on one record.
- Inventory with count and variance.
- Owner reporting page.
- Staff roles and access control.
