Turn paywall hits into upgrade conversations
Someone hit a limit inside your product. Find out which limit, who else at the account is affected, and offer help before the upgrade pitch.
The conversation
Sample accounts and numbers, for illustrationYouShow me the accounts where someone hit a paywall or usage limit in the last 7 days, with which limit, how many people at the account use the product, who the admin is, and whether there’s an open opportunity. Draft a note to each admin that offers help with the limit before mentioning the upgrade.
Unify3 checks · product events and CRM
- Read paywall and usage-limit events from the last 7 days, with the feature, the reason and the plan each person looked at.
- Counted active users at each account and found the admin from your identify events.
- Checked Salesforce for the current plan, the account owner and any open opportunity.
Nine accounts hit a limit this week. Three are on the plan right below the one that removes it, and none of those three has an open opportunity.
Limits are read from the event properties your product sends. An account with an open opportunity is listed for the rep, not drafted to.
YouWhich of these are real upgrade conversations, and which just need help?
UnifyTwo are upgrades: Merridian is out of seats with people waiting, and Halden hits the API cap every morning. Northwind needs help, not a plan.
Ten seats, ten in use. Two invites this week could not be accepted.
API cap hit before 10am on four of the last five weekdays.
Three export attempts on the same report. It should be scheduled, not upgraded.
YouDraft the notes. Help first, upgrade second, and route them to the account owners.
UnifyThree drafts are in review with their owners. Each opens on the limit, and only two mention a plan.
ToNils Berg
SubjectThe two invites that bounced
Nils, two invites from your team this week hit the seat limit. I can add two seats today so they land, and we can sort the plan afterwards if the team keeps growing. Ten minutes this week?
- Nils BergOwner AnaIn review
- Tara QuinnOwner ChrisIn review
- Dana HoltOwner SamIn review
Set up
- Drafts routed to owners Three notes, one per admin, waiting for approval with the limit and the people affected attached.
- Repeat-hit watch Accounts that hit the same limit again in the next 30 days come back to the owner as a task.
The limit is the reason to write. The plan is named once, after the help.
Paywall follow-up, with and without Unify
The limit is the signal. The help is the opener.
| Without Unify | With Unify |
|---|---|
| A usage-limit event fires in your analytics tool and nobody outside product sees it | Paywall and usage-limit events arrive in Unify with the feature, the reason and the plan the person looked at |
| The person who hit the limit gets an in-app banner and a pricing page, and that is the whole conversation | The account is read as a whole: how many people use the product, who the admin is, and whether a deal is already open |
| Sales finds out at renewal that three teams have been working around a limit for months | The account owner hears the same day, with the limit and the people affected attached |
| Upgrade outreach opens with the pitch, so it reads as a sales email rather than help | The first message offers a workaround or a call about the limit, and mentions the upgrade second |
Start from this prompt
Make it your own in Unify, then review the results.
Show me the accounts where someone hit a paywall or usage limit in the last 7 days, with which limit, how many people at the account use the product, who the admin is, and whether there's an open opportunity. Draft a note to each admin that offers help with the limit before mentioning the upgrade.
What else you can ask for
The walkthrough is one path through this workflow. These are the turns people take most often.
- Abandoned upgradesWho clicked the upgrade CTA in the last 3 days and hasn't changed plan, and what were they looking at when they clicked?Try in Unify
- One limitWhich accounts hit the seat limit this month, and how many of them are on the plan right below the one that removes it?Try in Unify
- Repeat hitsWhich accounts have hit the same limit more than twice in 30 days, and who owns them in the CRM?Try in Unify
How it changes by who you sell to
- Software
- Engineering and product teams hit seat and API limits first, and the person who hit it is rarely the buyer. Ask for the admin on the account alongside the person who hit the limit, and lead with the workaround before the plan.
- Financial services
- Limits at banks and insurers are usually hit by an operations team inside a procurement cycle. Ask whether the account has an open opportunity before writing, and route the note to the account owner rather than sending it cold.
- Healthcare
- Usage limits at provider and health-tech accounts often mean a second department started using the product. Ask which department the users sit in and whether a signed agreement covers it, and offer the compliance material with the upgrade.
- Retail and e-commerce
- Retail accounts hit limits in bursts around launches and peak season and go quiet after. Ask for limits hit in the last 7 days only, and for the head of e-commerce or operations rather than whoever hit it.
- Professional services
- At firms, a paywall is usually hit by one practice, and the upgrade decision sits with the practice lead or the COO. Ask for the practice the users belong to and the partner who runs it, and offer help with the limit first.
Next in product-led growth
+4Stalled signupsFollow up with stalled signupsPeople signed up, logged in, and stopped before the step that makes the product useful. Find where each one stopped and point them at the next step.
+4Product-ledRun outbound on product usageThe strongest signal you have is what people already do inside your product.- +4Free-plan conversionTurn free-plan usage into upgradesFree-plan users who use the product every week have already made the case. Find them, and write to the one who uses it most.
Connect what this workflow uses
Each guide covers the connection, what Unify reads and writes, and what to check before the first run.
- Connect PostHogConnect PostHog to Unify as a destination, choosing the product events and the person and company context to send.
- Connect SegmentSend supported Segment events into Unify through Webhook (actions).
- Connect SalesforceAuthorize Salesforce in Unify, configure CRM field mappings, and choose when to enable writing.
- Connect HubSpotConnect HubSpot to Unify, map Company and Person fields, and plan CRM exclusions and supported write-back.
- Connect GmailConnect Gmail to Unify for sequence emails and replies.
- Connect OutlookConnect Microsoft Outlook directly to Unify.
Questions about this workflow
Where does the paywall event come from?
From your product's own events. Forward them from PostHog or Segment, or send them with the Unify Intent client SDK. Unify's docs list a paywall or usage-limit hit as the strongest upgrade signal, and the event carries the feature, the reason and the plan the person looked at.
Should I install the Unify SDK if we already use PostHog or Segment?
No. Forward events from the tool you already have. Running the SDK alongside PostHog or Segment in the same app records every event twice, so the docs say to use one source per app.
Why does the note offer help before the upgrade?
Because a limit is a moment of friction, not a purchase decision. Unify's own guidance frames upsell plays as offering assistance or upgrade options, and a note that solves the limit first gets read where a pitch gets filed.
Does this also cover people who clicked upgrade and stopped?
Yes. An upgrade CTA click is a documented event and the clearest purchase intent there is. The abandoned-upgrades variant asks for clicks with no plan change after 3 days, and the note references what they were looking at.