Show IH: We built NotiLens for our own startups - so small teams like ours never miss what matters
We were building two marketplace products with a tiny team. No DevOps. No support team. No one to watch dashboards 24/7. Just us.
We needed to know the moment a payment failed, disk space filled, CPU hit 100, a new signup came in to follow up, a verification request landed, a brand form was submitted, a cron job silently processed zero records. The kind of signals that matter but nobody catches until it's too late.
So we built a tool internally. It ran quietly in the background and told us exactly when something needed attention. Nothing more. Not a replacement for dashboards or monitoring tools - just the signal that tells you when to go look at them.
As our products grew, simple alerts weren't enough. We started hitting subtler failures - flows that started but never completed, data pipelines silently skipping syncs, automations silently skipping steps. Then AI agents entered the picture. Token budgets burning silently, agents looping with no output, LLM pipelines hanging with no error thrown. We added detection for that too - because we were running into it ourselves.
As our team grew, we needed more. ML-powered anomaly detection to catch what rules miss. On-call scheduling and escalation so the right person gets paged at the right time, automatically. We built that too.
One marketplace was eventually shut down. The other, CollabZap, is still live and still uses NotiLens today. The tool outlived one product, kept running in another, and evolved under real production pressure across a year of building.
Then we found our people - solo founders and small teams with no DevOps, no support team, no one watching dashboards 24/7, and real budget constraints. Teams like us.
That's when we knew. So we launched it as a separate product - NotiLens, a business pulse monitoring tool that catches silent failures, anomalies, and broken flows before your users do.
We'd love to connect with solo founders and small teams moving fast and wearing multiple hats. If that's you - we built this for you.
This feels stronger than a basic alerting tool because the real pain is not “send me a notification.” It is catching silent failures before they become user-facing damage.
The best positioning angle is probably around signal quality. Failed payments, stuck flows, skipped jobs, token burn, agent loops, pipeline hangs — those are all different symptoms of the same deeper problem: small teams do not have a reliable layer watching for business-critical breaks.
One thing I’d be careful with is the name. NotiLens is clear, but it may keep people thinking “notification lens” or “alert wrapper,” while the product sounds like it is becoming more of a silent-failure detection and operational signal layer.
If you want this to age beyond notifications, something broader like Exirra .com would fit the intelligence/signal layer better. The product direction feels bigger than alerts.