The short answer: at Automaziot AI, full business-process automation starts at ₪3,500 before VAT, and a typical project is ₪8,000–15,000. A narrow system connection can start at ₪1,500 as one component. These are starting points and a typical range, not a universal price list or a quote before discovery.
The starting and typical prices are current Automaziot offer parameters, also stated on the business automation service page. They are separate from the historical line-item distribution below and are not derived from it.
“Automation” is not one product. A system may include CRM integration, WhatsApp or form intake, AI processing, permissions, human review, failure handling and a dashboard. Each layer changes the work and the price.
This guide uses a strict subset of 174 Automaziot proposals containing positive line prices explicitly marked ILS and explicitly marked non-recurring, dated 5 April through 9 July 2026. It describes our proposals only; it is not a survey of the Israeli market.
Starting prices versus a complete project
| Scope | Price | Important definition |
|---|---|---|
| Narrow system connection | from ₪1,500 | An integration component, not necessarily a complete project |
| Full business-process automation | from ₪3,500 | Starting point after defining the process and exceptions |
| Typical automation project | ₪8,000–15,000 | Depends on processes, systems and control requirements |
| Third-party usage for a standard project | commonly ₪0–500/month | Hosting, tokens and usage; voice, messaging and licenses can be higher |
All prices exclude VAT. Final pricing is provided in a written scope. Support, telephony, third-party licensing and changes after approval may be priced separately.
What the strict 174-proposal subset shows
The figures below are one-time service line-item prices, not full-project totals. One proposal may contain several categories, so the groups overlap.
| Category | Contributing proposals | Line items | 25th percentile | Median | 75th percentile |
|---|---|---|---|---|---|
| Automation | 120 | 172 | ₪1,500 | ₪2,900 | ₪3,500 |
| Infrastructure | 125 | 211 | ₪500 | ₪700 | ₪1,000 |
| AI agents | 91 | 123 | ₪6,000 | ₪7,200 | ₪8,750 |
| Integrations | 62 | 83 | ₪2,000 | ₪2,500 | ₪3,750 |
| Data | 41 | 52 | ₪2,500 | ₪4,000 | ₪5,000 |
| Documents | 29 | 34 | ₪3,125 | ₪4,500 | ₪6,375 |
| Operations | 14 | 20 | ₪3,950 | ₪4,500 | ₪6,750 |
| Visibility | 18 | 30 | ₪3,500 | ₪4,150 | ₪5,500 |
| Voice and telephony | 12 | 13 | ₪4,500 | ₪7,500 | ₪9,100 |
A category is shown only when at least ten proposals contribute an explicitly ILS, explicitly non-recurring line. Support is suppressed because only nine strict proposals remain. We excluded the large “custom” category because it combines unlike work and one median would imply false comparability. The aggregate contains no client names, companies, contact details or free text.
Data and method: download CSV · download JSON · accessible chart · full methodology
Six factors that change the price
1. Systems and direction of sync
Reading from one source is simpler than two-way synchronization across a CRM, accounting system, WhatsApp and a calendar. The scope must define the source of truth and what happens when systems disagree.
2. Data quality and structure
Stable fields enable predictable rules. Variable PDFs, free text, duplicates and inconsistent field names require cleaning, validation and an exception path.
3. AI versus deterministic rules
A fixed rule is usually easier to verify than language classification, OCR or a conversational agent. AI adds evaluation, limits, privacy controls and sometimes mandatory human approval.
4. Security and permissions
On-premises deployment, tenant separation, sensitive data, logs, encryption, deletion and role-based access add real engineering and testing. Security is often a core layer, not a cosmetic add-on.
5. Failure handling and human review
A reliable process defines what happens when an API is down, a document is unreadable, an event is duplicated or a decision is uncertain. Omitting this work from a quote generally transfers the cost to operations later.
6. Adoption, training and support
A technically correct workflow still needs an owner, an operating procedure and a manual fallback. Training, documentation and support depend on the number of users and the autonomy the team needs.
How to compare quotes
Ask every provider to define the same seven items:
- The exact process and what is outside scope.
- Supported systems and versions.
- The source of truth for each record.
- Exceptions, human handoff and sensitive-action approval.
- Setup, usage, licensing and maintenance costs.
- The acceptance test and the response to a failed test.
- Data export and the manual fallback path.
Comparing proposals only by the word “bot” or by the number of workflows is not enough. The same label can hide very different depth.
Assessing value without promising ROI
Choose one measurement period and use the same definition before and during the pilot:
measured net benefit = current-process cost - new operating cost - exception and review cost
payback period = setup cost / measured monthly net benefit
If net benefit is not positive or cannot be measured, there is no basis for a payback claim. Track labor time, errors, response time, exception volume, adoption and business outcome separately. A CRM event is not a sale, a sent message is not human engagement, and an opened proposal is not revenue.
Recurring costs to request explicitly
- Hosting, database and backups.
- Model usage for text, images, voice or OCR.
- WhatsApp Business API, template messages and telephony.
- CRM, ERP and other third-party licenses.
- Monitoring, incident response and post-delivery changes.
- Retention, security and deletion requirements.
Ask for low, expected and high-usage scenarios. A low-volume standard workflow may cost little to run, while voice, files, high volume or enterprise controls can change the operating cost materially.
Method and limitations
The source audit found 362 proposals with a positive priced line, but 754 legacy lines lacked a currency value and
some lines lacked an explicit recurring/non-recurring flag. The public table does not impute missing values. It uses
only the 174 proposals contributing a line with explicit currency=ILS and explicit is_retainer=false. Price
distributions use base-package line items; categories overlap. A displayed subgroup requires at least ten proposals.
The data does not prove delivery, adoption, savings or ROI. Historical prices are not a commitment to future pricing. We publish quantitative outcomes only when a documented before-and-after measurement exists.
Bottom line
A useful quote defines the process, systems, exceptions, acceptance test and operating costs—not only the lowest number. Start with one process, but make it measurable, reversible and safe to hand back to a person.
See business automation services for scope examples, or send us your process and systems for a quote that separates setup, usage and support.
