Freelance Scraping, Pricing, Clients, Contracts

Freelance scraping is one of the more profitable specializations in software contracting, the supply of competent scraping engineers is small, the demand from data-hungry companies is large, and the projects are typically discrete enough to scope cleanly.

This lesson is honest about how the work flows, including the hard parts.

Pricing models

Model	Pros	Cons	Right for
Hourly	Simple; safe when scope is fuzzy	Caps your income; clients flinch at totals	Open-ended scraping discovery
Fixed-bid	Aligned to outcomes; higher margins on speed	You eat scope creep	Well-defined "scrape these N sites"
Retainer	Predictable cashflow; deep relationships	Tied up; less variety	Long-term scraping ops for one client
Per-record	Easy to explain; scales with scope	Hard if quality matters more than quantity	Lead-gen and aggregation
Productized	High margins; scaleable	Requires marketing investment	Repeat-pattern services (see lesson 75)

A common mix: hourly for discovery, fixed-bid for the build, retainer for maintenance.

What rates look like

This varies enormously by region, skill, niche, and channel. Rough 2026 ranges for experienced scraping engineers:

• Upwork / Fiverr global pool: $15–50/hr; very competitive.
• Direct clients in US/EU, mid-skill: $60–120/hr.
• Specialized (e.g. anti-bot expertise, SERP at scale): $100–250/hr.
• Senior consultants / agency owners: $150–400/hr.

Fixed-bid totals for typical projects (rough):

• Single-site scrape, ~50 pages: $500–2k.
• Multi-site product aggregator with 5–10 sources: $5k–25k.
• Anti-bot-heavy scrape with ongoing maintenance: $10k+ initial + $1–5k/mo retainer.

These are starting points. Geography, niche, network, and reputation all shift them.

Where the work actually comes from

In rough order of quality-per-effort:

1. Referrals from past clients. Highest close rate, best margins. Worth investing in the relationships.
2. Direct outreach to companies in industries needing data (e-commerce, recruiting, real estate, finance). Lower close rate but more control.
3. Open-source visibility (lessons 69–72). Clients find you. Pre-qualified.
4. Twitter/X, Reddit r/webscraping, dev.to writing. Content brings inbound when you focus on a niche.
5. Marketplaces (Upwork, Toptal, Contra). Volume but rate compression. Toptal screens harder, pays more.

What rarely works: cold email "I do scraping" without specifics. Tight niche + visible work is the formula.

Qualifying a client (the 5-minute screen)

Before you invest time scoping:

1. What data, from where? If they can't name the sites, they're not ready.
2. What's the budget range? "I don't know" = not budgeted. Ask anyway.
3. What's the use case? Affects legal posture, timeline, complexity.
4. Who scraped this before, and what happened? Reveals difficulty.
5. What's the success criterion? "I'll know it when I see it" = trouble.

A client who can't answer these isn't ready for a fixed-bid yet, propose a paid discovery hour.

Scoping a fixed-bid

For a fixed-bid scrape, your scope should be specific:

- Source sites: [list]
- Fields per record: [list]
- Cadence: one-shot / daily / hourly
- Volume estimate: ~X records, ~Y refreshes
- Delivery format: CSV / Postgres dump / API
- Anti-bot complexity expected: simple / moderate / heavy
- Out of scope: [list]
- Change-order rate: $X/hr if scope expands

Vague scopes are the #1 cause of contractor pain. A client who won't engage with this level of specificity is asking for an open-ended fight.

The contract clauses that matter

Use a written contract, Bonsai, Hello Bonsai, or your own template:

Clause	Why
Scope of work	What you're building; nothing else
Payment terms	Net 14, milestone-based, deposit upfront
IP ownership	Usually transfers on payment; reserve your tools
Liability cap	Limited to fees paid; no consequential damages
Warranty disclaimer	Scrapers break when sites change; not your fault
Termination	14-day notice either side, pay-for-completed-work
Confidentiality	Both ways
Indemnity for legal	They indemnify you for their use of scraped data

The legal-indemnity clause matters specifically for scraping: if the client uses scraped data in a way that triggers a CFAA, GDPR, or copyright claim against the project, that should be their risk, not yours. Doesn't fully protect you, but tilts the field.

Getting paid

Almost everyone underestimates this:

• Deposit upfront, 30–50%, before any work. Non-negotiable.
• Milestones, not one big payment at the end.
• Net 14, not net 30 or 60. Smaller clients can pay quickly; larger ones will push longer terms but it's negotiable.
• Late-fee clause in the contract. Rarely invoked but useful.
• Stop work when invoices are unpaid. Tools like Bonsai or Stripe can enforce.

The freelancer-survival rule: never deliver final work before final invoice is paid. Once delivered, leverage is gone.

The scraper-specific risks

Scrapers fail when target sites change. Bake into your contract:

• A warranty period (e.g. 30 days) where you'll fix breakage from minor site changes for free.
• Maintenance retainer for ongoing breakage handling.
• Out-of-scope for "the site rebuilt completely; new project."

Without this, clients ask "didn't you build this last month? Why doesn't it work?", and you're answering for free.

Saying no

Frequent reasons to walk away:

• Target involves PII you can't legally scrape (consumer phone lists, scraped resumes from LinkedIn behind login).
• Client asks you to bypass technical access controls (CAPTCHAs of certain types, paywall bypass).
• Budget is far below your floor and won't move.
• Vibe is "I will haggle every line item."

Saying no is a skill. A clean "this isn't the right project for me, good luck" is better than a months-long bad project.

Building a freelance pipeline

The compound steps:

1. Get the first few clients any way (network, marketplace, cold outreach).
2. Deliver well; get testimonials/case studies.
3. Publish that work publicly (with permission). One blog post per project.
4. Build a niche reputation in a specific industry or technical area.
5. Inbound starts flowing within 1–2 years of consistent visibility.

The middle phase (steps 2–4) is where most freelancers stall. The grind is real but bounded.

What to try

If you're considering freelance scraping:

1. Write your "elevator description", 2 sentences answering "who are you and what do you do?" Specific niche beats generic.
2. Identify three industries that might need scraping work. Pick one.
3. Find five companies in that industry. What data would they want?
4. Write one cold outreach email focused on a specific data problem.
5. Send it.

Sending is the bottleneck. Everyone overthinks the message; few send the message.