AI automation pricing: fixed scope, fixed price, a pilot first.
Aldenebai prices its work in three steps: a free Automation Audit that ranks what to automate, a fixed-scope, fixed-price pilot on a slice of real traffic with a named target, then the full system at a price agreed before it is built. There is no price list, because the same system costs very different amounts depending on your integrations and volumes. This page explains what drives the number, what is always included, and what it costs to run. Websites, apps, and internal systems skip the pilot: one call, one fixed-price proposal, one launch. How a build is priced ↓
Why two support agents cost different amounts
The system is the same shape every time: intake, decision, action, escalation, audit trail. What changes is what it has to connect to and how much can go wrong.
A support agent for a team with one helpdesk and good documentation is a compact build. The same agent that also has to read billing, touch three legacy systems, and follow a regulated escalation policy is not. The audit makes those differences explicit before anyone talks about money.
From a free call to a running system, with a price at every step
The Automation Audit: free
Thirty minutes. You leave with a written map: every repetitive job ranked by return and risk, a realistic estimate for the first system, and the honest "not yet" where a machine would underperform. Book it →
The pilot: fixed scope, fixed price
The first system on a slice of real traffic, with a named target agreed in writing, for example a resolution rate on the top five ticket types or a turnaround time on one repository. It goes live early and proves the number on your data.
The full system: price agreed before the build
What it does, what it deliberately does not do, guardrails, tests, timeline, price. The price does not move unless you change the scope. Delivered into your repositories and accounts, with documentation, so your team owns it.
Small enough to prove, real enough to count
The pilot is not a prototype. It is the system, its monitoring, and its tests together, on a slice of real work, with a target written down before it starts. For reference, the client's support agent took about a month from kickoff to its first live ticket.
Who runs it at 3am: your team, or Aldenebai
Every system ships ready for your team to run. Whether Aldenebai keeps running it is a choice made per system, at proposal time, and it can change later.
What every price covers
These are not add-ons. A system without them is a demo, and Aldenebai does not ship prototypes.
What it costs after it is live
Systems run on your own accounts, so the running cost is model usage and infrastructure you can see on your own bills. Cheaper models handle routine reading and routing; the capable model is used only where the decision needs it. A hard monthly ceiling is set in the design so the bill can never surprise you.
There is no Aldenebai licence and no per-seat charge. Changes and new systems are scoped and priced when you want them.
How a website, app, or internal system is priced
A build has no pilot to run, so the shape is shorter: one call, one fixed-price proposal, one launch.
Questions about pricing
Why no price list?
Because the same system costs very different amounts depending on integrations, volumes, and guardrails; the section above explains what drives it. The proposal you receive is a fixed price for a fixed scope.
What does fixed scope, fixed price mean in practice?
Before any build, you get a written proposal: what the system does, what it deliberately does not do, its guardrails, its tests, its timeline, and its price. That price does not move unless you change the scope. Surprises are a design failure, and they are designed out.
What is a pilot?
The first system on a slice of real traffic, with its monitoring and tests, and a target named before it starts. The section above describes how it is scoped.
What does a system cost to run?
Running costs are the model usage and infrastructure on your own accounts, visible on your own bills, with a hard monthly ceiling set in the design. There is no Aldenebai licence fee and no per-seat charge.
What happens if Paul is unavailable mid-build?
Nothing is locked to one person. Every system is built inside your own repositories and accounts from the first commit, never on Aldenebai infrastructure, and ships with a runbook, the exported workflows, and its own tests, so any competent engineer can pick it up and run it. There is a team behind Paul for capacity, a defect warranty after go-live, and a kill switch you control. If the engagement ended tomorrow you would keep working software you already own, not a dependency on a supplier.
Do you offer retainers or ongoing support?
Yes, as the Operate option above: Aldenebai monitors the system, tunes thresholds, updates models and prompts, and answers within a named response time, for a monthly fee agreed in the proposal that you can cancel monthly. It is never bundled in by default. Your team can own and run what was built from day one and call only when you want more.
The first step costs nothing.
Thirty minutes, a written map, and a realistic estimate for your first system. Yours to keep either way.