Scope a web data project, separate development and operating costs and agree deliverables using measured workload rather than invented estimates.

The Beginner's Mistake
Quoting a fixed script price before measuring the workload and then discovering:
- The site changed within 30 days
- Getting banned requires changing proxies
- The client wants a dashboard, scheduling, and alerts
- You're on-call without getting paid for it
The 4 Components of Pricing
1. Setup (one-time)
Site analysis, architecture design, and initial implementation. Charge for 30-60 hours of work.
2. Monthly Fee
Maintenance, monitoring, and adjustments when the site changes. 15-25% of the setup fee, monthly.
3. Infrastructure Cost
Proxy + server + DB. Pass-through cost + 30% margin.
4. Volume
Per thousand records or per GB processed. Margin on top of proxy costs.
Authorized access and responsible testing
Use owned or authorized resources and documented APIs when available. Confirm source conditions before collecting. Stop on access denial or verification requests, honor rate limits and use official review channels instead of changing identity to continue. Record location, time, permitted scope and data usage.
Embedded Proxy Costs
For 100k e-commerce pages/month:
- ~15GB residential from RH7 Proxys
- Pass-through cost with margin: easily covered
- Don't forget to include in the contract that increased volume = increased cost
Proposal Template (Essential)
- Scope: what's included and what is NOT included
- SLA: incident response time, expected uptime
- Output: format, frequency, destination (database, S3, webhook)
- Site Changes: included adjustments vs. billable adjustments
- Limits: maximum volume in the contract
- Payment: setup upfront, monthly fee in advance
Authorized access and responsible testing
Use owned or authorized resources and documented APIs when available. Confirm source conditions before collecting. Stop on access denial or verification requests, honor rate limits and use official review channels instead of changing identity to continue. Record location, time, permitted scope and data usage.
Conclusion
Scraping is a recurring service, not a one-off product. Price it like a SaaS: setup + recurring fee + usage, with a margin on infrastructure.
Authorized access and responsible testing
Use owned or authorized resources and documented APIs when available. Confirm source conditions before collecting. Stop on access denial or verification requests, honor rate limits and use official review channels instead of changing identity to continue. Record location, time, permitted scope and data usage.
Published 2026-03-22 · RH7 Proxys editorial team