AI Implementation Cost in Iran (2026): A Line-by-Line Budget Guide

There is no honest single figure for the cost of implementing AI in an Iranian company, and a supplier who names one before seeing your workflow, your data, and your systems is guessing. What can be known in advance is the shape of the bill: eight cost lines, four stages, and a short list of drivers that push the total up or down. This guide is written for the managing director, CFO, or CTO who has to put an AI line into the 1405 budget and defend it later. It explains where the money actually goes, gives you a worksheet to fill with your own figures, and shows how to judge whether a pilot has earned the next tranche of spending.

The central recommendation is simple. Do not budget a programme from a vendor headline. Fund a small, measured pilot, and let every later stage be justified by what that pilot measured.

Commercial-interest disclosure: ZharfAI, the publisher of this guide, sells AI consulting and implementation. We therefore benefit when companies decide to spend on AI. Apply every test in this article to our proposals as strictly as to anyone else's. We quote no ZharfAI prices here, and we make no claim about the return any specific company will achieve.

Why the honest answer is a range, not a price

AI spending is harder to forecast than a conventional software licence because the expensive parts depend on things nobody has measured yet: how clean your data is, how many systems the output must reach, how often a person has to correct the result, and how much usage grows once people trust it. Gartner made the point bluntly in July 2024, when it predicted that at least 30% of generative AI projects would be abandoned after proof of concept by the end of 2025, citing poor data quality, inadequate risk controls, escalating costs, or unclear business value. The same release quotes its analyst saying that costs "aren't as predictable as other technologies."

That release also published the most useful public reference point we know of: typical cost ranges for five ways of deploying generative AI. The figures below are Gartner's, in US dollars, as of July 2024, for organisations outside Iran. They are not Iranian prices and should never be copied into an Iranian budget. Their value is in the ratios between the rows.

Two lessons carry over to an Iranian company of any size. First, the architecture is the largest single cost decision: moving from using a ready tool to building retrieval over your own documents multiplies the upfront figure by roughly four to ten, and moving from retrieval to fine-tuning multiplies it again by roughly five to nine. Second, recurring cost per user also climbs steeply down the table, from a few hundred dollars a year to more than ten thousand, so a design that looks affordable with ten pilot users can become expensive with a thousand. Most first projects we see in Iranian organisations, such as document extraction, internal knowledge search, or a Persian assistant for staff, belong in the Embed or Extend rows. Fine-tuning or training a model is rarely the right first step.

The eight cost lines of an AI implementation

Every proposal, internal or external, should be broken into the same lines so that you can compare them. We use eight, plus contingency.

The line most often underfunded is the first one. Gartner's February 2025 research on AI-ready data found that 63% of organisations either do not have, or are unsure whether they have, the right data management practices for AI, in a survey of 1,203 data management leaders conducted in July 2024. Gartner predicts that through 2026 organisations will abandon 60% of AI projects that are not supported by AI-ready data. In practice this means the data line is not a one-off tidy-up before the "real" work. It is often the real work.

Integration deserves the same honesty. Connecting to an Iranian accounting package or ERP can mean a documented interface, direct database access, a scheduled file export, or, in the worst case, nothing but the user screen. Reading data is far cheaper than writing it back, because every write into a financial or operational record needs validation, an audit trail, and a tested way to reverse it. Our guide to AI in accounting and financial document automation walks through that boundary for finance teams.

Model access in Iran: domestic API, self-hosted GPU, or foreign API

For an Iranian company, model access is not only a price question. It is a continuity question, and the cheapest option on paper can be the most expensive one to lose.

Foreign APIs. The largest foreign providers do not list Iran as a supported country. OpenAI's supported countries and territories page states that accessing or offering access to its services outside the listed countries may result in an account being blocked or suspended, and Iran is not on the list. Anthropic's supported regions list does not include Iran either. We do not advise on ways around these terms. For budgeting, the consequence is concrete: any design that depends on a foreign model needs a costed fallback path, and payment continuity has to be treated as a risk, not an assumption.

Domestic gateways. Several Iranian platforms sell model access in toman. As one dated example, not a recommendation, Liara's AI service page displayed two plans on 2026-09-24: 825,000 toman per month or 1,145 toman per hour with access to 66 language models, and 1,475,000 toman per month or 2,048 toman per hour with 113 models. On both plans, token costs are charged according to the model provider's tariff, and the model price list on the same page is shown in US dollars per million tokens. The lesson for a budget is general: the platform fee may be modest and local, but the usage line can still move with the exchange rate. The model list on such gateways can also include providers that do not list Iran as supported, so ask any gateway how it secures that upstream access and what happens to your service if it stops.

Self-hosted open models. Running an open-weight model on GPUs in an Iranian data centre, or in your own server room, removes per-token billing and keeps data inside your perimeter. It replaces a variable bill with a fixed one. A transparent way to estimate it is:

• monthly fixed cost = GPU lease (or purchase price divided by useful months) + hosting and power + storage and backup + operations hours × loaded hourly cost;
• cost per completed task = monthly fixed cost ÷ tasks completed in the month;
• break-even against an API = the monthly volume at which tasks × average tokens per task × price per token equals the monthly fixed cost.

The inputs to that formula change quickly. The Stanford AI Index 2025 reports that the inference cost of a system performing at the level of GPT-3.5 fell more than 280-fold between November 2022 and October 2024, while hardware costs declined about 30% a year and energy efficiency improved about 40% a year. Treat any multi-year hardware purchase or fixed per-token commitment with care, and write a review clause into it. The comparison between local and foreign tools is covered in depth in our guide to choosing between Iranian and foreign AI tools, and the technique of sending easy tasks to cheaper models is explained in AI model routing for cost and quality.

The stages of implementation and what each one costs

The phrase "implementation stages" hides the most important budgeting fact: the cost lines do not arrive at once. Each stage has a different dominant expense and ends with a decision.

A pilot should use the cheapest integration that still produces honest evidence, often a controlled file export rather than a live connector, and it should run in assisted mode, where a person approves each output. The rollout budget is where the organisation changes, not just the software. McKinsey's state of AI survey, published in August 2026, found that nearly three quarters of the respondents it classes as AI high performers report fundamentally redesigning workflows because of AI, compared with one quarter of other respondents. If the rollout budget contains no time for redesigning the process, it is budgeting for the tool and not for the result.

What pushes the cost up, and what brings it down

The same workflow can cost several times more in one company than in another. These are the drivers we see most often.

Cost rises when:

• the output writes into a financial, legal, or customer record instead of producing a draft;
• a wrong answer has high consequences, so every output needs human review;
• inputs are scans, handwriting, stamps, or dozens of different supplier formats;
• the data must stay on premises and the organisation has no suitable hardware;
• the service must answer in real time, at high volume, across several channels;
• there is no single owner who can approve acceptance criteria and data access;
• the plan includes fine-tuning or training a model before a simpler design has been tried.

Cost falls when:

• the first scope is one workflow, one user group, and one document type;
• the system reads from existing systems and hands its result to a person;
• clean exports or a documented interface already exist;
• a ready model is combined with retrieval over approved documents;
• simple, high-volume tasks go to a smaller model and only hard cases reach a large one;
• batch processing overnight replaces real-time calls where users can wait;
• the Persian evaluation set built for the pilot is reused for every later change.

Hidden costs and common failure modes

The gap between the quote and the final bill usually comes from costs that nobody wrote down. The failure patterns behind them are well documented. RAND's 2024 study, The Root Causes of Failure for Artificial Intelligence Projects, interviewed 65 experienced data scientists and engineers and identified five leading causes: stakeholders misunderstanding or miscommunicating the problem, lacking the data needed to train an effective model, focusing on the latest technology instead of the users' real problem, lacking the infrastructure to manage data and deploy models, and applying AI to problems that are too difficult for it. RAND also notes that by some estimates more than 80% of AI projects fail, about twice the rate of IT projects without AI. That figure is an estimate RAND cites from other work, not its own measurement, but its five causes map directly onto budget lines.

Hidden costs to put on the worksheet explicitly:

• Human review that never ends. If a person checks 20% of outputs for the life of the service, that time is a permanent operating cost.
• Exceptions. The cases the system cannot handle still need a person, a queue, and a response time.
• Re-evaluation. Every upstream model update, prompt change, or new document type needs the Persian test set run again.
• Exchange-rate movement. Any usage priced in dollars moves with the rate; budget a range, not a point.
• Security testing. Language-model applications need testing for prompt injection, sensitive information disclosure, and excessive tool authority, as listed in the OWASP GenAI LLM Top 10 2026.
• Expert time. Accountants, lawyers, or engineers who label data and judge outputs are not free because they are internal.
• Parallel running. The old process usually runs alongside the new one for a period, which doubles part of the workload.
• Exit. Moving data, configuration, and evaluation sets to another supplier or model has a cost; price it before you sign.

Operating cost is not a theoretical worry. In McKinsey's 2026 survey, about one in five respondents said their organisation is limiting AI use because of operating costs, including token costs.

Build, buy, or partner

The build, buy, or partner decision changes which lines you pay and who carries the risk.

Buy a ready product or platform when the workflow is common and the product already fits your data rules. Upfront cost is lowest and time to value is shortest, but customisation, data location, and integration are limited to what the product offers, and per-user or per-usage fees grow with adoption.

Build in-house when the workflow is a source of advantage, the data is highly sensitive, and you can staff data, application, and security roles for the long term. Building software has become cheaper: McKinsey's 2026 survey found that 32% of respondents say their organisation decided against buying at least one software product or feature because it could be built internally with agentic coding tools. Evaluation, security, and operations, however, do not get cheaper at the same pace.

Partner with an external team when you need speed and experience but want to keep ownership. The cost is the partner's fee plus your own owner's time. The risk is dependence, which you manage in the contract: ownership of code, configuration, prompts, and evaluation sets, documentation, knowledge transfer, and a tested exit. Our guide on how to choose an AI company in Iran sets out how to compare partners on evidence rather than presentations.

Many organisations end up with a hybrid: a bought platform for general tasks, a partner-built service for one high-value workflow, and an internal team that owns evaluation and operations.

A budgeting worksheet you can fill in

Copy this table into a spreadsheet and replace each formula with your own figures. It deliberately contains no prices. Where a line is not needed at a stage, write zero and say why.

Fill it three times: a low, an expected, and a high scenario. Vary volume, share of outputs needing review, exchange rate, and number of integration surprises. The spread between the low and high totals is itself useful information: a wide spread means the pilot has not yet answered enough questions to justify a large commitment.

How to read a vendor quote

A quote is comparable only when it is broken into the same lines as your worksheet. Ask every supplier to map their price onto those lines and to mark each one as included, excluded, or your responsibility.

Warning signs in a quote:

• one lump sum with no breakdown;
• a return on investment promised before anyone has seen your data;
• "unlimited" usage without a fair-use limit or an explanation of who pays for model calls;
• no evaluation plan and no acceptance criteria linked to payment milestones;
• no clause for exchange-rate movement on dollar-linked components;
• silence on ownership of code, configuration, and evaluation data, or on exit.

Questions to ask before you sign:

1. Which of the eight cost lines does this price cover, and which remain with us?
2. Is the price fixed, time and materials, per user, or per usage, and which parts are linked to foreign currency?
3. Who pays for model usage, and what happens to the price if the upstream model or API changes or becomes unavailable?
4. What Persian test set will you use, who builds it, and do we own it afterwards?
5. What is the integration method for each system, and who fixes it when it breaks?
6. How many hours of human review per month should we expect in the first quarter of operation?
7. What does support cost after go-live, and what response times does it include?
8. What will it cost us to leave, and what will we receive when we do?

How to measure the return on a pilot

A pilot earns the next budget only if it is measured against a baseline recorded before it started. Gartner's 2024 release notes that productivity gains are often difficult to translate directly into financial benefit, so write the arithmetic down in advance rather than reconstructing it afterwards. Three formulas are enough for most pilots:

• Net monthly value = hours removed × loaded hourly cost + errors avoided × average cost of an error − review hours × loaded hourly cost − monthly run cost.
• Payback period in months = one-off cost of the next stage ÷ net monthly value.
• Cost per accepted task = total monthly run cost ÷ tasks accepted without major rework.

Hours saved are not cash unless they are redeployed or avoid a hire, so record what happened to the time. Measure the review and correction effort honestly; our guide to measuring AI productivity after review and rework shows how easily that effort disappears from a report. Keep expectations grounded: in McKinsey's 2026 survey, 37% of respondents attributed at least some EBIT impact to AI, and only about 6% qualified as high performers attributing 5% or more of EBIT to it.

Two tools on this site can help you prepare. The AI pilot readiness check asks five questions about problem clarity, data, integration, access rules, and measurement, and suggests whether you are at discovery, pilot design, or controlled validation. For finance teams, the financial document automation capacity estimator estimates the monthly hours released after subtracting human review time. It reports hours, not money: multiply by your own loaded cost, and treat the result as an assumption to test, not a saving.

Decide in advance what result means go, what means revise, and what means stop. Stopping a pilot that missed its criteria is a successful use of a small budget.

A sensible next step

If you are preparing an AI line for this year's budget, start with discovery rather than a purchase: one workflow, its owner, a data sample, the systems involved, and the constraints you already know. Our AI consulting and implementation service begins at exactly that point and can end with an honest recommendation not to proceed. If you would like a scoped discussion, use the contact page, and hold our answer to the same worksheet and questions you would use for any other supplier.

Source Notes (reviewed 2026-09-24)

• Cost ranges by deployment approach and abandonment risk: Gartner, "Gartner Predicts 30% of Generative AI Projects Will Be Abandoned After Proof of Concept By End of 2025," July 29, 2024. Figure 1 gives global US-dollar ranges by deployment approach; they are reference ratios, not Iranian prices. The 30% figure is a prediction.
• Data readiness: Gartner, "Lack of AI-Ready Data Puts AI Projects at Risk," February 26, 2025. Survey of 1,203 data management leaders, July 2024; the 60% abandonment figure is a prediction through 2026.
• Enterprise returns and operating-cost constraints: McKinsey, "The state of AI in 2026: On the road to ROI," August 25, 2026. Online survey of 1,719 participants in 97 countries, May 4 to June 8, 2026, weighted by national GDP; self-reported.
• Root causes of failure: RAND, "The Root Causes of Failure for Artificial Intelligence Projects and How They Can Succeed," August 13, 2024. Based on interviews with 65 practitioners; the more-than-80% failure figure is an estimate RAND cites, not its own measurement.
• Falling inference and hardware costs: Stanford HAI, AI Index Report 2025. Figures cover November 2022 to October 2024.
• Foreign API availability: OpenAI supported countries and territories and Anthropic supported countries and regions, both checked 2026-09-24; Iran was not listed on either page.
• Domestic API pricing example: Liara AI service page, plan fees and billing method as displayed on 2026-09-24. Prices change; cited as a dated example of billing structure, not an endorsement.
• Security testing scope: OWASP GenAI LLM Top 10 2026. A threat-discovery resource, not a certification.