Competitor price monitoring
A collector picks up the current prices by itself and puts them into a form you can work with. No monitoring by hand.
- Buildfrom $1,400
- Timeline1–3 weeks
- Supportfrom $420/mo
Who this suits: Sellers repricing by hand, categories where a competitor’s discount is noticed late, and any market where the number on the screen has no export button.
What is in the first version
- catalogue matching
- price history
- change alerts
- spreadsheet export
The figures above are the package this sits on: Parsing and reverse engineering. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
The round runs on its schedule
At the set time the collector opens every source and reads the page the way a customer does.
- 02
It is matched to your catalogue
A price is useless until it stands next to your own line, and the matching is most of the work.
- 03
You get changes, not a table
A daily spreadsheet nobody opens is not a result; a message naming which items moved and by how much is.
What decides whether this works or annoys people
Sources change without warning
A layout change breaks a collector silently, and silence looks like «prices did not move», so every source is checked for plausibility.
Politeness is a technical requirement
Rate, timing and volume are set so the collection is indistinguishable from ordinary traffic: being blocked costs more than collecting slowly.
What is legal to collect
Public prices are one thing and personal data another: we take the first, refuse the second, and say which is which beforehand.
What to measure once it is live
- sources collected without gaps
- items matched automatically
- time to your alert
- manual checking removed
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- CollectionPythonPlaywrightGoDocker
- Storage and matchingPostgreSQLClickHouseRedisS3
- Schedule and alertsn8nTemporalTelegram Bot APIGrafana
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- Hosting and servers for the collector
- Proxies and anti-bot services, where needed
- AI model calls used for matching
- Paid access to subscription-only sources
Asked before the first call
- Is this legal?
- Collecting publicly published prices generally is; the limits are a source’s terms of use and any personal data. We check your specific sources before quoting and say plainly if one is a no.
- What happens when a source changes its layout or starts blocking?
- That is ordinary life for a collector, not an incident, so the repair is part of the support you already pay for, and you hear about the break from us.
- Does the data stay ours?
- The database sits in your own account, the history exports to standard formats from the first version, and you can take all of it without us. We keep no copy.