How Hevy Reached Two Million Downloads With Almost No Paid Marketing
Hevy, a workout planning and tracking app, went from single-digit downloads to more than two million in roughly four years. In a Sub Club podcast conversation, CEO and co-founder Guillem Ros explained how product focus, a social community, and a deliberately low price combined to drive that trajectory. The episode framed the ad-spend side of the story as a question — how do you get to two million downloads with just $15k in ad spend? — so treat that figure as the podcast's own framing rather than an audited total. This guide restates the core mechanics in a decision-oriented form so founders and product teams can judge whether the same levers apply to their own app.
The headline numbers, and what they do and do not prove
The figures discussed in the episode are a dated snapshot, not a live dashboard. Treat them as a historical reference point from the 2023 conversation and check current conditions before using them in any planning model.
- Downloads: more than two million, reached over about four years.
- Ad spend: the episode poses roughly $15k as the figure behind the question, not as a confirmed audited total.
- Acceleration: at the time of the conversation, about half of the two-million user base had joined in the preceding five months.
- Stated long-term ambition: 100 million users.
What these numbers support is a directional claim: a product-first, community-driven app can compound installs without a large acquisition budget. What they do not establish is that paid marketing is unnecessary in general, that the same curve is repeatable in a different category, or that the growth rate persisted after the conversation. Those are open questions a reader should test against their own retention and referral data.
Where the idea came from, and why shipping came first
Guillem's path to Hevy ran through two very different kinds of experience. He had been shipping apps since his mid-teens, beginning in mobile gaming, and he later spent time as a product manager at the fitness app 8fit. Separately, his own training as a triathlete and his use of Strava gave him a firsthand sense of what a fitness app could feel like when social connection sits at the center. The idea for Hevy came from that gap: a fitness app built around community rather than treating it as an afterthought. Shipping experience and category familiarity together shaped how the product was built.
The founding team prioritized the product over marketing, which is how they shipped version 1.0 quickly. The early growth that followed came from word of mouth and from store algorithms rather than from a heavy App Store Optimization program. That is a notable contrast with the common advice to invest in ASO early; the Hevy path suggests ASO can be a later lever when the product itself generates organic discovery.
The community loop as an acquisition and retention engine
The social layer became one of Hevy's strongest recurring pulls. Users followed other users, and those users followed each other, forming a network that gave people a reason to return. In a category where social connection is often thin, that density of mutual following functioned as both a retention mechanism and a referral surface.
A useful way to think about it: the community is not a marketing channel bolted onto the app. It is a product feature whose side effect is distribution. That distinction matters when deciding where to invest engineering time.
Bootstrapping, low prices, and the LTV trade-off
Hevy took no outside venture capital, and that choice gave the team room to chase both growth and profitability on its own timetable. The cost of that freedom showed up in the numbers: modest subscription prices meant modest lifetime value per user. Rather than lift prices to fix the math, the team chose to push harder on virality as the offset.
Guillem's view is that a lower price did not reflect a weaker product; the team considered what they had built to be better than the alternatives. For a reader weighing the same move, the useful distinction is between two situations that look alike in early revenue data. In one, a low price is deliberately trading margin for reach that a higher price would have blocked. In the other, a low price is simply hiding retention problems that no amount of virality will fix. The first calls for patience; the second calls for product work before any pricing change.
A checklist before copying the no-ads playbook
Use these questions to decide whether the Hevy pattern fits your app:
- Does your product have a natural social graph? If users have a reason to follow each other, a community loop can substitute for some acquisition spend. If not, the loop will not appear on its own.
- Can you ship a strong 1.0 without a marketing team? Product-first sequencing works when the founding team can build and iterate quickly.
- Is your price low because of strategy or because of weak willingness to pay? Low LTV from low price is a different problem from low LTV from churn.
- Are you willing to defer ASO and paid channels until the product generates organic signal? This is a sequencing choice, not a permanent ban.
- Do you have a funding structure that tolerates slower, profitable growth? Bootstrapping removes VC pressure but also removes a buffer.
If most answers point toward a product with a built-in social surface and a team that can ship fast, the Hevy approach is worth testing. If not, paid acquisition and ASO may still be the more reliable path.
Frequently asked questions
How many downloads did Hevy reach, and how much did it spend on ads?
In the 2023 conversation, Hevy was described as having passed two million downloads over about four years. The episode framed the ad-spend side as a question about roughly $15k rather than stating an audited total. At the time, about half of that total had arrived in the preceding five months. These are dated figures from the episode, not current metrics.
What made the community element work for Hevy?
Users followed other users, and those users followed each other, creating a dense social graph. That mutual following gave people a reason to return and acted as an organic discovery surface in a category where social connection was often missing.
Why did Hevy keep prices low instead of raising them?
Guillem Ros argued that low subscription prices created low lifetime value, and the team chose to offset that by leaning into virality rather than raising prices. He also noted that charging less than competitors did not mean the product was inferior. Whether that trade-off is right for another app depends on its retention and willingness-to-pay data.
Did Hevy rely on App Store Optimization early on?
The episode describes very little ASO in the early stages, in contrast with common advice to invest in ASO from launch. Early discovery came mainly from word of mouth and store algorithms. That is a sequencing observation, not a claim that ASO is unimportant.