A custom AI automation project is priced as a scoped build, not as a per-seat subscription. Discovery starts from $750 and is credited to the build if you go ahead. The published starting-from floors then give a first indication of the work, and the actual quote follows the process map, the integrations, and the approval gates that have to be built in.
That is the commercial shape. You pay to have a system built around how you operate, then you own it. Usage, such as model or telephony costs, is billed at cost. An optional retainer starts from $500 a month if you want ongoing improvement. There is no license that rises every time you hire. The current floors are on the pricing page.
What does Discovery include, and why is it credited?
Discovery is the first paid step. We map the repeated work, mark what already has a written rule, mark what must stay with a person, and name the systems the build would have to connect to. You leave with a clear first phase and a fixed-price path, not with a vague proposal.
The $750 starting-from fee exists so that this map is real work, not a free conversation that guesses at scope. If you go ahead with the build, that fee is credited, so you are not paying twice for the same thinking. If you do not go ahead, you still have the map.
Discovery is also where we will tell you if you should not build. If the current tool is fundamentally sound, or if a narrower integration will do, we will say so. A custom operations platform is not the right answer for every team, and the quote should reflect that.
Human approval is part of this map, not an afterthought. The Discovery output should say which steps a person must still approve: a booking outside the rules, a shortlist, a payment, a client or student message. Those gates affect scope, and they should be visible before anyone starts building.
What are the starting-from floors, and what are they not?
The published floors, in USD, are:
Discovery: $750, credited to the build
Lead response and qualification: $2,500
Back office automation: $3,000
Document and data extraction: $4,000
AI voice agent: $5,000
Custom operations platform: $12,000
Operations retainer: $500 a month
Usage billed at cost
These are starting points, not quotes, and not typical totals. A narrow first phase can sit at the lower floors. A platform that holds the workflow, the integrations, and the approvals will sit at the custom operations floor or above, once the map is clear. The quote is fixed for the agreed scope. It is not a sliding seat count.
The floors also help you see which first phase to start with. A freight desk that needs after-hours call cover is looking at the AI voice agent floor, often with document extraction beside it. A staffing team that needs after-hours applicant response is looking at lead response and qualification. A growing agency or academy whose CRM no longer fits is looking at the custom operations platform floor. The floor is a signal, not the invoice.
We do not quote Pratibha SaaS prices here. Pratibha is sold, and its pricing lives on pratibha.tech/pricing. This post is about custom automation work, which is priced as a build.
What changes the quote?
Four things, more than any other, change the number.
The first is the width of the process. One document type into an existing TMS is a smaller build than vetting, inbound calls, paperwork, tracking, and payment preparation for a brokerage. One after-hours acknowledgment and a recruiter-approved shortlist is a smaller build than a full hiring workflow with interviews and scheduling.
The second is the state of the inputs and the systems. If the rules are written, the fields are known, and the TMS, ATS, or CRM can receive the results, the first phase is tighter. If the work still lives in inboxes and side sheets, the map has to include that cleanup. Automation on missing data is not cheaper. It is only less reliable.
The third is the approval design. Gates for money, customers, candidates, compliance, and reputation have to be built into the process. A clean exception queue, with context already attached, is part of the work. It is also the part that makes the system safe. Removing those gates to make a quote look smaller would be the wrong saving.
The fourth is whether you need a new system of record or a layer on top of one you already trust. Extending a sound CRM or sitting on top of a TMS is usually a different scope from replacing the system the team lives in. See Should a Growing Agency Extend Its CRM or Replace It? for that choice.
What should not change the quote in silence is usage. Model, telephony, or messaging costs are billed at cost, separately, because they vary with volume. They are not hidden inside a per-seat license, and they are not treated as a surprise add-on after go-live.
How should a first phase be scoped so the price stays honest?
Scope a first phase that is useful on its own, then widen. Answering after-hours carrier calls and writing up exceptions is useful before the agent is allowed to book. Filing rate confirmations into a TMS is useful before payment release is added. Acknowledging applications after hours is useful before automated interviews begin.
Each phase should have a clear outcome, a clear approval line, and a clear connection to the system you already use. That is how a fixed price stays fixed. A phase that tries to automate the entire brokerage, agency, or hiring desk in one step is harder to quote honestly and slower to become useful.
This is the same 80/20 order we use in the work itself: written-down tasks first, then hand-offs, then one-click approvals, then more ambitious agents. See Which Operations Work Should You Automate First?. The pricing follows that order, because the earlier phases are easier to bound.
We have used this approach across 240+ projects since 2016, for 150+ clients in 7 countries. The industries change, from freight and logistics and staffing and recruitment to education, agencies, and ecommerce operations. The commercial rule does not: map first, quote a fixed first phase, keep a person on the important steps, and bill usage at cost.
Published examples of the work, not of a standard price, include the Dollar Traq AI operating system and recruitment automation. Those pages describe the pattern. They are not a price list.
What do you own after the build, and what does the retainer cover?
You own the custom work: the code, the data, and the roadmap. That is the point of a build rather than a rented workflow. If you add people, you do not add a license for each of them.
The operations retainer, starting from $500 a month, is optional ongoing help: improvements, monitoring, and changes as the process evolves. It is not a requirement to keep the system running as yours. Usage continues to be billed at cost, whether or not you are on a retainer.
If you later want a wider platform, the earlier phases should not be thrown away. A voice agent, a document layer, or a lead-response workflow should sit inside the operations platform if that is the later path, rather than being rebuilt from nothing. That is one reason to decide the system of record, or the layer around it, during Discovery.
Frequently asked questions
How is a custom AI automation project priced and scoped? Through Discovery first, starting from $750 and credited to the build if you go ahead, then as a fixed quote for an agreed first phase. The starting-from floors on the pricing page are a guide, not the invoice. Usage is billed at cost.
Is the $750 Discovery fee deducted from the build? Yes, if you go ahead. You are not paying twice for the same map. If you do not go ahead, you still have the map.
Why not just pay per seat? Per-seat pricing turns each hire into a software tax, and the workflow still belongs to the vendor. A custom build has a fixed scope and, once delivered, is yours. If your current tool already fits, extending it may be enough. We will say so.
What is billed separately at cost? Usage such as model, telephony, or messaging costs, because those vary with volume. They are not hidden in the build price, and they are not presented as a per-user license.
Do you have to buy a full operations platform first? No. Many teams should start with a narrow first phase, such as document filing, lead response, or an inbound voice agent, then widen. A custom operations platform, starting from $12,000, is for when the workflow itself needs a home.
How do we start? Book a call. We will map the work, show you which floor the first phase is likely to sit on, and tell you if you should not build.
If you want a clear, fixed-price path rather than another per-seat tool, book a call. Discovery starts from $750, credited to the build, and ends with a scope you can say yes or no to.





