Church admin

Is your church office held together by forms and email?

Churches run on processes nobody ever wrote down, and they all land on whoever’s in the office. I lead a production team at my church, so I’ve seen it up close. Tell me how yours works and let’s have a chat.

Sound like your office?

Already built: Five apps from running production at my church, for volunteers with no training. The office side is the same kind of problem.

What it could look like

One way in

Each kind of request comes in the same way and goes to the right person by itself.

See where it’s up to

Anyone who needs to can check on it, without asking the office.

Written down at last

The process in one person’s head, turned into steps someone else could follow.

What people ask first.

Our church admin lives in one person’s spreadsheet. Is there a better way?

Usually, yes. Planning Center, Elvanto and the rest cover the big things, but every church has a process they leave out: event sign-ups, connect cards, a budget only one person can read. That’s the piece I build, so it sits beside what you already use and anyone on the team can pick it up.

We already use Elvanto or Planning Center. Do we have to change?

No. They’re good at what they do. This is for the process they don’t cover, and it would sit beside what you already use.

What does it cost?

It depends on the job, so there’s no price list. First we talk through how you work and where it hurts. That’s a conversation, not a sales pitch. Then you get a quote that lists the cost and exactly what’s included, and nothing is built until you approve it.

Is my problem too small?

Probably not. A five minute job someone redoes every week used to cost more to fix than to put up with. AI has lowered the cost of building good software, and I still design, check and test every part of it. Now leaving the problem alone is usually the expensive option.

Will my team actually use it?

Most of what I’ve built is used by church volunteers who get no training at all. If a tool hasn’t paid off in the first two minutes, nobody opens it again, so that’s the bar.

What happens after it’s handed over?

If something needs fixing or changing, email me. I’ll look at it, tell you what it’ll take, and start once you’ve approved the quote.

Who owns it?

You do. Your data and the code belong to your business, so you’re never stuck with me. If it’s a tool several businesses share, there’s a monthly fee instead, and we’ll agree an arrangement that works for both of us before anything starts.

Have a problem like this?

Let’s have a chat. It goes straight to me, and I’ll reply by email.

Other problems I fix

Fynn Projects is an Australian one-person software business, building custom apps, websites and automation for small businesses, trades and churches.

Fynn Projects home