Signs the spreadsheet has run out
The same customer lives in a spreadsheet, a chat thread and a paper file. Managers ask people for updates instead of reading a screen. Documents are rebuilt by hand each time. Nobody can say quickly where an order stands. None of these is a crisis on its own; together they are the signal that several teams now depend on one shared record.
Follow one customer from end to end
Before choosing features, map the journey: first contact, follow-up, booking, delivery and after-sales. For each step, write down who touches it, what they need to see and what they must record. The system is the shared record of that journey.
Build the spine first, then the modules
Sales, service, parts and accounts look like separate screens, but they describe one customer story. Start with the spine — customer, order, delivery — and let each module hang off it. That keeps data consistent and makes later modules faster to add.
Give every role its own portal
- Sales staff need leads and follow-ups, not accounts.
- Managers need approvals and team performance.
- Back-office teams need orders and documents.
- Leadership needs one summary across teams or locations.
Role-based portals reduce noise and keep sensitive data in front of only the people who need it.
Make documents a by-product
Quotations, vouchers and delivery notes should be generated from the record in one branded format, not retyped. It saves time and removes a common source of mistakes.
Plan for several locations from day one
If the business has more than one branch or showroom, keep each location’s data separate while giving leadership a combined view. Retrofitting that separation later is far more expensive than designing it in.
Add notifications and reporting early
Reminders make sure follow-ups happen, and a dashboard answers “where are we?” without a meeting. They are small features that change how a team works every day.
Test what must not break
Approvals, calculations and permissions are where mistakes cost money. Automated tests on those paths are worth the effort, because they let the system keep growing without breaking what already works.
A good business system is quiet: it makes the next step obvious for each person and the whole picture visible to the people who run it.