Ask Claude to fix it :D

But first news for me (I was not here for a long time) :

you are coding! What are you coding ?

Most tools aren’t there yet.

That’s the problem we’re solving with Notifizz.

👇 What’s the one thing missing most from your current notification setup?

8 / It should be a product artifact.

Not plumbing.

Designed. Intentional. Governed. Measurable.

The same way you think about your UI, your pricing, your onboarding.

Notifications are a layer of your product. Treat them like one.

7 / It should be built for agents.

Not bolted on. Designed for it.
A dev agent. A market agent. A data agent.

Each covering their part of the journey, without stepping on each other.

That only works if the product underneath was built for the whole team first.

6 / It should handle pressure automatically

How many notifications did this user receive this week?

If your system doesn’t know, it’s already sending too many.

5 / It should measure what actually matters

Not opens. Not clicks on non-clickable notification

Did the user do the thing the notification was asking for?

That’s the only conversion that counts.

4 / It should require no redeploy.

New condition? No dev ticket.
New channel? No sprint.
Copy change? Done in minutes.

If shipping a notification takes days, your system is broken by design.

3 / It should work with fresh data.

Not data from the moment the trigger fired. Data from the moment the notification lands.

User context changes. Your notification should know that.

2 / It should have clear ownership.

Product owns lifecycle.
Marketing owns promotional. Dev owns transactional.

Not because of politics, because intent matters.

Mixing them is how you lose control of your user relationship.

1 / It should be visible.

Every notification live in production. Who created it. Why. When. What it does.

Not in the codebase. In a shared interface every team can open.

THREAD
Most SaaS notification systems in 2026 still look like 2018.

Scattered code. No ownership. No visibility. No metrics.

Here’s what a notification system should actually look like today. ⬇️🔥

#buildinpublic

Optional, see the label on the top right of the screenshot

Same for me.

And I’m working on it to fix it. 😅
We have probably something to prove to ourselves when times are hard.

Good luck with that 💪

This is definitely not a complex use case.

It’s a bug!

Install of MacOS Tahoe and iOS 26 in progress !

#buildinpublic

Cool your are next to the end.

And yes. Too many feature is a usual mistake. 😅

Oh I understand. I never built an extension before too ! Good luck on it.

How many time of work do you still need before to ship ?

Like in Interact?

Yes, we have to ship faster.

Hard to keep motivation some days.

I’ve been procrastinating for a week and I hate this feeling.
Notifizz new version is close to the finish line, but summer holidays broke my rhythm.

And you, are you staying motivated these days?

#buildinpublic

5+ social media ! But how can you manage and be as active as you are on all these accounts 😮😮😮

Maybe you started later but you literally explode everything now with your newsletter and audience.

🚀

At 15 I launched my first project
At 23 I was freelancing before graduation
At 30 I became a CTO & got married
Now I’m building SAAS in public

I bought fast growing real estate
took legal action
and traded markets

Life isn’t just about SaaS

Tell me your story !

#buildinpublic

Sadly, I don’t like coffee 🚪

Maybe record your training and sent video to an AI could work.

Haha I see.

How do you market it ? Crowded market no ?

Feel alone on your projects? 😢

3 months ago I teamed up with MathCam4 and DamCosset on Uniqrate & Notifizz. 💙

Finding the right team is hard! I tried several co-makers before.

But it’s worth it. Now it’s time to deliver! 🚀

Share your story ! ⬇️⬇️⬇️

#buildinpublic

Impressive congrats !

Curious about how many users you have?

You just disappear from my X feed. That’s why I though you stop. But I realized you worked hard on it.

💪