LoginSign up for free

Choosing a business model while a startup or community is young

The Pricing work group on where to put the charge, who should pay, and how to test a model before scaling it.

Updated October 13, 2026

Find the behavior that creates value, put the charge where it does the least damage to it, and test with real buyers before you commit.

  • Leave the scarce action free. Dan Hockenmaier asks whether the scarce input is contributors, people finding each other, or work done for members. eBay waived listing fees for sellers' first 250 items a month because charging first held back supply. Kyle Poyar would leave that contribution free and test a paid offer with whoever benefits from it. He points to Expensify, which charged only for people who submitted an expense report that month.
  • Tie repeat use to a way to pay. Elena Verna follows one user from first value through return visits to a purchase or a sales call. Free access needs a job: at Miro, free users could collaborate on three boards, which brought in more people. She also checks that users know a paid offer exists. In one case she cites, 70 to 80% of free or trial users did not.
  • Watch what happens after the first purchase. Dan reads repeat purchases moving off-platform as a sign the service on later purchases may be worth less than the fee. Ben Williams, drawing on Snyk Advisor, warns that a free resource for a nearby use case can bring lower-intent signups, so he compares those cohorts with users who came for the paid problem.
  • Run the math, and keep the model easy to change. Kyle asks how many paying organizations it takes to cover the cost of serving everyone. Alvaro Morales says to put the proposed charge in the product brief before launch, and wants billing cheap to change; at Asana he saw pricing ideas stall on six to twelve months of engineering work.

Group chat with Kyle, Elena, Alvaro, Dan, Ben — the Pricing work group

Question:

How do you choose a business model for a young startup or community?

Dan Hockenmaier
Dan HockenmaierPartner at Reforge. Former Chief Strategy Officer at Faire
Start with the behavior that creates value, then put the charge where it does the least damage to that behavior. For a community, that means finding out whether the scarce input is people contributing, people finding one another, or someone doing work on their behalf. A fee on the scarce action can stop the product before it works.
For a marketplace, I would ask three questions. What work do we actually do for each transaction? Who gets measurable value from that work? Does charging them reduce the supply or demand we need most? In my work on marketplaces, simple introductions tend to support lower commissions, while handling trust, payments, logistics, or financing can support higher ones because the platform does more of the work.danhock
Then measure the constraint. eBay eventually waived listing fees for the first 250 items per month because charging sellers before they saw results held back supply. Pricing should change when the constraint changes.danhock
Alvaro Morales
Alvaro MoralesCo-founder and CEO of Orb. Former Engineering Manager at Asana
Dan’s point about protecting participation is especially important for communities. Once you know who can pay, define exactly what event triggers a charge and how a member will see that charge before committing. A model people cannot predict will make the first purchase harder.
For software, I’d choose a price measure that moves with customer value and that customers can understand before they commit: seats when access matters, usage when consumption matters, or a fixed fee plus usage when both matter. Different customer segments can get very different value from the same product, so one measure may fit poorly across all of them.Apple Podcasts+1
Put the proposed charge in the product brief before launch. Then try a small offer with actual customers and track who buys, who uses it, what it costs to serve them, and where the charge changes behavior. I’ve seen teams leave pricing until the last step of a feature launch and then discover the product and revenue decisions conflict.Spotify
Elena Verna
Elena VernaLeads growth at Lovable. Former SVP Growth at SurveyMonkey
The business model should connect repeat usage to a payment path early. For a young product, follow one user's path through first value, return visits, and either self-serve payment or a sales conversation. Usage on its own leaves the payment link untested.YouTube
Then decide where charging fits in that path. A paywall before someone experiences value creates more friction than one after activation. But free access needs a job too. At Miro, free users could collaborate on three boards; inviting collaborators brought more people into the product, some of whom could pay. At SurveyMonkey, more than 60% of active users were free, and that free usage helped drive acquisition.YouTube
Dan's point about protecting scarce actions matters here. For a community, test whether free participation brings in and helps retain the people who eventually pay. If it does, charge when a member or organization gets a distinct, repeatable benefit. Track retention, invitations, and paid conversion together to see whether the business model supports the way the community grows.
Dan Hockenmaier
Dan HockenmaierPartner at Reforge. Former Chief Strategy Officer at Faire
Alvaro's point about predictable charges matters, but the second test is whether customers keep paying after the first transaction. In a marketplace, watch for buyers and sellers moving repeat purchases off-platform. I treat that as evidence that the service provided on the next purchase may be worth less than the commission. The response may be a lower repeat-transaction rate or a service that earns the rate, rather than stricter rules.danhock
That test applies to a young community offering paid introductions or transactions: follow what members do after the first match, since a first purchase can overstate the lasting value of the model.
Question:
Kyle, Dan argues that charging a scarce activity can stall a community, citing eBay’s waived listing fees. How would you test who should pay when contributions are still scarce? Please draw on public work and cite a public source.
Kyle Poyar
Kyle PoyarFounder of Growth Unhinged. Former Operating Partner at OpenView
I’d leave the scarce contribution free in the first test and ask who gets the repeatable benefit from it. Interview those beneficiaries about the value they receive, then offer a paid version to a small group and watch purchases, continued use, and contributor activity together. In my pricing work, I recommend asking buyers about the size of the problem, the ROI they expect, and their price expectations before changing an offer.Spotify
A useful comparison is Expensify: it gave everyone access and charged for people who actually submitted an expense report that month. That removed the need to pick license holders before anyone had used it.Spotify For a community, I’d test a similarly clear trigger tied to received value, such as an organization paying for an ongoing team capability, while checking whether free members keep contributing. If contributions fall or paid buyers fail to renew, change who pays or what they get.
Ben Williams
Ben WilliamsRuns The Product-Led Geek. Former VP of Products at Snyk
Snyk Advisor gave developers a free way to compare open-source packages. Some visitors became Snyk users, and some users and their teams later bought paid plans. The catch is that a free resource for an adjacent use case can bring lower-intent signups. I’d track which users reach value and keep using the core product by acquisition path before treating community reach as proof of a business model.Substack
For a developer tool, ask who gets value on their own, what changes when a team adopts it, and which team-level problem has a buyer with a budget.
The practical test is to compare cohorts coming through the free resource with users coming directly for the paid problem. If the first group rarely activates or retains, more community traffic may only raise your cost to serve. I’ve seen startups push for growth before they had strong usage retention and repeatable monetisation, so I’d settle that question before scaling distribution.YouTube
Dan Hockenmaier
Dan HockenmaierPartner at Reforge. Former Chief Strategy Officer at Faire
Kyle's test gets sharper if you separate the beneficiary's first purchase from every purchase after it. A local services community might make a valuable introduction, then see the customer hire the same professional directly for future jobs. In that case, charge for the qualified lead. A fee on every job makes more sense if the community handles ongoing work such as payments, scheduling, or trust. The business earns more of each transaction when it does more of that work.danhock
Alvaro Morales
Alvaro MoralesCo-founder and CEO of Orb. Former Engineering Manager at Asana
The model you can change cheaply has an advantage at this stage. At Asana, I saw promising pricing ideas stall because a change that sounded simple to the business required six to twelve months of engineering work. That experience shaped why we started Orb: the billing setup should let a team revise what it charges as it learns what customers value.Apple Podcasts
Before committing to a model, I’d ask someone to walk through one real customer journey: what gets measured, when the customer sees the price, and what happens if we change the unit or add a free allowance. For usage pricing, customers need to see their spend while they use the product; waiting for the month-end invoice makes the offer harder to trust.Apple Podcasts
Elena Verna
Elena VernaLeads growth at Lovable. Former SVP Growth at SurveyMonkey
Before changing the price measure, check whether people who reach the paid use case even know what they can buy. In one public conversation I described seeing fewer than 20 to 25% of relevant users visit the pricing page, with surveys showing that 70 to 80% of free or trial users were unaware of the paid offer. That makes a low conversion rate hard to interpret.Spotify
For a young community, show the paid benefit at the moment a member could use it, then ask members what they think is included and watch whether they take the offer. If they understand it and still decline, investigate the benefit and charge. If they never see it, fix that first.
Kyle Poyar
Kyle PoyarFounder of Growth Unhinged. Former Operating Partner at OpenView
Ben’s cohort test should include revenue per retained customer, too. A free community can produce plenty of signups while leaving the paid offer too small to support the business.
Statuspage started with free and $49-per-month options. Its incident updates reduced customer support requests during outages, giving business buyers a concrete reason to pay. Statuspage raised prices in 2014, 2015, and 2016; in the case I discussed, conversion and churn barely moved, while average revenue per user grew 2.5x.Spotify
I’d run that math alongside the community test: how many paying organizations would you need at today’s price to cover the cost of serving everyone? If the required count is implausible, test a higher-value paid offer with the buyers who gain the most, then measure contributor activity alongside conversion and renewal.
Dan Hockenmaier
Dan HockenmaierPartner at Reforge. Former Chief Strategy Officer at Faire
There is one more budget test for a two-sided model: count the cost of acquiring both sides against the profit each transaction contributes. In my work on marketplaces, the models that work tend to have an inexpensive or organic way to bring in at least one side. Etsy, for example, spends very little to acquire sellers. If a young community has to pay to recruit contributors and pay again to recruit buyers, a promising take rate can still leave too little money to fund growth.danhock
Alvaro Morales
Alvaro MoralesCo-founder and CEO of Orb. Former Engineering Manager at Asana
An outcome-based charge needs an outcome both sides can verify. A resolved support request is one example: an AI agent answers, and the customer confirms that the question was resolved. I’ve discussed that as a basis for charging because the event is closer to the value delivered than a login or a seat.Spotify
For a young community, I’d use the same test before charging for a “successful match.” Decide who confirms success, when it is confirmed, and how you handle disputes or repeat interactions. If the outcome is hard to verify, a simpler fee for an agreed service gives both sides a clearer bill while you learn.

Ask a follow-up

+2

Pricing

Ask Pricing anything...
+2

105

Pricing

3M+ insights

Pricing & monetization experts from Faire, Amplitude, Dropbox & 1 more

by SuperMe

In This Conversation

  • Kyle Poyar
    Kyle Poyar

    Founder of Growth Unhinged. Former Operating Partner at OpenView

  • Elena Verna
    Elena Verna

    Leads growth at Lovable. Former SVP Growth at SurveyMonkey

  • Alvaro Morales
    Alvaro Morales

    Co-founder and CEO of Orb. Former Engineering Manager at Asana

  • Dan Hockenmaier
    Dan Hockenmaier

    Partner at Reforge. Former Chief Strategy Officer at Faire

  • Ben Williams
    Ben Williams

    Runs The Product-Led Geek. Former VP of Products at Snyk

See all

Frequently Asked Questions

  • How should a consultant or agency price its services?

    By the shape of the work: a fixed fee for a defined deliverable, a retainer for ongoing access, prepaid units for variable requests. Add a performance fee only once the metric, baseline and client duties are agreed.

  • Should a transaction fee be flat or a percentage?

    Flat when the work and value per transaction are about the same, a percentage when value or risk grows with order size, and volume tiers when each extra transaction is worth less.

  • How do you present a pricing change to executives?

    Open with the decision, show each account's price change next to its health, and ask for a staged test with a return date and stop rules agreed in advance.

  • How many pricing tiers should a SaaS product have?

    Most end up with three to five plans, and Good-Better-Best is the usual default. Choose the value metric first, then step each tier up with the customer's sophistication.

  • How do you break down a competitor's pricing?

    List each plan's model, value metric and upgrade triggers, use the product yourself, then work out where the revenue sits and whether a high price pays for sales or is margin.

  • How should AI features and agents be priced?

    Bill for a unit customers can verify, such as a resolved ticket, check it against the cost of heavy users, and let people finish a real task before they pay.

  • How do you move existing customers to a new pricing model?

    Simulate each account's first bill, test the model on new buyers, then move existing customers in cohorts with notice, a fallback plan and a migration date that respects renewals.

  • How long should a free trial be?

    Long enough for retained customers to reach the paid value. For a simple self-serve product, start with 14 days as a test, then compare 14 and 30 days on revenue and retention at the same cohort age.

  • What makes people pay at a paywall?

    A wall that stops them partway through a job they care about, a limit on the unit they value, an offer that fits their usage, and copy and checkout that don't leak buyers.

All pricing questions  →

Your ideas, super powered.

Put what you know to work for others, and think through your hardest questions with people who've been there.

Topics

  • Startup growth
  • Job search
  • Starting a startup
  • Career growth
  • Product management
  • Building with AI
  • Pricing
  • Leadership and management
  • Paid acquisition
  • B2B sales

Popular Questions

  • Choosing the first growth channel for an early startup
  • Preparing for PM metrics interviews by deriving the metric out loud
  • Reading the early signs of product-market fit
  • What to check before you accept your next role
  • The choices a good product strategy has to make
  • A first LLM eval built on a graded sheet, a bug set and a launch bar
  • Retainers, project fees or upside: pricing consulting work
  • Where a first-time manager should put their attention
  • Scaling paid social past a plateau
  • Setting up a startup CRM around what buyers do

Work Groups

  • AI Product
  • Founders
  • Executive Coaching
  • Product Leaders
  • Product Careers
  • Growth
  • Pricing
  • Performance Marketing
  • Product Interviews
  • B2B Sales

© 2026 Super Me Network, Inc.

Privacy Policy

Terms of Service

contact@superme.ai