About
I built this because I could not find the tool.
I'm William. I started EngageNudge after years as a C-level tech manager in Nordic newsrooms. Getting visitors was always hard. Getting them back was worse. Web push actually worked. The products around it did not answer the questions I had.
Talk to usDon't spam your audience. Nudge them when it matters.
Someone mailed me
I had not thought about web push. Then a cold email showed up from a network that wanted to put a script on the site and push ads at readers. We said no. The channel stuck in my head. I still think about that. Most people in this market learn the same way. Someone writes. You look it up. You do not want a call.
The number on the screen
The first provider we used showed a huge subscriber base. Sends went out. I could not tell if they landed. Nothing in the product explained the gap. You pay a lot for a number you cannot trust. I got a bit obsessed with that.
Cheaper was not the fix
We moved to something cheaper that at least cleaned dead subscriptions. The channel started doing real work. People came back. Clicks were not imaginary. And still, most weeks, the list got smaller. Except when a Discover spike hid it. I asked the obvious question. Why are they leaving. The dashboard had CTR. It did not have an answer.
Minus something, again
You get used to a red week. Editors see a click rate and want another send. I saw a base that leaked. Those two views do not meet unless someone writes down what a push costs in subscribers, not only what it earns in clicks. I looked. I did not find that ledger.
You lose the argument
In a newsroom every journalist wants their story pushed. Fair. Traffic is the job. I wanted fewer, better sends. Without evidence I sounded like I was slowing people down. Volume wins that meeting. I got tired of showing up without numbers.
So I started building
Once I sat down and learned how web push actually works, the hard part was obvious. Delivery is a solved-enough problem. Judgment is not. Who should get this. Who should be left alone. What changed because you sent it. I could not buy that. EngageNudge is me trying to build it.
The person who wants restraint already exists
They just cannot win the meeting. Most tools surface the argument for sending. They hide the cost of sending. I want a line you can take into that room: this push got you the clicks, it cost you these subscribers, and here is what would have happened if you had skipped it. We are not all the way there yet. That is the job.
If this sounds familiar
I write some of this down as I go. You can read those notes, or just tell me what your list looks like.
Know when to nudge.
Know when a notification is worth sending.
The useful question is who should not get this one.