Teams zero-install link unfurling before app search
Use zero-install link unfurling to let shared links advertise the app before the user ever visits the Teams app store.
Why this can grow a startup
Teams link sharing can be an acquisition surface, not just a content surface. Microsoft's link-unfurling docs say zero-install unfurling lets your app preview shared links even before the user discovers or installs the app. That changes the order of operations. Instead of asking for installation before the user has seen any payload, the shared URL itself can carry the first useful preview. The preview teaches the job, signals relevance, and gives the install a reason to exist.
Source-backed example
Microsoft says zero-install link unfurling can preview shared links before a user discovers or installs the app, using the `composeExtensions/anonymousQueryLink` request.
Source-reported evidence
Source: Microsoft Learn: Add Link Unfurling to App Manifest
Microsoft documents pre-install previews for shared links and names the anonymous invoke path used for zero-install unfurling.
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.
When to use it
Use this when Product-led Growth, Acquisition, Onboarding is relevant to teams apps, link unfurling, pre-install proof and you can run a bounded test with a medium 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
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Product-led Growth and Acquisition, using evidence from Microsoft Learn: Add Link Unfurling to App Manifest as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- 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.
- 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.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.