What custom software and automation cost
Every build is priced from its scope, which is settled before any code is written. This page sets out every stage that already has a price, how long each kind of work takes, and what decides the rest.
VAT included
What is priced before any code is written
Every stage up to the specification has a published price. The build itself is priced once the specification is finished.
A 5–10 minute phone call
The possible solutions, what will set the budget, and whether the work is worth pursuing as described.
Technical Diagnostic
A written report on the integrations involved, what the effort depends on, and the first stage worth building.
Viability assessment
A build-ready specification for your idea or process.
Workspace setup
A day on site that ends with AI connected to your accounts and jobs already running.
Professional training
Three sessions of about two hours, on real infrastructure.
Consultation and advising
A review of an existing system, a second opinion, or someone technical in the room.
A build
The system, built to the finished specification.
All prices are in shekels and include VAT. Each stage above can be bought on its own.
Seven things decide what a build costs.
One project can cost ten times as much as another that sounds identical.
- 01
How many systems it has to touch
One system is a build. Four systems make an integration project, in which any one of them can change without warning.
- 02
Whether the data can be reached
A documented interface is cheap to work with. When a number exists only on a screen that someone copies from, estimates double.
- 03
How many decisions it has to make
Moving data is cheap. Judging it is the expensive half, because somebody has to settle which price holds and which exception a person needs to see.
- 04
How many kinds of user it serves
Every role is another set of screens, another set of permissions, another path to test.
- 05
Whether it has to run unattended
A job that runs overnight has to detect its own failures. Building that in is most of the work.
- 06
Whether the old system can be switched off
Building beside a live system is the expensive case, because both versions have to agree while people are working in them.
- 07
Whether it has to work in Hebrew
Right-to-left layout is a decision made before the first screen is built. Retrofitted later, it becomes a rebuild you pay for twice. OctoMonic works natively in Hebrew and English, so a bilingual system is specified once.
How long each kind of work takes
These effort ranges hold once the scope is settled. Anything still undecided can move them.
One process moved between two systems that already talk
Typical effortA few days
What moves itHow well documented both ends are.
Scheduled collection and a daily report
Typical effortOne to three weeks
What moves itHow many sources there are and how often they change shape.
An operational dashboard over data you already hold
Typical effortTwo to four weeks
What moves itWhether the numbers already agree with each other.
An internal tool with roles and a real workflow
Typical effortSeveral weeks to a couple of months
What moves itThe number of roles and approval steps.
A customer-facing platform
Typical effortMonths, starting smaller than the full idea
What moves itWhether money moves through it, how many separate customers share it, and whether it ships in both Hebrew and English.
AI configured around one person’s real work
Typical effortOne day on site
What moves itHow many accounts have to be connected and how deep the automations go.
A workshop that leaves people running AI themselves
Typical effortThree sessions of about two hours
What moves itGroup size and how much runs on your own tools.
Stabilising a system that is already live
Typical effortEstimated after the code is read
What moves itHow much of it was documented, and how much has to be read.
A range describes a kind of work. It becomes a number only when it is measured against a specific system and an agreed definition of done.
The cost that starts after launch
Monitoring, failure alerts, hosting, fixes and small changes continue month to month under the support retainer. You’ll know the monthly fee while the build is still being specified. It’s agreed before handover.
The questions that come before a budget
How much does it cost to build an app?
An app can be a week of work or a year of it. The cost depends mainly on how many systems it touches and how many decisions it’s expected to make. Every stage up to the specification is priced above.
How much does automation for a business cost?
Moving one process between two systems that already talk takes days. A system that collects, decides, reports and catches its own failures takes weeks. The ₪250 Technical Diagnostic establishes which one you’re describing and sets out the reasoning in a written report you keep.
Why is there no price list for builds on this page?
No single price can cover both a build that takes days and one that takes months. Everything that can be priced in advance is listed above. Build prices come from a specification, which the viability assessment produces for ₪1,500–2,500.
What does the ₪250 Technical Diagnostic actually buy?
You get 30 minutes on Google Meet to work through the problem and the options. Afterwards, the written Diagnostic Report sets out which of the four offerings fits, why it fits and what it would take. If none of them fits, the report says so. It’s yours to keep, whoever builds the system.
Should I take the cheapest quote?
Compare what each number includes: handover, monitoring and support after launch, and whether it was priced from a specification or from a conversation. Most of the gap between two quotes sits in what happens after the build. The headline figure rarely shows that part.
Find out which of these ranges fits your project.
A short phone call narrows it down to one. Most of the spread comes down to two things you already know: which systems hold the data and how often the job has to run.
Free · 5–10 minutes · by phone