A painting-inspection consultancy
I build and run the automation behind it. A site visit, with its voice notes and photos, comes back as a finished inspection report. The month's jobs land in one dashboard instead of a pile of PDFs.
About
An n8n Ambassador in KwaZulu-Natal, South Africa. I study one repeated job at a time, count what it really costs, then build the workflow that takes it off a person’s plate. It stops for a human where judgement is needed.

Most automation pitches start with the sale. I wanted to start with the homework. So NearTrigger is a research imprint first: I pick one niche business grind — the same boring job a team does over and over — and I study it properly. Where the time goes, what it costs, what the rules say about it. Then I publish the field report, free to read.
Every report ends in the same place: the n8n workflow that ends the job. Not a slide about what’s possible. The actual machine. If the grind turns out to be yours, I build the same shape on your stack. You keep the judgement; the machine takes the typing and the sums.
The whole thing only works if it’s honest. So every number in a report comes from a named source. Estimates are labelled as estimates. I don’t invent clients or dress up a demo as a screenshot. If I couldn’t verify it, I left it out. That constraint is the point. It’s what makes the research worth trusting.
n8n is the open workflow tool I build everything on. Being an Ambassador means they recognise the work I do with it in the community here: teaching it, writing about it, and shipping real systems on it. It’s also why you’ll see n8n named openly across this site. I’m not a reseller and this isn’t a paid endorsement. It’s the tool I actually use.
My public Ambassador profile on n8n.io is still on the way. When it’s live, I’ll link it straight from here so you can check it yourself.
There’s no team to hand you off to. I do the research, I build the workflow, and I’m the one who answers when something breaks.
I’d rather pilot one job on a handful of cases than promise the moon. You see it work on your own data before you trust it on everything.
The machine runs on your stack, on your n8n. You’re not locked in to me. If we part ways, the workflow stays and keeps working.
What I build with
Real systems for real operators. I’ve kept the names off out of respect for the businesses. Happy to walk you through any of them on a call.
I build and run the automation behind it. A site visit, with its voice notes and photos, comes back as a finished inspection report. The month's jobs land in one dashboard instead of a pile of PDFs.
Tablet forms from the factory floor flow into a checked database, then surface as live production numbers and a daily report. I built it and handed it over running.
A food-safety and traceability record system built to stand up to an ISO 22000 audit: every document versioned, every change accounted for.
A system that proves who really sat through a professional conference: scan in, scan out, certificate at the end. Built and tested. I'm lining up the first event to run it live.
A check that tells a managing agent, in one pass, whether a contractor's registrations and cover are real and current. It's drawn from a method that already works by hand.
Free 20-minute month-end teardown — no client data shared.Tell me what your team keeps re-keying and I’ll show you where a workflow earns its place, and where it doesn’t.
Or read Field Report No.01 first.