On the one hand, the SaaS model is dead. On the other, everyone's building one. Whichever narrative you subscribe to, this might seem like a strange time to build PixelWatcher. So why am I doing it?

A few reasons in this short thread ⬇️

1️⃣ I don't believe in the SaaSpocalypse. A certain type of SaaS is indeed in trouble – the one with crazy-high margins. But there's room for products that strike the right balance between price and convenience. That's the balance PixelWatcher aims for
2️⃣ A lot more people are building software right now. But that's still a tiny fraction of the population, and there's a huge gap between running a prototype locally and launching a real product in production. Very few will get there
3️⃣ The website-monitoring landscape is competitive. Many established players already occupy the space. But that's how PixelWatcher was born – from the frustration of using them. Too complicated, too expensive. I'm building the product I want
4️⃣ Recent AI progress is both amazing and scary. I do worry about the broader societal impact, but I’m choosing to see these tools as an opportunity. If we’re entering a period of creative destruction on an unprecedented scale, I’d rather be on the creative side
I expand on these thoughts in this article: https://yellowraincoat.co.uk/blog/why-im-building-pixelwatcher/
Why I’m Building PixelWatcher

In many ways, it is a strange time to be building a SaaS. This article addresses some common concerns and further explains my approach with PixelWatcher.

PixelWatcher is a website monitoring service. Give it a URL, describe the change you care about, and PixelWatcher notifies you when it happens. As a beta user, you’ll get a free account with generous limits.

Register here for early access: https://pixelwatcher.io/

PixelWatcher – Never miss a change

We're building a smarter and cheaper way to track what matters on the web. Sign up to get early access.