DEMO
Roofing
The lead that answers itself
Form to classified intent to a written reply to a booked slot, with the whole chain logged. Built to be narrated live on a call.
Target reply
Under 90s
14,000
lines of production code shipped, with row level security policies that actually hold. Not a tutorial clone.
10,950
rows of analytics pulled automatically, reaching back two years, with nobody opening a dashboard to do it.
17 years
in operations before I automated any of it. I have done the manual version of most of this work myself.
System 01
A lead comes in. Ninety seconds later it is a booked job.
Not an autoresponder. The system reads what they actually wrote, answers the thing they asked about, and puts it in your calendar.
SPEED TO LEAD / LIVE
00:87
elapsed
010.4s
Form submitted
“Roof leaking above the garage, been two days”
021.2s
Intent classified
emergency
repair
03writing
Reply written
“Two days with an active leak needs looking at today, not Friday. I have 2pm open.”
04sent
Booked and logged
Calendar hold, CRM contact, owner notified.
RUNS ON
n8n
GoHighLevel
Claude
Supabase
System 02
Every number you have, in one place, pulled while you sleep
Each platform holds a piece of the picture and none of them talk. I put all of it in one database daily, so a decision takes a glance instead of an afternoon.
Reach, 30 days
48,210
+18% on baseline
Followers
11,127
+142 this week
Best hook angle
Price reveal
2.4x the next best
Data freshness
6h ago
automatic, daily
Views in the first 48 hours, per post
This month
Baseline
Figures shown are illustrative of the report shape. Real client data is never published here.
Not a mockup
Open one and look inside
These are the systems, not stock screenshots of somebody else's template. Click any of the three.
Receipts
What I have actually shipped
Labelled honestly. Demo means I built it to prove the mechanism, not for a paying client.
LIVE
Social commerce
Two years of analytics, unattended
A daily job that stores every metric as a snapshot instead of a reading, so this month is genuinely comparable to last month.
Rows stored
10,950
SHIPPED
Mobile app
A whole app, to prove I could
React Native and Supabase, real row level security, and a written decision log for why each policy exists. Survives contact with real data.
Commits
91
How it goes
Three steps, and you see it working before you commit
01
We find the bottleneck
One call. I ask what you did yesterday that you also did the day before. That is almost always the thing worth automating first.
02
You watch it run
Not a slide deck. I build the smallest working version against your real setup and show it doing the job before you pay for the rest.
03
It keeps working
Handover with documentation you can read, and a maintenance option if you would rather I watched it. Systems break quietly. Somebody has to notice.
Who is behind it
I spent seventeen years doing the work I now automate
Call centre at eighteen, then three years as an executive assistant on a graveyard shift, which is exactly where you learn how much of a working day is the same eight tasks in a different order. I am an I.T. undergrad and I have been on a computer since I was six, so when I say I will build it rather than buy it, that is not bravado, it is the part I enjoy.
I work from the Philippines on GMT+8, which lines up with mornings in Australia and evenings in North America. Everything gets documented, because a system only one person understands is a system that dies the day they stop answering the phone.
n8nMakeZapierGoHighLevelSupabaseNext.jsReact Native
Tell me the task you are sick of doing.
Thirty minutes, no deck. If I cannot see anything worth automating I will tell you that, and you will have lost half an hour.
Book a 30 minute call
No deck, no sequence.
Not ready to book? It's all good. Tell me the task you're sick of and I'll send back how we'd approach it and I'll tell you whether it's worth automating. Sometimes the answer is no.