Skip to main content
Post-Sales Playbook

How Do You Get Existing Customers to Adopt New Features After Onboarding?

Onboarding covers the product at go-live, not features that ship later. Learn how to measure, target, and follow up on new feature adoption account by account.

Arushi Jain

Arushi Jain

·7 min read
How Do You Get Existing Customers to Adopt New Features After Onboarding?
On this page

You get existing customers to adopt new features by treating each launch as a small adoption project: decide which accounts the feature is for, measure whether those accounts start using it, and follow up only with the ones that haven’t. Announcing a feature to everyone and hoping they find it rarely works. Customers were trained during onboarding, but a feature that ships months later has no onboarding of its own unless you create one.

Quivly, the AI workforce for post-sales teams, supports that loop when your product sends feature usage as metrics. Quivly reads usage from a warehouse, a product analytics connection, or the Usage Push API, shows it on each customer, and lets you filter the customer list by those metrics. Plays and Agents can then find accounts that haven’t started using a feature and draft follow-ups for a person to review.

Key Takeaways

  • Onboarding training covers the product as it was at go-live. Features that ship later need their own adoption plan.
  • Track adoption per feature, per account. You can only follow up on what you measure.
  • Target the accounts a feature actually helps, not your whole customer base.
  • Follow up based on behavior: reach the accounts that haven’t tried the feature, and leave the ones already using it alone.
  • Keep a person in the loop for customer-facing messages, especially when outreach is drafted automatically.

Why Don’t Customers Pick Up New Features on Their Own?

An onboarding lead at a vertical software company listed it plainly among their pain points: customers are not trained on new features as they launch. Their team put real effort into onboarding each new customer, but once a customer was live, new releases reached them unevenly, if at all. The same team was already stretched handling several new onboardings every week.

The pattern is familiar. Release notes go to an admin who may not pass them on. CSMs mention a feature on calls with their most engaged accounts and miss the quieter ones. Months later, a customer asks for something the product already does. Meanwhile, the features most likely to deepen value go unused in exactly the accounts that would benefit. If you’re still defining what “active” means for your product, start with this guide to defining and tracking activation events.

What Makes a Feature Adoption Plan Work? 5 Criteria

  1. Feature usage is measured per account. Decide on one event or metric that shows real use of the feature. In Quivly, feature-level adoption is available when you send those events as usage metrics from a warehouse, PostHog, or the Usage Push API and link them to customers.
  2. The audience is defined before launch. Name the accounts the feature is built for, such as a plan tier, a segment, or customers who use a related workflow. Quivly Plays can target all customers or a specific customer segment.
  3. Non-adopters are easy to find. You need a list of accounts in the audience that haven’t used the feature yet. Quivly’s customer list can show any usage metric as a column over 30, 60, 90, or 180 days or one year, filter it with operators such as “less than” or “is empty,” and save the result as a view.
  4. Follow-up is triggered by behavior. Outreach should go to accounts that haven’t adopted after a set period, not to everyone on launch day. In Quivly, a scheduled Agent can run for a segment, look up usage and contacts, draft an email, and pause at a Review step before anything is sent.
  5. Results are reviewed and the plan adjusted. Check adoption a few weeks after launch, by segment. Quivly’s product adoption workflow covers reading usage trends on each customer, building working lists, and scoring usage in health.
ApproachWhat it reachesWhere it falls short
Release notes and announcementsEveryone, at the same timeNo way to tell who read them or started using the feature
CSMs mention it on callsAccounts with regular callsMisses quieter accounts and depends on each CSM’s memory
Usage-based list of non-adoptersThe accounts in the audience that haven’t used itNeeds the feature event sent as a usage metric first
Scheduled, reviewed follow-upNon-adopters, with a drafted message per accountNeeds a clear audience and someone to review drafts

How to Run a Feature Adoption Plan, Step by Step

These steps work for any feature you launch to existing customers. Each step shows how Quivly handles it.

  1. Pick the adoption metric before launch. Agree with product on the event that counts as real use of the feature, and make sure it reaches Quivly as a usage metric linked to customers. Quivly doesn’t track feature flags or session replay itself; it works with the usage metrics you map.
  2. Define the audience as a segment. Create a customer segment for the accounts the feature is meant for. Targeting a segment keeps outreach relevant and avoids sending the same message to accounts that won’t benefit.
  3. Build a non-adopter view. On the customer list, add the feature’s usage metric as a column and filter for accounts where it is empty or low. Save it as a custom view so CSMs can open the same list every week.
  4. Set up a scheduled follow-up. Create an Agent with a Schedule trigger for the segment. Have it look up usage and contacts, run a skill that drafts a short, account-specific note about the feature, and pause at a Review step. Approvals land in the Actions inbox, where the owner can edit the draft before sending.
  5. Offer a guided session to accounts that need it. For larger accounts or complex features, create a small project with tasks for the customer, such as attending a session or trying the feature on real data, and share it through the Customer Portal.
  6. Review adoption after a few weeks. Open the view again, compare adoption across segments, and decide whether to adjust the message, the audience, or the feature itself. If the feature’s metric is scored in health, slow adoption also shows in the Product Usage category.

Step three makes the rest possible. Once non-adopters are a saved list rather than a guess, follow-up becomes routine instead of a one-off campaign.

How to Choose: If You… Then…

  • If your product doesn’t send feature events yet, then start by instrumenting one metric for your next important launch before planning outreach.
  • If a feature is only relevant to some customers, then define a segment and target only those accounts.
  • If CSMs don’t have time to chase every launch, then let a scheduled workflow draft the follow-ups and keep the CSM as the reviewer.
  • If adoption stays low after outreach, then talk to a few non-adopters before sending more messages; the issue may be the feature, not awareness.
  • If you launch features often, then reuse the same view, segment, and workflow pattern for each launch instead of starting over.

Buyer Considerations

When you evaluate tools for post-launch adoption, ask how feature usage gets in and whether it can stay in your warehouse. Check whether you can filter accounts by a specific metric and save that list, whether follow-ups can be scheduled for a segment, and whether every customer-facing message can require a person’s review. This guide to behavior-based retention automation covers which usage signals are worth automating.

Feature adoption builds on the habits set during rollout. See how to plan customer training and change management during a rollout, what to check in a post-go-live adoption review, and how to keep customers engaged in a shared workspace after onboarding ends.

Conclusion

New features only add value when customers use them, and onboarding doesn’t cover what ships later. Treat each launch as a small adoption plan: measure the feature per account, define who it is for, find the accounts that haven’t started, and follow up with reviewed, account-specific messages. Quivly supports that loop with usage metrics on each customer, filterable and saved customer views, segment-targeted Plays and scheduled Agents, and drafts that wait in the Actions inbox for a person to approve.

If you’d like to see how a feature adoption follow-up could run on your own accounts, book a demo with Quivly.

FAQ

Frequently asked questions

From Quivly

AI workforce for post-sales.