Published price ranges in shekels for automation, websites, MVPs, AI agents and scraping - what each band actually includes, what pushes a project to the top of its range, and how to tell an honest quote from a low anchor.
Key takeaways
- A single automated workflow runs roughly ₪1,500-₪11,000; a brochure site ₪5,500-₪18,000; a standard MVP ₪37,000-₪92,000. The spread inside each band is driven by integrations, not by page count.
- The single biggest cost driver is how many external systems the project has to talk to, and whether any of them is a legacy Israeli system with an uncertain integration surface.
- A quote far below these ranges usually means the scope is smaller than you think, maintenance is excluded, or change requests will be billed separately. Ask which one before celebrating.
- Budget 15-20% of the build cost per year for maintenance. Software that nobody maintains does not stay still - dependencies age, APIs change, and it degrades quietly.
Almost nobody in the Israeli development market publishes prices, which means every buyer starts from zero and every conversation begins with "it depends". It does depend - but not infinitely, and the ranges are knowable.
These are my own published ranges, converted to shekels from the figures on my pricing page at approximately 3.7 ILS to the dollar. Verify the current rate, and treat all figures as before VAT where it applies. They reflect a senior freelance engineer, not an agency with account managers and not an offshore team.
The Ranges
| What you are buying | Range | Timeline |
|---|---|---|
| Business automation - one workflow | ₪1,500 - ₪11,000 | Days to 2 weeks |
| Business automation - multi-step system | ₪11,000 - ₪55,000 | 3 - 8 weeks |
| Brochure website | ₪5,500 - ₪18,000 | Days to 2 weeks |
| AI agent or chatbot | ₪11,000 - ₪55,000 | 1 - 3 weeks |
| Standard MVP or SaaS v1 | ₪37,000 - ₪92,000 | 6 - 12 weeks |
| Web scraping - one-off pull | ₪1,100 - ₪5,500 | 2 - 7 days |
| Web scraping - monitored pipeline | ₪7,500 - ₪30,000 + monthly | 2 - 5 weeks |
What Moves a Project Within Its Band
People assume the driver is size - more pages, more screens, more features. In practice it is almost always one of these four:
- Number of external systems. A project touching one system is at the bottom of its band. Three systems, each with its own authentication, error semantics and edge cases, is at the top. This is the dominant factor.
- Whether a legacy system is involved. Integrating a modern cloud API is predictable. Integrating a heavily customised Priority installation or a Hashavshevet deployment whose integration surface nobody can confirm is not, and the uncertainty has to be priced.
- Data quality. If customer records need cleaning before anything can be matched, that is real work that happens before the interesting part starts.
- How many people must approve. A project with one decision-maker moves at a different speed from one with a committee, and calendar time costs money.
Notably absent from that list: visual design complexity. It matters, but far less than most buyers expect.
What Is Usually Not in the Number
Ask explicitly about each of these, because their absence is how a low quote becomes an expensive project:
- Maintenance. Budget 15-20% of build cost annually. Dependencies age, APIs change, certificates expire.
- Hosting and third-party services. Usually modest, but they are ongoing and they are yours.
- Content. Someone has to write the text and supply the images. If that is not you, it is a line item.
- Data migration. Moving existing records into the new system is frequently a bigger job than building the system.
- Training and rollout. A system nobody was taught to use gets abandoned.
- Change requests. Ask how they are handled. "We will see" means they will be billed.
Reading a Quote
Three signals separate a considered quote from a guess:
It asks questions before quoting. Anyone who prices an integration without asking whether there is a sandbox environment is guessing. Anyone who prices an MVP without asking who the users are and what the first version must not do is guessing.
It states what is excluded. A quote that lists only inclusions is optimistic by construction. The exclusions are where the surprises live.
It has a phase one you could stop after. A proposal structured so the first deliverable is useful on its own is a proposal from someone who expects to be judged on results. An all-or-nothing six-month plan transfers all the risk to you.
Hourly, Fixed Price or Retainer
| Model | Best for | Watch out for |
|---|---|---|
| Fixed price | Well-defined scope, clear acceptance criteria | Change requests become negotiations |
| Hourly | Exploratory work, unclear requirements | No ceiling unless you set one |
| Monthly retainer | Ongoing evolution and maintenance | Drifting into paying for availability, not output |
A common and sensible structure is fixed price for a defined phase one, then a retainer for everything after. It gives both sides a predictable start and a sustainable middle.
Cheaper Options and Their Real Cost
Offshore teams at a third of these rates are real and sometimes the right choice. The cost shows up in timezone gaps, specification overhead, and the fact that ambiguity gets built rather than questioned. For a well-specified, self-contained piece of work it can be excellent value. For anything requiring judgement about your business, it usually is not.
No-code tools are genuinely cheaper for the first version and often the correct starting point. They become expensive at the point where you need behaviour the platform does not support, and the migration off them is rarely cheap.
The Honest Summary
If your project touches one system, has a clear owner and clean data, expect the bottom of the band. If it touches three systems, one of them legacy, with data that needs cleaning and three people who must agree, expect the top - and be suspicious of anyone quoting the bottom.
To get a specific number for your project, book a free call or use the project cost estimator. Related: MVP cost in Israel, how to reduce development costs, and questions to ask before hiring a developer.
Frequently asked questions
How much does it cost to build an MVP in Israel?
A standard MVP or SaaS v1 with multiple user roles, payments, integrations and an admin panel typically runs ₪37,000-₪92,000 over six to twelve weeks, working with a senior freelance engineer. A deliberately narrow first version with one user type and no payments can come in well below that. The main thing that pushes a project toward the top of the range is the number of external systems it has to integrate with, not the number of screens.
Why are these prices in shekels when your pricing page is in dollars?
Because Israeli buyers budget in shekels and converting mentally is friction. The shekel figures here are derived from the same published dollar ranges at approximately 3.7 ILS to the dollar, so the two pages do not represent different pricing. Exchange rates move, so treat the shekel figures as indicative and check the current rate. All figures are before VAT where it applies.
What should I budget for maintenance?
Roughly 15-20% of the build cost per year is a realistic planning figure for most projects. That covers dependency updates, API changes at third parties, certificate renewals, small fixes and monitoring. Software does not stay still just because nobody is changing it - the world around it changes, and an unmaintained system degrades quietly until something visible breaks. Projects with more external integrations sit at the higher end of that range.
Someone quoted me a third of these prices. Should I take it?
Possibly, but find out why first. The three usual explanations are that the scope being quoted is smaller than the one in your head, that maintenance and change requests are excluded and will be billed later, or that it is an offshore team where the saving is real but comes with timezone and specification overhead. All three can be acceptable if you know which one applies. The problem is only when you find out after signing.
Fixed price or hourly?
Fixed price suits well-defined scope with clear acceptance criteria, and the trade-off is that every change becomes a negotiation. Hourly suits exploratory work where the requirements are genuinely unclear, and the trade-off is no ceiling unless you set one. A structure that works well for most projects is fixed price for a defined phase one that is useful on its own, then a monthly retainer for ongoing evolution - predictable at the start, sustainable afterwards.
Keep reading
Related service
MVP Development
Turn an idea into a validated product in weeks, not months.
About the author
Yehonatan Saadia
Freelance automation, web & MVP engineer
I'm Yehonatan Saadia, a senior engineer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.