The useful starting point
There is no single meaningful price for “AI implementation”. Configuring an existing feature, connecting two business tools and building a custom operating system are different jobs. Ask for a scoped setup price, an ongoing cost breakdown and a way to check whether the workflow actually improves.
First, work out which job you’re buying
If you run a plumbing company and quotes go unanswered, the requirement might be as simple as setting up reminders in your job software. If enquiries arrive in several places and someone manually works out which quote, customer and next action belong together, the job may involve an integration. Those should not receive the same proposal.
Separate the work into three possible starting points. These are scoping categories, not fixed AppliedAgents packages or market price bands.
| Starting point | What you’re buying | What to check |
|---|---|---|
| Configure what you have | Settings, templates and training inside an existing product. | Does the feature cover the actual process, including when to stop or hand work back? |
| Connect one workflow | A defined trigger, supported connections, checks and a clear destination. | Can the systems exchange the required information reliably? Who handles exceptions? |
| Build a custom system | New software or a broader process spanning several tools, roles and permissions. | What is the smallest useful first release? Who owns, maintains and supports it? |
AI is one possible component. A fixed rule can move an approved record between systems; AI may help interpret an unstructured enquiry or prepare a draft. Ask what decision needs AI and what happens when its output is uncertain.
Separate setup, running costs and your team’s time
A cheap build can become expensive if it needs constant checking. A larger initial quote may include testing, handover and support that another supplier has left out. Compare the same boundaries.
- Discovery and process design: understanding the current steps, choosing a baseline and agreeing what “done” means.
- Implementation: configuration, connections, data preparation, permissions and any custom interface.
- Testing and launch: realistic examples, duplicate or missing records, failed connections, approval rules and a controlled rollout.
- Ongoing services: software subscriptions, usage charges, hosting, monitoring, support and future changes. Ask which are included and which are billed separately.
- Internal time: giving access, explaining exceptions, reviewing outputs and teaching the team the new process.
For an Australian quote, ask whether amounts are in AUD, whether GST is included, and whether any underlying subscriptions are charged in another currency. Request a normal-usage estimate and a higher-usage example based on your own enquiry or job volume.
A worked budget example
Suppose a business is considering automating part of a six-hour weekly admin task. The figures below are deliberately hypothetical: they are not our prices, market averages or a client result.
| Assumption | Illustrative value |
|---|---|
| One-off setup | A$3,000 |
| Ongoing system cost | A$150 per month |
| Current task time | 6 hours per week |
| Time actually released after checking | 50%, or 3 hours per week |
| Value assigned to that time | A$45 per hour |
| Monthly capacity value | 3 × 4.33 weeks × A$45 = about A$585 |
| Capacity value less running costs | About A$435 per month |
| Setup divided by that monthly value | About 6.9 months |
That last number is a capacity-value comparison, not a cash-payback promise. A salaried employee finishing the task sooner does not automatically reduce payroll. The value depends on what the business can do with the released time. The simple model also leaves out internal launch time and any later changes.
Stress-test it. If only one hour is released each week, the same calculation gives about A$195 of monthly capacity value. After A$150 of running costs, roughly A$45 remains: the setup comparison stretches to about 67 months. That is a very different decision.
Use a week of real observations to replace the assumptions. Count the time spent checking and correcting the new workflow, not just the steps it removes. Keep possible extra sales separate until you have evidence of an incremental contribution.
Ask every provider the same seven questions
- What exact process is included? Name the trigger, systems, users, output and work that remains manual.
- What can our existing software already do? Ask for the native option alongside any proposed custom work.
- What access or plan changes are required? Confirm permissions and integration feasibility before treating them as included.
- How will we accept the work? Agree representative examples and failure cases the system must handle before launch.
- Who sees mistakes? Establish an owner, a clear alert and a way to pause the workflow.
- What will we own and be able to export? Clarify accounts, documentation, source code where relevant, and the exit or handover process.
- What changes the bill? Identify usage allowances, exclusions, support boundaries and how new requests are quoted.
Choose a pilot you can judge
Start with a repetitive task that has a clear input and a clear end. “Get AI into the business” is too broad. “Prepare an enquiry record from the website form and send it to the office for review” is something you can scope and observe.
Before a pilot, record the current weekly volume, handling time, common mistakes and who owns the next step. During it, count completed handovers, exceptions and review time. Use those observations to decide whether to adjust, expand or stop.
For a trade business using ServiceM8, our guide to native and custom quote follow-up is a concrete place to start. For a wider process, see how we approach workflow automation and integrations.
How AppliedAgents approaches a quote
We start by understanding where work stalls, which tools you use and what you want to improve. We check the existing-tool option before recommending a connection or custom build. Scope, testing, handover and support should be clear in the proposal.
We do not publish a universal implementation price because a single follow-up workflow and a custom business system involve different work. Bring the task, approximate weekly volume and a list of your tools to a free strategy call. Those details make a useful discussion possible without having to arrive with a technical specification.
This is an AppliedAgents planning framework. All example costs and time values are invented for the calculation and should be replaced with your own evidence before committing to a project.