Loading page…
He bought a neglected WordPress classifieds plugin off Flippa for $1,000, added a shopping cart, a support forum and higher prices — and grew it from $300 a month to $2,000, then repeated the trick for $1,400
Business Directory: bought for $1,400 in January 2012 at ~$150/mo, surpassed AWPCP nine months later at roughly 30x its purchase-time revenue · bundles of ~12 modules discounted ~50% now account for about 65% of total revenue · total acquisition budget $2,000 (AWPCP bought for $1,000 after a failed $3,500 auction)
His entire edge was that 99% of the WordPress plugin repository is poorly supported and poorly documented — "all you really have to do is not trip over the bar to look like a complete hero."
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
By 2009 he had been freelancing for over a decade and was tired of trading hours for dollars. He did not want the VC-funded startup route, and then he saw a Hacker News post about an opening in the Micropreneur Academy and joined. Inside, he found a clear split. On one side were people trying to bring an original idea to fruition from scratch. On the other was the argument that you can buy something and fix and flip it, real-estate style. Either way he would need three things: a market with a solvable problem, a product that solved it, and a way to promote to that market. Building meant creating all three from nothing. Buying meant inheriting an existing market and an existing product with customers, and concentrating on promotion. Given his personality, buying suited him. His criteria were specific: established traffic, existing customers, a poor sales funnel he could optimise, ugly design, some revenue with room to grow, and within a budget of $2,000 — "the amount of money that I could possibly lose without causing great marital discord." Flippa was the venue, and his expectations were wrong. He had imagined "Indiana Jones waltzing into the temple simply plucking the golden idol off the pedestal." What he found was "a large pile of garbage that requires a huge amount of patience to sift through and an unbelievable amount of diligence." His first purchases were bad decisions — including an online cron job service, which he says he is not proud of — but they taught him how to rehabilitate a site. Then in May 2010 he found the auction for AWPCP, Another WordPress Classifieds Plugin. He knew nothing about WordPress or classifieds and was not remotely passionate about either. But it had customers, traffic, about $300 a month of revenue, and it was ugly. The owner had listed it at $3,500; the auction ended with no buyer. He contacted her privately afterwards, offered $1,000, and she accepted.
He never faced a zero. The first customers arrived with the purchase: AWPCP came with established traffic, an existing customer base and about $300 a month in revenue, and it cost $1,000 in May 2010.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself. The exact words are quoted below, with a timestamp that jumps to the second each figure is said.
“…traffic I was making revenue to the tune of about $300 a month which doesn't sound like much but it certainly had some potential oh and it was ugly…”
5:03 · hear it in the video“…the first month of revenue I got there was about $150 a month so nine months after I acquired that and did everything - business directory that I did…”
8:54 · hear it in the videoData credibility: Founder-reported in a recorded conference talk (MicroConf), with revenue charts displayed on screen and narrated aloud — so the figures have visual backing from the speaker's own dashboard but nothing independent. The speaker never states his own name in the transcript and explicitly says he has omitted a large amount of detail because of the session format, inviting people to ask him afterwards. Self-reported figures: a total acquisition budget of $2,000; AWPCP (Another WordPress Classifieds Plugin) listed on Flippa at $3,500, auction ended without a buyer, bought privately for $1,000 in May 2010 at about $300/month of revenue; about $600/month by June 2010; about $2,000/month by December 2011; Business Directory bought for $1,400 in January 2012 at about $150/month in December 2011, with revenue surpassing AWPCP nine months later at roughly 30x its purchase-time level; bundles of about twelve modules at roughly 50% off the sum of individual prices accounting for about 65% of total revenue; a bundle-size threshold somewhere between three and twelve items that he says he did not track precisely; and the previous owner's seven modules priced at $19.99, $25.99 and $39.99 among others. He also discloses failures: several bad Flippa purchases including an online cron job service, a first outsourced developer fired for non-responsiveness (replacement hired November 2011), a week-long removal from the WordPress repository over permissions the original author had failed to secure, and other purchased sites cratering after Google's Panda and Penguin updates. DATING CAVEAT: the talk references the 2013-era MicroConf sponsor set (Bidsketch, HitTail, Drip, Authority, Planscope) and Facebook ads in 2013 as recent, placing the recording around 2014 and the events in 2009-2012. Every figure should be read as that vintage. Region is null: no city, state or country is named anywhere in the transcript. He mentions a wife, PayPal, US dollars and attending MicroConf, none of which is a location claim, and we have not inferred one. The company names AWPCP and Business Directory are stated clearly; the platform is stated as Flippa, described as 'the eBay of websites'.
The first dollar under his ownership came through machinery he had not built and immediately wanted to replace. The plugin itself was free in the repository; money came from about seven paid add-on modules priced at $19.99, $25.99, $39.99 and whatever else the previous owner had picked.
Three loops fed each other. The first ran on ratings: better support lifted the plugin's score, higher scores pulled more installs out of the wordpress.org repository, and installs produced revenue.
His flat stretches came in two shapes, and neither of them was silence. The first was tuition.
AWPCP is a classified-ads plugin for WordPress, sold as a free core plugin in the wordpress.org repository with paid add-on modules. Business Directory, acquired later, is the same shape for directory listings. What he bought was not really software; it was a functioning market position wrapped in bad operations. The previous owner's setup is worth listing because every element was a fixable defect: The site did not look like a store. "It kind of looked more like a blog, so it didn't even look like you could buy something there." Sales were manual — the PayPal button in the corner was the entire sales machine: a customer clicked it, she received an email, and she manually sent out the module. "This is crazy. Nobody wants to deal with that." Support ran inside WordPress post and page comments, scattered across the site, not centralised and not searchable — "a nightmare on both sides." And pricing was chaos: about seven modules at $19.99, $25.99, $39.99 and whatever else, with no logic. His fixes were correspondingly unglamorous. A shopping cart with automated downloads. A proper support forum. A design that looked like commerce. Six months later the site looked professional, was easier to navigate, and customers were getting what they needed out of the plugin. Our read: this is the clearest example in the index of value created by operations rather than by product. He did not add features that made the plugin better at classified ads. He made it possible to buy, possible to get help, and priced coherently — and revenue multiplied several times over.
Paid modules on top of a free plugin, and three specific pricing moves did most of the work. First, levelling and raising. The previous owner's seven modules were priced at arbitrary numbers. He standardised them and raised them all. The obvious effect was more revenue; the second effect he did not expect: "it also had a second effect, and that was to actually get rid of my complaining high maintenance customers, the ones that were really burdening me down in support." Price is a filter on customer quality, and in a support-intensive business that filter is worth as much as the margin. Second, bundling — and this is the number to remember. He assembles about twelve modules into a bundle priced at roughly 50% off the sum of the individual prices. "Customers buy these things like hotcakes. Right now they account about 65% of my total revenue." He also found a threshold: too few items in a bundle and customers were not interested. His working range is somewhere between three and twelve items, and he admits he did not track exactly where it flipped — but it matters. Third, the revenue trajectory itself, which he shows on a chart during the talk. AWPCP was about $300 a month when he bought it and about $600 a month by June 2010. By December 2011 it was around $2,000 a month. Then January 2012: the original author contacted him. She had another plugin, Business Directory, plus a WordPress theme business she wanted to focus on, and the plugin was not doing well. Every problem in Business Directory was one he had already solved in AWPCP. He asked her price — $1,400 — and bought it the same day. It was making about $150 a month in December 2011. Nine months after he applied the same fixes, its revenue surpassed AWPCP's and was roughly thirty times what it had been at purchase.
The free repository is the channel, and the mechanism is almost embarrassingly simple. "WordPress.org is basically Google for WordPress plugins. If you have a WordPress plugin and you're not somehow in the free repository, you're just missing out on a huge stream of customers." The optimisation is a text file. "If you just create a readme text — which you're supposed to do as a plugin anyway — and you put your keywords in, you will rank inside of the WordPress search engines for your plugin on those keywords. That's a really easy thing to do because wordpress.org doesn't have any tricky algorithms. You don't have to worry about backlink strategies, no blood sacrifices to Matt Cutts." And then the compounding effect: "when you start to rank well in wordpress.org, because wordpress.org is a trusted domain, you also rank well in Google. So you get Google for free just by optimising your wordpress.org." The second channel is ratings, and it is downstream of support rather than of marketing. His first observation about the category is the whole competitive thesis: "support is absolutely everything for a WordPress plugin. Everything that's in the repository — like 99% of them are poorly supported and poorly documented. So all you really have to do is not trip over the bar to look like a complete hero." The consequence chain is direct: fix support, customers rate the plugin higher, higher ratings drive more installs, more installs drive more revenue. He had inherited poor ratings precisely because customers were not getting help. He also names the source of design ideas for anyone with none: look at the sites being discussed at the conference you are attending — he lists Bidsketch, HitTail, Drip, Authority and Planscope — pick one aspect of their onboarding, support or sales page that you like, and put it on your own site. "You're going to end up doing fairly well just by borrowing from sites that are doing it well." And the closing rule: get feedback only from customers. "Theirs is the only opinion that actually matters. Anybody else that's not a customer, it doesn't mean much for them to tell you that your site is good or bad."
The economics are the point of this entry: total capital at risk was $2,000, and the two acquisitions that mattered cost $1,000 and $1,400. The operating cost is one outsourced developer, and the story of hiring badly is the most useful cost lesson here. By December 2011 his original three areas of focus had become four, because support was consuming so much time that he could not do product development as well. So he hired an outsourced developer — and it went wrong. There is a visible dip in his revenue chart covering the months when "my developer was actually not responding to my emails, not dealing with customer bugs, my customers were getting mad, I was having to give refunds, and I didn't really have the gall to fire him at that point — and I really should have." He eventually did, hired a replacement in November 2011, and "things started firing on all cylinders." Our read: the dip is the most honest chart in this index. A support-driven business run by one person plus one contractor has exactly one single point of failure, and it is the contractor. The lesson is not "outsource carefully"; it is that in a business where support is the moat, an unresponsive developer directly attacks the moat. He is also candid about the failures that preceded the win: several bad buys on Flippa, including a cron job service he thought he could make money on. He frames them as tuition — they gave him the experience of rehabilitating a site, improving marketing, sales process and onboarding, before he found a good one. And he names an external risk that materialised: "you can actually have things change really radically. Like when Google Panda and Penguin came out, a couple of the sites that I bought just cratered. So it was lost money." His advice on funding matches the risk profile: stay within a budget, and "I would definitely not recommend getting a loan or a second mortgage or anything like that. There's definitely inherent risk involved in this and nothing is really certain."
Copy the acquisition criteria verbatim, because they are a genuine screening checklist: existing traffic, existing customers, a poor sales funnel you can optimise, ugly design, existing revenue with room to grow, and a price you can afford to lose entirely. Note that "ugly" and "badly run" are on the buy list, not the avoid list — the defects are the opportunity. Copy the private-offer-after-failed-auction move. AWPCP was listed at $3,500 and did not sell. He contacted the seller privately afterwards and got it for $1,000. A failed listing is a motivated seller with a public reserve you now know. Copy the operational fix list in order, because it is the actual value creation: make it look like you can buy something, automate the purchase and delivery, centralise and make support searchable, then level and raise prices. Copy the bundle. Twelve modules at roughly half the sum of their individual prices, producing about 65% of total revenue. And respect the threshold — a bundle with too little in it does not sell. Copy the raise-prices-to-shed-bad-customers insight, which is counterintuitive and free: higher prices removed the high-maintenance customers who were consuming his support capacity. Copy the platform-repository play. Whatever ecosystem you are in — WordPress, Shopify, Chrome, Figma, Notion, Slack, VS Code, an MCP registry — the free listing is the channel, the listing text is the SEO, and ranking on a trusted domain earns general search traffic for free. Copy the buy-a-second-one move. Once you have solved a category's operational problems, a second neglected asset in the same category is nearly pure margin: $1,400 became roughly 30x in nine months because the playbook already existed. What to change: the numbers are small and the era was different — this talk dates from roughly 2014, describing 2009-2012. Marketplaces have matured and multiples on small WordPress assets are higher. And WordPress specifically is a shrinking bet relative to newer plugin ecosystems. The mechanic transfers; the market should be reconsidered.
Platform terms of service nearly ended it, and the cause was inherited. "I ran afoul of the WordPress Terms of Service — except that this was something that the original author had just failed to secure permissions for things in the plug-in, and I didn't know about that." One of the customers who was angry during the bad-developer months reported him, and he was kicked out of the repository for a week. It took "a very set of tense conversations back and forth" plus promises to get back in. His warning: delineate free and commercial aspects very clearly and secure all permissions, "because they are extremely serious about that. No joke." That is a compound risk worth naming: you inherit the previous owner's compliance liabilities, you may not know about them, and the trigger for discovery can be an unhappy customer. Search-algorithm risk is real and he saw it. Google Panda and Penguin cratered a couple of the other sites he bought — money simply lost. Due diligence risk on the marketplace is the everyday hazard. He describes Flippa as a large pile of garbage requiring huge patience and unbelievable diligence, and admits to buying badly more than once before buying well. Single-contractor dependency is the operational risk, and it is visible as a dip in his own revenue chart: months of unanswered emails, unfixed customer bugs, angry customers and refunds, while he lacked the resolve to fire the person. Support load is the structural constraint. Support is simultaneously the moat and the thing that consumed so much of his time that he could not develop the product — which is why he had to hire in the first place. Platform concentration is total. Both assets live and die inside the WordPress ecosystem's free repository, its search, and its rules. On evidence: this is a conference talk (MicroConf) with revenue charts shown on screen and narrated, so the numbers have visual backing but nothing independent. The speaker never gives his own name in the transcript and says explicitly that he has omitted a huge amount of detail because of the format. The talk is old — it references 2013 Facebook ads and the same era's MicroConf sponsors — so treat all figures as 2009-2012 vintage. No location is stated anywhere in the transcript, so region is left null.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click