I'm Maor. I connect your CRM, WhatsApp and AI assistants into one workflow, so inquiries reach the right person, information stays current and your team has time for customers.
Good tools. The difference is how they work together.
Copying, chasing, searching, updating. The small tasks add up. This is where we start making room.
Four ways to turn recurring work into a workflow that works for you.
Choose a workflow. Follow the information, see what runs automatically and where your team takes over.
From a website inquiry to a calendar meeting. The context travels with it.
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 system for a real-estate team, independent products and a tool for an academic course. Different starting points. Each built around the people using it.
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.
Leads, meetings, calls and tasks come together in one Hebrew system built around a real-estate sales and investments team.
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 product I’m building with a partner: Garmin data becomes running analysis, with calculations in code and explanations from AI.
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.
From an exercise submission to checks and feedback. A system that gives course staff more time to teach and keeps grading with the lecturer.
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 independent product in development: an app for small local jobs, designed around verified identity and a defined payment flow.
From the first conversation to everyday use, you work directly with me and know what comes next.
Walk through a real process: who does what, which tools they use and where work gets stuck.
You show me. I map it.
Define what gets built, what runs automatically and which decisions stay with your team.
I propose. You approve.
Try working pieces against cases from your business, including exceptions and failed steps.
I build. You give feedback.
Roll out in stages, with a walkthrough and documentation, alongside the tools already in use.
I guide. Your team starts using it.
See what works and what needs adjusting. Monitoring and maintenance are agreed in advance.
I make adjustments. You share what you see.
Usually, we can start with what you have: CRM, spreadsheets, calendar, phone system and WhatsApp. We check what each tool supports and which connections are missing. If a system needs replacing, we plan a staged move alongside existing work.
Tools like Make work well for connecting workflows across systems. Custom development helps when the logic is more involved or your team needs its own interface. I choose based on the need, maintenance and tools already in use, and sometimes combine both.
Summarising conversations, understanding free-text inquiries and extracting tasks from messages. A clear, simple rule usually needs only regular automation. We always define what the assistant may do and which decisions need a person’s approval.
We define the handoff rules together: for example, when a customer asks for a person, a question falls outside the workflow or a commercial decision is needed. Your colleague receives the conversation and a summary, ready to continue with the context already collected.
Pricing is per project, once we understand the process and define what will be built and which systems it will connect. Before starting, we agree on the scope, rollout and what monitoring and maintenance include after launch.
I'm an independent developer in Israel with a background in mathematics and programming. I like taking a complicated process apart, understanding what needs to happen and building a simpler way to do it. From the first conversation to the tool in your hands, I'm your point of contact.
