The right Make plan depends on how much work your scenarios perform, which features your team needs and how often your workflows run. Start with one real workflow, measure its consumption and use that evidence to forecast the next month.

Understand credits before comparing plans

Make measures usage in credits. The number consumed by a scenario depends on its modules, the actions performed and the features involved. Some features can have different consumption rules. Consult the current Make pricing page and credit documentation before committing to a plan.

A scenario that runs 100 times does not automatically consume 100 credits. If each run processes several items or invokes multiple modules, usage can be higher. Failed runs, retries and tests also belong in your estimate when they consume credits.

Workflow 1: New client onboarding

Example: a signed agreement triggers creation of a project, a welcome email and an internal task. List every step and include any search, filter, router or update in your measurement. Run the scenario with representative sample data and record the credit change. Repeat with missing data and a client that already exists.

Monthly estimate: onboarding events × measured average credits per event, plus a buffer for testing and exceptions. For five new clients at an illustrative average of 15 credits, the baseline is 75 credits. This is arithmetic for planning, not a measured Make result.

Workflow 2: Content approval reminders

A scheduled scenario checks a tracker and reminds clients when a review is due. The crucial variable is not just the number of reminders: frequent checks may process records even when there is nothing to send. Test your actual schedule and account for weekends, duplicate reminders and changes of status.

Reduce unnecessary work by querying only records that are due, when the source supports it. Keep an owner responsible for reviewing failed reminders.

Workflow 3: Monthly reporting

A scenario can collect reporting data, prepare a draft and notify an account manager. Measure separately for five and ten clients. One client with several channels can involve more work than one client with a single source. Never send a report automatically until someone has checked its dates, permissions and missing data.

Build a useful estimate

  1. Record average credits for each scenario using realistic test data.
  2. Multiply by expected runs or processed items per month, as appropriate.
  3. Add a documented allowance for tests, retries and growth.
  4. Compare the total with each plan's current limits and billing terms.
  5. Confirm which plan includes the features, users and support your team needs.

Review actual consumption after the first month. Prices and plan terms can change; verify billing frequency, overage or additional-credit terms on Make's official pages.

Read Make vs Zapier and the client onboarding automation guide.

Editorial notes — remove before publication

Documentation-based draft; no scenario has been tested. Record actual usage, plan prices, screenshots and verification date before publishing. Add an affiliate disclosure if applicable.