What people ask me before we start.

The productized system is ₪4,800 one-time, built in 14 working days. If you need a custom build, it starts with ₪1,800 process mapping, credited in full against the build, and the build itself is priced only once there's a map. Optional monthly partnership starts at ₪540. The full price list is public on this site.

Yes. Payment structure is agreed on the call, based on what makes sense for both sides.

You won't know for certain, and I won't promise you a number. What you can do is calculate what manual operations cost you today — unanswered leads, no-shows without reminders, clients who quietly went inactive. There's a calculator on the Hebrew site that does this with your numbers, using deliberately conservative assumptions.

20 minutes, free, no obligation. We talk about how the business runs today, where it gets stuck, and what costs you the most time. At the end I tell you whether it fits and which path — and sometimes the answer is that an off-the-shelf tool solves it for a fifth of the price.

The productized system: 14 working days from signature to live. Mapping on the custom path: about a week. The custom build itself depends on scope, and you get the exact timeline in the quote that follows mapping, not before it.

Mostly at the start: a 20-minute call, then a short questionnaire and two or three working sessions in the first fortnight — roughly two to three hours total. After that you're mostly approving. I don't need you constantly available, but I do need an answer within a day or two when I ask something, or the timeline slips.

Small changes in the first month are part of the handover. After that, if you have monthly partnership it comes out of the development hours in your tier; if you don't, it's separate work priced by scope. The system is built so it can be changed without being taken apart.

That's exactly the audience: service and knowledge businesses with real one-to-one meeting volume — clinics, consultants, coaches, course creators, accountants, lawyers. The signal isn't size, it's this: if you're in a meeting, does the business stop? What doesn't fit is a pre-revenue startup, a sole practitioner with very low client volume, or a digital agency.

Yes, and that isn't a polite answer. You describe how the business works, I translate it into a system. You don't need to know what an API is. What you do need is to be able to explain what happens at your end today, and you know that better than I do.

Only where the business is essentially Israeli and operates in Hebrew. The service is built around how Israeli businesses work — WhatsApp as the primary channel, Israeli invoicing, a Sunday-to-Thursday week. Outside that context I'm probably not the right choice.

You do. Accounts are opened in your name, the data is yours, the code is yours. You get a handover document explaining how each component works so you can pass it to someone else if you want. The mapping document is yours too — including if you take it to another supplier and don't continue with me.

The system runs on standard, widely used tools, not a closed platform of mine. Every automation is documented. I'd rather you stay because it's worth it than because you have no choice — which is also why partnership is monthly rather than an annual commitment.

A fair question, and it's why everything is documented and runs on standard tools rather than something only I can maintain. The handover document is written assuming someone else will need to pick it up. It's also why I don't take on more concurrent projects than I can actually maintain.

I don't sell a money-back guarantee, because it's an easy promise to make and a hard one to honour. What I do offer is what's actually true: scope and price fixed before we start, one accountable person, your code and your data, a 30-day bug warranty, and a fit call that can end in "this isn't for you" — which is a legitimate outcome.