Changing prices without leaving contradictory versions behind

What a pricing policy has to define, how to communicate it, and what to check across site, proposals and scripts before it goes live.

FounderPublished
Changing prices without leaving contradictory versions behind

Changing prices is easy in the spreadsheet and expensive everywhere else: price lives on landing pages, proposals, emails, campaigns, presentations, and talking points. If you update the table but not those assets, marketing, sales, and support end up communicating different versions of the same price.

That's why a pricing policy isn't just deciding how much to charge, but coordinating how every sales asset gets updated and communicated when that price changes. When the change is planned in stages, the case is price skimming.

What a pricing policy should define

  • customer segments,
  • base price,
  • packages or plans,
  • allowed discounts,
  • commercial terms,
  • exceptions,
  • approval owners,
  • the value message.

Without these rules, every sale is negotiated from scratch.

How to communicate prices

Explain value before cost

The customer needs to understand what problem it solves, what's included, and what risk it reduces.

Use consistent materials

Presentations, pages, PDFs, proposals, and emails should all tell the same story. Polimake keeps sales material indexed as you upload it, so the approved version comes back from a description rather than from someone remembering the filename.

Control changes

If you change prices, update every touchpoint: website, proposals, campaigns, documents, and talking points.

Approval workflow

Any price change should go through:

  1. a commercial hypothesis,
  2. a margin analysis,
  3. a sales review,
  4. a marketing review,
  5. an asset update,
  6. internal communication,
  7. follow-up measurement.

Step five is the one that always jams: nobody knows how many pieces still show the old price. With the material indexed, asking for "the old rate on screen" returns the list in seconds, including the frame where it appears inside a video.

What to measure

  • conversion by plan,
  • margin,
  • discount rate,
  • frequent objections,
  • time to close,
  • churn or retention,
  • impact of promotions.

Checklist before publishing a change

Before announcing a new pricing policy, review:

  • the updated pricing page,
  • updated sales proposals,
  • the sales talking points,
  • internal FAQs,
  • emails and automations,
  • campaign pieces,
  • legal terms,
  • the effective date.

The most expensive mistake is usually marketing, sales, and support communicating different versions of the same price.

Frequently asked questions

Should a pricing policy be rigid?

No. It should be clear, but allow controlled, documented exceptions.

Who should approve discounts?

It depends on the business, but there should be a clear limit by role.

When should you review prices?

At least quarterly, or whenever costs, positioning, demand, or the competition change.

The old price is still inside a video somewhere

The expensive part of a price change isn't the table: it's the eight-month-old video with the old rate on screen that sales keeps sending. Upload your video and photography to Polimake, ask for the exact frame where the price appears, and let the AI layer — connected today over MCP to ChatGPT and Claude — produce the corrected version on top of your own archive. Start with whatever sales sends out every week: that's where the old price survives longest.