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 has two camps. Both are broken.

Camp 1: dev-only tools (Knock, Novu)

Every campaign means a code deployment. Every variable change is a ticket for engineering. Marketing is locked out by design.

Camp 2: marketing-first tools (Customerio, Braze)

6-month integration projects. Specialist consultants. Your entire user base mirrored into their cloud. You save engineering time and pay it back in GDPR exposure.

Result: dev, product, and marketing fight over the same notification from three different views.

Our bet: truly event-driven. Nobody actually does this today.

- Plug into any product event you already emit. No modification.

- Fetch fresh data at the moment of sending. No caching. No sync.

- Never duplicate the user base. Data stays in your infrastructure. Always.

Marketing ships a complex production campaign in 3 clicks. Devs keep full ownership of the events. Product sees everything in one cockpit.

Each team gets a dedicated AI agent for their workflow.

Where we are

- 3 co-founders (dev, stats, UX)

- Fully bootstrapped

- 1 pilot client live, not paying yet

- 0 paying customers

- 0 dollars raised, 1 VC offer declined

- GTM: France first, Italy from year 2

Our competitors are public companies and Series-B+ scale-ups. We're 3 people with no funding and no pressure to grow fast.

Going slow on purpose. This market needs patient, deep building. Not a runway clock.

Curious how other bootstrappers approach pacing when the incumbents have unlimited fuel. And for anyone who shipped notifications at scale: when did you realize your stack was wrong?