How We Scaled PitchGround to $25M GMV: The Complete Playbook
How PitchGround scaled from zero to $25M GMV — marketplace mechanics, flywheel, crisis moments, and lessons for any marketplace founder.
Whether you're looking for an angel investor, a growth advisor, or just want to connect — I'm always open to great ideas.
Get in TouchAI, startups & growth insights. No spam.
TL;DR: PitchGround was a SaaS lifetime deal marketplace I co-founded and scaled to $25M in gross merchandise value. This post is the complete playbook — the origin story, how we recruited SaaS founders onto the supply side before we had any audience, how we grew the buyer community into the demand engine, the flywheel mechanics that compounded GMV, the crisis moments that nearly killed us, and the hard lessons I would apply differently if I were starting over today. Nothing is sanitized.
The honest origin story of PitchGround does not start with a lightbulb moment. It starts with frustration.
I was working on a SaaS product myself — a tool for productivity, bootstrapped, no external funding, the whole nine yards. And I was trying to figure out how to get my first paying customers without spending money I did not have on advertising I could not track. I had a product. I had a landing page. I had exactly zero customers.
I started looking at what other bootstrapped founders were doing, and I kept seeing the same pattern emerge: AppSumo. Founders were listing their products on AppSumo, running lifetime deal campaigns, generating $50K–$200K in revenue in a matter of weeks, and using that capital to fund the next 12 months of product development. It was not recurring revenue. It was not VC money. It was a burst of upfront cash from customers who believed in what you were creating enough to bet on it once, forever.
I studied every AppSumo launch I could find. I watched the Facebook groups where buyers and founders would discuss these campaigns. I noticed something: the market had exactly one major player, and that one player had enormous leverage over the founders who listed on it. The terms were not always founder-friendly. The audience was locked inside AppSumo's ecosystem. And the product quality on the platform had started to become inconsistent — buyers were getting burned by tools that overpromised and underdelivered, and the trust signal of the marketplace was degrading.
I saw a gap. A marketplace that was more selective about quality, that treated founders as partners rather than inventory, that grew a buyer community with genuine trust and curation standards. Not just another place to dump deals. A platform with a point of view.
That was the thesis behind PitchGround. It was not a brilliant strategic insight. It was a direct response to market dynamics I had personally observed as both a potential seller trying to figure out how to get customers and an occasional buyer trying to find tools worth investing in at lifetime pricing.
The name came from a simple idea: this was a place where founders pitched their product, and where the community decided whether it was worth backing. Pitch. Ground. A platform to stand on and make your case.
I did not have a co-founder at launch. I did not have funding. I did not have an audience. What I had was a clear thesis about why the market needed something better, a network of SaaS founders I had connected with over years of putting my work in public, and a conviction that trust and curation were defensible advantages in a market where the dominant player had gotten sloppy.
What followed was the most difficult, exhausting, occasionally terrifying, and ultimately most formative professional experience of my life.
Anyone who has tried to create a two-sided marketplace has felt the cold-start problem in their chest at 2am. It is a chicken-and-egg problem with no elegant theoretical solution. Buyers will not come without sellers. Sellers will not come without buyers. And you need both sides to be warm simultaneously for any transaction to happen.
The mistake most marketplace founders make is trying to solve both sides at once. They spread themselves thin recruiting buyers and sellers in parallel, make no meaningful progress on either, and eventually collapse under the weight of two equally-difficult acquisition problems running simultaneously.
I made a deliberate choice: solve one side first, completely, before touching the other.
My instinct was to start with supply — with the SaaS founders. My reasoning was simple: if I had three or four compelling product launches lined up and ready to go, I could manufacture demand by creating an event worth showing up for. A launch window with a high-quality product is inherently marketable. An audience with no products to buy is just a mailing list that has nothing to click.
So for the first three months of PitchGround's existence, I did not try to grow a buyer community at all. I focused every hour I had on recruiting SaaS founders to list their first campaigns.
The supply-side problem was its own cold start, of course. Why would a SaaS founder list their product on a platform with zero buyers? The answer I developed — and refined over dozens of conversations — was threefold.
First, I was not asking them to take a chance on an untested audience. I was asking them to co-create the platform with me. I framed early listings as a founding partner relationship. You are not just another deal on PitchGround. You are one of the first five products to launch here, and that means your product helps define what PitchGround is.
Second, I made credible promises about the launch experience. Not audience size, because I could not honestly promise that. But I could promise something the dominant competitor could not: real attention, a personal relationship, and a founder-to-founder partnership where I would do everything in my power to make the launch succeed.
Third, I used my personal network aggressively and shamelessly. I sent direct messages to every SaaS founder I had connected with over the preceding two years. Every Twitter conversation, every Slack group exchange, every Product Hunt comment thread — I worked every single connection I had. Most people said no. But some said yes, and those yes conversations gave me the first pieces of supply I needed to grow from.
The cold-start problem in marketplaces is not a marketing problem. It is a trust problem. The first sellers on your platform are not evaluating your platform — they are evaluating you. Your reputation, your work ethic, your credibility as a person who will work as hard for their success as you are asking them to risk.
That insight changed how I ran every single early supplier conversation. I stopped pitching the platform. I started pitching myself.
Getting the supply side right was everything. The buyer experience is ultimately a function of product quality, and product quality is a function of how carefully you curate and support the founders who list with you.
Here is the honest breakdown of how we grew the supply side.
My outreach template in the early days was not polished. It was personal. I wrote every message individually, and I always referenced something specific about the founder's product or journey that showed I had done real homework.
The message was roughly this: I am creating a new lifetime deal marketplace that is going to be different in three specific ways — higher curation standards, a founder-first partnership model, and a community that is organized around trust rather than deal volume. I am looking for five founding partners to launch with. I think your product is exactly the kind of thing our audience will respond to. Can we get on a call?
The specific things that converted skeptical founders:
Transparency about the deal structure. I explained the revenue split upfront, before they asked. Most platforms make you dig for this. Being proactive about it signaled that I was not trying to hide something.
A clear launch roadmap. I would share exactly what the launch would look like — the email campaigns, the social promotion, the community posts, the review period, the campaign window. Founders felt like they knew what they were signing up for, which reduced the perceived risk.
A personal commitment. I told founders explicitly: if your launch is underperforming, I will personally reach out to our community to understand why and adjust our promotion strategy. I will not just let a campaign sit there and fail. They were trusting me with their product. The least I could do was promise to fight for them.
References from other founders. This was the highest-converting element, but I could only use it once I had a few successful launches under my belt. By launch number four or five, I had founders I could connect new prospects with directly. Social proof from peers was worth more than anything I could say myself.
This was one of the most consequential decisions I made in the first year: PitchGround would not list every product that applied.
I reviewed every submission personally. I used a simple but non-negotiable framework:
| Criterion | What I looked for | Dealbreaker if... |
|---|---|---|
| Product maturity | At least an MVP in users' hands, not vaporware | Zero real users, demo-only product |
| Founder responsiveness | Quick replies, clear communication | Took days to respond to basic questions |
| Support quality | Evidence of founder actively supporting users | App store reviews showing abandoned tickets |
| Roadmap clarity | Honest articulation of what was planned | Vague promises with no specifics |
| Pricing sanity | LTD price reflective of long-term value | Deal structured to extract cash before delivering |
| Refund policy | Willing to offer a meaningful refund window | Refusing any customer recourse |
Turning down deals was painful early on, when I needed supply badly. But every deal I rejected protected the buyer community's trust in PitchGround's curation. And that trust was the only durable competitive advantage we had.
The hardest decision I made in the first six months was saying no to a product that would have generated significant revenue but that I did not personally believe in. The founder was polished, the marketing was good, and the revenue projections were attractive. But the product was not ready. I passed. Three months later, that product launched on a different platform and had a wave of refund requests and angry community posts. That decision — and outcomes like it — is what grew PitchGround's reputation.
By the time we had a functioning audience, our supplier value proposition had evolved from "please trust me" to something more concrete:
| What we offered | Why it mattered to founders |
|---|---|
| Community-based discovery | Buyers who found products through community discussion converted better and churned less |
| Pre-launch review period | Community members could ask questions before buying, which grew launch momentum |
| Founder AMAs | Direct engagement drove authenticity and buyer confidence |
| Transparent sales reporting | Real-time revenue dashboards, not weekly summaries |
| Post-launch support structure | We stayed engaged after launch, not just during |
| Founder-referral introductions | Successful founders referred others to list with us |
That last item became our most efficient supply acquisition channel by year two. A founder who had a successful PitchGround launch would tell other founders in their network. The word-of-mouth recommendation carried far more weight than anything I could say directly, because it came from someone who had done it and had the revenue to show for it.
Once I had the first two or three product launches lined up and a launch calendar I was confident in, I shifted attention to demand.
The lifetime deal buyer community is a specific, identifiable group of people. They are typically small business owners, freelancers, agency operators, and bootstrapped founders who have a strong preference for paying once rather than subscribing indefinitely. They understand software. They are not looking for polished enterprise tools — they want functional, founder-made products at prices that reflect the risk they are taking as early adopters. And they talk to each other constantly, in Facebook groups, Slack communities, Reddit threads, and private Discord servers.
My demand strategy was not advertising. It was infiltration — in the best possible sense. I went where these buyers already gathered and became a genuine participant in those communities.
For the first six months, my demand acquisition playbook was entirely organic:
Facebook groups. The lifetime deal community lived heavily in Facebook groups dedicated to SaaS deals and tools. I joined every relevant group I could find. I did not post promotions. I answered questions, shared honest product opinions, and grew a reputation as someone with genuine knowledge and no hidden agenda. Over time, when I would mention PitchGround, people were predisposed to trust it because they trusted me.
Twitter build-in-public. I documented PitchGround's journey publicly — metrics, milestones, failures, decisions. The approach attracted two groups simultaneously: potential buyers who liked the authenticity, and potential seller-founders who related to the experience of creating something from scratch.
Direct community seeding. For our first launches, I recruited every real-world contact I could find who fit the buyer profile and personally invited them to be among the first members of the PitchGround community. These were not cold prospects. They were friends, professional contacts, people who had helped me, people I had helped. The first 500 members of PitchGround's email list were people who had a personal reason to want to see me succeed.
Content about the deals, not just the platform. We wrote detailed breakdowns of the products we were launching — not marketing copy, but honest assessments written from a buyer's perspective. What does this tool do, who is it for, what are its limitations, and why are we excited about it? This content ranked in search for product-related queries and drove inbound discovery from people who had never heard of PitchGround.
The email list was the most important asset PitchGround had, and I treated it accordingly.
Every person who joined the list received a genuine onboarding sequence that told them what PitchGround was, who the founder was (me), how we chose which products to feature, and what our standards were. This was not a generic newsletter welcome. It was a manifesto about why we were different and what they could expect.
The unsub rate for new subscribers who went through this onboarding was significantly lower than for those who did not. People who understood what they were signing up for were more likely to stay. Open rates in the early days were exceptional — above 50% — because the list was small enough to be genuinely curated and every launch announcement was for a product I personally believed in. Open rates are a trust metric before they are a volume metric, and they highlighted how important retention was to our growth model.
One of the demand-side innovations I am most proud of is the pre-launch review period we incorporated into every campaign.
Before a product went on sale to the general public, we gave a select group of community members early access and a structured discussion thread where they could ask questions, share first impressions, and engage directly with the founder. This did several things:
The buyers who participated in pre-launch reviews became the most vocal advocates for PitchGround deals. They had skin in the game — they had spent time evaluating the product — and they were invested in its success.
Turning passive buyers into active community contributors was the single highest-leverage thing we did on the demand side. A buyer who just receives an email and clicks a link is a transaction. A buyer who participates in a discussion, asks the founder a question, and shares their first impressions is a community member. Community members refer other buyers, return for future launches, and defend the platform's reputation when something goes wrong.
The moment I understood PitchGround's growth as a flywheel rather than a funnel was the moment everything clicked.
A funnel is linear: you put people in the top, they convert or they do not, and you move on. A flywheel is self-reinforcing: each part of the system feeds energy back into the other parts, and the whole thing spins faster as more energy is added.
PitchGround's flywheel worked like this:
Step 1: A high-quality product launch. A founder with a great product lists with us. We run a successful campaign. Buyers get a genuine tool at great value.
Step 2: Buyer trust compounds. Happy buyers share their purchase in community channels. They write positive reviews. They return for future launches because their previous purchase delivered value.
Step 3: Founder word-of-mouth. The founder whose campaign succeeded tells other founders. "PitchGround actually cares about making your launch work. You should list there." This word-of-mouth acquisition was far more efficient than paid channels.
Step 4: Better supply. Higher-quality founders apply. We can afford to be more selective. The curation standard improves, which increases buyer trust further.
Step 5: Community growth. More buyers join because the community reputation for quality is strong. More buyers means more revenue per launch. More revenue per launch makes listing with us more attractive to founders.
Step 6: Repeat. The flywheel spins faster.
The critical insight is that Steps 2, 3, and 4 are not things you can buy or shortcut. They are the compounding effects of doing Steps 1 and 5 right consistently. Every time we cut a corner — approved a product that was not quite ready, ran a campaign we were not proud of, overpromised on revenue — we put friction in the flywheel. Every time we held the line on quality, we took friction out.
| Flywheel Element | What fed it | What broke it |
|---|---|---|
| Buyer trust | Quality launches, honest curation, founder transparency | Mediocre products, refund controversies, overhyped descriptions |
| Founder referrals | Successful campaigns, personal attention, fair terms | Poor launch support, opaque reporting, slow payments |
| Community engagement | Founder AMAs, pre-launch reviews, buyer discussion threads | Generic promotional content, no founder interaction |
| Platform reputation | Curation standards, community culture, success stories | High-profile failed products, public buyer complaints |
The math behind flywheel compounding was more powerful than I had initially estimated. In year one, we ran campaigns roughly once a month. In year two, we ran two to three per month. By year three, we had a multi-track launch calendar with different product categories and buyer segments running simultaneously. Each additional successful launch added mass to the flywheel. The energy required to keep it spinning stayed roughly constant while the output scaled dramatically.
The first $100K of GMV came from the first four or five product launches we ran. Each one taught me something critical.
Launch one was humbling. We had about 400 people on the email list. We sent the campaign announcement. We generated a few thousand dollars in revenue. By any absolute measure, it was not impressive. But the percentage of email subscribers who bought was high — far higher than industry averages — and that conversion signal told me that the quality thesis was real. People were buying because they trusted the curation, not just because of the price.
Launch two was better. Not because our email list was dramatically larger — it had grown, but not exponentially. It was better because the buyers from launch one came back, and they brought two or three friends with them. The referral loop was beginning.
By launch five, we had crossed $100K in total GMV. I remember the exact moment I refreshed the dashboard and saw the number. I sat with it for a minute. Then I wrote a post about it publicly, because I had promised to document this journey honestly, and the journey had just crossed a threshold that mattered.
The first $100K proved three things: the buyer community was real, the curation model worked, and the flywheel was beginning to spin.
The jump from $100K to $1M GMV happened faster than I expected. Not because we had cracked some marketing code — it was because the flywheel had enough rotational energy to start pulling itself forward.
Between the $100K and $1M milestones, the key changes were:
Email list growth accelerated through referrals. Our referral mechanics were primitive — mostly word of mouth — but the community was enthusiastic enough that it worked. We went from a few thousand subscribers to tens of thousands.
The founder pipeline filled through word-of-mouth. I was no longer cold-messaging every potential listing. Founders were coming to us through referrals from other founders who had launched successfully. The inbound quality was higher than the outbound quality had ever been.
Launch revenue per campaign increased. Partly because the list was larger, but primarily because the community's trust in PitchGround recommendations had deepened. A new buyer visiting PitchGround for the first time was landing in a community with months of positive social proof. That context meant they were more likely to buy, and more likely to buy without extensive deliberation.
We developed a launch formula. By launch ten or fifteen, we had a repeatable structure: pre-launch review period, community discussion, email announcement sequence, founder AMA, promotional campaign window, post-campaign support. This formula reduced variance and gave founders a predictable experience.
The $1M GMV milestone was the point at which PitchGround stopped being an experiment and became a real business. We had demonstrated that the model worked. The question was no longer "can this work" but "how big can this get."
The journey from $1M to $25M GMV took time and involved significant growing pains. A few of the things that drove it:
Expanded launch cadence. We increased the frequency of launches without sacrificing quality standards. This required process improvements — better pre-launch review systems, more structured communication workflows, faster payment processing.
Community infrastructure investment. We created better community infrastructure — dedicated platforms, more active moderation, content calendars that kept the community engaged between launches rather than only during them.
Geographic expansion. The SaaS buyer community is global. We started with a primarily English-speaking audience and gradually expanded outreach to founder communities in India, Southeast Asia, Eastern Europe, and Latin America — both on the supply side and the demand side.
Affiliate and referral programs. We formalized the referral mechanics that had been driving organic growth. Community members who referred new buyers earned commissions. Founders who referred other founders received benefits. These programs turbo-charged the word-of-mouth loops that were already working organically.
Lifetime deal pricing is one of the most misunderstood aspects of the LTD marketplace business. I have seen founders make mistakes on both ends — pricing so low that they generate revenue but doom themselves financially, and pricing so high that the deal value proposition falls apart entirely.
The framework we developed at PitchGround for helping founders set lifetime deal pricing:
The most important number in any lifetime deal is not the LTD price. It is the monthly or annual subscription price that the LTD is being discounted against. If a product normally costs $99/month ($1,188/year) and the LTD is priced at $299, the buyer is paying for roughly three months in exchange for lifetime access. That math needs to be intuitive and defensible.
We pushed founders to be honest about their regular pricing. Artificial list prices designed to make the LTD look like a bigger discount than it was always created problems — buyer communities are sophisticated, and inflated reference prices get called out publicly and loudly.
Almost every successful PitchGround launch was structured with multiple tiers:
| Tier | Typical Price Range | Features | Target Buyer |
|---|---|---|---|
| Tier 1 | $49–$79 | Core features, usage limits | Individual users, freelancers |
| Tier 2 | $99–$149 | Enhanced limits, additional features | Small teams, growing businesses |
| Tier 3 | $199–$299 | Unlimited or near-unlimited use, advanced features | Agencies, power users |
Tiering served multiple functions: it increased average order value by giving buyers a reason to upgrade, it served different buyer segments simultaneously, and it created natural social dynamics in the community as buyers debated which tier was the right value for their situation.
One of the most important protections we put in place for both buyers and founders was a revenue cap on each campaign — a maximum number of license codes sold. This protected buyers from a scenario where the product became overwhelmed with customers the founder could not support. It also created genuine urgency: when a campaign was approaching its cap, the community knew the deal was truly limited.
Refund windows were non-negotiable. Every PitchGround launch offered a minimum 30-day refund period, and we recommended 60 days. Founders who resisted this were not ready to list with us. The refund window is a quality signal — founders with good products are not afraid of it, because they know their product delivers value.
One conversation I had dozens of times was with founders who were excited about the revenue projection for their LTD campaign but had not thought through the long-term implications. Selling lifetime access to 500 customers means those 500 customers will receive support indefinitely, and the incremental cost of that support needs to fit within the margin from the LTD revenue.
The rule of thumb I developed: a lifetime deal campaign should generate enough revenue to fund 18–24 months of product development and support costs. If the math does not work at that horizon, either the LTD price is too low, the campaign scope is too large, or the product is not ready for a lifetime commitment.
PitchGround was bootstrapped. There was no seed round. There was no runway cushion. Revenue from one launch funded the operations for the next two weeks, and the next launch funded the two weeks after that.
This is an intensely uncomfortable way to operate a company, and I would not recommend it as a strategic philosophy. It was a constraint I was working within, not a badge I was collecting. But it created a discipline that shaped PitchGround's culture in ways that were ultimately positive.
Every hire was justified against current revenue, not projected revenue. Every operational cost was scrutinized. Every system was made to be as lightweight as possible because we could not afford complexity.
My first hire was not a developer. It was a community manager.
This was a deliberate decision. The buyer community was the most valuable asset PitchGround had, and it needed dedicated attention. I was spending increasing amounts of time managing community discussions, responding to buyer questions, running launch AMAs, and moderating pre-launch review threads — and that was time I could not spend on supply acquisition, founder relationships, and platform strategy.
A great community manager could multiply the value of everything else we were doing. A developer, at this stage, would have been creating features nobody had asked for.
The second hire was a launch coordinator — someone who owned the operational workflow for each campaign, from initial founder onboarding through post-launch support. This freed me to focus on founder relationships and platform strategy rather than campaign execution logistics.
The third and fourth hires were in customer support and operations. By this point, the volume of buyer inquiries, refund requests, and technical issues had grown beyond what I could personally manage.
I had never managed anyone before PitchGround. I had always been an individual contributor — creating, writing, selling. Managing people was a skill I had to develop in real time, and I made a lot of mistakes.
The biggest mistake: assuming that people who shared my urgency would naturally produce outputs at the same pace I did. They did not, and my frustration at that gap was unfair and counterproductive. The people I hired were skilled. The problem was that I had not given them enough structure, clear priorities, or defined success metrics. That was on me, entirely.
The second-biggest mistake: not letting go of things I should have delegated earlier. I continued running launch communications directly for months after hiring a launch coordinator, which undermined their authority, created confusion for founders about who to contact, and burned my own time on tasks I had explicitly hired someone to handle.
Creating a company is a series of identity transitions, not just a series of decisions. The transition from individual contributor to founder-manager is one of the hardest, and nobody tells you it is coming until you are in the middle of it and drowning. The earlier you can recognize the transition and intentionally step into the new identity, the less painful it is.
I want to be honest about this section in a way that founders almost never are publicly. PitchGround nearly died multiple times. Here are the three moments that came closest.
In our second year, we listed a product that had passed our review process but that I had reservations about. The founder was charismatic and responsive, the product worked in the demo, and the community showed strong pre-launch interest. I overrode my own instincts and listed it.
Within a month of the campaign closing, buyer complaints started arriving in volume. The product was crashing for significant percentages of users. The founder's support response time went from same-day to days to nothing. Buyers were posting publicly in our community with angry messages. We had approximately 300 customers who had paid real money for a product that did not work, and the founder was becoming unreachable.
We issued full refunds to every buyer who requested one, funded from PitchGround's own revenue. The total cost was significant — several months of operating margin in a business that did not have much margin to spare. It was painful. But there was no alternative that would have preserved the community's trust.
The lesson was not "never take risks on founders." It was "trust your instincts when something feels off, and do not let revenue pressure override that signal." I had seen a red flag in the founder's communication style during our pre-launch conversations. I had rationalized it. I paid for that rationalization.
At our peak growth phase, a competitor emerged that was transparently modeled on everything PitchGround had created — the curation model, the community structure, the pre-launch review mechanic, even the brand aesthetic. They had more resources than we did, and they were aggressively recruiting our top seller-founders with more favorable short-term terms.
I spent approximately three weeks in a state of barely-contained panic. We lost two deals I had been counting on for the quarter's revenue. I had late-night conversations with advisors about whether we could survive a well-funded competitive assault.
The way through was not a features arms race or a terms war. It was doubling down on the relationships that we had cultivated over years and that no competitor could replicate quickly. I personally called every founder we had worked with and had an honest conversation: here is what is happening, here is why we are different, here is what we are working toward, and I would like you to stay. Most of them did. Not because our terms were better in every case, but because the relationship was real and the track record spoke for itself.
Relationships are the only sustainable competitive moat in a marketplace business. Products can be copied. Processes can be reverse-engineered. Pricing can be undercut. The trust accumulated through years of genuine partnership with both sides of your marketplace cannot be replicated on a six-month timeline, no matter how much money a competitor throws at it.
By year three, we were running a volume of launches that had outgrown our operational infrastructure. We were using manual processes for things that should have been automated, and the cracks were starting to show.
A launch payment processing failure caused a two-day delay in license code delivery for a high-profile campaign. Buyers were furious — they had paid for software they could not access. The founder was furious — their launch momentum was being killed by a problem they had not caused. I spent 72 hours in near-continuous communication managing the fallout across email, community threads, and direct messages.
The operational breakdown forced an investment in systems we should have made six months earlier. We rebuilt our license delivery infrastructure, automated our payment reconciliation processes, and created redundancy at every critical operational point. It cost money and time we did not have to spare. But the alternative was a slow operational death as launch volume continued to increase and manual processes continued to fail at scale.
The lesson: operational infrastructure is not exciting, and it does not generate revenue directly. It is also the unglamorous work that determines whether your business can grow past a certain point without imploding. Invest in it before you are forced to.
I get this question from founders and operators often, and I have been honest and unsparing in my thinking about it.
I would create the community platform before the marketplace. PitchGround's community was its most valuable asset, but for the first 18 months, it lived in fragmented places — Facebook groups, email threads, ad hoc forum posts. We should have invested earlier in a dedicated community platform that we owned and controlled. The dependency on third-party platforms created fragility that bit us more than once.
I would hire a head of operations earlier. The operational crisis we experienced in year three was predictable and preventable. I was not equipped to think clearly about operational systems while simultaneously running launches, managing founder relationships, and growing the buyer base. A dedicated operations leader could have prevented that crisis entirely.
I would have been more aggressive about publishing our quality standards publicly. We had internal curation criteria, but they were not public. Making them explicit — here is exactly what it takes to list on PitchGround, here is what disqualifies a product — would have raised the quality of inbound applications and made our community's trust easier to explain and defend to newcomers.
I would not have avoided pricing experiments for so long. PitchGround's take rate remained largely static for the first two years. I was nervous about changing it because I was afraid of losing founders. In retrospect, we had more pricing power than I was using, and earlier experimentation would have improved our unit economics without meaningfully affecting founder willingness to list with us.
I would have documented the playbook from day one. So much of what made PitchGround work lived in my head — my instincts about product quality, my approach to founder conversations, my sense of what the community valued. When I needed to delegate or scale those functions, I was starting from scratch every time instead of handing someone a document they could learn from. Institutional knowledge that lives in one person's head is a single point of failure.
I would have taken more care of my own health. The early years of PitchGround were genuinely punishing. I worked hours that I am not proud of in retrospect, slept poorly, skipped exercise, and was perpetually one major problem away from complete overwhelm. I did not have the tools or the self-awareness to manage that differently at the time. If I were starting over, I would incorporate rest and recovery into the operating plan rather than treating them as luxuries I would get to eventually.
These are the distillations I share with founders creating two-sided marketplaces and community-driven businesses today.
Pick the harder side of your marketplace — usually supply in deal-based or content marketplaces, usually demand in professional services marketplaces — and solve it completely before putting real energy into the other side. Half-solving both sides simultaneously is the fastest path to stalling out on both.
Before your platform has network effects, before you have an audience that speaks for itself, the only thing you have is your personal reputation. Every interaction with a founder or buyer is a deposit or a withdrawal from the trust account. Be relentlessly honest. Keep every promise. When you cannot keep a promise, tell the other person immediately and without spin.
The instinct in most product companies is to treat community as a marketing channel — a place to announce things, run promotions, and acquire users. In a marketplace business, community is infrastructure. It is the trust substrate that makes transactions possible. Invest in it like you invest in servers: because your business does not function without it.
In a market where the default is to maximize deal volume and take whatever listings are available, creating explicit limits — a finite number of launch slots per month, a meaningful rejection rate for applicants, a public quality standard — signals curation in a way that no marketing copy can replicate. Scarcity is a quality signal when it is real.
In a marketplace, the most valuable growth mechanism is not advertising. It is the referral loop between satisfied buyers who refer new buyers and successful founders who refer new founders. Create infrastructure to facilitate and incentivize this loop as early as possible, and track it obsessively. The referral coefficient tells you more about your business's health than almost any other single metric.
When something breaks operationally — a payment delay, a communication failure, a product disaster — the root cause is almost always a system that was not designed to handle the volume or complexity it was asked to handle. Do not just fix the immediate problem. Redesign the system so the problem cannot recur at the same point.
The founders who create the most resilient community businesses are the ones who invest in trust relentlessly during the good times, so that they have reserves to draw on when something inevitably goes wrong. Buyers and sellers alike are forgiving of honest mistakes from people they trust. They are not forgiving of dishonesty or avoidance from people they feel were never fully invested in their success.
What was PitchGround's take rate, and how did you decide on it?
Our take rate evolved over time. In the early days, it was set based on what I thought the market would bear relative to the dominant competitor, adjusted for the additional value we were providing through community-based launches and founder support. The more important variable than the take rate itself was the total value we delivered to founders — a higher take rate on a larger revenue outcome is more attractive than a lower take rate on a smaller one. I will not share the specific number here, but founder communities do discuss the range for established LTD marketplaces publicly.
How do you prevent burned buyers from destroying your community?
The most effective prevention is not having burns to start with, which requires rigorous curation. But when problems do occur — and they will, in any marketplace — the protocol is speed, transparency, and completeness. Respond immediately. Acknowledge the problem publicly. Communicate what you are doing to fix it. Follow through completely. Buyers who see a platform respond to a problem with integrity often become more loyal, not less, because they now know what to expect when things go wrong.
How did you handle founders who went dark after a successful launch?
This was a recurring challenge. A founder would run a successful campaign, take the revenue, and then become unreachable for support tickets. Our approach evolved into pre-launch agreements with specific support response time commitments, community-visible support threads so buyers could see whether founders were responding, and in severe cases, a warning system that affected founders' eligibility for future listings. The most effective tool was community transparency — a founder who ignores support tickets while the community watches is far more motivated to respond than one operating in private without accountability.
Did you ever consider taking VC funding to accelerate growth?
Yes, several times. We had conversations with investors at different stages. The fundamental tension was that the investors who were most interested in PitchGround wanted to accelerate growth in ways that I believed would compromise the quality standards that made the platform valuable. Flooding the platform with lower-quality listings to increase GMV in the short term would have accelerated metrics that investors cared about while undermining the community trust that was the actual business. We stayed bootstrapped. I do not know with certainty that this was the right decision for long-term scale, but it was the right decision for the kind of business I wanted to create.
What is the biggest misconception about the lifetime deal model?
That it is purely a discounting strategy. The best lifetime deal campaigns are not about offering a steep discount on an existing product. They are about co-creating a founding customer base — a cohort of highly engaged early adopters who are invested in the product's success because they are financially committed to it. The best LTD buyers are advocates, beta testers, and referral sources, not just customers who got a good price. Founders who understand this create very different launches than founders who treat it purely as a one-time revenue event.
How did you think about the long-term relationship between PitchGround and its buyer community?
My mental model was always that the buyer community was the core asset, and every decision I made was evaluated against whether it strengthened or weakened that community's trust in us. Short-term revenue decisions that compromised community trust were bad decisions, full stop, even if the revenue numbers looked attractive in isolation. Long-term, the only way to create a marketplace that could sustain itself was to have buyers who would show up for every launch because they believed the platform was working for them. Everything else flowed from that one commitment.
What advice would you give to someone starting a niche SaaS marketplace today?
Pick a vertical where you have genuine domain expertise or existing relationships. The cold-start problem is hard enough without also having to become an expert in the space you are operating in. Find the underserved side first — the supply or demand that exists but has no adequate platform to aggregate it — and work toward that gap. Resist the temptation to go horizontal too early; the most defensible marketplaces start narrow and expand with compounding advantages. And be honest with yourself about your competitive differentiation: if the only thing separating you from the dominant player is better marketing, you do not have a real business yet. Find the structural advantage — curation, community, access, specialization — and create everything around it.
How long did it take to reach $25M GMV in total?
The full journey from first launch to $25M GMV took several years of consistent operation, not months. The important thing about that number is not the headline — it is the trajectory behind it. The first $1M was the hardest. Each subsequent million came faster as the flywheel compounded. If you are starting a marketplace today and expecting exponential growth from month one, recalibrate that expectation. The compounding is real, but it requires sustained investment in community trust, curation quality, and supplier relationships before it reveals itself in the numbers.
PitchGround taught me more about marketplace mechanics, community creation, founder psychology, operational design, and my own limits than anything I had read or studied before working on it.
The lessons in this post are not theoretical. Every one of them cost something — money, time, relationships, sleep, pride — to learn. I share them because I wish someone had shared them with me before I started, and because I believe the founders creating two-sided businesses today deserve the unfiltered version of the journey, not the highlight reel.
If you are working on something similar and want to compare notes, you know where to find me.
A founder and angel investor's breakdown of the exact month-by-month playbook AI startups use to reach $10K MRR — what works, what kills momentum, and why.
The complete bootstrapped growth playbook — capital efficiency metrics, zero-CAC acquisition channels, pricing strategy, and real benchmarks by ARR stage for founders scaling without external capital.
How to write growth OKRs that drive outcomes — with 20+ real examples, scoring rubric, quarterly cadence, and a ready-to-use template.