New reviews, de-duplicated
Each run collects reviews published since the last one, for you and each rival, and drops ones already seen.
Loop · in build
Know what customers are saying, about you and about them.
Your rivals' customers publish what annoys them about your rivals. Almost nobody reads it. This loop will collect new reviews on a cadence, sort them into themes, and show which themes are moving, quoted from the reviews themselves.
In build · not on sale Planned on code that already runs inside the reports. The loop itself is not built, does not run for customers and is not on sale.
Review themes, compared with the last run
- NewYou · deliveryNew theme: late delivery — new reviews this run
- ChangedRival A · communicationMore reviews about slow replies than last run
- GoneRival B · priceNo new reviews in the price theme this run
- Not checkedRival C · sourceSecond review site unreadable this run — flagged, not counted as quiet
- The first source, read through the Google Places API
- Google reviews
- Source: src/lib/connectors/places.ts · checked 2026-10-13
- A broken reader shows as unreadable, never as no reviews
- Health flag per source
- Source: docs/LOOPS.md (branch feat/loops) "Kinds" (reviews_watch) · checked 2026-10-13
- The loop executor, as of this page
- Not built
- Source: docs/LOOPS.md (branch feat/loops) "Kinds" · checked 2026-10-13
What it will be
What it will be, and what it is built from.
A loop that collects new reviews for you and the rivals you name, groups them into themes and shows which themes grew or shrank since the last run.
Your reviews tell you what your customers value and what annoys them. Your rivals' reviews tell you the same about theirs. The difference is often the gap you can win on. Reading both by hand, every month, is a job nobody does twice.
The reviews watch will do it on a cadence. For you and each rival you name it will collect the reviews published since the last run, remove duplicates, and place each one in a theme: delivery, price, quality, communication, whatever the reviews themselves are about. Then it will compare against the last run and show which themes grew or shrank, with the reviews that moved them quoted verbatim so you can judge the evidence.
It is built from code that already runs. The reports read reviews today: the Google Places connector, the review-source readers and the review analysis that groups comments into themes. The loop adds what a one-off read does not need: a history of reviews seen, de-duplication across runs, and a comparison of themes over time.
One lesson from earlier work is designed in from the start. Review sites change their pages. A scraper that breaks silently reports "no new reviews" when the real answer is "we could not read the source". Every source will carry a health flag, so an unreadable source is shown as unreadable. This loop is in build: nothing runs for customers and it is not on sale.
Who it is for
- Local service firms whose rivals are judged on Google reviews
- Online stores watching what rivals' customers complain about
- Owners who want review themes, not a star average
What it will do
What each run will look at.
Themes, with the evidence
Reviews are grouped into themes, and every theme links back to the reviews in it, quoted as written.
What moved
Themes that grew or shrank since the last run, per business, so you can see a problem starting before it shows in the average.
Source health
Each review source is checked on every run. One that cannot be read is flagged as unreadable rather than counted as quiet.
By hand, or with it
The same job, two ways.
By hand
- Scroll through your own reviews, then each rival's
- Remember what people were complaining about last quarter
- Judge rivals on a star average that hides the detail
- Cannot tell a quiet month from a broken page
With the loop, once it ships
- New reviews for you and each rival, collected per run
- Each review placed in a theme you can open
- Themes compared with the last run
- Unreadable sources shown as unreadable
What you walk away with
What you keep.
Themes per business
What customers praise and criticise, for you and each rival, grouped and quoted.
Movement since last time
Which themes gained or lost reviews since the previous run, with the reviews behind the change.
A gap list
Themes where rivals' customers are unhappy and yours are not: the points worth saying out loud in your own marketing.
A record you can trust
Per-source health on every run, so a missing review is a known gap rather than a silent one.
How it will work
Three steps.
Name the businesses
You and the rivals you want watched, matched to their review listings.
Set the cadence
How often new reviews are collected and themed, in whole days.
Read the themes
See what moved since the last run and open the reviews behind each theme.
Limits
What it does not do.
- It is not built. The review readers and theme analysis run inside today's reports; the loop around them is not written.
- Google reviews come through the Places API, which returns a limited selection of reviews per listing rather than a full history.
- Other review sites are read only where they can be read reliably. Some change often; those will carry a health flag and may be unreadable on a given run.
- It does not reply to reviews or contact reviewers.
- Themes are assigned by a language model and can be wrong; every theme links to its reviews so you can check.
Price
See current pricingNot on sale. No price yet.
The reviews watch is being built. When it runs in production the pricing page will say which plans include it; until then nothing is charged and nothing is promised.
FAQ
Reviews and reputation watch: questions
Can I use it today?
Not as a loop. The free Insight Report and an Intel loop already read reviews once; the recurring watch is in build. Join the loops list to hear when it ships.
Which review sites will it read?
Google reviews first, through the Places API. Other sources only where they can be read reliably, each with a health flag on every run.
Will it see every review?
No. The Places API returns a selection of reviews per listing, not every review ever written. The watch builds its own history from what it sees on each run.
Does it reply to reviews for me?
No. It reads and groups reviews. Replying stays with you.
What will it cost?
Nothing is priced yet. When it runs in production, the pricing page will say which plans include it.
Get on the list for this loop.
Planned on code that already runs inside the reports. The loop itself is not built, does not run for customers and is not on sale.