The simple answer: deploy to everyone
Our honest recommendation is to turn Usivity on for all of your users. Personalizations render only in each user’s browser. They never write to your database, call your APIs on their own or change your business logic. There is nothing destructive a user can do with it.
Every user who can see your product can benefit from personalizing it. Limiting the rollout by default means holding back value from accounts that are right in front of you.
- Usivity changes only what users see, never what your system stores or computes.
- Each user’s personalizations apply to them alone. Nothing leaks across accounts.
- You choose which areas of your product (zones) Usivity can change.
- Your team can review, pause or reset personalizations at any time.
If you want to phase it
A phased approach is also valid. Some teams prefer to move step by step: to build internal confidence, gather early feedback, or line the rollout up with Customer Success plans.
If that’s you, the rest of this guide is for you. The cohorts below are ranked by how quickly and clearly they show Usivity’s value to your users, your CS team and your leadership.
- P1
Strategic and at-risk accounts
Highest visibility, fastest feedback and the strongest return story.
- P2
Accounts with high ticket volume
A measurable support impact within 30 days.
- P3
Power users and advocates
Deeper product stickiness, and word of mouth.
- P4
Everyone else
A full rollout, with confidence and internal case studies behind it.
Six cohorts worth prioritizing
Each cohort benefits from Usivity for a different reason, and shows a different kind of impact. Use them to decide where to start and how to explain the rollout internally.
Biggest and strategic accounts
Highest impactYour largest accounts have the most users, the most varied workflows and the most built-up frustration with a one-size-fits-all product. Giving them Usivity first shows you take them seriously, and makes them harder for a competitor to win.
What you’ll see: Fewer feature requests and escalations from your most visible accounts, and stronger QBRs.
How to spot them
- Top 10–20% of ARR
- Several teams or business units use the product
- A history of asking for personalization
Customers with the most support tickets
Fast returnHigh ticket volume often means users are working around your product instead of with it. Usivity fixes the frustration at the source, with no code, no sprint and no wait, and frees your support team from triage loops.
What you’ll see: Fewer tickets about how the product looks and shows data within the first 30 days, and support time moved to higher-value work.
How to spot them
- Repeat tickets about the same screens
- Tickets Engineering closes as “by design” or “not on the roadmap”
- Accounts where CSMs spend outsized time on ticket reviews
Escalated and at-risk accounts
RetentionWhen an account threatens to churn, speed matters. Usivity gives you something concrete to offer: real relief now, without engineering promises you can’t keep. The conversation moves from “we’ll look into it” to “here, done.”
What you’ll see: A way to de-escalate that CSMs can use in the meeting, not three weeks later, without a single dev ticket.
How to spot them
- Active churn conversations
- Executive escalations in the last 60–90 days
- Health scores below your threshold
High adopters and power users
Deeper valuePower users are already invested in your product. Usivity lets them tune it to how they actually work. They become self-sufficient, file fewer tickets, and show you which Usivity capabilities matter most.
What you’ll see: Higher engagement and satisfaction, and early evidence of what your market values.
How to spot them
- Daily or weekly active users
- Users who have sent detailed feature requests
- Accounts that use many of your features
Advocates and champions
Word of mouthYour advocates already talk about you. Give them something new to talk about. Champions who use Usivity mention it to peers, in case studies and in renewal conversations with their own leadership.
What you’ll see: Expansion within the account, referrals, case study material and proof points for Sales.
How to spot them
- NPS promoters (9–10)
- Named references or case study participants
- Users who refer other companies to you
Recently onboarded customers
Habit formingThe habits users form in their first 30 to 90 days tend to stick. Introduced during onboarding, personalization becomes part of how they learn your product, not an add-on they find later.
What you’ll see: Higher long-term engagement, lower early churn, and customers who feel from day one that the product fits them.
How to spot them
- First 30–90 days after go-live
- Still in onboarding or implementation
- CSMs still doing regular check-ins
What to tell your customers
Good rollouts don’t need a training session or a change-management plan: Usivity is self-serve by design. But a short, well-placed announcement lifts early adoption a lot.
Keep the message simple: your product now lets users personalize their own experience. No tickets, no waiting. Just ask for what you want.
In-app announcement
A one-time tooltip or modal at first login after launch. Show where Usivity lives and give one example of what they can do. That is often enough.
CSM-led introduction
For strategic or at-risk accounts, have the CSM introduce it live during a check-in and make one personalization together, in real time.
Email or release note
A short note focused on the outcome: “You can now change how your workspace looks without submitting a request.” Avoid technical language.
Seed your power users
Reach out to known power users first. They explore on their own, find the best uses for their account and spread it internally.
The bottom line
Not sure yet? See whether Usivity fits your product, or plan your first 30 days.