A Series B software company wanted to know what its competitors were doing. Product, marketing and sales each had a use for the answer, and each of them got it the same way: somebody was asked to look.
The team’s own description of the tracking was time-intensive and inconsistent. That is what manual competitor research always becomes: a snapshot, taken whenever someone has a spare afternoon, of whatever they happened to check.
Watching a competitor properly is a lot of reading across a lot of places: their pricing page, their changelog, the ads they are running on LinkedIn and Meta and Google, their blog, their job postings, their new case studies and partnerships, what customers say about them in reviews. Multiply by several competitors and it is a full-time job that nobody was hired to do, so it was done by nobody in particular, in between other things.
Inconsistency is the part that costs more than it looks. When different people check different things on different weeks, nothing is observed twice in the same way, so there is no way to see a trend. A competitor hiring a dozen enterprise reps over a quarter is a signal. A dozen separate job posts, noticed by different people on different weeks, is noise.
This is the kind of gap that shows up late and in other people’s budgets: a deck positioning against old pricing, a roadmap debate held without knowing a rival already shipped the feature, messaging that drifts toward a competitor’s without anyone noticing. None of it traces back to the missing research, because nobody knows what they did not see.
The decisions inside competitor intelligence split cleanly, which is what made it a good fit. What changed this week? Which of those changes matter? And what do we do about it?
The first is pure reading, high volume and low stakes, and a coworker can own it outright. The second takes judgment about the market, but a wrong call costs a paragraph of attention, so the coworker can make it as long as it shows its reasoning and a person can disagree. The third is where the money is: repricing, re-prioritising the roadmap, changing the pitch. That is a leadership decision, and the coworker never comes near it. It hands over a briefing and stops.
Which competitors, which six areas to watch for each, what counts as a significant change, who reads the report and what they need to decide from it. The autonomy line: the coworker collects and assesses, people act.
Every week the coworker reads across six areas for each competitor: product and pricing changes, advertising and content, partnerships and customer announcements, hiring and personnel, customer reviews and forum discussion, and how their positioning is shifting. It pulls from more than fifteen sources through the enrichment platform the team already paid for, with a dedicated research agent per area so that a change in one does not get lost in the volume of another.
Then it writes. A weekly report with the significant movements up top, each section’s findings underneath, and a short assessment of what the pattern across all of it suggests. Fortnightly it compares against the previous report and flags what changed and how much it matters. Monthly and quarterly it looks back further, so a hiring push, a pricing drift or a messaging pivot shows up as a trend rather than as a series of unrelated Tuesdays. Everything lands in the Notion workspace the team already lived in, with the history kept, so any claim can be traced back to what was actually seen and when.
Six research agents per competitor, weekly synthesis, fortnightly comparison and monthly trend analysis, delivered into the team’s existing Notion workspace with a searchable history.
Nobody logged into anything new.
The report has arrived every week since launch. Manual competitor research fell by about ninety percent, and what remains is the part worth a person’s time: reading the briefing and deciding. The same intelligence now feeds product priorities, marketing positioning and competitive sales conversations, from one source instead of three people’s memories.
The other number is coverage. Six areas for every competitor, read from more than fifteen sources, every week without a gap: across a handful of competitors that is a few dozen checks a week, and over a year it is well over a thousand observations, each made the same way as the last so they can be compared. No team does that by hand. The realistic manual alternative was never the same coverage at higher cost; it was a fraction of the coverage, whenever someone had time.
The trend view is the part nobody had before. That is what the history is for: a competitor’s push into a new segment shows up as hires, then a partnership, then a case study, then a pricing tier, in that order, instead of as four unrelated surprises spread over a year.
The reading is done before anyone arrives on Monday. The decision about what to do with it was never delegated.
Collection and weekly assessment run on their own, with the sources cited. What to change in pricing, roadmap or messaging stays with the people accountable for it.
Sources break quietly. A competitor redesigns their pricing page and the coworker, if nobody is watching, reports no change forever. So the first thing we check each week is not the report but its coverage: did every area for every competitor return something, and does “nothing new” mean nothing happened or nothing was read. A new competitor gets added in a day. A new channel becomes a seventh area when the team asks for it.
The coworker’s judgment goes as far as the assessment. It ranks what changed by how much it matters and says what deserves a conversation, and it keeps that authority for as long as the team keeps agreeing with its calls. If they started missing, it would go back to listing changes and leave the ranking to a person. Recommending an action is as far as it goes. Taking one is not on offer, and that is by design rather than a limit of the tooling.
Bring us the workflow that is costing you the most. A first call is a conversation about one workflow and what could reasonably be delegated.
Book a call →