A price increase post is one of the few things you can publish on X that people genuinely read word for word, because some of them are about to pay you more money. That tension is exactly why so many founders fumble it. They either bury the news in corporate fog or they overshare and turn a routine business decision into a public apology tour.
I have written and watched dozens of these go out, from $9 SaaS bumps to consulting rates that doubled. The posts that land share a pattern, and the ones that blow up in the replies share a different one. Here is how to write the version that holds up.
Decide what the post is actually for
Before you type a word, get clear on the job this single post is doing. A price increase announcement on X usually serves one of three goals, and they pull in different directions:
- Inform existing customers so nobody feels ambushed when their next invoice is higher.
- Create urgency so people on the fence buy at the old price before the deadline.
- Signal positioning so the market reads your product as more premium than it was last week.
Most founders try to do all three in one post and the message gets muddy. Pick the primary job. If you are mostly protecting current customers, the tone is reassuring and the call to action is "nothing changes for you." If you are mostly driving last-minute sales, the tone is confident and the call to action is a hard date. You can nod to the other goals, but one of them leads.
A clean example. A founder raising from $19 to $29 wrote: "We are raising prices on March 1. If you are already a customer, your rate is locked forever. If you have been waiting, this is your last week at $19." That post knows its job. Current customers exhale, fence-sitters feel the clock, and the brand looks organized rather than greedy.
Lead with the news, not the backstory
X rewards getting to the point. People scroll fast, and a post that opens with three sentences of throat-clearing about your "journey" gets skipped before the actual news lands. Put the change in the first line.
Compare these two openers:
- Weak: "We have been thinking a lot lately about the value we deliver and where we want to take this product over the next year..."
- Strong: "Pricing goes up 40% on April 15. Here is exactly what is changing and why."
The second one respects the reader. It tells them the what (a 40% jump), the when (April 15), and promises the why is coming. That structure is the hook, and if you struggle to compress the news into one tight line, a hook generator can spin out a dozen openers you can react to and edit down. The goal is not a clever metaphor. The goal is a sentence that makes the right person stop scrolling.
Once the news is out, the rest of the post earns trust. But you cannot earn trust on a claim the reader has not seen yet.
Give a real reason, and keep it short
People accept price increases. What they reject is vagueness. "Due to increased costs and our commitment to excellence" reads like a press release written by a committee, and it makes the increase feel arbitrary. Give one concrete reason and stop.
Reasons that work because they are specific:
- "We added unlimited team seats and an API. The old price did not cover the support load."
- "Hosting and AI costs tripled this year. The math stopped working at $12."
- "We have shipped 40 new features since launch and the price never moved. It is time."
Notice that none of these are apologies. You are not asking permission to run your business. You are explaining a decision you have already made. There is a confidence difference between "we hope you understand" and "here is the reasoning." Aim for the second.
A short, honest reason also protects you in the replies. When someone tries to dunk on you with "lol money grab," your own post already answered them, and your existing customers will often jump in to defend the price before you have to.
Protect your existing customers loudly
This is the single most important line in any price increase post, and it is the one founders forget. Tell current customers what happens to them, in plain words, near the top.
The strongest move is grandfathering: existing customers keep their current rate. If you can offer that, say it in bold terms because it turns a potential churn event into a loyalty moment. "If you are already paying, your price never changes. This only affects new signups after the 15th." That one sentence stops the panic cancellations cold.
If you cannot grandfather everyone, be just as direct about the change and give a runway. "Current customers move to the new price on your next renewal after June 1, so you have until then at the old rate." People can handle a higher bill. What they cannot handle is finding out by surprise on a credit card statement, because that is the version that ends up screenshotted and quote-tweeted.
When you draft the customer-facing line, read it back as if you are the customer who has paid you for two years. Does it feel like a thank-you or a shrug? Rewrite until it feels like the former.
Add the urgency, but make it honest
If part of your goal is driving signups before the change, urgency is fair game. Just make it real. A fake deadline you quietly extend trains your audience to ignore every future deadline you set.
Honest urgency looks like:
- A specific date, not "soon."
- A specific old price versus new price, so the savings are concrete.
- A single clear action: "Lock in $19 here before Friday."
You do not need ten exclamation points. The number and the date do the work. "$19 today, $29 on Friday" is more persuasive than "AMAZING deal, ending SOON, do not miss out." Restraint reads as confidence, and confidence is what makes a premium price believable.
One practical tip: pin the post and update the pinned version as the deadline approaches. A reply from you saying "48 hours left at the old price" keeps the post alive in the feed without you having to write something new.
Format it so it is actually readable
A price increase post is information-dense, and a wall of text kills it. Break the post into short lines with white space. On X, line breaks are formatting, and they make a post feel scannable and calm rather than ranty.
Before you publish, preview how the post will look in the timeline. The first two lines are what most people see before the "show more" cutoff, so the news and the customer-protection line should both be visible there if you can manage it. A free X post preview lets you see the real layout, line breaks, and truncation point before you commit, which beats publishing and then deleting because a line broke in an ugly spot.
Keep the whole thing tight. You are not writing a blog post. Three to six short lines is plenty for the main announcement, and you can drop extra detail in a reply if needed. Density plus white space is the formula.
Read the room before you hit send
The reception of a price increase post depends heavily on context, and ignoring that context is how a routine update becomes a pile-on. Two things to check.
First, your recent track record. If you just had an outage, shipped a buggy update, or went quiet for a month, a price hike on top of that reads as tone-deaf. Fix the trust problem first, or at least acknowledge it: "I know last month's downtime was rough. Here is what we fixed, and yes, pricing is also changing." Naming the elephant disarms it.
Second, the worst-case reply. Price posts attract critics, and a cluster of angry replies can produce the ratio, where the replies outnumber the likes and the post starts to look like a public referendum on your decision. You will not avoid every critic, and you should not try to. But you can pre-empt the loudest objection inside the post itself so the critics have less to grab onto. If you know people will say "this is too expensive now," answer it before they ask.
It also helps to watch the right metric afterward. Likes feel good but they do not tell you much here. Track engagement rate and, more importantly, signups and cancellations in the days after. The post is a means to a business outcome, not a popularity contest, and a post with modest likes that drives a wave of last-minute purchases did its job perfectly.
Common mistakes that sink these posts
Even founders who write well get tripped up by the same handful of errors. Watch for these:
- Apologizing for charging money. A hedged, sorry tone makes customers nervous and invites pushback. State the decision plainly.
- Hiding the actual numbers. "Pricing is changing" with no figures makes people assume the worst. Show old price and new price.
- Forgetting existing customers entirely. If your post only talks about new pricing and never mentions what happens to current subscribers, you have created panic for no reason.
- A vague deadline. "Prices going up soon" creates no urgency and no clarity. Use a date.
- Treating it as a one-off. People who follow you for your actual work do not want to feel like the only reason you post is to sell. If this is your only revenue-related post in months, it lands harder. Founders who regularly share revenue numbers and behind-the-scenes business updates can announce a price change as a natural next chapter, not an out-of-nowhere ask.
- Burying the news below the fold. If the price change is not in your first line, you are betting on people clicking "show more." Most will not.
The throughline is the same: clarity beats cushioning. Every time you soften the message, you make it murkier, and murky is what gets you dunked on.
Putting it together
A great price increase post is short, leads with the news, gives one honest reason, protects existing customers out loud, and sets a real deadline if you need urgency. Write it as someone who runs a business and made a call, not someone asking the internet for forgiveness. Preview the layout, watch your signups instead of your likes, and reply to your own post to keep the deadline alive.
If you want help drafting and scheduling posts like this without staring at a blank box, PostInstantly can generate, preview, and queue them for you, so the next time you raise prices the announcement is already written before you lose your nerve.