Hello world
The first post on the SeenShift blog, on why watching a page yourself is a bad use of a person, and what we are building instead.
Every so often you find yourself waiting on a web page. A price that might drop. A release page that might finally say something. A form that might open. A number somebody else controls and you cannot influence, but very much need to know about.
So you do the only thing the web offers you. You come back and look again. Then again the next day, and a few more times that week, until either the thing happens or you quietly give up and find out about it too late from someone else.
That is what SeenShift is for.
Say it once, in a sentence
You give SeenShift a public page and one plain sentence about what you are waiting for. Tell me when this drops below 220 francs. Tell me when this stops saying sold out. Tell me if a new model gets announced here.
There is no selector to pick, no rule builder to learn, and nothing to configure per site. SeenShift reads your sentence, works out what on the page it refers to, and checks it on its own schedule from then on. When the answer changes, you get an email. When it does not, you hear nothing at all, which is the entire point.
Quiet by default
The hard part of watching a page is not noticing that it changed. Pages change constantly. Banners rotate, timestamps tick, related items shuffle, an entire template gets rebuilt over a weekend. A tool that emails you every time the bytes differ is worse than no tool, because now you have a second inbox to ignore.
So SeenShift is built around a narrower question than “did this page change”. It asks whether the specific thing you named changed, and it treats a rebuilt page carrying the same answer as no news. That decision shapes almost everything else, from how pages are fetched to how often, to what counts as worth an email.
What comes next
We are in early access, which means the product is real, the list is short, and the roadmap is still genuinely movable. This blog is where the thinking behind it will show up. Expect posts on how the scheduling works, why checks cost what they cost, what happens when a site says no, and the failures that were interesting enough to write down.
If you want in, request access. If you already have an account, your monitors are here.