Back to blog

How to announce a price change on X without losing customers

By Naod Tadele · · 5 min read

Loudcode guideAnnounce aprice change

Most indie founders raise prices too late and announce it too quietly. They worry the post will start a pile of angry replies, so they slip the change into a footer and hope nobody notices.

People do notice. And a price change found by surprise feels worse than one you explained up front. Handled well, a pricing post can even bring in signups, because it reminds people the product is real, growing and worth paying for.

This guide covers how to plan the announcement, what the post should say, and a few example posts you can adapt.

Decide the facts before you write anything

A pricing post goes wrong when the plan is still fuzzy. Before you draft a word, write down plain answers to these:

  • What exactly changes? New price, new plan names, new limits, or a feature moving between plans.
  • Who is affected? New customers only, existing customers, or both.
  • When does it take effect? A specific date, not "soon".
  • What happens to current customers? Kept on their old price, given a notice period, or moved with a discount.
  • Why now? One honest reason. More features, higher costs, or a price that was simply too low.

If you can't answer one of these, you're not ready to post. Fix the plan first.

Tell existing customers first

Your paying customers should never learn about a price change from a public post. Email them before you post on X, with the same facts and a clear date. If they're keeping their current price, say so in the first line of the email.

Then post publicly. That order matters because some of your customers follow you. When they see the post, it should confirm what they already know, not surprise them.

What a good pricing post says

Keep it short. A good pricing post answers the reader's questions in the order they ask them:

  1. What changed.
  2. Does it affect me.
  3. When.
  4. Why.
  5. What do I get for it.

Don't start with a long story about your journey. Don't apologize for charging money. And don't hide the new number. Vague pricing posts make people assume the worst.

Example posts

These are for Nightshift, a fictional tool that writes incident summaries for on-call engineers.

Price increase with existing customers kept on their old price:

Example post
Nightshift pricing changes on December 1. New customers: Team plan goes from $19 to $29 a month. Existing customers: nothing changes. You keep $19 for as long as you stay subscribed. Why: since launch we added Slack summaries, timeline export and on-call handoff notes. The old price was set when Nightshift did one thing.

New plan structure:

Example post
We're splitting Nightshift into two plans. Starter, $12/mo: summaries for one team. Team, $29/mo: multiple teams, Slack, timeline export. Everyone on the current plan moves to Team at their current price. No action needed.

A free tier getting smaller:

Example post
Nightshift Free now includes 20 summaries a month instead of unlimited. Honest reason: free usage was most of our model costs, and we want Free to stay around for good. The limit covers a typical small team's month. Starts January 1. Paid plans are unchanged.

The follow up a few weeks later:

Example post
A few weeks after the Nightshift price change: Signups didn't drop. Two customers asked about it. Both stayed. We used the extra revenue to cover a second on-call region. I waited a year longer than I should have to do this.

The follow up is often the most useful post of the set. Other founders want to know what actually happened, and it closes the loop for your own customers.

How to handle the replies

Some replies will push back. That's normal and usually fine.

  • Answer real questions plainly. "Does this affect annual plans?" deserves a direct yes or no.
  • Don't argue about value. If someone thinks it's too expensive, thank them and move on. You set the price for the people who get value from it.
  • Fix confusion fast. If several people ask the same thing, the post was unclear. Reply with the answer and add it to your pricing page.
  • Don't delete critical replies. It looks worse than the criticism.

Mistakes to avoid

  • Changing the price with no date. People need time to decide.
  • Raising prices on existing customers with no notice. Even when it's fair, it feels like a trick.
  • Blaming costs vaguely. "Rising costs" sounds like an excuse. Name the cost if you can.
  • Burying it in a changelog. A pricing change deserves its own post.
  • Over apologizing. It tells people you don't believe the product is worth it.

How Loudcode helps

Loudcode reads your GitHub activity and your revenue from Stripe, Polar or RevenueCat, so when you change pricing it has the context to draft the announcement and the follow up a few weeks later in your voice. Every draft waits for your review, so you decide exactly how the numbers are framed before anything posts to X. For more on talking about money in public, see how to share your MRR publicly.

You ship the code. We write the posts.

Your commits, revenue, traffic and a 30-second weekly check-in become build-in-public posts for X, in your voice. You approve every post.

Keep reading

All posts