# The Teams app should meet the work before the help doc > Why Teams growth often comes from default scope choices, stronger first tabs, admin pinning, zero-install previews, and message-extension context that matches the user's real moment. - Canonical HTML: https://growth.iangoh.com/blog/the-teams-app-should-meet-the-work-before-the-help-doc/ - Published: 2026-06-09 - Updated: 2026-06-09T02:07:48.000Z - Categories: onboarding, product-led growth, brand trust - Niches: SaaS, AI products, B2B software, collaboration tools, developer tools ## On this page - Pick the install scope that matches the first job - The first pinned tab should explain the job, not the settings - Admin pinning is distribution work - Let shared links do some of the selling - Commands should match the moment that triggered them - Where this cluster is strongest ## Start with these related tactics - [Teams default install scope matches the first job](/growth-ideas/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. - [Teams static tab pinned before configurable detour](/growth-ideas/teams-static-tab-pinned-before-configurable-detour/): Ship one strong static tab for the first read, because Teams pins the static tab by default when you also offer a configurable tab in the same scope. - [Teams admin pin path before adoption drift](/growth-ideas/teams-admin-pin-path-before-adoption-drift/): Treat admin pinning as part of distribution, not IT cleanup, so the app lands in the app bar or compose area where repeat usage can actually happen. A lot of Teams app teams still treat growth like a store problem. They polish the listing, wait for approval, and hope the user will figure out the rest after install. That is usually backwards. In Teams, the first useful move often depends on where the app shows up, what surface opens first, and whether the product helps inside the conversation before it asks the user to leave it. ## Pick the install scope that matches the first job [Teams default install scope matches the first job](/growth-ideas/teams-default-install-scope-matches-the-first-job/) is the quiet growth lever in this batch. The first recommendation in the install flow should point at the place where the user can finish something quickly, not at the broadest scope your manifest can support. It belongs beside [Teams Store long description names audience benefits and setup](/growth-ideas/teams-store-long-description-names-audience-benefits-and-setup/). One tactic sets the expectation in the listing. The other keeps the install flow from immediately breaking that expectation. ## The first pinned tab should explain the job, not the settings [Teams static tab pinned before configurable detour](/growth-ideas/teams-static-tab-pinned-before-configurable-detour/) is a useful rule because Teams already chooses the first tab for you when both tab types exist in the same scope. If the static tab opens first, it should carry the explanation, the proof, and the next step. I would read that with [Teams Store first-run account with preloaded proof](/growth-ideas/teams-store-first-run-account-with-preloaded-proof/). Both moves ask the same question: what does an outsider see before anyone on your team intervenes? ## Admin pinning is distribution work [Teams admin pin path before adoption drift](/growth-ideas/teams-admin-pin-path-before-adoption-drift/) matters because an approved app that nobody can find is not really deployed. If the app belongs in the app bar or the compose area, the rollout plan should say so out loud. This fits next to [Teams Store publisher verification and attestation before promo](/growth-ideas/teams-store-publisher-verification-and-attestation-before-promo/). Enterprise distribution does not end when the store says yes. It ends when the app is both trusted and easy to reach. ## Let shared links do some of the selling [Teams zero-install link unfurling before app search](/growth-ideas/teams-zero-install-link-unfurling-before-app-search/) is the strongest product-led move here. A shared URL can show the app's usefulness before the user has learned the app's name. That is close to [Slack app suggestions from shared domain links](/growth-ideas/slack-app-suggestions-from-shared-domain-links/). In both products, the workflow itself becomes the introduction. ## Commands should match the moment that triggered them [Teams message extension context matches the user moment](/growth-ideas/teams-message-extension-context-matches-the-user-moment/) is mostly a restraint rule. Do not ship one giant command and hope the user sorts out when to use it. The compose box, the command box, and the message itself are different prompts. I would keep it near [Google Chat app command menu for fast and typed jobs](/growth-ideas/google-chat-app-command-menu-for-fast-and-typed-jobs/). The common lesson is to meet the user's intent in the surface where it naturally appeared. ## Where this cluster is strongest This cluster is strongest for SaaS teams building copilots, knowledge tools, approval flows, support products, and internal software that only becomes useful if it stays inside the daily collaboration path. If I were tightening a Teams growth system this week, I would revisit the default install scope, turn the first pinned tab into a real introduction, decide where admin pinning should put the app, add zero-install previews for the links users already share, and split message-extension behavior by the moment that triggered it. That work is less glamorous than another listing rewrite. It usually gets the app closer to the real job. If you want help tightening collaboration-product onboarding, enterprise rollout paths, and trust-heavy product-led growth loops, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Teams default install scope matches the first job](/growth-ideas/teams-default-install-scope-matches-the-first-job/) - Onboarding, Activation, Product - [Teams static tab pinned before configurable detour](/growth-ideas/teams-static-tab-pinned-before-configurable-detour/) - Onboarding, Brand Trust, Product - [Teams admin pin path before adoption drift](/growth-ideas/teams-admin-pin-path-before-adoption-drift/) - Activation, Retention, Distribution - [Teams zero-install link unfurling before app search](/growth-ideas/teams-zero-install-link-unfurling-before-app-search/) - Product-led Growth, Acquisition, Onboarding - [Teams message extension context matches the user moment](/growth-ideas/teams-message-extension-context-matches-the-user-moment/) - Product, Onboarding, Retention ## Essay chronology - [Newer essay: The lifecycle message should follow the last real signal](/blog/the-lifecycle-message-should-follow-the-last-real-signal/) - lifecycle marketing, onboarding, retention - [Older essay: The Slack app should start helping before the docs tab opens](/blog/the-slack-app-should-start-helping-before-the-docs-tab-opens/) - onboarding, product-led growth, brand trust ## Keep reading - [The Slack app should start helping before the docs tab opens](/blog/the-slack-app-should-start-helping-before-the-docs-tab-opens/) - onboarding, product-led growth, brand trust - [The Google Chat app should survive the first admin and the first space](/blog/the-google-chat-app-should-survive-the-first-admin-and-the-first-space/) - marketplaces, onboarding, brand trust - [Onboarding should change when the customer changed](/blog/onboarding-should-change-when-the-customer-changed/) - activation, product-led growth, brand trust ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Microsoft Learn: Configure default options for your app](https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/deploy-and-publish/add-default-install-scope) · [GrowthDex source hub](/sources/microsoft-learn-configure-default-options-for-your-app-learn-microsoft-c/) - [Microsoft Learn: Tabs in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/what-are-tabs) · [GrowthDex source hub](/sources/microsoft-learn-tabs-in-microsoft-teams-learn-microsoft-com/) - [Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users](https://learn.microsoft.com/en-us/microsoftteams/teams-app-setup-policies) · [GrowthDex source hub](/sources/microsoft-learn-use-setup-policies-to-manage-install-and-pin-agents-and-/) - [Microsoft Learn: Add Link Unfurling to App Manifest](https://learn.microsoft.com/en-us/microsoftteams/platform/messaging-extensions/how-to/link-unfurling) · [GrowthDex source hub](/sources/microsoft-learn-add-link-unfurling-to-app-manifest-learn-microsoft-com/) - [Microsoft Learn: Message extensions](https://learn.microsoft.com/en-us/microsoftteams/platform/messaging-extensions/what-are-messaging-extensions?tabs=nodejs) · [GrowthDex source hub](/sources/microsoft-learn-message-extensions-learn-microsoft-com/) - [Microsoft Learn: Understand App Structure to Design Apps](https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/design/app-structure) · [GrowthDex source hub](/sources/microsoft-learn-understand-app-structure-to-design-apps-learn-microsoft-/) ## Editing notes - Kept the essay focused on one claim: Teams growth gets easier when the app meets the workflow before the user detours into setup or docs. - Used plain objects like scope pickers, the first pinned tab, admin pinning, shared links, and command surfaces instead of inflated platform language. - Linked the new tactics to existing Teams, Slack, and Google Chat pages so the piece reads like operating advice rather than a standalone manifesto. - Ended with a concrete weekly tightening sequence and one advisory CTA instead of a padded conclusion. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.