WhatsApp booking
Never lose a WhatsApp booking while you are busy with a client.
Capture the request, collect the necessary details, create the booking and send reminders without requiring an immediate manual response.
Business Automation
Your business runs on manual work. It doesn't have to.
I design and build automation systems around the way your business actually works, so requests are not lost, repetitive tasks disappear and your team can focus on customers.
The starting point
Where businesses lose time
What holds most small businesses back is work that has to be done by hand, every day, by someone who could be doing something else.
01 / Lost requests
Messages arrive at the worst possible moment
A booking request comes in while you are with a client. By the time you answer, the customer has already asked someone else.
02 / Re-typing
The same data is entered three times
Once in the chat, once in the calendar, once in the spreadsheet. Every copy is an opportunity to lose or corrupt something.
03 / Follow-ups
Nothing moves unless a person remembers
Confirmations, reminders, approvals and status updates depend on someone noticing that they are due.
04 / Reporting
Numbers exist, but nobody has time to assemble them
The data is already in your tools. Turning it into a usable report is still a manual evening of copy-paste.
Outcomes
What automation is actually worth
What matters is what a bot, an integration or a script changes on an ordinary working day.
Lead handling
Every new lead reaches the right person.
Collect requests from forms, messengers or ads and automatically route them to the correct workflow.
Reporting
Reports should be ready before you open the spreadsheet.
Collect data from multiple sources and generate recurring reports without copy-paste work.
Internal operations
Repetitive internal tasks become predictable workflows.
Notifications, approvals, document generation, data synchronization and routine checks can run automatically.
Scope
What I automate
Whatever the interface looks like, the deliverable is the same: a workflow that keeps running when nobody is watching it.
Build, buy or ignore
Not every process is worth custom code
For each process you describe, I'll tell you whether it's worth building, buying or ignoring. Only one of those answers means paying me to build something.
01 / Buy
A ready-made service already does it
Booking pages, schedulers and form-to-CRM tools cover many common workflows for a monthly fee. If one fits the way you work, use it.
02 / Build
Your process does not fit a ready-made tool
It runs across systems you already use, follows rules of your own, or the tool makes the team work around it. Then I build the smallest system that does the job.
03 / Ignore
The task is not worth the money
If a task takes a few minutes a week, automating it can cost more than it will ever save. Then the answer is to leave it as it is.
Process
Analyze · Design · Build · Handover
Four steps, in that order. I don't start building until I understand where the process loses requests, time and money.
Step 01
Analyze
I map the current workflow and find where time, requests or information are being lost.
Step 02
Design
I propose the smallest system that fits the team, tools and budget.
Step 03
Build
I implement, test and document the solution.
Step 04
Handover
The system should continue working without permanent dependence on me.
Workflow examples
What a finished workflow looks like
Two common shapes. Yours will be different in the details. The structure rarely is.
WhatsApp request
collect service and time
check availability
create booking
send confirmation
send reminder
handle cancellation
Form or message
validate data
create CRM lead
assign owner
send notification
track response
How we start
You describe one process: where the request arrives, who touches it and where it gets stuck. I map it and come back with a picture of where that process loses requests and time, and the smallest automation worth building first. From there, you decide whether we build it.
FAQ
Questions I get before we start
Usually no. The first option is to connect the tools you already use.
No. I build the workflow, and a bot is one of the interfaces it can have.
Yes. The solution should match the scale and economics of the business.
No. A description of the current process and problem is enough for the first discussion.
How we work together
The terms, before you have to ask
You work directly with the engineer who reads and writes the code. No account managers, no juniors in between.
01
The code is yours from day one
Repositories, servers and accounts stay in your name. I work with the access you grant, so nothing depends on me holding the keys.
02
NDA on request
If the project needs one, send your NDA and I sign it before we go into details.
03
Work in steps, estimated in writing
Each step starts with a written estimate of what it covers and what it costs. After each one you decide whether to continue.
04
Prices and invoices in USD
Every estimate and every invoice is in US dollars.
05
UTC−3
My working hours overlap with business hours in both the US and Europe.
06
A reply within one working day
Every request gets an answer within one working day, including the ones where the answer is that I am not the right person.
Case studies
When the process that was missing was being told
Sometimes the step a business is missing is the one that tells a person anything happened at all.
The automatic updates that kept switching themselves off
A property site's price importer dropped developers and told nobody. Rebuilt so bad files are held back and every failure reaches a person.
The login emails stopped and nobody was told
The worker logged every failure. The business found out a week later, from a customer.
Tell me what your team still does manually.
Describe the process in a few sentences: where the request arrives, who touches it and where it gets stuck. I'll tell you whether it is worth automating and what the smallest useful first step would be.