Make: what we check before we recommend it

Make is an automation tool built around visual scenarios: a trigger, a set of modules, and a mapping between them. The useful question for a small team is not whether the editor looks good, but how many operations a week of real traffic costs.

This is the checklist we run before we publish a link. The terms below are the ones we could confirm from the vendor’s own pages on 2026-11-05.

Where Make fits

Make fits when the work is a chain: a form submission that creates a record, enriches it, posts a message, and writes a row. It fits less well when the work is a single conditional sentence, because a scheduled scenario that runs every minute burns operations while doing nothing.

Our rule of thumb: if the scenario has fewer than three steps and runs more than a few hundred times a day, it probably belongs in code.

The limit that actually binds

Every plan is measured in operations, and operations are consumed by module executions, not by scenarios. Two things follow:

• Polling triggers spend operations even when nothing changed. A 15-minute poll is 96 checks a day per scenario.
• Error paths that retry quietly double the count for the failed runs.

Before choosing a plan, we log one week of the real scenario with a free account, then multiply. The vendor’s page has the current per-plan operation counts, and we do not repeat them here because they change.

What we verify about the program

• Commission and window. The program pays a share of the referred subscription for the first 12 months, counted from the referral date.
• Excluded revenue. Extra operation purchases are outside the commission.
• Payout. Payouts go through Wise only, and require a minimum balance plus a number of paying users. That is a second account to open and a reason to wait before linking. The current terms are on the program help page.
• Cookie window. We could not confirm it from the vendor’s documentation, so this review does not claim one.

Those terms matter to the reader only in one way: they tell you the vendor expects a long evaluation, not a coupon rush.

What we will write next

The scored review will document one real scenario end to end: what we built, how many operations a week it used, what broke on retry, and what the invoice showed. Until then, treat this as the checklist, not the verdict.

Corrections are welcome and get priority. If a limit on this page is out of date, tell us and we will re-check it against the vendor’s documentation.