Frequently Asked Questions

Because I think of so many possibilities, here are some questions I imagine you may have - whether you found me through a letter in your mailbox or just landed here.

Do you do AI?

Sure. I mean, who doesn't? But I take a specific approach: the responsible and sustainable use of AI. I work out which part of a process really needs it, protect the data it's given, confirm the output is correct, and use exactly as much as I need and no more. A lot of problems can be solved with traditional programming, with a sprinkling of AI on top.

There's a whole page on this.

Do I write emails, letters, and documentation with AI?

I try to write by hand where possible and where needed, to properly capture my knowledge and personality.

However, the AI tools come in and restructure, reorganise, and make the content more understandable. They earn their keep when used responsibly, and all results are checked and reviewed afterwards.

You can see my full philosophy on AI.

How can I trust you?

Initially - you shouldn't! What you should do is meet me and see what my actions show you.

My process is to start small: automate small things that help, and then as you see my work and attention to detail, take on bigger projects.

I'm my own harshest critic, and I hold myself to the highest possible standards. You'll see that in my work. My actions will speak for themselves.

You're just one person. What if something happens to you?

I'm a forward planner, always looking at what could go wrong and how to guard against it. Here are the specific ways I protect you:

• You own what I build for you - the code and the documentation. You can take it anywhere, any time.
• I document everything, with the intent that someone else can continue my work. For the fire safety system I worked on, I wrote over 300 pages of documentation describing how it worked, single-handedly.
• You pay for third party subscriptions directly. No markup from me. You control them, and you can take them elsewhere if you need to.
• Backups. I make sure data is backed up safely, and that the backups are regularly verified.
• Testing. I write extensive automated tests, so the next person who works on the code can be sure it still works as they change it. I write manual test checklists too, as a way to double check everything.
• You can leave any time. No lock in contracts. If it's not working out, you keep everything and walk away.

In short, I plan for the worst - because I don't like making the call to say something is wrong without also being able to say "it's fixed".

What's your insurance situation?

I've had a business before, so I know what I need. I hold Professional Indemnity insurance for the work I do, and Public Liability insurance so I can visit you and cover anything I break (including myself). I've never needed to use my insurance, and I don't plan to - but it's there to protect everyone. I'm happy to show you proof of both.

I'm also registered for GST. I've got a joke about GST, but the ATO has the other 10% of it.

How many arms and legs will this cost?

I don't accept arms and legs as payment!

The pricing page has the full breakdown. It's based on an agreed monthly cost that we adjust up and down based on the value I'm providing to you. You know exactly what it will cost before I start. I've chosen my price points to be affordable, keep me sustainably busy, and support my family. I'm not in this to extract every dollar I can - I just want to be useful.

Personally, I don't like accepting money unless I'm providing value. So I'm keen to make sure you're getting something from every dollar you spend with me.

Why is everything named after saws?

Systems Automation Workshop - SAW. It cuts down the time and cost of running your business. And a saw is a powerful tool that you have to use properly and carefully - when you do, you build things that last for decades. Used carelessly, you hurt yourself. That's how I think about automation, and about AI too.

Do you have a team? Can you handle a big project?

No team. It's just me, and I'm keeping it that way on purpose - a small handful of clients I can properly focus on, rather than hundreds I can't.

For big projects - absolutely I can - I'm fast, efficient, and surgical in how I do things. I've rewritten core platforms for a safety-critical fire alarm company and built the entire system that ran my own business.

But I'm also realistic - if a project gets to the size where you'd be better off with a developer in house or a bigger company, I'll tell you, and I'll help you get there. See the Sawmill package for what that looks like.

What do you need from me?

Access to the systems and people involved, honesty about what's not working, and a bit of patience while I learn your story. And an open mind about doing things differently - there's no point in me suggesting something if it's going to stay in a drawer.

I've got a question that isn't here

Ask me. I'll answer honestly, and if it's a good question I'll probably add it to this page.