[Dev-Docs AI Improvement]: Growth lifecycle for your app #13659
Conversation
…blish/app-growth/app-growth-lifecycle.md by yashy797
Acrolinx ScorecardsWe currently enforce a minimum score of 80. Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:
More info about Acrolinx Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 14d4f81: 💡 Validation status: suggestions
msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/app-growth-lifecycle.md
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
| # Growth lifecycle for your app | ||
|
|
||
| Growing your app is a journey. It's a process that’s not overnight and goes through various stages. A typical growth lifecycle of a collaborative app on Teams looks like depicting critical barriers that once crossed puts the app into the next orbit for even higher growth: | ||
| Growing your app follows a defined journey. It involves a process that evolves over multiple stages. A typical growth lifecycle of a collaborative app on Teams depicts critical barriers that, once overcome, move the app into the next orbit for higher growth: |
There was a problem hiding this comment.
This change is not required. The original one is more fluid. Also, contractions shouldn't be removed.
| :::image type="content" source="../../../../../assets/images/app-fundamentals/growth-lifecycle.png" alt-text="App growth lifecycle." lightbox="../../../../../assets/images/app-fundamentals/growth-lifecycle.png"::: | ||
|
|
||
| - **Build stage**: In this stage, developers plan, envision, design, build, and publish their collaborative app on the Microsoft Teams marketplace. The Teams developer platform documentation is the one-stop shop for platform features, best practices, and developer guidance. Strategic developers can join an invite-only Teams engineering’s build-with partner program on this journey. | ||
| - **Build stage**: Developers plan, envision, design, build, and publish their collaborative app on Teams Marketplace at this stage. Teams developer platform documentation provides a one-stop resource for platform features, best practices, and developer guidance. Strategic developers join an invite-only Teams engineering’s build-with partner program during this journey. |
There was a problem hiding this comment.
Original one is more conversational and should be kept as is. Replacing shop with resource takes away the guiding and informational tone in which this page is written.
| To accelerate growth of third-party apps and increase adoption rates, consider these strategies: | ||
|
|
||
| - **Leverage a freemium model**: It's proven that a basic freemium account significantly improves user conversion rates. It allows users to experience the core benefits of your app without initial costs and increases the chances of conversion to paid plans. It's recommended to offer a free trial period of 30 days. | ||
| - **Leverage freemium model**: A basic freemium account improves user conversion rates by allowing users to experience core app benefits before incurring costs. Offer a free trial period of 30 days. |
There was a problem hiding this comment.
Keep the original one as it fully retains nuance about “without initial costs” and “increases chances of conversion to paid plans.”
| - Optimizing customer sales and conversion based on PQLs | ||
| - Investing further in more user-valuable scenarios or experiences inside the app | ||
| - Building public references that directly drive SQLs and MQLs by highlighting app impact among customers. | ||
| - Optimizing sales and conversion processes based on PQLs. |
There was a problem hiding this comment.
Original one is better. 'Processes' not adding any value in this scenario.
| - Investing further in more user-valuable scenarios or experiences inside the app | ||
| - Building public references that directly drive SQLs and MQLs by highlighting app impact among customers. | ||
| - Optimizing sales and conversion processes based on PQLs. | ||
| - Investing further in high-value user scenarios or experiences within the app. |
There was a problem hiding this comment.
There's a difference between more user-valuable scenarios and high-value user scenarios. Revert to original.
| ## Review the Teams partners GTM guide | ||
|
|
||
| Get started first by reviewing (and sharing with your GTM leaders) this high-level visual [Guide to ISV success with Microsoft for Teams Partners](https://aka.ms/teamsappsGTMguide) flipbook. This resource orients you about how to plan and strategize your Teams app offering, insights about key industry-wise personas and trends, how to define your app’s value proposition, create content to maximize your app’s reach among customers and sellers, access various partner benefits available to you, how to visualize a simplistic customer journey with your app, how to align your marketing activities with key opportunities from Microsoft and how to sell your app through Microsoft’s global marketplace. As you can see from the flipbook, Microsoft partners with app developers once they’ve launched their apps on the marketplace by offering select, programmatic GTM investments depending on the app’s maturity in the market. You're encouraged to get in touch with your Microsoft field, account, or engineering representatives before spending cycles on your app growth planning and execution, so that you can get the most appropriate guidance you’re eligible for. | ||
| Begin by reviewing (and sharing with your GTM leaders) this high-level visual [Guide to ISV success with Microsoft for Teams Partners](https://aka.ms/teamsappsGTMguide) flipbook. This resource explains how to plan and strategize your Teams app offering, provides insights on key industry personas and trends, explains how to define your app’s value proposition, guides you on creating content to maximize your app’s reach with customers and sellers, outlines available partner benefits, depicts a simplified customer journey with your app, aligns marketing activities with key opportunities from Microsoft, and illustrates how to sell your app through Microsoft’s global marketplace. As the flipbook shows, Microsoft partners with app developers once they publish their apps on Marketplace by offering select, programmatic GTM investments that depend on the app’s market maturity. Get in touch with your Microsoft field, account, or engineering representatives before investing cycles on your app growth planning and execution to receive the most relevant guidance. |
There was a problem hiding this comment.
The suggested changes rephrase the original one quite closely, but original version provides better context and clearly specifies points like eligibility-based guidance. It also uses broader, more detailed phrasing like “launched their apps” and “visualize a simplistic customer journey,” which conveys a wider scope and richer context.
This PR updates the content of the file: msteams-platform/concepts/deploy-and-publish/appsource/post-publish/app-growth/app-growth-lifecycle.md.
Submitted by: @yashy797