How I work.
Three stages, no surprises. At every point it is clear what the next stage is, what it includes, and how much it costs. There is no running clock and no commitment before you know what you are committing to.
Three stages.
- 01
A message
You write on WhatsApp, two or three lines: what the system is, what hurts, and by when. I come back with focused questions or an offer of a short call.
- No charge
- No slide deck
- A clear answer if it fits, and if not, why
- 02
Entry stage
A focused review of the system or the idea, before anyone commits to building. Paid at a flat fee, so you get a real answer and not a proposal written to close a deal.
- What exists, what is missing and what is at risk
- A work plan and a timeline
- A fixed price for the build, split into milestones
Flat fee, agreed before we start · usually one to two weeks
- 03
Build in milestones
Each milestone defines what is delivered and when. You pay per stage, see a working version early, and get regular updates.
- A first version you can touch, early
- Regular updates on what was done and what comes next
- After launch: maintenance, if you want it
What is delivered to you.
- System
- A working system that is live, not files in a folder
- Code
- The complete code, in your repository
- Access
- Servers, domains and service accounts, in your name
- Documentation
- Documentation in Hebrew: how it is built at a level a manager can read, and how to operate it
- Training
- A short walkthrough with whoever will work with the system
- Warranty
- A fix period after handover, defined in the proposal
How I price.
A fixed price, not a clock
Every stage is priced in advance, at a fixed price. You know what it costs before it starts, not after.
An entry stage at a flat fee
For an existing system that already works, the entry is a flat fee agreed in advance: learning the system, setting up an orderly working environment, and giving a clear review of the state of the code and the security. At the end you have a real picture and a plan, even if you decide to continue with someone else.
For a new system, the entry stage is a short specification, priced by scope.
Payment by milestones
The build is split into stages, and you pay for each stage by what was delivered in it. There is no big sum up front.
Changes in scope
A new idea halfway through is natural. It gets a written price before we start it, and you decide.
Maintenance
After launch you can continue on a monthly retainer, in a scope agreed in advance. It is not required, and it is not a condition.
Not everything fits a template
There are other ways to work: supporting an existing team, a retainer with no project, or a single defined task. Each case is its own. So the simplest thing is to schedule a short call, free of charge, go over what you need, and move on from there.
What I do not do.
- Starting to build before I understand what is being built and why
- Working on an open clock with no ceiling
- Building a product for free in exchange for a percentage
- Promising a timeline I do not believe in
- Holding your code or your access hostage
Always.
- A fixed price for every stage
- The code and the access are yours
- Documentation in Hebrew
- One person accountable for the whole project
Start with a message.
Two or three lines about what you need. No long forms and no hour-long introduction meeting.