Nobody is measured on it
No vendor loses a renewal because two of your systems disagree.
Volvo Ebal · open for new projects
I build systems that reduce manual work for busy business owners. GoHighLevel, n8n, and Claude Code: three stacks I use that help my clients scale by giving back their time.
Six businesses since 2023, and every number on this site came from the person who paid for the work.
Book a call › Follow the route ↓ Watch the intro ›
Volvo EbalWhy it stays broken
Your CRM has a rep.
Your forms have a vendor.
Your ad platform has a dashboard and somebody whose job is that dashboard.
The handoffs between them belong to nobody, so they get done by a person instead, quietly, forever.
No vendor loses a renewal because two of your systems disagree.
Nothing alerts. A lead just does not get called, and the month still closes.
The most reliable person you employ quietly becomes the integration.
That gap is the entire job.
The route
Six stops. Each one says what I do there, what is proven, and what is not on the route. Every figure was stated by the person who paid for the work, not estimated by me. Their words, not mine.
Open a tool's page to watch its builds run, step by step, from the thing that sets them off to the thing they leave behind. Client names are withheld throughout.
A 9pm inquiry gets a 9pm answer. The phone, the website chat, a voice agent that picks up, and the site they land on.
Stop 1 › 2Follow-up that runs itself: pipelines, segmentation and reactivation that fires, so nobody is chased after they say yes.
Stop 2 › 3Your tools stop disagreeing. Records move between the CRM, the sheets, the inbox and the ad platforms on their own.
Stop 3 › 4The piece that does not exist. When nothing on the market does the job, I build it with Claude Code.
Stop 4 › 5A content pipeline that runs without you watching it, and a video editor for the clips.
Stop 5 › 6A silent failure is worse than no automation at all, so what I build tells somebody when it breaks. Audits, repair, ongoing care.
Stop 6 › –Logos, running your ads, reputation management. If what you need is a designer, I will tell you that on the first call rather than in the third week.
Who I work with ›Stop 1 of 6Capture
Three ways a customer gets in, and every one of them is answered: the phone, the website chat, and an AI that phones people for you. Plus the one word that stops everything.
What happens when the phone rings.
Open and shutThe chat that books without a person.
144 chats, 11 bookedAn AI that phones people for you.
10 stops, 13 notesThe way out.The one word that stops everything.Read how the word switches everything off ›
"We were bleeding leads after hours and didn't even know it. Volvo fixed that. 40% more leads captured the first month alone."Kevin Zucker, COO · Omni Power Solar
A site is where the first door opens, so I build one when the route needs it. Each was built to a real reference in a different industry, then rebuilt for how the web works now.
PropertyA coastal development launch. Six rooms, a giant arch, and every photograph drawn or shot for it.
Open it ›
DentalA clinic site built around comfort: services, real questions answered, hours and a booking path.
Open it ›
TradesA dated contractor site rebuilt for now, with a thermostat that falls from 88 to 72 as you scroll.
Open it ›
HospitalityA cafe with a working shop: menu, products, and a bag you can actually add to and empty.
Open it ›Stop 2 of 6Convert
Pipelines, segmentation and reactivation that fires. Leads move without anyone pushing, nobody is chased after they say yes, and every conversation has an exit.
One build, end to end
Follow-up that runs on its own.
16 workflows"Quoting used to take forever. Now it's under 10 minutes and nobody has to touch it."Rob De Ciantis, Owner · Corlan Electric
Stop 3 of 6Connect
Records move between the CRM, the sheets, the inbox and the ad platforms on their own. Broken workflows get found and repaired.
Tools that do not talk, made to. Nothing is done twice. It posts, files and writes while you sleep.
The wiring between everything else.
19 scenariosThe jobs that have to wait, retry or loop.
9 workflows"Handed him a messy CRM and he gave us back 12 hours a week. Three campaigns running on their own now."Martin Williams, CEO · Leadworx.io
"Five platforms, one clean system. Data stopped getting lost between tools."Seth Royce, Senior Developer · Godzilla Digital
Stop 4 of 6Build
When nothing on the market does the job, I build the piece. Nothing here is a mockup: the live ones load in your browser and the rest run every day.
An AI SMS agent that texts a CRM's dead leads, qualifies the replies and books the calls.
Open it ›Backs up an iPhone's photos and video so the storage can be cleared. Installs to the home screen.
Open it ›An offline paint-by-number game with fifteen generators, built for my wife and daughter.
Scan a QR code and the phone sends files into a folder on the PC, realtime, no app installed.
Raw clips in, captioned vertical cut out. Cuts dead air, times captions to the word, ducks the music.
A voice-driven operations dashboard with a daemon that runs the work and reports back.
Six of the eleven are shown here.
Stop 5 of 6Create
A pipeline that posts on a schedule nobody has to watch, and a video editor that turns raw clips into a captioned vertical cut. The editor runs like this.
"I stopped worrying about content schedules the day he set this up. 20 posts a week, automated."Tina Sivaraj, CEO · Heartaccent
The part with no client numbers yet
Concept work lives on its own page. It carries no client-stated figures, and I would rather say so than dress it up.
See the creative work ›Stop 6 of 6Keep
Anything I build reports to a channel you already read, and says so when it fails. Handover comes with the runbook, and if it breaks it tells somebody.
"Found issues in our automations we'd been ignoring for months. Fixed 8 workflows, cut our error rate by 70%."Dom Ricci, Team Lead · Your AI Army
The stack
Six tools carry most of the work, and each one is here because it was the right one for that job rather than the one I happened to know.
The payoff
Same customer, same hour. This time someone is there.
Week 0
Twenty minutes on a call. You describe what eats the most time, I tell you whether it is worth automating, and I say so when it is not.
Week 1
Not a platform, not a transformation. One process, working, in your own tools, where you can watch it run.
Ongoing
Handover with the runbook. If it breaks it tells somebody, because a silent failure is worse than no automation at all.
Three ways this usually starts.
Shape 01
The single worst bottleneck, end to end, inside your own tools. About a week.
Shape 02
The system, the app if one is needed, the migration and the handover. Three to six weeks.
Shape 03
It breaks, I fix it. Your process changes, I change it. Monthly, cancel whenever.
What it costs depends on your stack and how much of it already works. I will give you a number on the call, not a package page.
Who this is for
The retainer is signed and the build is queued behind three other things. I build it under your name, on your stack, and I do not appear on the client call unless you want me there.
Leads arrive, somebody retypes them into three places, and the one that came in at 9pm is gone by morning. What is missing is not a tool. It is the thing between the tools, and nobody owns it.
Not for: logos, or running your ads. I do the plumbing, not the paint. If what you need is a designer, I will tell you that on the first call rather than in the third week.

Who I am
The part worth knowing
I will tell you when a process is not worth automating.
It has cost me work twice. I would rather lose the build than wire something you will turn off in a month.
The awkward questions
Usually it did not break, it stopped being watched. Anything I build reports to a channel you already read, and says so when it fails. A silent automation is worse than none, which is why failure is a feature I build on purpose.
Good. Simple setups rarely need me. I start by wiring one process end to end rather than mapping everything, so you see it working in week one instead of reading a discovery document in month three.
Then we skip the audit. Send me the process, I will tell you on the call whether it is worth automating, and I will tell you when it is not.
An agency sells you a retainer and a project manager. You get the person who builds it. And every build I have shipped is on this site with the part that went wrong, which is not a thing a brochure can fake.
Then the honest answer may be no. If the process does not cost you real hours or real leads, automating it is a hobby. Bring the one that hurts and we will size it in twenty minutes.
That is the whole job. GoHighLevel, HubSpot, n8n, Make, Zapier, Apify, Slack, OpenPhone, Intercom, Monday. If it has an API or a webhook, it can be wired in. If it does not, I build the missing piece.
Next
If it is repetitive, has a clear input and a clear output, and a person is doing it by hand, it is probably mine. Twenty minutes, and you get a straight answer about whether it is worth building.
Book a call › Read the CV › Download resume (PDF) ↓
Volvo Ebal · Philippines, working your hours · © 2026