What Should a Good Follow-Up System Actually Remember for You?
The best follow-up system is not the one that stores the most information. It is the one that remembers the right things so you don’t have to.
G’day. Once you decide memory is not a great business system, the next temptation is to swing too far the other way. Capture everything. Add dozens of fields. Create stages, labels, notes, categories, dashboards and reports. Before long, keeping the follow-up system updated becomes another job.
For a small business, the useful question is simpler: what does the system need to remember so I can get on with the actual work?
Who, what and where did this come from?
Every follow-up needs enough context that you recognise it immediately. Who is the customer or contact? What job, quote, invoice or enquiry is this about? Did it start in email, a website enquiry, an accounting system or somewhere else? You should not have to reconstruct the whole story every time a reminder appears.
What happened last?
A reminder saying “follow up John” is not very helpful if you cannot remember whether John owes you an answer or you owe John one. The last meaningful contact matters: quote sent, customer replied, supplier promised availability, invoice reminder sent, question asked. That gives the next action some context.
Who is waiting on whom?
This is one of the most useful distinctions. Waiting on customer is different from customer waiting on us. Waiting on supplier is different again. When those states are clear, you can see which quiet conversations are normal and which ones represent something you have forgotten to do.
What needs to happen next — and when?
A good system should turn vague intentions into a next action. Call Tuesday. Check quote Friday. Chase supplier tomorrow morning. Revisit invoice after the promised payment date. The date matters because follow-up is mostly about timing. Too early can be annoying; too late can lose the opportunity.
It should know when to stop
Remembering follow-up is only useful if the system also recognises completion. Customer said no? Close it. Quote accepted? Move on. Invoice paid? Stop reminding. Customer said call again in November? Put it away until November. Nobody wants automation that keeps nagging people after the conversation is finished.
It should bring the work to you
The biggest difference between storage and follow-up is that storage waits for you to search. Follow-up should surface what is due now, what is overdue and what can wait. That is how the system starts carrying some of the mental load instead of simply becoming another place to look.
This is the problem Dazza Follow-up is being built around
The direction for Dazza Follow-up is deliberately closer to a personal secretary than a giant CRM. The aim is to keep an eye on the journey from enquiry to conversation to quote to invoice, remember the next action and bring the loose ends back to the business owner when they need attention. It is still being built and tested, so the focus right now is getting that remembering logic right rather than piling on features.
If a follow-up system can reliably answer “who needs something from me next?” without making you spend your evening maintaining it, it is doing the job that matters.
Comments