I built a Vestiaire Actor, but “scraper” might be the wrong headline
I built an Apify Actor for Vestiaire Collective and I’m stuck on the positioning.
The obvious label is “scraper”.
But the workflow I keep coming back to is resale comps.
If someone is researching a bag, watch, or pair of shoes, they usually don’t just need a table of listings. They need to compare:
- live listings vs sold items
- condition
- seller country
- price changes over repeat runs
- seller-level patterns
- duplicate-ish listing signals that deserve manual review
So I’m testing a different frame:
A first-pass comps layer for luxury resale, exported as CSV/JSON/API, before building any SaaS UI.
I’m testing the current version here: Vestiaire Collective Smart Scraper
I’m deliberately not claiming it detects authenticity, private sold prices, or whether a seller is safe. It works from public pages, and the duplicate/risk signals are only heuristics for review.
My positioning problem:
Who would you lead with first?
- resellers looking for sourcing leads
- sellers pricing items from sold comps
- data teams wanting a Vestiaire API/export
- researchers tracking resale prices over time
- non-technical operators who would need a SaaS UI
My instinct is #2 or #3, because they feel more repeatable than “find deals”.
If you had to write the landing page headline, would you call this a scraper, sold comps tool, price tracker, seller intelligence layer, or data API?
I’d avoid leading with “scraper” — it describes the mechanism, not the value.
I’d lead with #3 first, because Apify users already want structured data/API/export, then use #2 as the main use case.
Headline idea:
“Vestiaire Collective comps API for resale pricing and market research.”
Keep “scraper” for SEO, but position it as a comps/data layer, not just a scraper.
Possibly.
The reason I'd still be careful is that I don't think the interesting question is what someone needs to see before caring.
I think there's a bigger decision sitting underneath that question.
That's not something I'd try to unpack properly in a thread.
If useful, drop your email and I'll put together the tighter version.
That makes sense.
I’d rather keep the first version public here, since the whole point is to pressure-test the positioning.
If you had to compress the bigger decision into one sentence, is it mainly:
Even a rough take would be useful.
Possibly, but that's exactly why I stopped short.
All four of those can end up looking important at the same time.
I wouldn't feel comfortable compressing it into a sentence because the value is in understanding which decision actually matters most.
That's not something I'd try to do properly in a thread.
If you change your mind, feel free to drop your email and I'll put together the tighter version.
Extra context: I’m leaning away from a SaaS UI until the workflow is clearer.
The current product is dataset/API-first. The proof artifact I’m considering next is a small sample run showing active vs sold rows for one narrow query, with condition and seller country filters.
Would that make the positioning easier to judge, or would you need to see a no-code UI before caring?