Give the work a proper home.
The job list lives in a spreadsheet. Its history is in email. To find out who is doing what, someone has to ask around. I build focused software that brings an agreed process into one place.
Quoted after a short scoping conversation. Price, timing and ongoing costs are agreed in writing before work starts.
Tell me what you needKnow who has the next step
An example of the kind of work we can scope together.
- A team member submits a request
- The right person reviews it
- Everyone can see the status
When something goes wrong. A rejected request goes back with a reason. A failed save stays visible so someone can recover the work. Access rules decide who can view, change or approve it.
What you get
A working tool for one defined process, connected to the agreed data and tested with the people who will use it.
A useful starting point
A small team with a process it understands and a person available to try the first version. Request queues, approvals and job tracking are examples of a manageable starting scope.
Replacing every system at once makes the first version harder to judge and maintain. We start with one process, compare existing software and agree who will own hosting, access and ongoing support.
Tell me what you need
What is your team trying to keep track of? Describe who uses the process, where it lives today and what they need to see or do.
I’m based in Newcastle and work remotely across Australia. You do not need a technical brief. We discuss the task, check access and feasibility, then agree a written scope, price and timing before work starts.
See how I build
BESF is my public build-and-check case study. It shows how I test software, investigate failures and repeat the work. It documents my own project, rather than a result from a client engagement.
Explore my projects