Verified against ChatGPT · 2026-08-08
Write an upsell conversation triggered by a customer hitting a usage ceiling
Turns a specific usage-limit trigger into an upsell conversation that reads as a helpful heads-up about their own growth, not a sales pitch disguised as a check-in.
The prompt
Ready to copy — highlighted parts are example details you can swap.
A customer just hit a usage ceiling on their current plan, and I need to reach out about upgrading before it becomes a problem for them, not pitch an upsell out of nowhere.
CUSTOMER AND WHAT THEY HIT
They've hit 95% of their monthly API call limit for the third month running.
CURRENT PLAN AND WHAT THE NEXT TIER UNLOCKS
Currently on Growth plan (100K calls/month); Scale plan raises the limit to 500K and adds priority rate limiting.
HOW THEY'VE BEEN USING THE PRODUCT
Usage has climbed steadily as they've rolled the integration out to two more internal teams.
RELATIONSHIP CONTEXT
Technical lead I've emailed with a few times, generally responsive, no prior pricing pushback.
PHASE 1 — FRAME THE TRIGGER AS THEIR SIGNAL, NOT MINE
Open by naming the specific usage pattern that triggered this outreach, framed as evidence of their own growth or adoption, not as an account limit I'm enforcing. The message should read as if I noticed something about their success and I'm flagging it proactively, because that's actually what happened — I shouldn't manufacture urgency that isn't there.
PHASE 2 — CONNECT THE NEXT TIER TO WHAT THEY'RE ALREADY DOING
Explain what the next tier unlocks specifically in terms of the usage pattern they're already exhibiting, not a generic list of everything in the higher tier — if they're hitting the ceiling on one specific feature, lead with what changes for that feature, and only mention other tier benefits briefly afterward.
PHASE 3 — MAKE THE NEXT STEP LOW-FRICTION
End with an easy next step — a short call, or just a yes/no on moving forward — rather than a hard pitch for a meeting, since this is a warm, expected conversation given the usage trigger, not a cold ask.
WHAT NOT TO DO
Do not use scarcity or urgency language ('upgrade now before you lose access') unless the account will actually be functionally limited soon — if it's a soft ceiling with no real consequence, say so honestly rather than inventing pressure.
OUTPUT FORMAT
A single outreach message (email or in-app message, matching Email), 120-180 words, plus one alternate subject line if it's an email.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Framing the usage ceiling as the customer's own signal rather than an account limit being imposed is the mechanism that keeps this from reading as a disguised sales pitch: a model asked to 'write an upsell message' without this framing instruction defaults to product-benefit language centered on what the vendor offers, when the actually persuasive angle here is what the trigger says about the customer's own success, which they experience as being seen rather than sold to. Tying the next tier's benefits specifically to the usage pattern they're already exhibiting, instead of listing the full feature set of the higher plan, matters because a generic upgrade pitch forces the reader to do the work of figuring out which of five listed benefits actually applies to them — leading with the one thing directly tied to what triggered the message removes that translation work and makes the relevance immediately obvious. The explicit ban on manufactured urgency addresses a known weak spot in AI-generated sales copy: models trained on marketing text default toward scarcity language ('upgrade now') because it's a common persuasive pattern in the training distribution, but applying it to a soft, consequence-free usage ceiling creates false pressure that a technically sophisticated buyer (the kind hitting API limits) will notice and discount, damaging trust in every future outreach from the same sender. Ending on a low-friction next step rather than a meeting request reflects that this conversation is already warm and expected given the trigger — asking for more commitment than the moment calls for is a common upsell mistake that turns a natural next step into something that feels like a bigger ask than it needs to be.
What you get back
Subject: You're close to your API limit again this month — noticed the pattern. Hi Jordan, I saw your team's hit about 95% of the monthly API call limit for three months running now, which tracks with rolling the integration out to two more teams. That's a good problem to have. The Scale plan raises that ceiling to 500K calls and adds priority rate limiting, so you wouldn't need to think about this again for a while. Want me to send over what that would look like, or happy to hop on a quick call if easier?
Verified against
ChatGPT GPT-5.1 · 2026-08-08
Changelog
- 2026-08-08 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
