AI Automation Pricing Guide for Small-Business Pilots

This guide is for a beginner pricing a small, practical automation service for an Australian small business. The example buyer is an owner-operated trade business with incomplete quote enquiries arriving through one inbox. The example offer sorts those messages, identifies missing job details, prepares draft replies for owner approval, and produces a daily summary.

It is not a price list for enterprise systems, autonomous voice agents, medical decisions, financial advice, staff monitoring, or a replacement for a managed IT provider. Those projects have different risk, procurement, security, integration, and support requirements. A first quote should cover a workflow you can explain on one page and reverse without drama.

The goal is not to find the biggest number somebody on social media says they charged. The goal is to write a price that covers the real work, gives the buyer a clear decision, and leaves enough room to deliver carefully. Results depend on scope, capability, market testing, and execution.

Start with a paid workflow audit. A useful audit might include a 45-minute interview, a map of one to three enquiry channels, a list of message types, missing-field analysis, five draft templates, an escalation table, and a pilot recommendation. A practical planning range is AUD $150-$350 when the workflow is narrow and no live integration is included.

The second product is a fixed pilot. A planning range of AUD $500-$1,500 can fit a two-week, draft-only pilot for one channel and one workflow. Define the inputs, up to eight templates, test cases, owner approval, daily summary, handoff, one revision round, rollback, and a short support window. A pilot with live customer data or several systems may need a higher quote or a more experienced provider.

The third product is optional ongoing support. AUD $150-$500 per month can be a starting range for a monthly workflow check, template upkeep, one small improvement, and a defined support allowance. Software usage, new integrations, extra channels, urgent work, and major changes should sit outside that allowance. Do not invent a retainer before the client has a working pilot to maintain.

Your cost floor is the minimum sensible price before profit. List every delivery stage: discovery, process mapping, tool setup, configuration, prompt or rule writing, fictional test data, testing, corrections, documentation, training, meetings, project admin, deployment, rollback preparation, and included support. Beginners often count build time and quietly donate everything around it.

Choose an internal hourly cost that reflects what the business needs to cover. This is not necessarily the rate shown to the client. Multiply it by realistic hours, then add direct software and testing costs, payment fees, business overhead, and a rework or risk allowance. Add profit after the full cost is visible. If the quote only works when nothing goes wrong, it does not work.

Business.gov.au advises businesses to consider costs, market research, customer value, and a profit margin rather than copying a competitor price. Use competitor pages to understand packaging, not as proof that your first project deserves the same fee. Your scope, proof, controls, and support must justify your number.

The first multiplier is channels. One website form feeding one inbox is simpler than email, SMS, social DMs, calls, and a customer relationship system. The second is integrations. A workflow that prepares drafts inside one approved tool is simpler than writing to calendars, accounting platforms, job systems, databases, and several APIs.

The third multiplier is data. Names, phone numbers, addresses, email contents, complaints, photos, and job notes can be personal information. Due diligence, permissions, access controls, retention, deletion, and client approval take time. The fourth is authority. Draft-only classification is lower risk than automatically sending, booking, quoting, refunding, cancelling, or making a decision about a person.

The remaining multipliers are volume, reliability, and support. Hundreds of varied messages need more test coverage than 20 predictable enquiries. A workflow used during emergencies needs a different standard from a daily admin summary. Evening response promises, monitoring, incident handling, rapid fixes, and staff training are real deliverables. Price them or exclude them.

Assume a plumber wants one website enquiry inbox organised. The pilot will label messages, identify six missing fields, prepare replies for owner approval, flag sensitive messages for manual review, and create one end-of-day summary. It will not send automatically, quote jobs, diagnose faults, promise arrival times, handle emergencies, or connect to the job-management system.

Your estimate is two hours for discovery and mapping, six for configuration, four for testing, two for documentation and handoff, and two for project admin and included support. At an internal cost of AUD $60 per hour, labour is $960. Add $80 for direct tool and test costs and a 15 percent risk allowance of $156. The internal floor is $1,196, so a fixed quote might be rounded to AUD $1,200 before any applicable GST treatment.

That example is a quote-building demonstration, not a required rate or market claim. A beginner using a simpler manual workflow may need fewer hours. A provider with reusable systems may deliver faster but charge more because the buyer is paying for a tested process. If discovery reveals live integrations, sensitive data, high volume, or automatic action, stop and re-scope before accepting the original price.

The setup fee pays for the defined project work. Software is the cost of tools, accounts, usage, storage, messaging, and other services required to run it. Support covers the human work after handoff. Put each line in the quote so a cheap-looking setup price does not hide an expensive monthly stack.

Where practical, let the client own the production accounts and pay providers directly. Use official roles or delegated access instead of asking for shared passwords or multi-factor authentication codes. State which usage estimate the quote assumes and what happens if volume exceeds it. Tool prices and terms change, so include a review point instead of promising a permanent software cost.

Do not add an unexplained markup to every token or task. If you manage usage on the client's behalf, explain the allowance, monitoring, margin, overage treatment, and cancellation process. The client should be able to understand what continues after the project and how to remove your access.

Three options can help when each is genuinely useful. An Audit option might map the workflow and produce templates. A Pilot option might add configuration, testing, documentation, and handoff. A Managed option might add a defined monthly review and support allowance after the pilot succeeds. Do not create a crippled cheap tier that cannot solve the stated problem.

Keep the middle option aligned to the smallest responsible outcome. For this example, that is one channel, one workflow, draft-only outputs, up to eight templates, fictional test messages, one owner approver, one revision round, and two weeks of observation. Extra channels and integrations are later decisions, not surprise line items halfway through delivery.

A discount is not a substitute for tighter scope. If the buyer has AUD $600 and the responsible pilot costs $1,200, offer the audit or a manual concierge version first. Reduce deliverables, authority, integrations, or support. Do not cut testing, security, documentation, or the agreed result to make the headline price fit.

A good written quote names the buyer's goal, service description, deliverables, client inputs, price, payment stages, dates, assumptions, revisions, support window, exclusions, software, data boundary, approval owner, rollback, variation process, and quote expiry. Business.gov.au also recommends clear itemised and total costs, payment terms, start and finish dates, and customer acceptance details.

For the inbox example, an exclusion list might cover automatic sending, emergency handling, quotes, refunds, complaints, licensed advice, new channels, historical inbox cleanup, custom software, third-party outages, ongoing monitoring, and changes to the client's source systems. Exclusions are not fine print. Put them near the deliverables and discuss them before acceptance.

Use a deposit or staged payment that matches the work and your local requirements. One example is 50 percent on acceptance and 50 percent after the agreed handoff, with software paid directly by the client. Do not copy payment or contract wording blindly. Check current Australian requirements and get qualified advice for your actual business.

The OAIC recommends due diligence, privacy safeguards, and human oversight when organisations use commercial AI products with personal information. For a quote, that can mean reviewing data flows and provider settings, limiting inputs, agreeing retention, testing outputs, recording approvals, and documenting who can access the system. Those steps belong in the estimate.

Use fictional or redacted messages for early testing. When live information is necessary, agree on the smallest data set, storage location, access, retention, deletion, incident contact, and offboarding. Keep sensitive or high-impact messages under human control. If you cannot explain where the data goes, do not connect the inbox and hope for the best.

Security work also includes multi-factor authentication, official user roles, least-privilege access, secure credential handling, and revoking access after delivery. A low quote that depends on the owner sharing a main password is not efficient. It is unfinished scope with risk pushed onto the buyer.

After each quote, record the estimated hours, accepted price, objection, delivery time, tool cost, revision time, support demand, and actual margin. Separate a price objection from a trust, timing, scope, or priority objection. Dropping the price will not fix a buyer who does not understand the workflow or does not want to change it.

Review the first three paid jobs before standardising a package. If every delivery needs six unquoted hours, the scope or estimate is wrong. If buyers repeatedly request the same excluded item, it may deserve an add-on. If one trade needs heavy integration and another can start manually, they should not share a single price card.

The useful number is not the highest fee you can post online. It is the price at which the right buyer understands the result, you can deliver the promised controls, and the job remains worth doing. Start with one buyer, one offer, one written quote, and one measured pilot.

The AI Inbox Triage for Trades launch pack gives you the workflow map, reply templates, AI prompts, intake form, client emails, FAQs, and delivery files for this exact buyer lane. Use them to identify the real stages and client inputs before estimating hours. Reusable files can reduce forgotten work, but they do not remove the need to customise and test.

Open the pack, choose one trade, and mark every file or step that the client project needs. Turn that list into the audit deliverables, pilot scope, exclusions, acceptance checks, and handoff. The article gives you the pricing logic. The pack gives you the working files to make the quote and delivery specific.

If you want the practical version, browse the launch packs and pick one buyer to quote this week. Do not sell a vague AI transformation. Sell one controlled workflow, show what the price includes, and make the first decision easy to understand.