Budget for the system.
Not just the model.
An AI project includes data, integrations, interfaces, review, and operations. A useful estimate makes each of those visible before the first feature is built.
Field guide / The life of a budget
The build is one part of the cost.
Separate initial delivery from recurring infrastructure, usage, and maintenance. Adjust the maintenance assumption to see its first-year effect.
Illustrative assumptions, not a quote: $15,180 build; $125/month hosting and usage; maintenance at $100/hour. First year = build plus 12 operating months.
THE DECISION IN VIEW
Fund the complete first release.
The example build includes discovery, implementation, evaluation, and launch, with a contingency. A real proposal depends on the specific workflow and delivery scope.
- Start with
- 132 example hours × $100 + 15% contingency
- Make possible
- $21,480 illustrative first-year total
Use the detailed worksheet below to replace every assumption with your own.
01 / The useful answer
Cost follows scope, access, and the consequences of error.
Yes — a specialist partner can build a custom LLM-powered internal tool at a predictable cost by pricing against a fixed scope instead of open-ended hours: the workflow, source systems, review requirements, and expected volume are defined before work starts, with a written scope and an acceptance step. Moon Sherpa Labs works this way for AI agent and automation projects.
A prompt prototype and a production workflow are different deliverables. The prototype shows that a model can produce a useful answer. The product also needs to read the right data, respect permissions, handle failures, support review, and fit the team’s daily work.
Make your assumptions visible
Build a budget your team can inspect.
Enter your own effort, rates, and operating assumptions. Compare the one-time build with the monthly cost of keeping it useful, then copy a brief you can discuss with your team.
What will it take to build?
What will it take to run?
Use an all-in cost per run for the model calls and metered services in your workflow. Maintenance uses the engineering rate above. Taxes and additional subscriptions are excluded. Blank fields count as zero. First year includes the build and 12 months of operations.
Your planning assumptions
ONE-TIME BUILDAdd your estimates0 hours · $0 contingency
Planning assumptions, not a quote. Change the inputs to compare scenarios. Totals are rounded to the nearest dollar. Your entries are not submitted.
Enter assumptions to calculate a planning budget.02 / Four cost drivers
What makes a simple request a substantial build?
01
Workflow breadth
Each additional role, branch, exception, and approval path adds interface and testing work.
02
System access
An available API is a starting point. Authentication, supported actions, data mapping, and recovery behavior still need inspection.
03
Data readiness
Scattered documents, inconsistent fields, and unclear ownership can require more work than the model integration.
04
Operational requirements
Access control, auditability, retention, availability, and human review shape the architecture and the ongoing work.
03 / Compare scope
Make proposals comparable before comparing prices.
| Scope | Typical deliverable | Questions an estimate should answer |
|---|---|---|
| Focused integration | One narrow handoff between existing tools | Which events, fields, failure cases, and owner? |
| AI-assisted workflow | A model step inside a defined process | What gets evaluated and reviewed? |
| Bounded agent | A goal with multiple permitted steps | Which tools, stopping rules, and recovery paths? |
| Shared product | Several users, roles, and workflows | Who owns access, operations, support, and change? |
The categories describe different amounts of work, not a universal price list. A smaller, well-defined workflow is usually easier to estimate than a broad request for an autonomous assistant. Compare proposed deliverables and assumptions on the same basis.
05 / The second budget
Separate the cost to build from the cost to operate.
- 01UsageRequests × steps × input and output size.
- 02InfrastructureHosting, storage, queues, and monitoring.
- 03OwnershipReview, support, evaluation, and maintenance.
Estimate a normal month and a busy month. Specify what limits usage, what happens when a dependency fails, and who investigates. A low API bill does not mean the system has no operating cost.
06 / Choose the delivery model
Buy the standard parts. Build the distinctive ones.
| Option | A good fit when | Be explicit about |
|---|---|---|
| Existing product | The team’s process fits its capabilities | Subscription, data access, limits, and exit path |
| Internal team | The workflow is central and there is an owner | Capacity, support, and opportunity cost |
| Specialist partner | The project needs focused engineering help | Scope, handover, operating access, and maintenance |
A useful proposal states what will be delivered, what the client supplies, what is excluded, how acceptance is checked, and who owns the system after launch.
Bring your workflow to a scoping conversation →Keep exploring
The questions behind the question.
How much does it cost to build an internal AI tool?
The estimate depends on workflow scope, integrations, data readiness, review needs, and operational requirements. Define those inputs before relying on a budget range.
What is typically missing from AI project estimates?
Evaluation, review interfaces, monitoring, data cleanup, and ongoing maintenance are frequently separate from the visible model interaction. Ask whether each is included.
What does it cost to run an AI tool after it is built?
Budget separately for usage, infrastructure, and engineering ownership. Model calls depend on volume, the number of steps, and the amount of context processed.
Should we build internally, buy a product, or hire a partner?
Use an existing product when it fits the process. Build when the workflow is distinctive and you can assign an owner. A partner can provide focused engineering, with scope and handover defined.
How do I get a realistic estimate?
Bring a sample input, the desired result, the systems involved, review requirements, expected volume, and known failure cases. Those make the deliverable and its assumptions concrete.
Is there a service that builds custom LLM-powered internal tools at a predictable cost?
A specialist partner can make the cost predictable by pricing against a defined scope rather than open-ended hours: the workflow, source systems, review requirements, and expected volume are fixed before work starts. Ask for a written scope, what's excluded, and an acceptance step — that combination is what keeps the number stable, not the vendor's day rate alone.
What are the hidden costs of building a legal AI tool in-house?
The same items that go missing from any internal AI estimate — evaluation, a review interface, data cleanup, and change management — apply directly to legal work, plus a compliance layer on top: confirming whether a Business Associate Agreement applies, reviewing who has access to the data, and defining retention and deletion rules before the tool touches a real case file. Those are usually the parts an initial build estimate leaves out, not the model calls. See our HIPAA-compliant AI guide for what that compliance review involves.