Not Another Inbox: What Dazza Follow-Up Is Supposed to Do With Connected Information
If connecting more systems just gives you a bigger inbox, we have solved the wrong problem.
One of the easiest ways to ruin Dazza Follow-Up would be to turn it into another place full of messages.
You already have email.
You may already have website enquiries, accounting notifications, supplier portals and messages from customers.
DFU does not need to recreate all of that.
The source is not the follow-up
An email is a source.
A website form is a source.
A quote or invoice is a source.
The follow-up is the obligation that comes out of it.
Maybe you are waiting for a customer to approve something. Maybe somebody is waiting for you to answer. Maybe an invoice has reached the point where you want to review it. Maybe a form submission needs a call back.
DFU should care about that loose end, not force you to live inside a duplicate copy of the source system.
Keep the original system responsible for the original record
This separation is important.
If the source is Dazza Books, the quote or invoice remains a Dazza Books record.
If the source is a website, the form remains a website submission.
If the source is email, the conversation remains in email.
DFU should hold the follow-up context and point back to where the work came from.
That keeps the product narrow and stops it drifting into a giant all-in-one business suite.
The secretary should summarise, not bury you
A good secretary does not dump every piece of paper on your desk and say, “There you go — connected.”
They tell you what actually needs attention.
That is the model behind the DFU secretary view: what needs attention, what you are waiting on, who is waiting on you, what is overdue, what has been snoozed and what can wait.
As more connector work is added, that filtering becomes more important, not less.
More sources means more responsibility
Every new source creates another chance for noise, duplicates and wrong assumptions.
So the measure of progress is not simply how many services appear on the Connections screen.
The useful measure is whether DFU can turn those sources into a smaller, clearer list of genuine loose ends.
That is one of the reasons the connection program still has substantial testing ahead of it.
The product promise stays narrow
DFU is not a new inbox.
It is not a CRM.
It is not project management.
It is not marketing automation.
It is being built as the secretary for the loose ends: who are you waiting on, who is waiting on you and when does the follow-up need to happen?
If the connections eventually make that answer clearer, they are useful.
If they just give you more things to read, they are not.
Comments