Sign in

Jeremie C.

@jeremieca.bsky.social
572 followers 379 following 408 posts

🚀 3 Makers working on 🇫🇷 💬 uniqrate.com - Analytics & feedback for blogs 🔔 notifizz.com - Notifications for SAAS

PostsRepliesMedia
Jeremie C. @jeremieca.bsky.social · 25/05/2026
We built a tool to find and qualify marketing opportunities across the entire web → 0 AI cost (no API usage) → 0 social network API cost → 0 hosting cost → Gold data for your business and marketing ! Want to know how we did it? Reply "GROWTH", I'll send you a DM. #buildinpublic
060
Jeremie C. @jeremieca.bsky.social · 25/05/2026
Thank you, coming from you with you pro background, it means a lot. 🔥
000
Jeremie C. @jeremieca.bsky.social · 24/05/2026
Excellent project good luck on it ! Clinician softwares are very hard market. Very closed. But once you succeed it’s also very locked in so good luck on it !
000
Jeremie C. @jeremieca.bsky.social · 21/05/2026
Notifizz Notifications on Autopilot for Saas Teams
010
Jeremie C. @jeremieca.bsky.social · 20/05/2026
En conclusion, je pense que l’aspect non déterministe dérange le plus quand l’utilisateur final est à son contact.
000
Jeremie C. @jeremieca.bsky.social · 20/05/2026
Dès lors l’expérience d’un user donné se met à dépendre d’une variable aléatoire. Et bien que les renforts qui peuvent être mis en place pour itérer jusqu’a un résultat satisfaisant pour l’utilisateur soient réels. Ces itérations coûtent du temps et donc dégradent in fine l’expérience utilisateur.
100
Jeremie C. @jeremieca.bsky.social · 20/05/2026
Ok pour la generation de code, cela peut s’entendre. Mais le non déterminisme est un problème lors de l’intégration d’IA dans un parcours UX classique. Car pour la première fois, le parcours n’est pas garantie et n’est pas testable.
100
Jeremie C. @jeremieca.bsky.social · 10/05/2026
Knock makes you redeploy. Customerio duplicates your data. We are building the third option at Notifizz. #buildinpublic www.indiehackers.com/post/knock-m...
indiehackers.com
Knock makes you redeploy. Customer.io duplicates your data. We built the third option.
I'm Jérémie, CTO of Notifizz. 3 founders. Bootstrapped. Built from France. We just turned down our first VC offer.Here's the bet.The notification market...
041
Jeremie C. @jeremieca.bsky.social · 10/05/2026
Beautiful representation of your agents configurations ! How are you doing it ?
110
Jeremie C. @jeremieca.bsky.social · 04/05/2026
Don't want to write the enricher yourself? Use a native integration : HubSpot, Stripe, and more landing every week. Notifizz holds no customer data. Privacy friendly by default. Save weeks on GDPR compliance for large projects.
020
Jeremie C. @jeremieca.bsky.social · 04/05/2026
"Ok but what if my event is missing data? What if I only have a `customerId` and not the customer details?" Plug an **enricher**: a webhook you implement once, that Notifizz calls in real time to pull exactly what each campaign needs. No data duplication, no sync jobs.
210
Jeremie C. @jeremieca.bsky.social · 04/05/2026
With Notifizz I’m building the simplest way to send notifications. Nothing else comes close on the market.🔥 client.track(event, { ...props }) That single call triggers all campaigns you built in the dashboard on this event. ⬇️
110
Jeremie C. @jeremieca.bsky.social · 04/05/2026
😢
000
Jeremie C. @jeremieca.bsky.social · 04/05/2026
Existing email editors are too granular for AI to generate consistent templates across the user journey. Working on Notifizz email editor today. Trying to build the first mail editor usable by AI & humans. Design is still very complex but fundamentals are there. Let simplify it. #buildinpublic
040
Jeremie C. @jeremieca.bsky.social · 03/05/2026
What are you expecting from a good multi channel notification product ? ⁉️ Trying to figure out if notifzz could have a free plan for indie hackers (built for larger teams first) 🆓 #buildinpublic
041
Jeremie C. @jeremieca.bsky.social · 27/04/2026
Or just solve a problem you have yourself. Lot of project success based on it.
130
Jeremie C. @jeremieca.bsky.social · 26/04/2026
I just read your article. LinkedIn is very sensible. 😬
110
Jeremie C. @jeremieca.bsky.social · 26/04/2026
Why ? What happens on LinkedIn ?
120
Jeremie C. @jeremieca.bsky.social · 26/04/2026
Forg sounds cool. Is it free ?
110
Jeremie C. @jeremieca.bsky.social · 25/04/2026
Seriously ? How ? Curious to know !
100
Jeremie C. @jeremieca.bsky.social · 25/04/2026
Thank you ! I’ll hope to spend good time here and also get my x account back. So I can benefits from both community 🤞
110
Jeremie C. @jeremieca.bsky.social · 25/04/2026
I reply to people on Buildinpublic hastag. To message I find interesting.
310
Jeremie C. @jeremieca.bsky.social · 24/04/2026
Btw I love you description « delete your account if you are an ai » hahaha
110
Jeremie C. @jeremieca.bsky.social · 24/04/2026
Thats an excellent things that give me hope to find a good place to build here. Thank you !
100
Jeremie C. @jeremieca.bsky.social · 24/04/2026
I agree. And honestly, I’m just disgusted by X. There are AI replies and bots everywhere doing propaganda or running follow/unfollow strategies. And people like me, who never spam anyone, just get banned. That’s a joke.​​​​​​​​​​​​​​​​..
100
Jeremie C. @jeremieca.bsky.social · 24/04/2026
My X account has been suspended 😡 But why?! 16 years of manual posting replies likes shares I took a 1.5y break, and the moment I come back and start replying a lot because I’m motivated to relaunch my account… I get suspended?! So now I’m thinking to come back in Bluesky instead #buildinpublic
360
Jeremie C. @jeremieca.bsky.social · 24/04/2026
Should I build in public on Bluesky or X ? #buildinpublic
250
Jeremie C. @jeremieca.bsky.social · 17/04/2026
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 ?
110
Jeremie C. @jeremieca.bsky.social · 12/04/2026
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?
010
Jeremie C. @jeremieca.bsky.social · 12/04/2026
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.
100
Jeremie C. @jeremieca.bsky.social · 12/04/2026
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.
100
Jeremie C. @jeremieca.bsky.social · 12/04/2026
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.
100
Jeremie C. @jeremieca.bsky.social · 12/04/2026
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.
100
Jeremie C. @jeremieca.bsky.social · 12/04/2026
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.
100
Jeremie C. @jeremieca.bsky.social · 12/04/2026
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.
100
Jeremie C. @jeremieca.bsky.social · 12/04/2026
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.
100
Jeremie C. @jeremieca.bsky.social · 12/04/2026
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.
100
Jeremie C. @jeremieca.bsky.social · 12/04/2026
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
120
Jeremie C. @jeremieca.bsky.social · 13/02/2026
Optional, see the label on the top right of the screenshot
110
Jeremie C. @jeremieca.bsky.social · 04/10/2025
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 💪
110
Jeremie C. @jeremieca.bsky.social · 19/09/2025
This is definitely not a complex use case. It’s a bug!
020
Jeremie C. @jeremieca.bsky.social · 16/09/2025
Install of MacOS Tahoe and iOS 26 in progress ! #buildinpublic
031
Jeremie C. @jeremieca.bsky.social · 13/09/2025
Cool your are next to the end. And yes. Too many feature is a usual mistake. 😅
010
Jeremie C. @jeremieca.bsky.social · 13/09/2025
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 ?
120
Jeremie C. @jeremieca.bsky.social · 13/09/2025
Like in Interact?
110
Jeremie C. @jeremieca.bsky.social · 13/09/2025
Yes, we have to ship faster.
110
Jeremie C. @jeremieca.bsky.social · 13/09/2025
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
051
Jeremie C. @jeremieca.bsky.social · 12/09/2025
5+ social media ! But how can you manage and be as active as you are on all these accounts 😮😮😮
110
Jeremie C. @jeremieca.bsky.social · 12/09/2025
Maybe you started later but you literally explode everything now with your newsletter and audience. 🚀
110
Jeremie C. @jeremieca.bsky.social · 12/09/2025
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
140