April 15, 2026
Push the big red button
Forcing an Inversion of Control on the SaaS Stack
A browser bot adds your own buttons to SaaS apps — geeks cheer, IT panics
TLDR: 100x Bot’s Page Booster lets people add custom buttons and automations to existing web apps, bypassing slow vendor roadmaps. Commenters celebrate user control and dream of “API-only” SaaS, while skeptics warn enterprise security and business incentives could curb this rebellion—making the power struggle the real story.
A new feature called Page Booster from the 100x Bot browser tool promises the dream: slap your own buttons, highlights, and scrapers onto the apps your company already uses, and automate tasks without begging a vendor for six months. The community reaction? Part jailbreak, part fire drill. One side is buzzing that this is basically “enterprise userscripts,” a sneaky superpower for workers tired of waiting. The other side is clutching badges and binders: will corporate security even allow overlays that inject custom UI?
The hottest take calls for a total shake-up: make SaaS “just an API” so users fully control the interface. That fantasy meets a hard reality check from pragmatists who say vendors must prioritize the 80/20 features and, yes, protect profits—calling them “evil” is rich. Meanwhile, a builder jumps in to say they’re embedding “vibe coding” directly with SaaS vendors for thousands of users, hinting at a peace treaty: customization with permission.
Humor flew fast. Folks dragged the industry’s glacial pace—Figma’s late “find” button and GitHub’s delayed dark mode—reviving the “hello, darkness” meme. And when someone asked if this could go as far as full page rewrites, the thread basically answered with the internet’s favorite GIF: “Hold my coffee.”
Key Points
- •100x launched Page Booster, enabling users to inject custom UI elements into existing web apps to automate workflows.
- •Page Boosters can trigger API sequences or workflows, show contextual highlighters, and scrape structured data; they’re created in plain English and are shareable.
- •A banking use case showed Page Boosters bypassed a vendor’s six-month timeline for simple feature changes.
- •The article argues large SaaS platforms resist replacement due to enterprise moats like SOC 2, security perimeters, concurrency handling, and painful data migration.
- •Major SaaS vendors prioritize broad-impact features (80/20 rule), leading to delays on user-specific requests, exemplified by Figma’s and GitHub’s slow delivery of requested features.