WordPress was the SaaS stack all along — we just had to build the missing piece

For over a decade, I’ve been developing and selling a standalone PHP QR code generator on Envato. Over the years it found its way to more than 1,800 customers, and with that many people using it, the feedback never really stopped coming.

Most of it converged on one question: “How do I monetize this?”.

People wanted to turn the generator into a service — sell access to it, charge for QR generation, run it as a business. A smaller group asked something more specific: “How do I integrate this into my WordPress site?”

Two different questions, but they pointed toward the same answer.

Why WordPress

Most SaaS solutions assume you want a VPS and a framework like Laravel or Symfony. While these are solid tools, they aren't beginner-friendly, requiring days of setup and server maintenance that most users want to avoid.

In contrast, WordPress installs in seconds, is easy to customize, and provides a battle-tested SEO foundation out of the box. It’s the perfect platform to build a business around.

The catch : subscriptions, billing, and user dashboards on WordPress usually mean stitching together several heavy premium plugins on top of each other — a membership plugin, a payment gateway plugin, WooCommerce just to handle recurring charges. Each one comes with its own license to pay for, and that’s only half the problem. The real headache is getting them to actually talk to each other: plugin updates breaking integrations, conflicting hooks, mismatched user roles, support tickets that bounce between three different vendors because nobody wants to own the bug. So instead of going that route, we built it all native, into a single plugin.

The build

The QR engine itself was already solid after more than a decade in production — generation, design customization, the full range of static content types. The real work was everything around it: native Stripe subscription billing (no WooCommerce, no third-party checkout plugins), per-plan quotas, client dashboards, and dynamic QR codes with scan analytics. That’s the layer that turns a generator into a SaaS.

The free core — static QR generation, full design customization, 14+ content types — lives on WordPress.org. The PRO layer on top of it unlocks dynamic codes, the client dashboard, and billing.

The takeaway

Packaging it as a plugin meant solving the monetization problem once, in a way that fit the platform a good chunk of our users were already asking about — rather than pushing everyone toward a separate, heavier stack they’d have to learn and maintain.

Curious how others here have approached the same build-vs-package tradeoff — especially anyone who’s tried wiring up subscriptions on WordPress without going all-in on WooCommerce.

If you want to see what the native billing and dashboard setup looks like in practice, the free plugin is on WordPress.org — just search “qrcdr”.