How Recyclops put its highest-revenue workflow on autopilot with Browserless

Recyclops' biggest partner hands off pickup requests through a portal with no API and a 24-hour clock. That workflow now runs on its own.

JULY 23, 2026

Customer
Recyclops
Industry
Recycling & sustainability
Use case
Pickup-request scraping & dispatch
Deployment
Cloud
Customer since
2025
Stack
BrowserQL
Browserless products
BrowserQL (BQL)

At a glance

15
Hours saved per week on the automated workflow
~1 hr
Monthly maintenance, down from days of setup and weekly upkeep
15K+
Automated browser sessions since 2025
~96%
Session success rate

The challenge

Recyclops is a recycling and sustainability company with two sides to its business: helping large brands keep hard-to-process, high-volume material out of landfills, and bringing curbside recycling to rural communities that lack easy city-based options.

Its most important workflow sits with Recyclops' largest partner. When the brand has material ready to move, it drops a pickup request into an internal portal, with no API and no export, just a web form and a paginated table. Recyclops often has only 24 hours to process each request and dispatch a truck. Missing a request means missing a pickup.

Recyclops first tried building the scraper itself in Puppeteer, but the portal layout was awkward, and VP of Technology Spencer Olsen also ran into deployment issues getting it into production.

The solution

Spencer found Browserless while searching for a way past his deployment roadblocks, and had it live in production within a day, which mattered for a launch on a very short timeline.

I'd hit a ton of roadblocks trying to deploy web scraping myself. With Browserless I had things up and running within a day, and for a launch that was very time-sensitive, that mattered a lot.

Spencer Olsen · VP of Technology · Recyclops

His workflow now runs through Browserless's BQL endpoint via a simple POST request. A job fires every 20 minutes, roughly 10 to 11 hours a day, logging into the portal, paging through the request table, extracting the details, and pushing them straight into Recyclops' system so the team can dispatch.

The results

With Browserless, Recyclops turned a fragile, manual, revenue-critical workflow into one that runs on its own. Maintenance is now the exception, not the routine: the team only touches the job when the partner changes its portal layout, and the hours that used to go into babysitting the scrape now go back into the rest of the platform.

Want the same outcome?

Running a revenue-critical workflow against a site with no API and a hard deadline? Browserless got Recyclops from roadblocked to live in a day.

Stop fighting deployment. Start dispatching.