A single enquiry-routing workflow may need only a few steps and one supported integration. A custom AI agent that reads company records, calls several APIs and manages approval rules requires more planning, testing and operational support. Both may be marketed as AI automation, but they represent different engineering commitments.
Start with the process rather than a package name
Before comparing quotes, document the current process. What initiates it? Which records must be checked? Who takes responsibility when information is missing? What can run automatically, and what requires approval? How often does the process occur, and what happens when a connected application is unavailable?
These questions determine whether the project needs a simple sequence of rules, a classification model, a retrieval system, bespoke software or some combination of the four. They also reveal costs that a short promotional price cannot communicate. For prioritisation help, see How to Identify Processes Worth Automating.
The main components of a project budget
Discovery and requirements. The first cost is understanding the problem. For a clearly defined workflow, this may be brief. For several departments or complex systems, an assessment is needed to map requirements, dependencies, permissions and realistic implementation stages.
Development and integration. Building the workflow includes connections to the relevant applications, data mapping, exception handling, interface changes where necessary and documentation. Work involving undocumented legacy systems can be more expensive than work using reliable, supported APIs.
Testing and controlled rollout. A workflow must be tested with valid, incomplete and unexpected information. The test plan should also address duplicate submissions, service interruptions, missing permissions and decisions that should return to a person.
Ongoing operation. Running costs may include hosting, API requests, AI model usage, third-party software subscriptions, monitoring and technical support. Some of these vary with usage. Others depend on the service coverage agreed with the developer.
Why a published starting price is not a final quote
A starting price is useful for establishing the minimum investment for a defined scope. It should not imply that every integration, workflow or security requirement is included. For example, an enquiry-handling implementation with one website form and a supported CRM is significantly different from a multi-channel customer-service system with permissions, conversation history, escalation, analytics and custom interfaces.
Miguelito AI publishes one-time starting development fees and optional monthly management starting fees by market. In euro markets, service starting prices currently begin from €1,200 for defined scopes such as SEO digital intelligence workflows, with higher starting points for document automation, custom agents and platform work. Business Consultation & Discovery currently starts from €500 in Cyprus markets (and the equivalent published amount in AUD, GBP, USD or CAD). The full eligible discovery fee is credited toward the related one-time development price if the development agreement is signed within 30 calendar days of assessment delivery. See the live Pricing & Discovery page for current figures in your currency.
When comparing providers, request a breakdown of what is included. Ask which software accounts you will own, who manages the integrations, what happens if a vendor changes its API and whether you receive documentation for handover.
What should a monthly management fee cover?
A useful support agreement states exactly which workflows are monitored and what maintenance is included. It should define response windows, corrective work allowances, security responsibilities, usage limits and who pays external software charges. Avoid assuming that a monthly fee includes unlimited feature development, continuous human monitoring or unrestricted AI API consumption.
Some organisations prefer a documented handover and manage the system internally. Others need an ongoing technical partner. Both can be sensible choices, provided responsibilities are clear. Miguelito AI quotes ongoing management separately from one-time development.
How to assess value without inventing ROI
Estimate the present cost of the process using facts the business can verify. Record the average handling time, monthly frequency, error or rework rate and escalation burden. Then identify how much of that workload is realistically addressable. A process with 1,000 monthly transactions but frequent exceptions may require more human review than a smaller, stable workflow.
A project should be assessed against a baseline, not a marketing promise. Time saved is one measure; reduced omissions, faster handoffs and clearer accountability may also matter. Avoid presenting forecast savings as guaranteed results. Pair this with How to Build a Business Case for AI Automation.
How Miguelito AI scopes a project
Miguelito AI begins with a short introductory discussion of up to 20 minutes. When technical analysis is required, a paid Business Consultation & Discovery produces an assessment of the relevant systems, processes and proposed approach. The resulting development quotation identifies the agreed deliverables and any separate ongoing costs.
View current prices for Business Process Automation, Custom AI Agents and AI Workflow Integration on each service page and on Pricing. The published figures are budget guides for specific minimum scopes; the actual proposal reflects your business requirements.
Questions to ask before approving an automation proposal
Ask the supplier what problem the first release solves, which systems are required, what the approval boundaries are, how errors are surfaced, who owns the resulting code or configuration and what is needed to maintain the implementation. These answers are often more valuable than comparing two headline setup prices.
A well-scoped project leaves the customer with a defined process, measurable acceptance criteria and clear ownership. That is the foundation for expanding automation responsibly. If you want a scoped discussion for your organisation, request a business consultation.