> ## Documentation Index > Fetch the complete documentation index at: https://docs.noimosai.com/llms.txt > Use this file to discover all available pages before exploring further. # Increase Renewals and Account Expansion > Learn how to help customers achieve the expected outcomes, reduce renewal risk, expand successful use cases, and build advocacy. Renewals and account expansion depend on whether customers achieve the outcomes they expected when they signed. Support each stage from implementation and adoption through value measurement and the renewal decision. Expand the account only when broader use or an additional product addresses a real customer need. ## How retention and expansion develop Post-contract relationships generally progress along the following flow. ```text theme={null} Implement → Start using → Become embedded in operations → Verify outcomes → Renew contract → Expand usage ``` Do not wait until the renewal date to assess the relationship. Review the objectives and success metrics agreed during implementation throughout the contract. High usage does not necessarily mean the customer has achieved the desired outcome, and low usage is not automatically a failure; evaluate progress against the business result the customer wanted. ## Align success criteria during onboarding To prevent a gap between expected and delivered outcomes, confirm the following items before and after implementation. | Item to confirm | What to align | | ------------------------ | ---------------------------------------------------------------------------- | | Problem to solve | The processes to improve and their priorities | | Scope | Departments, users, and processes to be implemented | | Owners | Customer and provider sponsors and implementation leads | | Implementation tasks | Configuration, data, integrations, training, internal coordination | | Implementation milestone | Observable conditions and deadline for considering the solution ready to use | | Success metrics | How to check time, cost, quality, revenue, risk, etc. | | Communication channels | Contact points for inquiries, incidents, change requests, and regular checks | Define completion criteria as well as implementation tasks. Replace a vague task such as “complete configuration” with an observable outcome such as “users in the target department can complete the intended workflow.” Do not choose success metrics solely based on values that are easy for the provider to confirm. Tie metrics to the customer’s reasons for adopting, and align the pre-implementation baseline, the goals, and the timing of checks. ## Support onboarding and adoption After onboarding, verify not only how often the product is used but whether it is being used for the business processes the customer intended. Responses differ depending on whether users don’t know how to use the product or cannot integrate it into their workflows. | Item to confirm | What to investigate if there’s a problem | Main actions | | ----------------------------- | ----------------------------------------------------- | -------------------------------------------------- | | Initial setup and preparation | Are the required tasks and owners clear? | Confirm steps, owners, and deadlines | | User understanding | Do users understand operations and decision criteria? | Provide operation guides, training, and FAQ | | Use in target processes | Can it be integrated into actual process steps? | Review process flows and roles | | Usage frequency and scope | Why isn’t it being used? | Verify required features, permissions, and support | | Inquiries and issues | Are the same questions or incidents recurring? | Improve guides, settings, or the product | Tailor support by user role: end users, administrators, and decision makers. For end users, show actual process steps; for admins, focus on configuration and incident handling; for decision makers, demonstrate progress and outcomes. If help pages or FAQs are publicly available, use NoimosAI to review the website and improve any fragmented or missing prerequisite explanations and ensure the next actions are clear. ## Prove outcomes and value Use the metrics agreed at implementation to compare before and after adoption. Check not only usage volume but the time, cost, quality, revenue, and risk improvements the customer sought. When verifying outcomes, summarize the following: * Pre-implementation state and goals * Current usage scope * Metrics that improved and metrics that haven’t improved * Use patterns that led to outcomes * Issues preventing outcomes * Actions the customer and provider will take in the next period If outcomes fall short of goals, examine not only product issues but also the customer’s department, process design, required data, training, and internal priorities. Avoid attributing the cause to a single factor; choose actions to verify in the next period. When sharing results with the customer, show not only the changed numbers but what actions produced those changes and under what conditions they are reproducible. Use this both for renewal discussions and to help end users improve their work. ## Identify renewal risk early Confirm the information and timing needed for renewal decisions and address issues early rather than just before renewal. Common renewal risks include: * The implementation objectives were not achieved * Initial implementation tasks remain incomplete * Users or decision makers have changed * Use is limited to certain users or departments * Unresolved inquiries or incidents remain * The customer’s business, budget, or priorities have changed * The customer is considering competitors or alternative approaches * Renewal conditions or procedures have not been shared For each customer, confirm the renewal date, the customer’s decision timing, current outcomes, unresolved issues, and next actions. Some companies decide budget or usage policies before the contract renewal date, so use the customer’s actual decision timing as the baseline. | Risk | First action | | ------------------------ | ------------------------------------------------------------------------ | | Objectives not achieved | Confirm unmet metrics and causes, and define an improvement plan | | Adoption not embedded | Confirm reasons for non-use and the target processes | | Change in decision maker | Share implementation objectives, outcomes to date, and outstanding items | | Outstanding issues | Clarify status, owners, and deadlines for resolution | | Change in priorities | Reassess whether current problems align with provided value | If there are a notable number of public social mentions about your company or product, use NoimosAI’s social listening to quickly detect questions, complaints, and misunderstandings. Use this to identify common improvement areas across customers, not as decision data for individual renewals. ## Propose account expansion Make add-on proposals based on the usage patterns that produced results and the problems the customer wants to solve next—not on what the provider wants to sell. | Expansion option | Questions to answer | | -------------------------------------- | ----------------------------------------------------- | | Increase the number of users | Are there others doing the same work? | | Expand to additional departments/sites | Are conditions in place to reproduce the outcomes? | | Broaden the scope of usage | Can unused features or support solve other problems? | | Upgrade to a higher-tier contract | Are needed usage, features, or support increasing? | | Add related products or services | Do these tie to current outcomes and next challenges? | Before proposing, confirm that current usage is embedded and that the same outcomes can be reproduced in the expanded scope. If current issues remain, resolve them before proposing additions. In proposals, show current outcomes, the scope to be added, expected impact, and required cost and tasks. When expanding to another department, verify any differences in processes, permissions, training, and success metrics. ## Turn customer success into advocacy For customers who have achieved outcomes, request participation in case studies, reviews, speaking at events, or referrals. Before requesting, confirm what company name, figures, processes, and comments the customer can disclose and the internal approval process. A case study should explain not only outcomes but also pre-implementation challenges, selection reasons, implementation tasks, usage patterns, and the time until outcomes appeared. This helps new prospects assess reproducibility for their own organizations. Publish case studies beyond the website—link them from industry- and use-case pages, SEO articles, social posts, and events. NoimosAI can generate social posts and article blurbs based on published case study pages. ## Measure retention and expansion Segment customers not only by overall average but by product/service contracted, onboarding date, customer size, and other similar conditions to evaluate outcomes. The table below maps outcomes to the indicators used to judge changes in the renewal/add-on flow. | Outcomes to check before renewal/add-on | Indicators to judge those outcomes | | --------------------------------------- | ------------------------------------------------------------------------- | | Implementation complete | Initial setup, training, and first business process completion | | Adoption embedded | Use in target processes, number of users/departments, recurring issues | | Perceived value | Agreed success metrics, customer feedback, unresolved issues | | Retention | Number of renewals, renewal rate, churn count, churn reasons | | Expansion | Number of add-on contracts, increases in users/departments/contract value | | Advocacy | Case studies, reviews, referrals, event speaking | Check changes monthly and prioritize customers whose implementations are incomplete, whose outcomes are unverified, or whose renewal decisions are imminent. Track not only renewal rate but whether the number of customers achieving the outcomes expected at implementation is increasing. ## Related pages * [Improve win rate](/playbooks/b2b/improve-win-rate) * [Grow awareness](/playbooks/b2b/grow-awareness) * [Expand awareness and trust via social media](/playbooks/b2b/sns) * [Build and improve your website](/playbooks/b2b/build-website)