I connect the tools, conversations and processes your business runs on.
Illustration: an inquiry from Dana Levi arrives from a website form, a CRM record is created and routed to Yoav, a meeting is scheduled for Thursday 17:30, and Yoav receives the context before he calls.
One inquiry, written in six places, becomes one route that ends with a person.
Illustration: the same inquiry is written in six places — form, CRM, spreadsheet, WhatsApp, calendar and a document — then gathers onto one route that ends with Yoav and the context ready.
What comes in, what runs alone, and where a person decides.
A website inquiry becomes a scheduled meeting, with the context attached.
New inquiry received
Dana Levi asks about a 4-room apartment in Ramat Gan. Tuesday, 09:14.
Lead created in CRM
No duplicate found. Source: website form. Status: New.
Assigned and acknowledged
Routed to Yoav by area. Dana gets a WhatsApp confirmation, 09:15.
Yoav calls back
He sees the inquiry, the property and past contact before dialling.
Meeting scheduled
Thursday 17:30 in Google Calendar, reminders set for both sides.
3 steps the system did on its own · 1 decision by a person
A signed agreement becomes a customer record, tasks and a welcome message, without retyping.
Agreement confirmed
Noa Peretz of Peretz Interiors approves the service agreement. Sunday, 11:40.
Customer record created
Contact, company and agreed scope copied from the form. Stage: Onboarding.
Tasks opened
Three onboarding tasks with due dates, owner Maya. Kickoff flagged.
Maya reviews and adjusts
She checks the scope, moves one date, approves the welcome message.
Welcome sent
Email and WhatsApp at 12:05. Kickoff invite in Noa's calendar.
3 steps the system did on its own · 1 decision by a person
The manager gets a short summary that points at what needs attention.
Yesterday's activity collected
07:00. Fourteen open leads, six calls, three meetings, two tasks overdue.
Exceptions identified
Two leads silent for five days. One meeting without a follow-up task.
Summary drafted
A short report grouped by owner, sent to Eran at 07:30.
Eran decides
He reassigns one lead, calls the other, closes a finished task.
Changes recorded
CRM updated from his replies. Tomorrow's report starts from the new state.
3 steps the system did on its own · 1 decision by a person
A client system, two products, a university course, and labelled concepts.
Recreated CRM screen for a real-estate team: a lead list, an open lead drawer with property details, tasks, a call log and a scheduled meeting.
One Hebrew CRM built around the team, with calendar, WhatsApp, phone and AI assistants connected to it.
Illustration: a finished run arrives as raw Garmin data, code scores it (scoring, de-duplication, training load, patterns), the AI explains it in plain language, and Maya the runner decides what to do with the advice.
A running coach built with a partner. Code does the math; AI explains it.
Illustration: an exercise submissions queue — pull requests come in, tests and drafted feedback go out, and a submission whose test timed out is flagged for the lecturer, who decides the grade.
Pull requests in, tests and drafted feedback out, the lecturer decides the grade.
Illustration: a small job is posted, a verified helper takes it, payment is secured before work starts and released on completion, an attempt to share a phone number outside the app is hidden, and the job owner leaves a fair review.
An app where strangers get small local jobs done and the money moves safely.
Five steps, each with a clear owner. You always know what's next.
We map how the work happens today: who does what, and where it sticks.
You explain. I ask and map.
I propose what to automate, what stays a human decision, and how tools connect.
I design. You review and approve.
I build and test with realistic data, including what happens when a step fails.
I build. You check it against real cases.
The new flow goes in stages, next to how you work today.
Together, with your team using it.
After launch I watch for errors and gaps, and we agree on maintenance.
I monitor. You tell me what changed.
Usually not. Most of my work connects what you already have: CRM, spreadsheets, calendar, phone system, WhatsApp. Replacing a tool happens only when it genuinely blocks the process, and then in stages, with the old system running alongside.
Both. Platforms like Make are quick to set up and easy to inspect. Custom code comes in when a flow needs logic a platform can’t express, or the team needs an interface. I recommend the simplest option that holds up.
AI helps when the input is messy: a voice message, a free-text inquiry, a thread to summarise. It doesn’t help where a clear rule exists; plain automation is cheaper and more predictable there. Decisions with weight stay with a person.
Whenever your rules say so: the customer asks for a person, the question is outside the flow, the tone suggests frustration, or a commercial decision is needed. The handoff includes the conversation and a summary, so nobody starts from zero.
Scope is written down before building. Pricing is per project, by inquiry. Rollout is staged, with a walkthrough for your team; accounts and data stay in your name; and we agree in advance what I monitor after launch.
Hi, I'm Maor, an independent developer in Israel. You work directly with me, from the first conversation to the last deployment.
