The architecture of a Web Scraping API pricing
Designing a fair and predictable pricing model for Zyte API.
When it comes to web scraping, uncertainty can drive over-spending. Customers often overspend on infrastructure, unsure of what they truly need. This issue was a key topic in a recent conversation between James Kehoe, Senior Product Manager at Zyte, and Zyteâs CEO, Shane Evans.
That was one of the key insights I got as I listened to James and Shane discuss how they arrived at the pricing model for Zyte API.
I also gained a deeper understanding of the three core principles: predictability, fairness, and transparency, which shaped their approach to designing a customer-centric pricing model.
Below, Iâll outline the key takeaways from their conversation.
Balancing complexity and simplicity
âWhen people arenât sure what they need, they tend to oversubscribe. Again and again, we saw customers second-guess their web scraping infrastructure requirements and overspending just to err on the side of caution. We realised there is a major infrastructure efficiency gap that customers donât know theyâre facing, and we can close that gap for them.
From a technical standpoint, we knew how to assemble the pieces, but just as crucial was figuring out how to embed predictability, transparency, and fairness into the Zyte API pricing model.â James reflected.
As a "Swiss army knife" for extracting data from millions of websites, Zyte API caters to a wide range of use cases, each with different needs and expectations. The challenge of designing a pricing model for Zyte API lay in balancing this functional sophistication with a simple, fair user experience.Â
It took time, customer feedback, and extensive data analysis to get it right. Hereâs how Zyte approached the problem.
Predictability: reducing uncertainty
âOur customers need predictable costs,â James said. âScraping needs can change overnightâseasonal spikes like Black Friday, technical changes on websites, or new business priorities all play a role. But we made a choice to absorb as much of that variability as possible, rather than passing it directly onto customers.â
For example, even during periods of high demand like Black Friday, Zyte avoids price hikes. âIf a website becomes temporarily harder to scrape, we donât immediately bump its tier. Only if the change is permanentâfor instance, when a website introduces significant new restrictionsâwe do move it up, and even then, we give customers two weeksâ notice,â he added.
Enterprise customers, in particular, value this stability. âThey told us, âWe donât want pricing surprises disrupting our annual budgets,â so we locked their pricing in for a year as we launched it. That stability is non-negotiable for them.â
Fairness: charging for what worked
James emphasised that fairness is central to Zyteâs approach. Speaking of Zyteâs five-tier pricing model: âMost websitesâabout 80%âfall into our simplest tiers. It wouldnât be right to have those customers subsidising the few highly complex sites.â