How Much Does Web Scraping Cost
There is no honest price list for web scraping, only a price for your project. What follows is what actually moves the number, so you can estimate before you ask.
The five things that set the price
How many sources. One site is one set of page structures to learn. Five sites is five, plus the work of making their output comparable. In one project we monitored five European property portals, and the harder half of the job was not collection at all but bringing five different ways of describing a property into one structure the client's analytics pipeline could read.
How much data. Volume drives infrastructure and time. Our projects have ranged from about 13,000 rows a day to just over 400,000, and one runs about 200,000 rows every day from a single catalogue.
How often. A single complete extraction and a daily feed that has to land before the client's working day are different products. The second one costs more because it has to keep working unattended.
How difficult the source is. Some sites are straightforward. Others need a login, guard themselves against automated traffic, or hide the data behind interactions rather than links. That difference shows up in the build time: our fastest launch was 2 working days, a typical project lands in 4 to 9, and one with heavy protection and 150,000 lookups a day took 12 working days of development and testing.
What the output has to fit. A CSV you open in Excel is cheaper than a feed that has to arrive in your database through an API on a schedule. Both are normal requests; they are just not the same amount of work.
Why price per row is a bad unit
Per-row pricing suggests the cost is in the volume. On easy sources it roughly is. On difficult ones almost all of the cost is in getting reliable access to the first page, and the millionth row after that is nearly free.
That is why a plan with a row limit works for predictable sources, and why anything unusual gets quoted as a project. Our published plans start at 169 EUR per month with a limit of 100,000 rows per month, run up to 549 EUR per month, and anything above the listed tiers is quoted individually. The current tiers are on the pricing page.
What the price includes besides collection
The part people forget when comparing quotes:
- Keeping up with the source. Sites get redesigned. One platform in our portfolio went through several major updates over the years, including significant changes to how it handles automated traffic, and the client kept receiving the same dataset in the same shape throughout. That work happens on our side.
- Structure that stays stable. If the columns move every month, the data is not usable for history.
- Delivery. Files in real projects have gone out as CSV, Excel and JSON, by email on a schedule, and straight into a client database through an API.
- Support. Response time in our plans is 48 to 72 hours.
How to get a real number
Send us the sources, the fields and the frequency. That is enough for a scope, a timeline and a price. If the target is one of the roughly 185 sources we already cover, the answer comes back faster: browse them from popular sites.
If you would rather see the output before discussing budget, order a data sample: a real extraction from a live source in CSV, JSON and XLSX for 9.99 EUR. It answers the question a quote cannot, which is whether the fields you need are actually there.
For anything non-standard, custom development is the route, and a couple of lines about your target is all we need to start.
