Skip to content
AppDues
Log in
Contact salesSign up

Building an App Marketing Team from Scratch

Most app teams start with product. Marketing arrives later, often as a single generalist who is expected to run paid acquisition, social, brand and commerce at once. That arrangement rarely survives the first serious growth target. This guide sets out the decisions that matter when you are assembling an app marketing function: which roles to hire first, how to split budget between awareness and measurable conversion, and how to add revenue models without confusing your users. The framing draws on a recorded conversation with Lisa Kennelly, Chief Marketing Officer at the fishing app Fishbrain, whose experience spans a crowded period-tracking category and a large hobby niche.

Why app marketing now starts with revenue, not just installs

The early app store rewarded whoever moved first. In categories with hundreds of near-identical products, the winning move was to claim attention and look different, and brand carried much of that load. Questions about how the app would eventually earn money were often parked.

That order is risky today. Paid installs cost more, attribution is thinner, and subscribers expect a clear reason to keep paying. None of this means an app must charge on day one. It does mean the marketing plan should state where revenue will come from and which channels are expected to support it.

A one-page brief is enough to start. Answer these four questions in writing:

  • What job does the app do for the user?
  • Which channels have produced installs so far, and at what cost?
  • Which of those channels can be measured reliably today?
  • What would need to be true for a paid tier or add-on to make sense?

If the answers are thin, your first marketing hire should be someone who can run experiments and read results, not someone who only produces campaigns. Kennelly's account of the period-tracking era makes the point: growth came easily through cheap social ads and early influencer partnerships, which made it tempting to postpone the harder monetization questions. The teams that answered those questions earlier had more room later.

Pricing against what users already spend, not against other apps

Some categories look small to outside investors but contain users who already spend heavily on the activity. Fishing is the example from the conversation: boats, trips, guides, tackle and fish finders are expensive, so an app that replaces even part of that spend can justify a subscription. The same logic applies elsewhere. A fitness app that substitutes for some personal training sessions can be priced against the cost of those sessions rather than against other apps. The comparison that matters is the user's existing spend.

Before setting a price, decide what kind of product you are selling. Kennelly framed this as a set of questions: is the app a tool, a social network, a platform, or something else? Each answer implies a different pricing model and a different acquisition message. Utility tends to sit at the top of the funnel because it is what people search for and talk about.

A short pricing check:

  1. List what your target user currently pays for the job your app performs.
  2. Identify the single most valuable action inside the app.
  3. Decide whether that action belongs behind a paywall, a usage limit, or a free tier.
  4. Test the price against a small segment before rolling it out.

Being conservative on price is common. Kennelly noted that Fishbrain could likely have pushed pricing harder and was evaluating it. That is a useful admission: under-pricing is a frequent default, and revisiting it is normal rather than a sign of failure.

Which roles to hire first, and how to fund awareness

Measuring marketing impact is difficult, especially for awareness work. One approach is to reserve a defined share of the acquisition budget for awareness activities and another share for commerce, then protect those shares in planning. In Kennelly's account, roughly ten percent of the performance acquisition budget went to awareness and a further ten percent to the commerce business. Treat those figures as a reference point from one team, not a benchmark to copy.

The important part is that stakeholders understand and agree to the split. That requires the marketing lead to explain how money is allocated and why, and to show what awareness spending is expected to produce even when it cannot be attributed click by click. Where measurement is possible, push for it. QR codes let offline or non-social touchpoints be tracked. Radio can reach people who are not on social platforms. The goal is not to make every channel measurable but to make more of them measurable over time.

On hiring, the sequence that worked in the original case was:

  • A performance lead who could buy media and coordinate campaigns.
  • A dedicated design resource for marketing, separate from product design.
  • Junior designers focused on specific channels and social content.

The design hire mattered because product designers were busy and marketing creative was not their specialty. Clear brand guidelines and shared messaging across teams reduced friction between performance and brand work.

A simple first-year hiring checklist:

  • Can one person own paid acquisition end to end?
  • Is there someone who can produce channel-ready creative without borrowing product design time?
  • Does everyone working on campaigns have access to the same brand guidelines?
  • Is there a named owner for the awareness budget?

Lifetime value and the hard part of social commerce

Adding a marketplace or commerce layer to a subscription app is attractive because it can raise revenue per user. It is also hard to execute well. Kennelly reported that most of Fishbrain's commerce revenue came from the web rather than mobile, and that outside investors were drawn to the marketplace potential more than to current results.

The core tension is user experience. Free users who see marketplace ads often do not buy. Paying users may question why they see ads at all. That is why many subscription-based social apps avoid stacking additional revenue models on top of the subscription.

Where teams do proceed, the work starts with segmentation. Regular market research helps separate users who are looking for deals from users who joined for the community. From there, a custom journey can be built from a single ad through the funnel, addressing different needs at each stage. Lifetime value and repeat purchase behaviour become the metrics to watch.

A practical test before adding commerce:

  • Can you describe two distinct user personas and what each wants from the app?
  • Does the ad experience differ for free and paying users?
  • Is there a web path for users who prefer not to buy in-app?
  • Which metric will tell you whether the layer is working: repeat purchase rate, LTV, or something else?

If those answers are unclear, the commerce layer is likely to create more confusion than revenue.

Talk to customers, and hire people who understand the niche

There is no single marketing playbook that fits every app. The most reliable input is direct conversation with users. When the user base is large enough, in-app messaging makes it possible to reach people quickly and ask what they think.

Geography can get in the way. If your customers are concentrated somewhere your team is not, virtual conversations help. A short video call with a customer, followed by questions from the wider team, can give product and marketing staff a clearer picture than any dashboard. Kennelly described running exactly this kind of session, with a Fishbrain customer taking questions from the team for about twenty minutes in front of the whole company.

Hiring is the other lever. Recruiting people who already care about your niche, not only people who match your customer profile, tends to improve marketing judgment. It also helps when the team is distant from the customer base.

A lightweight customer research routine:

  1. Pick five users from different segments each month.
  2. Invite them to a short call or send a small set of questions in-app.
  3. Share the notes with product, marketing and support.
  4. Record which decisions changed as a result.

Over time this creates a feedback loop that no amount of channel optimization can replace.

Frequently asked questions

What should an app's first marketing hire focus on?

Start with someone who can run acquisition experiments and read the results. Brand and design support can follow once there is a clear picture of which channels work and what the product's positioning should be.

How much of an app marketing budget should go to brand awareness?

There is no universal figure. One reference point from the original discussion was around ten percent of the performance acquisition budget for awareness and a similar share for commerce. Treat that as a starting point to discuss with stakeholders, not a target to copy.

How can awareness marketing be measured without IDFA?

Use the measurable touchpoints you control. QR codes can track offline or non-social placements, and radio campaigns can reach audiences outside social platforms. Combine those signals with brand tracking and stakeholder agreement on what awareness spending is meant to achieve.

Why is social commerce hard to add to a subscription app?

Free users who see marketplace ads often do not buy, while paying users may object to ads in a product they already pay for. Getting the user journey right across both groups is the main obstacle, which is why many subscription apps keep commerce separate or web-based.