Growth idea action plan
Teams default install scope matches the first job
Set the default install scope to the first place the user should get value, so Teams recommends the right surface instead of forcing them through a scope choice they do not understand yet.
Why this can grow a startup
A lot of Teams apps lose momentum on the first screen because the buyer has to decide where the app belongs before they know what the app is good for. Microsoft's install-scope docs make the tradeoff plain. You can set one default install scope, Teams labels that scope as recommended, and the resulting install flow becomes quicker and more straightforward. That is not just a manifest convenience. It is a positioning choice. The best default scope usually points at the first job you want completed, not the broadest surface your app happens to support.
Ian's take
From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where teams default install scope matches the first job can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Onboarding and Activation channel.
- Use the evidence from learn.microsoft.com to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
Source-backed example
Microsoft says apps can set one `defaultInstallScope` to `personal`, `team`, `groupChat`, or `meetings`, and the configured scope appears as the recommended option in the install flow.
Source: Microsoft Learn: Configure default options for your app (learn.microsoft.com)
GrowthDex source hub: Microsoft Learn: Configure default options for your app
Last checked: 2026-06-09T02:07:48.000Z
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Slack onboarding starts at the first invocation context 3 shared channels · 1 shared stage
- Figma Community playground file before broad promotion 2 shared channels · 1 shared stage
- Manual empty-state concierge onboarding 2 shared channels · 1 shared stage
- Manual chat onboarding before self-serve 2 shared channels · 1 shared stage
Related GrowthDex essays
- The Teams app should meet the work before the help doc onboarding, product-led growth, brand trust
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory