Custom systems
Custom systems that automate a specific business process
I build systems that take over work your team now does by hand, from a single team's workflow up to company-wide operations. I work with the tools you already use, and I hand over something your team can run without me.
How I work
Three steps, start to handover
01
Understand the process
I sit with your team, map how the work happens today, and find the steps worth automating.
02
Build the system
I build around your real process, not a generic template, and test it against your own data.
03
Hand over and support
I hand over a system your team can run, with clear documentation and support while it settles in.
Time and cost
How long it takes, and what decides the price
How long
A first project is usually a few weeks rather than months, because we narrow it to one process instead of your whole operation. The sequence is a short call, a written scope and quote, the build, then handover with documentation.
What decides the price
Three things. How clearly the process is defined, because rules a person can write down are rules a system can follow. Where your data lives and how consistent it is. And how many tools the system has to connect to, since every connection is another piece to build and test.
You can see what finished work looks like in the systems I have built. View systems
Questions
Before you send anything
- I am not technical. How does this work?
- You do not need to be. I start from how your team works today, talk in plain language, and show you what the system does at each step. Nothing gets signed off in jargon.
- Is my company data safe?
- The system runs on your own accounts and tools. I take only the access a task needs, and that access ends at handover. Your data is never used for anything else and never shared.
- Who maintains it after handover?
- Your team runs it. You get documentation written for the person who will use the system, not for a developer, and a support period after handover while it settles in. I am available after that if something needs changing.
- What if our process changes later?
- It will, so systems are built to be adjusted. The parts that change often, such as rules and lists, are editable by your team without touching code.
- I am not sure I need a system. Should I still get in touch?
- Yes. Some work is better left in a spreadsheet, and I will say so. A short conversation costs you nothing, and it usually makes clear where the real problem is.
Request a quote
Tell me what you want to build
Fill in a few details and I will come back to you with a plan and a quote. No obligation.
What happens after you send this
- 01I read every request myself and come back within two working days.
- 02If it looks like a fit, a short call to go through how the work runs today.
- 03Then a written scope and quote, before any work starts.
Prefer to talk first?
Book a call
If you would rather talk it through before sending anything, book a short call and we can start there.