Process documentation

Wrote the SOP? Now make it the way the work gets done.

A process map or an SOP is a great start. Then it sits in a folder while the work happens the old way. An app can be the process: the steps in order, nothing skipped, nobody needing to remember.

Sound familiar?

Already built: Booth Check turns a production Mac’s start-up routine into checks that run themselves.

What it could look like

Steps you can’t skip

The process on a screen, in order, ticked off as it’s done.

Knowledge out of one head

What the experienced person knows, built into the tool itself.

A record that it happened

Who did what and when, without a separate log.

What people ask first.

We wrote the SOP. Why isn’t anyone following it?

Often because it describes how the work should go, not how it really goes. I work out what actually happens first, then build a tool that walks the team through the real version, so following the process is the easy way.

Do we need to document everything before you start?

No. If it’s only in someone’s head, working it out together is part of the job. If you’ve got a map or an SOP, that’s a head start.

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