A platform announces a price change. Before moving client projects or rewriting your packages, establish which accounts are affected, when the cost changes, and who absorbs it. The dependency could be a website platform, a video review tool, or podcast hosting.

Read the terms behind the headline

Start with the provider’s official announcement and the applicable account terms. Record the affected plan, billing currency, billing period, effective date, renewal treatment, usage limits, and any exceptions for existing customers. Confirm unclear details with the provider.

A change for new subscriptions may not affect an existing annual plan immediately. A higher usage allowance may matter more than a headline subscription price. Keep confirmed details separate from assumptions.

Map the change to actual client work

Create one row per affected account or shared tool. Capture these fields before making a portfolio-wide decision:

  • Client, service, platform, and current plan.
  • Account owner and who pays the provider.
  • Current cost, proposed cost, and the relevant usage level.
  • Renewal or effective date, including any notice deadline.
  • Whether your fee bundles the cost or bills it separately.
  • Work dependent on the tool and the effort needed to replace it.

Distinguish client-paid subscriptions from costs your studio absorbs. Shared team tools need an allocation across services if you want to understand which offers bear the increase.

Calculate the effect before choosing a response

Use the same billing period for the old and new figures. The added direct cost is the new applicable cost minus the current cost. Add any extra operational work separately; do not assume the subscription difference is the entire impact.

Compare options over a realistic period

Absorb: Assess whether the remaining contribution supports delivery and overhead. Adjust: Review the package, client commitments, and communication timing. Replace: Include migration, quality assurance, retraining, support, and disruption in the comparison.

In the example, an alternative that saves $120 a month but costs $2,400 to migrate takes 20 months to recover that one-time cost, assuming no other differences. A lower platform bill alone does not establish a better outcome.

Set an owner and a decision date

Work backward from the first affected renewal. Assign responsibility for confirming account details, reviewing client arrangements, and testing any alternative. If the impact is small, recording the change and keeping the current setup can be a considered decision.

Where Basetack fits

The subscription connects provider announcements to the platforms and services in your studio profile. A useful alert identifies possible exposure, what needs account-level confirmation, and when a decision matters.

You supply the private billing and client context needed to assess the actual effect. Basetack keeps watching the dependency; you carry out any migration.

Basetack

What does this mean for your studio?

A weekly brief on your question, read by Micah before it goes out. Start by email; no call needed.

Talk about a platform your studio relies onSee how we help →