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 tactic
Best-fit channelOnboarding · Activation · Product
Stage + contextteams apps · install flow · scope strategy · activation
BudgetFreebudget tier
Suggested operator signalShare of target users completing the product's first-value action

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.

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-reported evidence

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.

Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.

Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.

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.

How to do it

  1. Choose one target segment and define the exact next action this tactic should prompt.
  2. Adapt the tactic to Onboarding and Activation, using evidence from Microsoft Learn: Configure default options for your app as context—not as a promised result.
  3. Record a baseline for: Share of target users completing the product's first-value action. Set a guardrail that would make you pause the test.
  4. Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
  5. Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Next move

Compare a stack for your situation

Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.

Build my stack

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
Close the loop

Did you launch this experiment?

Report a launch to help us understand which growth ideas founders put into practice.

This report uses a pseudonymous browser ID. Prompts, names, email, or free-text are not included in outcome events.

Advisory bridge

Apply this with an operator

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

Work with Ian