What determines the cost of AI automation?
The useful starting point is the work you want completed: which records arrive, what the system can change and what an employee must receive. A chatbot that answers questions and a workflow that updates a CRM, requests missing information and assigns a task have different requirements. A software subscription alone cannot price either implementation.
This guide gives you a scope brief and usage worksheet to send to prospective implementation partners. It does not quote Monchera fees or claim a market-average project price. The worked example uses fictional planning assumptions; replace them with your own records before approving a budget. Provider billing documentation was checked on October 9, 2026.
Separate four parts of the budget
Ask every supplier to show these categories separately, even if its commercial proposal combines them into one fee. That makes it possible to compare what is included and identify who pays when volume or requirements change.
- Implementation: process discovery, access checks, field mapping, workflow construction, representative tests, documentation and employee handover. Ask whether data cleanup and migration are included.
- Provider and infrastructure costs: workflow software, AI usage, messaging, storage, hosting and any required CRM plan changes. Identify the billing account and usage unit for each.
- Ongoing management: monitoring, investigating failures, reviewing output quality, maintaining connections and making an agreed amount of changes. Request the support hours, response commitments and exclusions in writing.
- Retained employee work: approving consequential actions, resolving exceptions, checking ambiguous information and owning customer decisions. Include this time in the business budget even when it is absent from the supplier invoice.
Send a scope brief that describes a finished job
Use a narrow process for the first estimate. In this illustrative example, service requests arrive through a business website. The proposed workflow matches or creates the CRM inquiry, summarizes the request, prepares a missing-detail message and assigns a coordinator task. Prices, service availability and customer commitments remain with an employee.
A sample employee output would read: “SAMPLE-COST-01 — service inquiry received. Two locations supplied; preferred start date missing. Owner: account coordinator. Next action: review the prepared date request. Message: draft, not sent. Quote: awaiting employee assessment.” This describes the required output, not a completed deployment.
Copy the fields below into the brief. Attach anonymized examples of a complete request, an incomplete request and a customer reply, plus screenshots of the destination fields. A diagram without these details leaves important estimating decisions to each supplier.
- Start and finish: a new website inquiry starts the process; a correctly matched CRM record and owned coordinator task finish it.
- Systems and access: name the form, CRM and messaging service, the exact record types and required read/write permissions. Mark unconfirmed API access as an open dependency.
- Volume: monthly inquiries, busy-day arrivals, replies, reminders, documents and expected review cases. Identify which figures are measured and which are assumptions.
- Allowed actions: summarize, check required fields, prepare messages and update agreed fields. Specify who approves sending and which commitments are prohibited.
- Exceptions and ownership: duplicates, ambiguous record matches, unavailable connections and replies that arrive after a reminder is prepared. Name the employee responsible for each queue.
- Operating boundaries: working hours, access roles, record retention, alert destination, handover requirements and the process for approving a new workflow.
Convert activity into the provider’s billing units
Providers count different things. n8n’s pricing uses workflow executions, with an execution described as one workflow run. Make uses credits; its guide distinguishes operation-based consumption from AI features whose consumption also depends on tokens and other factors. One inquiry is therefore not automatically one billable unit across products.
For every trigger, ask what runs when an inquiry arrives, a reply arrives, a reminder becomes due or an action fails. Include scheduled checks and recovery work. Have the implementation partner translate that design into the chosen plan’s units rather than comparing an equal number of credits and executions.
Make also distinguishes custom AI-provider connections, where you pay the provider separately for tokens, from connection options with different credit logic. Confirm the actual connection type so the estimate does not omit a provider bill or count the same included usage twice.
Worked worksheet: size the volume before inserting rates
Suppose the proposed process receives 1,000 inquiries per month. For planning only, assume 200 require a first missing-detail reminder, 50 of those need a second reminder and 80 inquiries need employee exception review. These are invented workload inputs for arithmetic, not measured response rates, projected sales or promised savings.
Assume one text summary per inquiry, using 1,200 input tokens and 200 output tokens each. That gives 1.2 million input tokens and 200,000 output tokens. OpenAI’s pricing separates input and output rates; selected tools and storage can add charges. The simple text estimate below excludes those extras and does not assume a cache discount. Validate token use with representative requests and include instructions and retrieved context in the input count.
The 200 first reminders plus 50 second reminders produce 250 outbound messages. If each SMS uses two billable segments, the estimate contains 500 outbound segments. Two segments is an assumption to check against the actual message text. Twilio’s US pricing bills SMS by segment and lists additional carrier, number and applicable registration charges. Replies and other message types need their own rows.
If each of the 80 exception cases takes six minutes, budget eight employee hours. This is retained work, not eight hours saved. Additional approval time belongs in a separate row if all outgoing messages require review.
- Text-model estimate: 1.2 × selected input rate per million tokens + 0.2 × selected output rate per million tokens. Add other model calls, retries and selected tool charges separately.
- SMS estimate: 500 outbound segments × applicable segment rate, plus inbound usage, carrier charges, numbers and applicable registration fees. Record each rate’s source and date.
- Workflow software estimate: chosen plan and included allowance, plus expected overage calculated from the proposed triggers and steps. Keep hosting separate where applicable.
- Employee estimate: eight exception-review hours × the business’s internal hourly cost, plus message approval and other retained tasks.
- Monthly total: provider and infrastructure charges + agreed management fee + retained employee cost. Add applicable taxes and currency assumptions consistently.
Ask what the implementation fee actually delivers
Request a fixed deliverable for each setup milestone, or an estimated number of hours and agreed rate if the work is billed by time. A useful breakdown covers discovery, integration access, construction, acceptance tests and handover. Separate one-time provider charges from implementation labor.
Require a written dependency list. For this example, an unavailable CRM task API, inconsistent customer identifiers or permission to read only some records could change the design. Ask which uncertainties the discovery phase will resolve and how a change is approved before extra work begins.
Define acceptance around the employee’s output: a complete request creates the intended task; a missing date produces a specific draft; a duplicate does not create another inquiry; a reply stops the obsolete reminder; a denied CRM write stays visibly unresolved. Ask to inspect these cases in the destination system. A successful demo animation is separate from integration acceptance.
Define monthly management and spending limits
Have the agreement distinguish repairing the existing workflow from adding a new capability. For example, restoring a broken field mapping and introducing a second CRM may have different treatment. Ask who monitors failures, who receives alerts outside working hours and which changes require a separate estimate.
Request an expected-month estimate and a busy-month estimate using stated volumes. Specify a spending threshold, its alert recipient and who can approve more usage. Decide what should pause or enter an employee queue at the limit, so a cost control does not silently drop customer requests.
The handover should include account ownership, workflow configuration, field maps, recovery instructions and access removal. If the proposal includes self-hosting, ask who patches, backs up and restores the installation. Infrastructure responsibility remains work that someone must own.
Compare quotes against the same scope
Give each supplier the same scope brief and ask it to return the setup deliverables, provider assumptions, monthly management boundaries, retained employee work and open dependencies. Do not treat an excluded integration or a shorter support window as a like-for-like saving.
Before approving the project, replace the worksheet assumptions with observations from your own process. Compare the budget with current handling time, unresolved requests and employee capacity. Keep a proposed improvement separate from a result that has actually been measured.
For a Monchera scoping conversation, bring one recurring process, the systems it touches, representative records and the employee output you need. That gives us a concrete basis for discussing implementation and ongoing ownership.
