Why We Don't Have a Marketing Team (And What We Do Instead)

Most app companies in our category have a marketing team before they have a usable product. We did it the other way around. Two years in, we still don’t have one, and we don’t plan to hire one until the day shipping slows down enough that we need someone whose full-time job is talking about the app instead of improving it. That day might never come. Here’s what we do instead, and why we think it produces better growth than the alternative.

The decision wasn’t ideological at first. It was financial. We didn’t have the budget for a marketing hire, and the work of building the app was the work that mattered most. Over time, though, the absence stopped feeling like a constraint and started feeling like an advantage. We noticed that the apps in our category with the loudest marketing were the ones whose users complained the loudest. We noticed that the apps people actually recommended to friends were quieter, smaller, and run by people who answered their own support emails. We decided to be one of those.

What marketing teams optimize for

Marketing teams optimize for what marketing teams can measure. That means impressions, click-through rates, cost per install, and the soft metrics of reach — followers, mentions, share of voice. None of those numbers tell you whether the app is good. They tell you whether the funnel is moving, and a funnel can move while the product underneath it quietly rots.

What we optimize for instead

We optimize for the gap between “a user asked for this” and “a user has it.” When that gap is short, people stay. When it’s long, they leave. Everything else — retention, word of mouth, renewal — is downstream of that one number. We don’t have a dashboard for it. We feel it in the inbox.

The feedback box as the marketing channel

There’s a feedback box in the app. It’s not buried, and it’s not a form. Every note routes to someone who can act on it. The Celsius toggle came out of three notes from Canadian anglers. The CFS / gauge-feet switch came from one Idaho user who said the app was unusable without it. Both shipped within the week.

Instagram DMs as the customer interview

Instagram is where new users find us and existing users tell us what we got wrong. We read every DM. We answer every DM. A DM thread is a free, opt-in customer interview you cannot pay an agency to replicate. The hatchery alerts feature began as a DM from a guy in Oregon. Six weeks later it shipped.

The Founder text thread

There’s a group thread with our founding members. It’s small. It’s noisy. It’s the highest-signal channel we have, because everyone in it has bought the premise and is negotiating what it should become. The emergency rules pipeline started there as a screenshot of a bulletin that closed a river he was about to fish. Two months later it shipped.

How features become marketing

A shipped feature is a story. A story has a person attached. When we announce a new feature we say who asked for it, and we tag them. That isn’t a tactic — it’s the truth of how the work got done — but it functions as marketing, because everyone watching sees the app responding to its users.

What we lose by not having a marketing team

We lose paid acquisition velocity. We almost certainly grow slower than a comparable app with a six-figure ad budget. We don’t show up in App Store featured banners. We aren’t on the podcasts where outdoor-tech founders get interviewed. There are weeks when nothing about us happens in public — the work is happening, but no one is narrating it.

What we gain

We gain a product that improves faster than the conversation about it. We gain a user base that knows it’s heard — the only durable answer to churn. We gain the ability to ship on Tuesday because someone texted Monday, without running it past a positioning doc. We gain the freedom to be honest.

---

None of this is a manifesto. We aren’t anti-marketing as a category. There are companies that need a marketing team, and there are stages of growth where one becomes structurally necessary — when the volume of inbound exceeds what the people building can hold, when the brand has to be defended in places the founders can’t be, when the story is bigger than any one feature ship. We just haven’t hit that stage, and we suspect we’ll know when we have. Until then, the loop we have works, and we’re suspicious of solutions to problems we don’t yet have.

What we are against is the substitution that happens inside most early-stage companies, where the marketing team becomes the proxy for the user. Marketers write the copy that decides what the app is. Marketers run the surveys that decide what gets built next. Marketers own the relationship with the people paying for the thing, and engineering ends up two degrees removed from the people they’re supposed to be serving. We’ve watched that pattern collapse good products into mediocre ones, again and again, in this category and others. The cure is to keep the people building close to the people using. A marketing team, structured the way most marketing teams get structured, makes that harder.

There’s a version of growth that’s loud, paid, and fast, and there’s a version that’s quiet, earned, and slow. We’ve picked the second one. We picked it because the people who find Baseline Maps through a friend, or through a DM thread, or through a feature ship that solved their specific problem, are worth ten of the people who arrive through an ad. They renew. They tell more friends. They send the next note in the feedback box, which becomes the next feature, which finds the next user. The loop compounds.

The math on the loop is genuinely better, not just morally satisfying. A paid install costs more every year as the ad networks consolidate and the auctions get more crowded. A loop install costs nothing on the margin and tends to retain at multiples of what a paid install does, because the person arriving was already pre-qualified by someone they trust. We track both quietly, and the gap keeps widening in favor of the loop. The temptation to short-circuit it with paid spend is real, but every time we’ve tried, the numbers have argued us back out.

If you want to see what we’re working on next, it’s in the app. The Development Queue lists the features in flight and the ones queued behind them, and the order of that queue is set, more often than not, by what’s been arriving in the inbox that week. We don’t keep it a secret because the queue itself is part of how we earn the next user — it’s an admission that the app isn’t done, and that the people using it are the ones deciding what done looks like. Most companies treat their roadmap like a competitive secret. Ours is a public ledger of promises we’ve made and the order we plan to keep them in. When a feature moves up the queue, it’s because someone made the case. When something gets bumped, we say why. That kind of transparency is uncomfortable in places, but it’s the closest thing to honest marketing we know how to do.

Baseline Maps will probably hire someone someday whose job touches what a marketing team would do. When we do, we’ll hire someone who is good at listening, not someone who is good at broadcasting — because the work that built the app is the same work that will keep it growing, and that work has always started with a user typing something into a box and one of us reading it.