The Honest CAC Math for an Indie Outdoor App at $34.99 a Year

Most indie founder posts about CAC are either bragging or grieving. This one is neither. It’s the actual shape of the math behind a $34.99-per-year outdoor app, why each acquisition channel behaves the way it does, and the unit economics that ended up dictating our strategy more than any framework or playbook did. If you’re building something in the same shape — a small subscription product in a niche category — the logic below should save you a quarter of guesswork.

The starting math: $34.99/year, what’s your CAC budget?

Baseline Maps is $34.99 a year (or $7.99 a month) with a fully unlocked 14-day free trial. At the annual price, gross revenue per paying subscriber lands well below the sticker price after platform fees take their cut. That net is your realistic ceiling for sustainable year-one CAC if you want each subscriber to pay back inside twelve months. Spend more than you net and you’re borrowing against retention you haven’t earned yet. We treat year-one net revenue as the hard line and refuse to cross it. Some weeks that line feels arbitrary; most weeks it feels like the only honest number in the spreadsheet.

Why year-one LTV is the only number to trust

Three-year LTV models are seductive because they make almost any CAC look reasonable. They are also fiction for a year-one indie app in a seasonal category. Outdoor users ebb and flow around fishing season, hunting season, and weather. Until we have multiple full annual cycles of cohort data, we treat LTV as roughly one year of revenue, period. If the math doesn’t work on year one, it doesn’t work. The day we let ourselves write an optimistic retention multiplier into a CAC budget is the day we start losing money slowly.

What we learned measuring channels

We watched our channels closely, and the pattern was consistent: the gap between the best and worst acquisition channel was enormous — far larger than any other lever in the business. Paid search and paid social came in expensive and high-variance. Comparison-content articles and forum word-of-mouth converted for a fraction of the cost. App Store search, when we ranked for a term, was effectively free. We’re not going to dress this up with precise per-channel CAC figures we can’t stand behind a year from now — the honest takeaway is directional, and the direction is unambiguous: paid was the most expensive way to grow, and organic was the cheapest.

Why paid CAC runs high in outdoor apps

Outdoor apps share auction space with much larger players — onX, Gaia, fishing forecasters, and weather apps with deep pockets. The CPM is set by competitors who have venture funding or a decade of retention data behind their bids. As a small indie product, you’re paying tourist prices in a market priced for locals. Install-to-trial dropoff made it worse: a meaningful share of paid users installed, never opened the app, and the spend evaporated. Better targeting got us closer, but never close enough to bend the math past breakeven for a $35/year product.

Why organic CAC runs low (and what ‘organic’ actually means)

Organic isn’t free — it’s deferred cost. A comparison post that pulls in subscribers cheaply still took real hours to write and weeks to rank. A good forum answer that converts a handful of users took an evening. The actual cost is founder time, which is real, but it compounds. Paid spend evaporates the moment you stop. Organic content keeps converting long after publish at roughly zero marginal cost, and the conversion rate on intent-driven traffic stays meaningfully higher than any paid channel we tried. Someone reading a careful comparison of mapping apps already has the problem you solve; someone scrolling past an ad mostly does not.

Trial-to-paid conversion: the lever that hides under everything

Conversion from trial to paid varies enormously by where the user came from. People who arrive through word-of-mouth and comparison content convert noticeably better than people who arrive through paid ads, who disproportionately install and never come back. Channel quality matters more than channel volume. Nudging conversion up a few points on high-intent traffic moves more revenue than doubling install volume from a low-intent channel — and it costs nothing except shipping the right onboarding for the right kind of user.

When community-first growth is structural, not philosophical

We didn’t choose community-first growth because it was virtuous. We chose it because paid CAC against a net-revenue ceiling well under the sticker price is arithmetic that doesn’t bend for a niche outdoor app. The community-first model emerged from the spreadsheet, not the mission statement. Once you accept that paid acquisition will likely lose money in a niche outdoor category at this price, every product decision shifts toward earning a recommendation rather than buying an install. The philosophy follows the math, not the other way around.

When raising prices is the right move (and when it isn’t)

A modest price increase would lift revenue per subscriber and expand the CAC budget proportionally. It would also tighten trial-to-paid conversion, especially among the price-sensitive users who are most likely to leave honest feedback. We’ll raise prices when the product clearly justifies it and when churn data shows users staying past renewal. Until then, affordability is part of the feedback loop — the people who tell us what’s broken are the same people who’d churn first on a price hike.

What the math forced us to actually do

Once the unit economics clarified, the product roadmap reorganized around them. We stopped chasing features that would impress investors in a deck and started shipping the things our highest-intent users — the ones who convert best and stick around — were asking for in the in-app feedback channel. Every feature now gets evaluated against a simple question: does this make a recommendation more likely? Map quality improvements pass that test. Marginal feature parity with bigger competitors does not. Polish on the moments a user is most likely to screenshot and send to a friend passes the test. A long tail of secondary settings does not.

We also stopped pretending paid acquisition was a temporary funding problem. It isn’t. A $34.99 yearly product in a niche outdoor category will probably never make paid social work at scale, and that’s okay. The companies running expensive paid campaigns in our space have different fundraising structures and longer payback horizons. We’re not in that game and we don’t need to be. Recognizing that early kept us from burning a pile of test spend chasing a channel that was never going to math out.

The Development Queue inside the app is where this philosophy actually lives. Users can see what’s being built next, vote on priorities, and watch features ship against the queue they helped shape. It’s a public commitment to the loop: feedback in, features out, recommendations earned, growth followed. The queue is also the cheapest marketing asset we have. Every shipped item generates a small wave of social proof that paid ads simply can’t manufacture, and every user who watches a feature move from suggestion to ship becomes more likely to tell someone else about the app.

The honest summary is this: if you’re building a small subscription product in a niche outdoor category at a sub-$50 annual price point, the math will quietly refuse to let you scale through paid acquisition. You can fight it for a quarter or two and burn cash to learn the lesson, or you can read the spreadsheet now and route every dollar of effort toward the channels where the unit economics actually work — comparison content, forum presence, App Store search, and a product good enough to recommend without a referral bonus. We chose the second path after a brief detour through the first, and the picture got dramatically healthier once we cut paid spend entirely.

There’s no shortcut around the arithmetic. There’s also no shame in it. The smallest viable customer base for a $34.99 yearly app is meaningfully smaller than a venture-backed competitor needs to survive, which means we can serve a tighter user base, charge a fair price, and build a product the most engaged users in the category actively want to talk about. That’s not a growth hack. It’s just what the numbers permit, and once you stop arguing with the numbers, the strategy gets a lot quieter and a lot more obvious.

Our growth model is structurally community-first because the math forced it. The Development Queue is open in-app — every shipped feature is the actual marketing.