What enquiry automation costs to operate

Price the workflow, including the work around it.

A subscription price is only one line in an automation budget. Start with a specific task, the number of times it runs and who checks the outcome. Separate what you already pay from what this change adds.

Keep six lines in the budget.

Implementation

Mapping, building, testing and handover. Record hours and an agreed rate or a fixed scope; keep this one-off cost separate.

Platform subscription

Your existing CRM or automation plan. Count only the upgrade or new subscription when calculating incremental cost, while still recording the full bill.

Executions and usage

Credits, tasks or other billable units. Include tests, repeat runs, polling and exception paths where the provider charges for them.

AI usage, if chosen

The selected provider and model, input/output volume and any platform credits. A rules-only workflow may not need this line at all.

Hosting and storage

Any new runtime, database, logs or backups. Do not assume another product's free tier covers the whole system.

Support and maintenance

An owner for failures, access changes, provider changes and regular checks. Time has a cost even when no new invoice arrives.

Write the currency, billing period, tax treatment and source date beside every price. An annual bill divided by twelve is a monthly budget equivalent; it does not mean the provider collects that amount each month. Do not combine currencies without a stated conversion.

What the current public plans say

These are selected planning facts, not a recommendation to subscribe. Recheck current prices, billing terms, region, seats, integrations and account eligibility before making a choice. No Make or Zapier paid price is used in the calculations below.

Work out the units before the money.

Imagine a service office with 100 enquiries per month. For planning, assume each enquiry causes three billable operations at one credit each, plus 20 credits for testing during the month. This is an accounting example, not a tested three-module integration. It assumes no additional polling, branches, repeat runs or AI usage unless they are added explicitly.

Make's credit documentation describes one credit per operation as the default fixed rate, with exceptions and dynamic usage for some features. Inspect the exact modules and a test run before using that rate for a real budget.

With no runs, tests or other billable activity, this variable-usage model is zero. A fixed subscription can still be payable. If a connector's rate or an exception path is unknown, mark the estimate incomplete; do not extrapolate from the happy path alone.

Compare the same job three ways.

1. 1

   Use a native feature

   If your current plan already includes the required feature and you stay within its limits, the additional subscription line could be zero. Your existing bill, configuration effort and review time still exist. An upgrade needs its own account-specific price.

2. 2

   Use a rules-based connection

   Estimate the actual steps and exception paths. In the fictional 320-credit example, the Make Free subscription line is zero only if the whole proposed setup fits the free plan. Implementation, other software, hosting if needed and maintenance remain separate or unknown.

3. 3

   Add an AI-assisted step

   Specify what the model is for and which records it sees. Add its billable units and the review effort. Do not add AI merely to apply a date or status rule that a template already handles.

For AI, Make documents that a custom provider connection can incur platform operation credits plus the provider's token charges. Its own AI provider can use credits based on tokens and operations. A free chat interface does not establish free integrated usage. Read the chosen service's terms and current billing model; no AI provider price is assumed here.

For a provider priced per million tokens: monthly model cost = (input tokens ÷ 1,000,000 × input rate) + (output tokens ÷ 1,000,000 × output rate) + other applicable charges. Unknown model or rate means unknown cost, not zero.

Put the unknowns in the estimate.

Start a monthly budget with the known subscriptions and usage. Add agreed support, maintenance, hosting and other incremental charges. Keep implementation as a separate one-off amount. If any required item is unpriced, call the result a known subtotal and list what is missing.

Editable Markdown · version 1.0 · includes the formulas and fictional example. Keep your completed copy locally; nothing is submitted.

Free planning tools do not make production free.

The Fireflax browser samples use local rules and prepared templates; running them does not call a paid model. The browser calculators also use local arithmetic. Our zero-incremental-cash marketing work uses existing infrastructure. Neither statement is a price for a customer's connected workflow.

Fireflax's website plan is separate from automation. A live automation needs a defined scope, implementation price, software budget and support arrangement. Bring one workflow and the unknowns in this worksheet to the discussion; no universal implementation fee or ongoing-cost guarantee is implied.