Built, Tested and Still Developing: Where Dazza Follow-Up Is Up To
There’s a big gap between “we built an app” and “we're ready to hand it to customers”.
This week I've shown a bit more of what Dazza Follow-Up actually looks like.
Not a mock-up.
Not a sales page promising fifty features.
The real product that is being worked on.
So it is probably worth finishing the week with a straightforward progress report.
The core secretary exists
The main DFU experience has been built.
You can create follow-ups.
See who is waiting on whom.
Set follow-up times.
Snooze something until later.
Pause it.
Mark something urgent.
Finish it.
See what needs attention on the secretary dashboard.
And keep a record of what has happened.
That gives us the core product we originally wanted:
A digital secretary for loose ends.
The reminder engine has had serious work
Remembering a follow-up isn't just storing a date in a database.
You have time zones.
Missed reminder windows.
Snoozed items.
Paused items.
Items that became actionable after an earlier reminder.
Urgent follow-ups.
Daylight-saving changes.
Retries.
Duplicate processing.
All the boring stuff nobody sees until it goes wrong.
A lot of work has already gone into those parts.
That's a good thing.
The user shouldn't have to understand any of it.
They should just see their secretary summary when they need it.
Real connections are being built
DFU is also no longer isolated from the outside world.
Website form intake has been built and proven in our Wix environment.
The Dazza Books connection has been built and tested.
Zoho Mail integration has been built and extensively tested, with live connection work still part of the current development program.
And more connectors are now being developed.
That last part is significant.
The more DFU can safely recognise loose ends from the tools a business already uses, the less manual admin the owner should have to do.
The Connections screen is becoming a bigger part of the product
Originally, DFU could have remained a very simple standalone reminder tool.
The more we have worked on it, the clearer something has become.
The secretary becomes much more useful when it can listen to the right places.
Not everything.
Not every piece of data.
Just the things that genuinely create a follow-up obligation.
That is the direction we are now developing.
What isn't finished?
There is still work ahead.
More connector development.
Simplifying customer connection and onboarding.
More live-provider testing.
Device and notification checking.
Final interface polish.
Regression and security checks as the integration surface grows.
And probably a few things we'll only discover when we put each new connection through real use.
That's software development.
Finding those things before customers depend on the product is considerably better than finding them afterwards.
So when is Dazza Follow-Up being released?
There isn't a release date being announced yet.
That's deliberate.
Dazza Follow-Up is under development.
There is enough working now that I can start showing you what we're actually building.
But showing progress is different from declaring the product finished.
When DFU reaches the point where we're satisfied with the important customer workflows, connections and testing, we'll be able to talk properly about what comes next.
Until then, we'll keep building it.
The promise hasn't changed
Despite all the technical work underneath, the product still has a very simple job.
Remember:
who you're waiting on;
who is waiting on you;
and when the follow-up is due.
That's the secretary.
Everything we're building around it is supposed to make that one job easier.
Not turn DFU into another giant system that takes over your business.
And that's where Dazza Follow-Up stands today:
A substantial working app.
More connections being developed.
Plenty of testing still to do.
And no pretend release date.
Comments