User acquisition

How do invites and referrals grow a work app from one user to a company?

In a work app the strongest acquisition channel is often the app itself. A site report goes to the office, a work order goes to a customer, a checklist goes to a supervisor, and each one is a chance for the next person to start using it. This page shows how to design that on purpose.

By the ShoutEx Team · Updated October 2026 · Facts checked October 6, 2026
The best invite is a piece of work someone needs to see. Build the share into the job, then make joining one tap.Mobile App Marketing · Updated October 2026
3 stages
Individual, team, company: the path most practical work apps follow
1 tap
What it should take an invited colleague to open the shared item
Shared work
What a good invite carries: something the receiver needs to see

How do invites spread a work app?

How do invites spread a work app?

One professional gets value alone, shares the output with people they work with, and some of those people start using the app too. Once enough of a team uses it, someone asks for shared folders, admin and one invoice, and the company buys.

Referral rewards can speed up the first step, but the path to a company account runs through shared work.

Example · individual to team to company
IndividualOne supervisor, one phone
Trigger
Needs to file a daily report faster
Shares
PDF report to the project manager
Invite moment
"Get these reports live in the app"
TeamA crew and their PM
Trigger
PM wants every report in one place
Shares
Project folder with the other foremen
Invite moment
"Add your crew to this project"
CompanyEvery project, one account
Trigger
Ops director sees five teams paying separately
Buys
Company plan, admin, templates
Sales moment
"Combine your teams on one invoice"
How invites spread: each stage has its own trigger and its own invite moment. Fictional site report app.

What is the difference between invites and referral programmes?

An invite asks a colleague to work with you in the app. A referral programme rewards a user for bringing in someone new. Both help, but they grow different things.

Collaboration inviteReferral reward
Why people send itThey need the other person to see or do somethingThey get a reward
Who receives itCo-workers, customers, subcontractorsFriends and peers, often at other companies
What it growsTeams and company accountsIndividual sign-ups
Typical rewardNone needed: the work is the reasonA free month, extra storage or seats
RiskLow, if invites are chosen one by oneFake sign-ups and reward farming
FitsReports, schedules, work orders, checklistsCalculators and solo tools

Invites also cross company lines. A general contractor who asks every subcontractor to file reports in the same app, or a field service firm that sends signed work orders to its customers, puts the app in front of people at other companies who have the same problem. Treat those receivers as a separate audience: they did not choose the app, so their first screen should explain what it does for them, not only for the sender. Some of them will become the first user at their own company and start the path again.

Calculator apps such as engineering tools lean on referrals between peers. Report, schedule and work order apps such as construction apps grow mostly through collaboration invites, then internal champions.

What should invite and referral screens look like?

Put the invite at the moment the user has just created something worth sharing. Pre-fill the message with the work itself, let them pick people one at a time, and show what the receiver will get.

Example · invite flow mock-up
9:41
Report ready
Daily report, Oct 6Ready
Photos12
Crew hours46
Share with project
1 · Share prompt right after the report is finished
9:41
Share this report
Priya Shah, PMUses SiteSnap
Marc Dubois, foremanInvite to app
Add name or phone

Marc gets the report as a link. He can open it without installing.

Send
2 · Choose people one by one; non-users get an invite
9:41
Marc's view

Ana shared today's report for Harbour Tower.

Daily report, Oct 6Open

File your own reports for this project in the app.

Join the project
3 · Receiver sees the work first, then a reason to join
Collaboration invite flow: the invite carries the report, and the receiver can read it before installing. Fictional app, people and project.
Example · referral reward screen
9:41
Give a month, get a month
Your linktorquecalc.example/r/jk42
Friends who joined3
Free months earned2 of 6 max

Rewards apply when a friend saves their first calculation.

Share link
Referral screen for a solo tool: the reward triggers on activation, not install, and has a cap. Fictional app.

How do you know whether the invite loop is working?

Follow a group of active users through each step: how many send at least one invite, how many invites are opened, how many receivers activate, and how many of those form a team. The weakest step is where to work next.

Invite loop for 100 active users, one monthFictional site report app
Active users100
Sent at least one invite35Share prompt after each report
Invites sent80Some users invite several people
Invites opened52
Receivers activated18Filed their own report
New teams formed4Three or more users on one project

Illustrative example written by ShoutEx for this guide, not a benchmark.

Here the leak is between opening and activating. Receivers saw the report but had no clear first task. Fixing that is an onboarding job; see onboarding and activation.

ShoutEx rule

Share the work, not a promo code.

An invite that carries a report, a schedule or a job the receiver needs is opened. An invite that only says "try this app" is ignored.

What mistakes and trade-offs come with referrals?

  • Rewarding installs. Reward only when the invited person reaches a useful result, or you will pay for empty accounts.
  • Uncapped rewards. Set a maximum so a few users cannot farm free months.
  • Asking for the whole address book. Request contacts access only if it truly helps and explain why; see permissions.
  • Forcing an install to view shared work. A web view of the shared item gets far more people to the next step.
  • No path to the company plan. When three or more people from one company share a project, prompt for a team plan and tell sales.

The main trade-off is control. Free web views and easy joining spread the app faster, but they also mean more people use it without paying. ShoutEx view: accept that early, and put the limits where teams feel them, such as shared project history, admin controls and company templates. See free plan limits.

What should you measure for referrals and invites?

Invite and referral metricsTrack by cohort of active users
MetricQuestion it answersWhere to find it
Share of active users who inviteIs the share moment working?Product analytics: invite sent event
Invite open rateDoes the message carry real work?Link clicks or web view opens
Invited users who activateDo receivers find a first task?Product analytics, source = invite
Teams formed per 100 active usersIs usage spreading inside companies?Projects or workspaces with 3+ users
Company plans from invited teamsDoes the loop reach revenue?Billing system or CRM
Source: ShoutEx invite loop measurement.

See also individual to company and communities and partners.

Frequently asked questions

Do referral programmes work for B2B apps?

They help for solo tools such as calculators. For apps where work is shared, collaboration invites built into the product usually grow teams and company accounts faster.

What reward should a referral programme offer?

Something that costs little and suits the product, like a free month or extra storage, paid only when the invited person activates, with a cap per user.

When should an app ask users to invite colleagues?

Right after they create something another person needs to see, such as a finished report, a schedule or a closed work order.

Should invited people have to install the app to see what was shared?

No. Let them open the shared item on the web first, then give them a reason to join.

How do invites lead to a company plan?

When several people from one company work together in the app, they need shared folders, admin and one invoice. That is the moment to offer a team or company plan.

Is it OK to import a user's contacts for invites?

Only if the user chooses each person and you explain why you ask for access. Never message contacts automatically.

What is a good invite metric to start with?

The share of active users who send at least one invite each month, followed by how many invited people activate.