Paying-customer feedback rebuild before scale
Use feedback from paying customers to rebuild the product before scaling acquisition, even if it means scrapping the first version.
Why this can grow a startup
Baremetrics is a good antidote to vanity traction because the first version was not sacred. Josh Pigford says Baremetrics launched quickly, got the first $2,000 in MRR, then scrapped the first version and rebuilt based on paying-customer feedback. Within a month of that next version, recurring revenue doubled. The tactic is uncomfortable but practical: once people pay, their friction is more valuable than a roadmap guess. Rebuild the part that blocks the bigger pain from being solved, then scale the sharper product.
Source-backed example
Baremetrics says the first version was scrapped two months after launch, rebuilt from paying-customer feedback, and recurring revenue doubled within a month of the next version.
Source-reported evidence
Source: Baremetrics: How we got our first 100 customers · Browse Baremetrics: How we got our first 100 customers tactics
Baremetrics reported its first $2,000 in monthly recurring revenue, then doubled recurring revenue within a month after rebuilding from paying-customer feedback.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Product, Customer Success, Revenue is relevant to first customers, paid feedback, product iteration and you can run a bounded test with a medium budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Product and Customer Success, using evidence from Baremetrics: How we got our first 100 customers as context—not as a promised result.
- Record a baseline for: Qualified prospects who complete the intended paid action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose the first market, local proof, partners, and distribution sequence with operator context.
SOURCE HUB
More tactics from Baremetrics: How We Got Our First 100 Customers
Explore related GrowthDex examples and evidence connected to Baremetrics: How We Got Our First 100 Customers.
Open Baremetrics: How We Got Our First 100 Customers source hub