Size the workflow before choosing the plan.
Use your own branch counts and measured credits. Include retries and scheduled checks instead of guessing from enquiry volume alone.
Every branch counts.
Enter a value for every branch and overhead field. Use 0 for known zero usage; leave unknown values empty until you have evidence. The reserve is optional.
Add the work.
Show the buffer.
Monthly volume alone does not describe the execution paths. Enter the cost of each complete path from your run log.
For account context, open Org → My Plan → Credit usage. Make’s credit usage history documentation explains the view. Use controlled runs to identify the costs of your individual branches.
Keep retries separate from the first attempt. If a retry is already counted in a branch, do not add it again.
- Base credits
- Σ (branch count × credits per branch)
+ retries × credits per retry
+ scheduled checks × credits per check
+ maintenance - Planning reserve
- Base × reserve percentage ÷ 100
- Monthly estimate
- Base + reserve
Counts must be nonnegative whole numbers. Credits may be nonnegative decimals. Inputs and calculation results use up to six decimal places. A separate whole-credit ceiling is optional planning information, not a billing rule.
453 + 45.3 = 498.3.
100 new × 3, 50 existing × 2, 10 rejected × 1, 5 repeated × 1, 4 retries × 2, and 30 scheduled × 1. Maintenance: 0.
The base is 453 credits. A 10% reserve adds 45.3, making an estimate of 498.3 credits.
An estimate is one part of the decision.
Current plan limits are not hard-coded here. Missing plan evidence prevents a recommendation.
- Timing & limitsCheck scheduling, active scenarios, retention, and execution limits for your route.
- Connections & accessCheck required modules, permissions, and the seats your team needs.
- The whole toolchainInclude the form service, CRM features, and any required add-ons. Avoid counting an included feature twice.