Quoted on scope, after we've looked at your sources.
There's no price list, because a real number depends on what you actually need collected. Scoping is free, the quote is fixed, and it arrives with a sample from your own sources so you can judge both together.
Four inputs. Nothing else is priced.
- Sources
- How many sites, and how hard each one defends itself
- Volume
- Records per run, not seats or users
- Cadence
- Quarter-hourly costs more than monthly
- Fields
- Depth per record, and how much resolving they need
Three ways we typically work.
Every project is quoted after we've looked at your actual sources. These describe the shape of the engagement, the number comes with your sample.
Pilot
One dataset, one delivery, fixed scope
Best forTeams validating whether outsourced collection works for them
- Up to 3 sources scoped and extracted
- Schema designed with you and signed off
- One validated delivery in your chosen format
- Written feasibility notes on each source
Quoted as a one-off after scoping
Scope thisManaged pipeline
Recurring delivery on your cadence
Best forTeams that need the same dataset refreshed on a schedule
- Unlimited sources within an agreed scope
- Delivery from every 15 minutes to monthly
- Full validation suite and per-batch QA report
- Source monitoring and extraction repair included
- Direct line to the engineers on your project
Monthly, scaled to sources and volume
Scope thisCustom / enterprise
Bespoke scope, integration, or compliance needs
Best forTeams with security review, custom infrastructure, or unusual scale
- Everything in Managed pipeline
- Delivery into your own infrastructure
- Custom schema and transformation logic
- Security and compliance documentation
- Defined response times in writing
Scoped and quoted per engagement
Scope thisFour rules we don't bend.
Priced on scope, not seats
Cost follows the number of sources, the volume, and how often you need it, not how many people on your side open a file.
Quoted after we look
We assess the actual sources before quoting. A fixed number arrives with a sample, so you can judge the data and the price together.
Maintenance is included
Repairing extraction when a site changes is part of a managed pipeline, not a separate line item you get billed for later.
No lock-in on your data
Everything we deliver is yours, in open formats. Stop whenever you like and keep every record we've sent.
So you can estimate before you ask.
We'd rather you understand the shape of the cost than be surprised by it. These are the factors that actually drive a quote.
Number of sources
High impactEach site needs its own extraction logic and its own monitoring. Five sources is meaningfully more work than one, but the tenth costs less than the first, because the surrounding infrastructure is already there.
How often you need it
High impactA monthly snapshot and a quarter-hourly refresh are different products. Higher cadence means more infrastructure, tighter monitoring, and less room to repair a break before you notice it.
Volume of records
Medium impactVolume matters less than people expect. A million rows from one well-structured source is often simpler than ten thousand scattered across sites that each model their data differently.
How difficult the sources are
Medium impactSites that render client-side, paginate awkwardly, or actively resist collection take more work to extract reliably. We flag these during scoping so there are no surprises after you've signed.
Transformation complexity
VariesDelivering raw fields is straightforward. Matching SKUs across retailers, resolving duplicates by address, or normalizing inconsistent taxonomies is real engineering and priced accordingly.
Delivery target
Low impactA file in a bucket is standard. Writing into your warehouse, hitting your API on a schedule, or working inside your own infrastructure adds integration work up front.
In every engagement, at every size.
- Source feasibility assessment before you commit
- Schema design, agreed in writing
- A real sample from your actual sources
- The full validation suite on every batch
- Per-batch QA report with coverage and null rates
- Monitoring and extraction repair when sources change
- Direct access to the engineers on your project
- Your data in open formats, yours to keep
Things that shouldn't be line items.
- Per-seat or per-user fees
- Charges to repair extraction we built
- Setup fees on top of an agreed quote
- Export fees to get your own data out
Not sure whether your project is even feasible? That's the most common first question, and it costs nothing to answer. Send the sources and we'll tell you honestly.
kazmi@pyronets.comFrom source list to fixed price
No retainer, no obligation, and a real sample at the end of it.
Tell us the sources
Send the sites and the fields you need. URLs are ideal. If you're not sure what's possible, describe the outcome and we'll work backwards from it.
We assess feasibility
We look at each source and check what's reliably collectable. You get a written read on every one, including any we'd advise against.
Schema and sample
We propose a schema and extract a real sample from your sources, so you can judge the data itself rather than a description of it.
Fixed quote
A price for the work as scoped, arriving alongside the sample. No retainer to reach this point, and no obligation after it.
Pricing questions
Because any number we published would be wrong for most projects. Three sources at monthly cadence and thirty sources refreshed hourly are entirely different pieces of work. We'd rather look at your sources and give you a real number than publish a range wide enough to be meaningless.
Usually two to three working days from the point we have your source list. Complex or unusual sources can take longer, and we'll tell you up front if that's the case rather than going quiet.
Yes. Assessing feasibility, proposing a schema, and producing a sample happens before any commitment. If the answer turns out to be that we're not a good fit, you've lost nothing but the conversation.
We fix it, and it's included. Detecting and repairing extraction breakage is the core of a managed pipeline. Charging separately for it would mean charging you for the thing you hired us to handle.
That's what the pilot is for. One dataset, one delivery, fixed scope. It's the cheapest way to find out whether the data is what you expected and whether working with us suits you.
No. Managed pipelines run month to month. If you stop, you keep every record we've delivered, in open formats.
Adding sources or fields is normal and gets re-quoted transparently against the existing scope. We'd rather adjust the agreement than quietly absorb scope until the relationship stops working.
Send us your sources and we'll price it.
Scoping is free. You'll get a feasibility read on every source, a proposed schema, a real sample, and a fixed quote.
No retainer required to find out whether your sources are feasible.