Make pricing: choose a free or paid plan around your workload

Use the free plan to establish the job

The free plan includes 1,000 monthly credits. Use a small sample to establish the result before upgrading. Also inspect the schedule, scenario and storage limits that matter to your job. A low-volume workflow can still require a feature outside its current plan; conversely, a working trial is not a reason to buy a larger allowance without a workload estimate.

Choose features and ownership before the tier

Separate a single-owner process from a team-operated service. List required controls for access, ownership, execution and investigation, and match them to the current plan matrix. A higher tier does not repair duplicate writes or an incorrect recipient. Describe the functional gap that justifies the upgrade so a later reviewer can tell whether the paid feature is still necessary.

Separate monthly billing from annual-equivalent prices

A per-month figure may be the equivalent of an annual commitment. If your quote shows USD 9 per month billed annually, the base commitment is 9 × 12 = USD 108. That is an arithmetic example, not a universal current quote. Record currency, allowance, payment frequency and tax treatment from the purchase screen before comparing alternatives.

Translate expected work into an allowance

Estimate how many records reach each paid operation at 100, 1,000 or 10,000 monthly requests. Then add trigger checks, trials and recovery separately. A request with several items may create more downstream work than a single row suggests. Treat a general calculator as a planning aid and reconcile it against the actual execution history of the selected workflow.

Budget for exhaustion and external services

Decide whether the workflow may pause when its allowance is exhausted or needs additional capacity. If you enable automatic extra purchases, include a review process for spending. Keep independently billed AI, email or other applications in separate budget lines. The automation subscription is only one part of the operating cost.

Example: a purchase worksheet

Create columns for normal requests, busy-month requests, trigger checks, downstream operations, selected allowance, base cost, extras and external services. Leave an unverified price unresolved rather than entering zero. If an introductory benefit applies, make the adoption decision against the ongoing cost after it ends.

The approval note should say when the plan will be reviewed and what workload would justify more capacity. A quote saved only at purchase does not prevent an exhausted allowance in a busy month or an unused renewal later. Assign the review date while the reason for buying is still clear.

Make the purchase decision inspectable

Assign an operator as well as a budget owner. Before an annual commitment, consider what happens if the workflow changes or is retired. Preserve the quote and the reason for selecting its allowance. Any referral promotion should be checked in the actual signup flow; do not assume an offer remains available to every reader.

• Confirm allowance, billing period, currency and taxes.
• Check capacity changes, renewal and cancellation conditions.
• Save both normal-month and busy-month estimates.

• How to estimate Make credits: polling, rows and retries
• Get started with Make: registration to a first spreadsheet notification