What each stage costs, and what decides the next one.
A short call, then the Technical Diagnostic. What follows is one of four separate pieces of work, each scoped and priced before it starts.
VAT included
- Step 1 · Free
A 5–10 minute call
5–10 min · phoneTen minutes on the phone, and the expensive part of the project has a name.
- Optional · Paid
Technical Diagnostic
₪25030 min · Google Meet · written reportThirty minutes on Google Meet, ending in the Diagnostic Report that turns the direction into a plan you can budget from.
From there, one of the four below.
Free · 5–10 minutes · by phone
Viability assessment
This is the stage before a build. Whatever the Diagnostic Report points to is mapped end to end and answered in writing, down to the single integration that decides the timeline.
Mapping and project specification
Fixed scopeThe idea, or your existing processes, mapped end to end and written up as a specification: architecture, integrations, data flows, timeline and budget.
A technical evaluation covering feasibility, approach, effort, cost and risk. It answers what building the system would take, which is a different question from whether the market wants it. The build itself is quoted from the finished specification and decided separately.
The document a viability assessment produces
The sample walks an invented company through the frame a real assessment uses: the verdict, how the system would work, what it touches, the access it needs, the risks, and the smallest version worth building first. Effort comes in bands, because a single number at this stage is a guess.
Professional training
Three sessions of roughly two hours, for individuals or inside a company. People leave able to run AI on infrastructure they set up themselves, which is a different skill from typing a good prompt into a chat window.
For individuals
Open workshopFor anyone whose week is full of drafting, chasing and copying between tools. You leave with a live workspace and something you built running in it.
For companies
On site or remoteThe sessions run on your own tools and workflows, so what people build takes over work they were doing manually.
Three sessions, about two hours each
- Session 1
Infrastructure
Accounts, a project, a database, storage and hosting, wired together so the model can create, change and publish real things that other people can open.
- Session 2
Method
Prompt engineering as problem-solving rather than question-and-answer: feeding work back in as recordings and screenshots, being specific enough to be useful, and knowing what to do when you are stuck.
- Session 3
Build
Everyone ships a working tool on the infrastructure from session one. It runs. It has a URL you can send someone.
Price depends on the group and how much of the material is adapted to your own workflows. The ₪250 Technical Diagnostic sets the scope, the session dates and the price, and the Diagnostic Report carries all three in writing.
Workspace setup
A single on-site day, scoped to one person, that ends with AI configured on your own machine and a few recurring jobs already running.
One day, on site
One person · one machine · one accountTools installed where you work, connected to your own email, calendar and files. Everything stays on your machine and in your accounts afterwards.
Two people or more
Priced per groupA group is a different day, scoped and priced after a short call.
The full page covers what the day includes, what moves the price, and a separate enquiry form.
Consultation and advising
Technical judgement with no build attached. Reviewing something already built, choosing between tools or vendors, or sizing a project before the budget is committed.
On an existing system
ReviewWhat something already built or bought does well, where it will break, and what fixing or replacing it involves.
Before you commit
Second opinionAn engineering opinion on a quote, a vendor or a plan, while it can still change the decision.
Scope, schedule and price are set in the ₪250 Technical Diagnostic and written into the Diagnostic Report, so what you are agreeing to is on paper before anything starts.
All prices are in shekels (ILS) and include VAT.
What happens after a build
A system is handed over working, then supported month to month: monitoring, alerting, hosting, fixes and small changes. New scope is quoted separately. You hear the moment a request has moved past what was quoted.
Where this fits best, and where it fits least
The first call locates a problem, so it works best when automation already looks worth doing and the open question is which part goes first. It is a poor answer to a pure price comparison, because the cheapest quote will always come from somewhere else. An idea with nothing built yet is exactly what the viability assessment is for.
Which route applies is a technical question.
It turns on which systems hold the data and how often the work runs. Both come out of the first call.
Free · 5–10 minutes · by phone