Prepared for St George's
The role needs a builder. Here's the proof I'm one.
The Communications and Operations role really comes down to a handful of things. Online giving that actually works. A website someone looks after. Welcome and admin that run on their own. Finances you can read at a glance. I've already built and shipped a version of every one of those, and everything I link below is real and running right now.
Online giving that actually works
Wire Airwallex into the church website so people can give by recurring card or PayNow, and have it reconcile itself and send donor statements.
A paid payment integration, already live
I got paid to build the same shape of thing for a real shop. Card payments, plus a nightly sync across about 91,000 products, live in production right now, with reconciliation and an alert when something fails. Airwallex is basically Stripe's cousin. So the giving side isn't something I'd be working out on the job. I've done it, for money.
Build and run the website
Build, run and improve the church site, and put the giving pages on it.
A web and automation practice, with live sites
I run an automation studio for small businesses, GlideOps, and I build and ship real sites (glideops.co.uk, jordanbee.cloud, this one). A church website is the kind of thing I do already.
Welcome and comms that run themselves
Newcomer follow-up, registrations, rotas, email and WhatsApp workflows, so the front door and the admin stop leaking.
Assistants and workflows I run every day
I built an assistant I text on WhatsApp that handles jobs and reminders, and I run automated email triage and follow-up. Getting newcomer follow-up and admin to just happen on their own? That's normal work for me.
Clear finance and reporting
Reconciliation, giving statements, and simple dashboards the treasurer and PCC can actually read.
Clean dashboards out of messy data
I'm good at pulling clean dashboards and reports out of messy inputs. I've built a document-extraction engine that turns paperwork into tidy PDF and spreadsheet reports, and live financial dashboards fed straight off an API. Giving reconciliation and clear statements are the same job.
The IT person they don't have yet
Someone who can build and look after the systems, and be trusted to finish them and check they work.
Everything here is live and tested
None of this is a folder of mock-ups. The systems run, and I check my work properly before I call it done. What the church has been missing is one dependable person who can build the giving flow, look after the site, wire up the automation, and keep it all running. That's the role. It's what I do.
If you're saying a word for me, all of this is true and easy to repeat
- I've seen his work up close. He's not learning this on the job, he already builds this stuff and runs it for real businesses.
- That online-giving piece you need? He got paid to build the same shape of thing for a shop, card payments and reconciliation, live in production. Wiring your Airwallex into the site is right in his wheelhouse.
- Websites and back-office automation are his actual work, that's GlideOps, not a weekend hobby.
- He's reliable and he's thorough. Everything he showed me was live and working, not a slideshow.
Or open the chat in the corner and ask it what I could do for a church website and online giving.