How Pricing Roaster uses Allscreenshots to see pricing pages the way visitors do

Behind the fairly playful name is a sophisticated bot.

When someone submits their pricing page, Pricing Roaster crawls the site and checks it against nearly 100 different rules.

It looks for things like overstuffed enterprise tiers, missing anchors, sprawling feature matrices, weak proof, confusing calls to action and other patterns that can make a pricing page harder to understand or less convincing.

But analysing the HTML only tells part of the story.

A visitor doesn't experience a pricing page as headings, DOM nodes and CSS classes. They see the finished page.

That's where Allscreenshots comes in.

As part of every roast, Pricing Roaster uses Allscreenshots to capture the pricing page.

That screenshot gives the bot visual context alongside everything it learns from crawling the site.

This matters on a pricing page because presentation is part of the pricing strategy. The order of the plans, which tier draws your attention, how much space a feature matrix occupies, where the calls to action sit and how much information you're confronted with at once can all affect how someone interprets the offer.

Some of that can be inferred from HTML. A screenshot gives the bot a much better view of what the person considering the purchase actually sees.

So rather than analysing just the content of the page, Pricing Roaster can also take its presentation into account.

For the person using Pricing Roaster, none of this complexity is visible.

They paste in their pricing page URL and get their findings around 90 seconds later.

Behind the scenes, the site is crawled, dozens of pricing checks are run and Allscreenshots captures the rendered page to provide additional visual context.

Allscreenshots handles the browser and screenshot generation, leaving Pricing Roaster to concentrate on the interesting part: figuring out what's working on the pricing page and what could be improved.

We really like this use of Allscreenshots because the screenshot isn't there for decoration. It becomes another input into the analysis.

Pricing Roaster reads the page, but it gets to look at it too.