Separate setup from ongoing operation
An AI automation quote should explain what is built once and what is paid for while the workflow runs. Setup can include discovery, conversation design, knowledge preparation, channel configuration, integrations and testing. Ongoing operation can include platform usage, maintenance and the support arrangement.
SwitchToAuto quotes a defined scope in USD. There is no single published price that covers every business workflow. A simple assistant using approved FAQs requires different work from one that verifies a customer, checks a live system and completes an action.
Integration depth changes the work
Reading information is different from changing it. Showing business hours from approved content is relatively contained. Confirming an appointment may require calendar availability, appointment types, conflict handling and a clear response if the calendar cannot be reached.
List the tools involved and the actions each connection needs to support. Confirm whether the platforms allow those actions and what permissions are required. Include unusual conditions, such as duplicate enquiries, incomplete contact information and requests that need a person’s decision.
Make usage assumptions explicit
Phone minutes, conversation volume, messaging charges and platform subscriptions can affect ongoing cost. An included allowance and an overage rule are useful only if you understand what they count. Ask how a transferred call, repeat conversation or failed connection is treated.
Estimate a normal month and a busier month from your own records. Use a range when the volume is uncertain. Confirm which charges are included in the proposal, which are billed directly by a platform and who monitors usage. Avoid comparing packages by a single monthly number.
Budget for keeping information current
Hours, prices, services and policies change. Agree who submits updates, who checks them and how quickly the change can be applied under the support arrangement. A workflow also needs a route for reporting incorrect answers or failed handoffs.
Distinguish maintenance from new scope. Adding another channel, changing a booking process or connecting a new system can be a separate project. Ask for these boundaries in the quote so that a routine update is not confused with a new integration.
Estimate value without counting it twice
Start with an operational measure: enquiries recovered, appointments requested, repeat questions resolved or staff time saved. For a revenue scenario, use your own enquiry volume, plausible conversion and average sale value. Revenue is not profit, and a recovered enquiry is not automatically a new sale.
Keep staff time value separate from projected sales. If the same improvement is counted in both, explain the overlap. Subtract ongoing costs and account for setup over an appropriate period when comparing an investment. Our automation value calculator makes its assumptions visible so you can adjust them.
Prepare a brief that produces a useful quote
Describe one starting workflow, the channel, connected tools, approximate volume, opening hours and the next action you want completed. Include the circumstances that should reach a person and any data restrictions the project must observe.
Compare proposals against that same brief. Ask for deliverables, acceptance checks, responsibilities, payment terms and what happens after launch. See our pricing and scope page, delivery process and project enquiry form to prepare the next step.
Plan your first workflow
Share the customer question, the channel and the next action you need. We will use that information to scope the work and its test plan.
Discuss your project →