The Solo WordPress Businesses Nobody Talks About
Hosting resellers, niche plugins, and $50K exits, real numbers from founders who shared everything.
The WordPress transparency reports from companies like WP Fusion and Barn2 get attention because the numbers are big: $775K, $1.7M, multi-million dollar plugin suites. They’re inspiring, but they’re also the success stories that survived long enough to have something worth reporting.
What about the middle? The solo operators clearing $20K/month on a productized hosting bundle. The agency-turned-plugin-shop doing $25K/month on a page builder add-on. The recipe plugin that peaked at $3K MRR and sold for $50K. The reservations tool stuck at $400/month.
These businesses exist everywhere on Indie Hackers, buried in forum posts and casual comments. They’re not publishing annual transparency reports, but they are sharing numbers—and the patterns are different from what you see in the polished case studies.
Here’s what I found.
Anchor Hosting: $237K/Year Reselling Other People’s Servers
The Business Model Nobody Expects to Work
Anchor Hosting is a solo-operated business that sits between WordPress professionals and managed hosting providers. The founder doesn’t run servers. They resell infrastructure from hosts like Kinsta and layer services on top.
From their Indie Hackers post:
| Metric | Number |
|---|---|
| Monthly Revenue | ~$19,750 |
| Annual Run Rate | ~$237,000 |
| Sites Managed | ~900 |
| Team Size | Solo operator |
What They Actually Sell
The pitch isn’t “hosting.” It’s “the essentials of WordPress maintenance, handled for you.” That includes:
- Migrations
- Monitoring
- DNS and domain management
- Security updates
- Fixes when things break
The founder explicitly describes it as “no more, no less”—not a full agency retainer, not raw server access. A productized layer that removes the pain of dealing with hosting directly.
Why This Works
The customer is the agency, not the end client. Designers and developers building WordPress sites influence where those sites get hosted. If you make their life easier, they bring you repeat business—every new client project is another potential site on your platform.
Bundling maintenance into hosting changes the pricing conversation. Raw hosting is a race to the bottom. “Hosting plus we handle the maintenance stuff” justifies a premium and reduces churn because switching means losing the service layer, not just moving files.
Growth channel: relationships, not ads. The founder emphasizes word-of-mouth through the designer/developer community. When your customers are professionals who talk to each other, reputation compounds.
The Math
At ~900 sites and ~$19,750/month, that’s roughly $22/site/month average revenue. Not huge per site, but the model scales without proportional support costs because the customer (the agency) handles most end-client communication.
PowerPack for Beaver Builder: $20-25K/Month on a Page Builder Add-On
From Agency Client Work to Plugin Revenue
PowerPack started the way a lot of successful plugins do: the founders were running a digital agency, kept hitting the same gaps in Beaver Builder, and eventually productized the solution.
From their Indie Hackers interview:
| Metric | Number |
|---|---|
| Monthly Revenue | ~$20,000 (interview) |
| Revenue Widget | $25,000/month (self-reported on IH) |
| Free Version Installs | 10,000+ sites |
| Pricing | $69/year (launched at $49/year) |
The Install Multiplier Effect
Here’s what makes agency tooling different from consumer plugins: many PowerPack customers use it across 100-200 client websites. One license sale can mean hundreds of active installs.
This changes the economics. You’re not optimizing for raw customer count—you’re optimizing for customers who deploy at scale. A freelancer with 50 client sites is worth more than 50 individual site owners, and they’re probably less support-intensive per site.
Why “Modules + Templates” Is Smart Packaging
The product is essentially “more stuff for your page builder”: additional modules, pre-built templates, design options Beaver Builder doesn’t include out of the box.
This is a packaging hack:
- High perceived value (templates feel like “done-for-you” work)
- Low marginal cost (once built, templates cost nothing to deliver)
- Workflow stickiness (once templates are embedded in how an agency builds sites, switching is painful)
Pricing Evolution
They launched at $49/year and later moved to $69/year, positioning it as “pocket-friendly.” The annual model means predictable renewals, and the low price point reduces purchase friction for freelancers and small agencies watching every dollar.
The $3K MRR Recipe Plugin That Sold for $50K
Small Numbers, Real Exit
Not every plugin business scales to seven figures. Some peak at a few thousand dollars monthly, plateau, and then… what? One founder shared their path in an Indie Hackers post:
- Built a WordPress recipe plugin (2016-2019)
- Grew it to $3,000 MRR at peak
- Felt stuck on what to build next
- Sold it for $50,000
What This Actually Tells You
A $3K MRR plugin generating ~$36K/year sold for roughly 1.4x annual revenue (or ~17x monthly revenue). That’s a reasonable multiple for a stable, boring, niche WordPress product.
The “boring niche” part matters. Recipe plugins aren’t sexy, but food bloggers need them, the market is stable, and buyers exist who want cash-flowing assets without building from scratch.
The lesson: You don’t need explosive growth to have an exit. Stability and profitability in a defined niche can be worth more than a larger, more volatile business.
The $400/Month Reservations Plugin (And Why the Expansion Failed)
When the Plugin Works But the Platform Doesn’t
On the other end of the spectrum, one founder shared their struggle:
- Built a WordPress reservations plugin for sports clubs
- Reached $300-400 MRR
- Tried to expand into WaaS (Website as a Service)—multisite setup, quick deployment, the whole platform play
- After a year, the WaaS side failed to gain traction
Why the Expansion Didn’t Work
The plugin sold. People paid $300-400/month in aggregate for reservation functionality. But when the founder tried to turn it into a hosted platform, the market didn’t respond.
Possible reasons:
- The ICP is too niche. Sports clubs with WordPress sites and reservation needs is a small pond. “Platform” implies scale that may not exist.
- Buyers don’t self-identify as needing “platform.” They want a plugin that solves a problem, not a whole new way to run their website.
- Distribution mismatch. The people who find WordPress plugins aren’t necessarily the people looking for hosted solutions.
What This Actually Tells You
Plugin revenue and platform revenue require different customers, different positioning, and different distribution. A working plugin at $400 MRR is a real business (small, but real). Assuming it can become a platform because the functionality exists is a different bet entirely.
The Pattern: What These Micro-Businesses Have in Common
1. Sell to Implementers, Not End Users
Anchor Hosting sells to agencies. PowerPack sells to freelancers and agencies. Even the recipe plugin likely served food bloggers who are essentially solo content businesses—people who implement, not casual users.
Implementers bring repeat business. An agency that likes your hosting will put every new client on it. A freelancer who uses your page builder add-on will install it on every project. Your customer’s growth becomes your growth.
2. Bundle a Simple Promise
Anchor Hosting: “Maintenance essentials included.”
PowerPack: “Modules and templates that speed up builds.”
Neither is trying to be everything. They’re packaging a narrow, clear value proposition that justifies the price and makes the purchase decision easy.
3. Revenue Outcomes Are Wildly Variable
Even within “WordPress businesses started by solo founders,” the range is enormous:
| Business | Monthly Revenue | Notes |
|---|---|---|
| Sports club reservations plugin | $300-400 | Niche tool, WaaS expansion failed |
| Recipe plugin (at exit) | $3,000 | Sold for $50K |
| Anchor Hosting | ~$19,750 | Solo operator, 900 sites |
| PowerPack for Beaver Builder | $20-25K | Agency-focused add-on |
Same ecosystem. Same rough business model (recurring revenue from WordPress users). 50x difference in outcomes.
4. Exits Exist at Every Level
The recipe plugin exit proves you don’t need to be doing $100K MRR to sell. Acquirers exist for stable, profitable micro-businesses—especially in niches where someone wants cash flow without the build phase.
Why These Stories Matter
The big transparency reports are useful, but they describe a specific outcome: plugin businesses that grew large enough and lasted long enough to publish annual reviews. They’re the visible success stories.
The Indie Hackers posts capture something different—the distribution of outcomes before survivorship bias kicks in. Some founders hit $20K/month and keep going. Some peak at $3K and sell. Some get stuck at $400 and can’t figure out why the expansion isn’t working.
All of these are real WordPress businesses. All of them are generating (or generated) revenue. The variance is the insight.
If you’re building in WordPress, the question isn’t just “what’s possible at the top?” It’s “what does the realistic range look like, and which factors push you toward which end?”
These micro-cases won’t tell you the answer. But they’ll give you a better sense of the actual distribution than any single success story can.
All Sources
Anchor Hosting:
PowerPack for Beaver Builder:
- Pausing Our Digital Agency to Build a $20k/mo WordPress Plugin (Indie Hackers)
- PowerPack Revenue Widget (Indie Hackers)
Recipe Plugin Exit:
Reservations Plugin / WaaS Struggle: