I work in a legal/compliance role where missing a filing deadline can create real headaches. For years, I watched teams juggle UCC filings, PPSA/PPSR registrations, trademarks, insurance certificates, and domain renewals using a mix of spreadsheets, calendar reminders, and hope. It always felt brittle. If one person was on vacation or updated the wrong tab, something slipped.
A few months ago, I finally tried building a lightweight fix instead of complaining about it. The result was a simple Excel-based expiry tracker that monitors filings across multiple entities and sends email alerts as deadlines approach. It calculates renewal windows, handles overrides, and keeps everything in one place. Nothing fancy. Just practical.
I originally built it for myself at work, but the more I used it, the more I wondered if others had run into the same issues: juggling important dates across scattered systems, dealing with alert fatigue, and trying to keep the logic transparent so people actually trust the tool.
Here’s what I’m trying to figure out now:
• When you design a workflow meant for non-technical users, how do you keep things simple without hiding the logic they need to trust the output?
• Have you hit pitfalls when building automated alerts, like people tuning them out?
• If you’ve built internal tools before, how did you validate the problem beyond your own experience?
I put together a quick demo video here if you want to see how it works:
https://youtu.be/5f1uXenbq7o
I’m still iterating, still learning Excel’s quirks, and trying to understand whether something like this is useful beyond my own niche. Any perspective or critique is welcome.
This is a solid first build — tools that seriously reduce deadline anxiety often feel simpler than they end up being valuable.
Curious — as you iterate on this, what specific user behavior are you treating as the first sign that it’s genuinely useful beyond your own workflow?
For example:
Those kinds of leading signals often show whether simplicity and trust are both sticking.
Thanks! That’s a great way to frame it — I’ve been thinking much more about leading signals than outcomes like “missed fewer expiries,” which take a long time to verify.
The first signal I’m watching is whether people put real deadlines into it and then stop double-tracking them elsewhere. When someone deletes their parallel calendar reminder or spreadsheet tab, that’s a big trust signal for me.
A second early indicator has been stability after entry — fewer follow-up edits and fewer “just in case” overrides once the logic is set up. When users leave an entry alone and let the alerts run, it tells me the transparency is working.
I’m also paying attention to how people react to alerts: not just clicks, but whether they act on them without needing a manual check first.
Still very early, but I’m trying to treat trust-building behaviors as the real milestone before worrying about scale.