Monitor competitor prices by keeping a dated record of what changed and what the page actually says.

Define the price fields before you collect them.

A monthly number alone does not make two offers comparable.

Capture the plan name, currency, billing interval, included allowance, seat minimum, trial or discount condition, and the page where each term appears.

Strawberry can assemble those fields into a compact pricing ledger. Leave values blank when the page requires a quote or does not make the condition clear, rather than inventing an equivalent price.

Compare the page with its own previous version.

A price-monitoring system should identify what is new, removed, or materially revised since the prior run. That may be a changed amount, a renamed tier, a new cap, a different included feature, or an altered eligibility rule.

Ask for the old wording and current wording in the report. It gives the commercial team evidence to assess the change without relying on a summary that cannot be checked.

Keep promotions and regional prices out of the wrong conclusion.

A struck-through amount may be a launch promotion.

A currency selector may show geography-specific pricing. A lower entry price may exclude support, require annual payment, or apply only below a usage threshold.

Make those conditions first-class fields in the review. Strawberry can flag a price as conditional or non-comparable so a weekly dashboard does not convert caveats into a false headline.

Send a small exception report to the people who own pricing.

The useful weekly output is not a spreadsheet replaying every unchanged tier.

It is a short list of confirmed changes, unavailable sources, and unclear items with the evidence needed to resolve them.

When the watchlist and report format are accepted, save the method as a skill and run it as a routine. The routine prepares the observation; pricing, product, and sales leaders decide the response.

Frequently asked questions