What I actually do
Onboarding, support ticketing, progress tracking, content repurposing, lead research. The admin layer that grows faster than the business does, and that nobody wants to own.
I spent about two years running that layer daily inside a paid community of several hundred members. Answering questions, onboarding people, recording tutorials, keeping the classroom current, and building automations for whatever kept coming up. The community went from around 200 members to around 900 and churn fell from 24% to 9%.
That's where the approach comes from. Most people who run community support can't build the automation that would stop the ticket happening again. Most people who build automations have never sat in the inbox. Doing both, every day, is how you learn which problems are worth a system and which ones just need a better answer.
How I work
- On your accounts, not mine. Every system I build runs in your Make, n8n, Airtable and whatever else you already pay for. Nothing is hosted behind me.
- Handed over, not held. You get a walkthrough recording and documentation, so you or anyone on your team can change it later without me.
- The audit is honest. If nothing is actually broken, I'll tell you that and leave it there. That happens, and it's a fine outcome.
- Built before billed. On the coaching offer, the first system is built on your accounts before any money changes hands, and paid for only once it has run.
Where I am
India, working with clients in the UK, the US and Europe. Two years independent, after the community operations work that started all of it.
What I use
n8n, Make.com, Airtable, Zapier, the Claude API and Claude Code, plus whatever the job needs. The tools matter a lot less than knowing which part of the problem shouldn't be automated at all.
Start with the free audit. I'll look at your setup and tell you where the time is going. No obligation, and no pitch if there's nothing to fix.