Automation systems built on n8n
Your clinic does not have a staff problem. It has a follow-up problem.
A patient books on Tuesday and does not arrive on Friday. An enquiry lands at 9pm and gets answered at 11am, after they already called somewhere else. None of that needs a person. It needs a system that runs whether anyone remembers or not.
Where the money leaks
Friday, 10:30
The chair sits empty. Nobody called to confirm on Thursday, because Thursday was busy.
Tuesday, 21:04
An enquiry arrives after hours. It waits in an inbox until the morning, and by then it is somebody else's patient.
Every week
A happy patient walks out and is never asked for a review, so the listing stays quiet.
What I build
Custom systems, not templates off a shelf.
How it works
01
You message me
Tell me the task somebody keeps doing by hand. Over text. There is no call to book.
02
You get a written scope
What I will build, what it will do, what it costs. We disagree on paper, before anything is built.
03
I build and test it
Every branch gets run, not assumed. You see the executions, not a claim that it works.
04
You get the keys
It runs on infrastructure you own, with written handover docs, so the next person does not need me.
Work
Three systems I built and tested end to end.
These are demo builds on my own infrastructure, not client engagements. Every number below came off a real execution. I would rather show you that than borrow somebody else's case study.
Zapier stack rebuilt on self-hosted n8n
A multi-step Zapier automation running at 75 dollars a month, rebuilt to run self-hosted. Every conditional branch preserved rather than simplified away, then tested branch by branch.
Lead qualifier with no human triage
Incoming enquiries scored and classified by a language model, then routed automatically. Nobody reads a form to decide where it goes.
WhatsApp appointment reminders for a dental clinic
Reminders sent on the WhatsApp Cloud API the day before each appointment, with a summary back to the owner. Built twice, once reading a spreadsheet and once a calendar, so a clinic keeps whichever it already uses.
Pricing
Clear numbers, decided before I start.
Single system
₹12,000 setup, then ₹3,000 per month
- One automation built, tested and documented
- Written scope before the build starts
- Runs on infrastructure you own
- Monthly hosting, monitoring and fixes
Best when one specific thing keeps getting forgotten, like confirmations or review requests.
Full clinic stack
₹25,000 to ₹35,000 setup, then ₹5,500 per month
- Several connected systems, scoped together
- Reminders, intake and follow-up working as one flow
- Written scope and handover documentation
- Monthly hosting, monitoring and fixes
Setup varies with how many systems connect and what your existing tools are. The exact figure is fixed in the written scope, never after.
Straight talk
I am 18 and I work solo. You deal with the person who builds the thing, not an account manager, and my rates are lower now than they will be in a year.
It also means I do not have a client roster to show you yet. The three builds above are my own demos, tested on my own infrastructure, and I have labelled them that way rather than dressing them up as client results. There are no testimonials on this page because I have not earned any yet. When a paid build produces a number worth showing, it will replace one of the demos here.
If something in your clinic runs on somebody remembering to do it, send it over and I will tell you straight whether it is worth automating.
Start here
Tell me what keeps needing a human to remember it.
Written reply, usually the same day. WhatsApp is the fastest way to reach me. Phone works too if you would rather talk.
Message on WhatsApp