Back to GrowthDex
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.

rare tacticfree budget

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.

Company 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 and metric

Source: Microsoft Learn: Configure default options for your app

Microsoft documents a single recommended default scope and says the configured install flow is quicker and more straightforward.

OnboardingActivationProductteams appsinstall flowscope strategyactivation
GrowthDex operator note

When to use it

Use this when Onboarding, Activation, Product is relevant to teams apps, install flow, scope strategy and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

Founder checklist

  1. Read Microsoft Learn: Configure default options for your app and identify what is directly supported.
  2. Choose one channel context: Onboarding, Activation, Product.
  3. Define the test around Microsoft documents a single recommended default scope and says the configured install flow is quicker and more straightforward..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Product-Led GrowthOnboardingActivationProduct

Related tactics

Slack onboarding starts at the first invocation context

Start onboarding from the first Slack surface the user actually touches, and vary the flow for App Home clicks versus slash-command intent instead of making every newcomer take the same route.

rareOnboarding, Product, Activation

AI install wizard for 90-second setup

Turn AI setup into a short guided wizard so a user can get from curiosity to first answer in about 90 seconds instead of ten wandering minutes.

rareOnboarding, Activation, Product

Figma Community playground file before broad promotion

Ship a playground file before broad promotion so users can try the plugin in a safe example file instead of guessing how to set it up from screenshots alone.

rareOnboarding, Product, Marketplaces

Manual chat onboarding before self-serve

Set up the first users manually over chat or in person before you automate signup, so you can watch friction show up in real time.

rareProduct, Onboarding, User Research

Notion template linked-content audit before submit

Before you submit a template, move every promised linked asset into the template itself so duplicators do not hit invisible pages right after install.

rareMarketplace, Product, Onboarding

Telegram group add link requests admin rights up front

Use `startgroup` or `startchannel` links with the right admin permissions before rollout, so the bot lands in the team context with enough authority to do the job on day one.

rareOnboarding, Product, Activation
Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian