A consumer subscription app might have eleven people when the founder first asks about HR. A product manager, two mobile engineers, a designer, a growth marketer, an analyst and four support agents share a chat workspace. Ask what is already hurting and the answers are specific: the app store rating dipped after a release, the Sunday support queue is hard to staff, and the growth marketer wonders whether her job depends on one channel.
In this setting HR is not a department. It is a handful of decisions made early and written down. This guide sets them out in order.
What makes a consumer subscription team different
A B2C SaaS company sells to individuals, so signals arrive daily: installs, trial starts, conversion, churn, refunds. Priorities move with the dashboard. Squads are small, so one designer or analyst leaving stalls an experiment cycle. Support answers thousands of users through chat and email, across hours when families use the app, which means evenings, weekends and festival days.
Set up in this order
- 1
Write the roles and levels
One page per role family: product, engineering, design, growth, data and support. Include two or three levels and what separates them. See role design and job descriptions.
- 2
Build a pay band sheet
A simple table with fixed pay, variable pay and any equity range by level. It keeps offers consistent while you move fast.
- 3
Set the support roster rules
Shift lengths, weekly off, rest between late and early shifts, festival day cover and who handles escalations at night.
- 4
Agree how growth is judged
Decide which numbers count, over what period, and what context is noted when a channel changes. Put it in the goal sheet.
- 5
Start a hiring tracker
One list for all open roles with owners and stage dates, reviewed weekly.
- 6
Draft the core policies
Leave, working hours, remote work, data handling for user information, and a code of conduct. See the HR policies page for the typical set.
The support desk deserves early attention
Agents hold the brand's voice with paying users. Burnout shows up as short replies and rising refund disputes. Build the roster from the ticket curve. Cross-train for refunds, account recovery and payment failures so one absence does not choke a queue. Give a team lead a clear path to escalate to engineering, with a severity guide that says what counts as a P1.
Growth roles and moving targets
A growth marketer may be praised in June and doubted in July because an ad channel changed its rules. Agree a small set of leading indicators, a monthly review with context, and a rule that one bad month does not trigger a conclusion. This protects both the person and the company from decisions made on noise.
Hiring the first dozen well
Early hires set the culture and the bar. For a consumer app, the first engineers should be comfortable shipping to app stores and reading crash reports, not just writing features. The first growth hire needs to handle paid channels and lifecycle emails with equal ease. The first support lead should have run a queue under pressure. Write a one-page scorecard for each, run the same practical test with every candidate for that role, and keep notes. A tracker of stage dates avoids the common failure of a good candidate sitting for a week without a reply.
Goals that survive a pivot
A subscription app may change pricing, onboarding or even the target user within a quarter. Annual targets feel brittle in that world. Use short goal cycles of six to eight weeks, tied to a single shared metric per squad, and allow a mid-cycle reset if the plan changes. Record the reason for the change so the reviewer later understands why a goal vanished. This keeps people from feeling that their work was wasted without explanation.
Pay talk without a spreadsheet war
Consumer app teams share a chat workspace, and salary rumours travel fast. Decide in advance what you will say when someone asks why a colleague earns more. Pointing to level, scope and the date of hire is a fair answer if the bands exist. Without them, every answer sounds like favouritism, and the designer who joined a month ago starts comparing notes with the engineer who joined last year.
What can wait
- A full performance system: begin with a light quarterly review tied to goals.
- A detailed policy manual: begin with ten pages that people read.
- An HR system: a shared sheet is fine until the team crosses a size where leave and records become tiring to manage.
When the company grows, the HR strategy and workforce planning page and the retention page are the next stop. The SaaS and product companies hub places this type among its neighbours.
