Some Harvest customers face renewal price increases of up to 1,500% following a pricing change at the time-tracking and invoicing platform, according to Subscription Insider.

The figure — a fifteen-fold jump on existing contracts — is the sharpest concrete data point in the report and lands squarely in the territory where B2B SaaS pricing teams most often lose accounts. A 1,500% increase is not an upsell; from the buyer's seat it reads as a repriced product, and it invites the procurement conversations that precede churn.

What does a 1,500% renewal jump actually mean?

For product managers, the mechanics matter more than the headline. Renewal increases of this magnitude almost always signal one of three structural changes rather than a simple list-price edit:

• A shift in the pricing metric — for example, moving from per-user to usage-based or seat-tiered billing, which re-prices legacy configurations overnight.
• The retirement of a legacy plan that existing customers occupied, forcing migration onto current SKUs at current rates.
• A discount removal or true-up on contracts that had been grandfathered for years at early-adopter rates.

Subscription Insider's report names Harvest as the vendor but does not specify which of these levers drove the increases, so buyers should verify their own renewal quotes directly before budgeting.

When do repricing moves like this work — and when do they break?

Repricing legacy bases works under fairly narrow conditions. It succeeds when:

• The vendor has clear usage data showing the affected customers receive outsized value relative to what they pay.
• Migration paths are short, well-documented, and priced to soften the cliff.
• Sales has advance warning and a script for the conversation, months before the renewal date.

It fails when the increase arrives as a surprise on the invoice. The failure modes are predictable: procurement escalation, a spike in competitive evaluations, and public complaints that compress the vendor's pricing power for every future negotiation. Time-tracking is a particularly exposed category — Harvest competes with low-cost and bundled alternatives, and switching costs for a team logging hours are modest compared with, say, a CRM migration.

What should product and pricing teams take from this?

If you run a subscription product, treat this story as a stress test for your own grandfathering policy:

• Audit how many customers sit on retired plans and what their effective renewal delta would be under current pricing.
• Cap single-renewal increases at a threshold your sales team can defend without escalation — 1,500% is not defensible.
• Give affected accounts a transition window with interim pricing, and instrument win/loss on those renewals separately.

For Harvest customers, the practical step is to model the renewal quote against the migration cost to a competitor before the renewal window closes.

As SaaS vendors push toward usage-based and value-aligned pricing to defend margins, legacy-base repricing will keep generating stories like this one — and the teams that sequence increases, communicate early, and price the transition will keep the accounts that less careful vendors lose.