Every founder I talk to has a version of the same story. A deal goes quiet. Weeks later they find out the buyer went with a company they had never heard of. Not the big name they were worried about. Someone small, focused, and already selling to the exact people they wanted.
The problem was not that the information was hidden. It was public. A job post, a case study, a changelog, a talk at a regional conference. The problem was that nobody was looking for it, because looking for it is boring, and nobody had the time.
The dashboard nobody opens
The usual answer is a competitor dashboard. You list ten companies. You track their pricing pages, their blogs, their LinkedIn. You set up alerts.
I built one of these once, back when Waveloom was a workflow builder. Competitor price tracking, a check every hour. It worked. It also produced a stream of updates nobody wanted. A price moved by two percent. A product went out of stock and back. Every change was real, and almost none of it mattered.
That is the pattern with every alert product I have used. Week one, you read everything. Week two, you skim. Week three, you mute the channel. The alerts keep firing into a room with nobody in it. Then the one that mattered lands in the same pile and you miss it.
Alert floods fail because they answer the wrong question. They tell you what changed. You want to know whether the answer to a question you care about has changed.
Follow a question, not a company
Here is the shift. Instead of "track these ten competitors", ask something specific:
- Who is selling to compliance teams in DACH?
- Is anyone shipping approval-gated AI agents?
- Which agencies have started offering Linear migrations?
- Has anyone raised money to do what we do, but for hospitals?
A question has a bar built in. Most updates from most companies do not change the answer. A new hire at a competitor does not. A new customer logo in your exact segment does. A blog post about their culture does not. A pricing page that now lists a compliance tier does.
When you follow a question, most of what happens in the world is irrelevant by definition. That is the whole point.
What a good watch looks like
A watch, in my experience, needs three things.
A question. Not a keyword. "AI agents" is a keyword and it will bury you. "Is anyone shipping approval-gated AI agents for operators?" is a question, and a careful reader can tell whether a given page answers it.
A small set of sources. Two or three places where the answer would show up first. A competitor's changelog. A niche newsletter. A conference schedule. A handful of search queries that get re-run. Not the whole internet, because the whole internet is mostly noise about your topic.
A bar for what counts as a change. This is the part most tools skip. A watch should have an explicit idea of what would make it speak. A new company entering the segment. A named customer in your target market. A product that does the thing you thought only you did. Everything below that bar is silence.
If you write these three things down, you already have a better system than a dashboard. You could run it by hand every Friday. Most founders do not, because Fridays fill up. So I built it to run in the background.
How watches work in Waveloom
You describe the watch in plain language. The topic or question, the sources you care about, and what would count. Waveloom follows it in the background alongside your other tools.
When a source changes, it reads the change and asks the only question that matters: does this move the answer? If it is a repeat of something it already surfaced, it drops it. If it is on-topic but weak, it drops it too. Waveloom does not queue low-confidence items for later. It produces nothing, on purpose, and moves on.
When something clears the bar, you get one discovery card in your feed. The card has a one-line "why this matters" written against your question, and the evidence links so you can check the claim yourself. You can open a thread on the card and ask for more, or dismiss it. Dismissals teach it what the bar really is.
Some things it will not do. It will not create a card for every mention. It will not surface the same topic twice: a topic that already has a card doesn't get a second one, and new events on it join the existing card's thread. And it will not fire ten cards at once just because ten things happened. Events are processed in small batches, and a hard cap in the code limits how many cards a batch can create and how many notifications go out per day, across everything Waveloom watches.
A watch that says nothing is working
This is the part I want to be honest about. A well-formed watch can go a week without saying anything.
That feels wrong at first. You set something up, it stays quiet, and you wonder if it is running.
It is running. It is reading, comparing, and deciding that nothing changed the answer. That is correct behaviour. The alternative is the dashboard you muted in week three. If the question is "who is selling to compliance teams in DACH?" and nobody new started this week, the right number of cards is zero.
The feed shows what was reviewed and what was surfaced, so you can see the work happening even when the result is silence. If a watch surfaced something, it shows up in the morning brief.
Why this matters for a founder
You do not lose deals to competitors because you failed to read enough alerts. You lose them because the market moved and you found out last.
A watch is a cheap way to find out early. One question, a few sources, a clear bar, and a system that only speaks when the answer changes. The first time a discovery card shows you a company you had never heard of, selling to your exact buyer, you will understand why the quiet weeks were worth it.
Waveloom is in an invite-only founding beta. Watches are one of the things I am tuning most actively with early users, especially the bar for what counts as a change. If you have a question you would like followed, join the waitlist and tell me what it is.