Day 492: Pricing Plans
I’m consistently surprised by how much easier things get once you get started.
I’ve been putting off working on billing plans forever, but once I wrote the first bit of code to track usage for a user over a given billing cycle, everything else just started falling into place. Even though I intended to only put limits on total execution time for the sake of simplicity, I ended up developing a full pricing plan that would incentive people to upgrade in order to use more powerful features within Browserflow:
Pricing Plans
| Free | Starter | Professional | Business | |
|---|---|---|---|---|
| Monthly cost | $0 | $29 | $99 | $299 |
| Monthly credits (1 credit per second of execution time) | 1,000 | 10,000 | 50,000 | 200,000 |
| Max active flows | 1 | 5 | Unlimited | Unlimited |
| Max frequency | 24h | 1h | 5m | 1m |
| Max execution time per flow | 60s | 60s | 5m | 10m |
| Residential proxies (5 credits per second of use) | No | No | Yes | Yes |
| Captcha solving (100 credits per use) | No | No | Yes | Yes |
| Support | Community | Standard | Standard | Priority |
(Notion automatically created this table when I tried pasting it from Google Sheets — how slick!)
I expanded to four plans instead of the original three I had planned yesterday (I edited yesterday’s post while iterating on the pricing plans more today but maybe I should’ve left it alone for posterity).
All the features / limits I have above are chosen pretty arbitrarily and I expect most of them to change. I just want something somewhat reasonable to start with and I’ll iterate from there rather than trying to get it perfect from the beginning.
I took heavy inspiration from Zapier’s pricing/plan structure since they’re the most successful company in the no-code automation space — here’s a list of various pricing plans I’ve been looking at for companies with browser automation products: