The approach
You work with the person making the technical decisions and building the software. The context doesn't have to survive a series of handovers.
01 / Understand
We start with how the operation runs today: who does the work, which systems are involved, where the exceptions happen and what the friction costs you. The aim is to find the actual problem, not just capture a feature list.
02 / Architect
I map the workflows, data, integrations and technical foundations. We separate the essentials from later improvements, discuss the trade-offs and agree a scoped approach before committing to the build.
03 / Build
I develop the application across the frontend, backend and database. You review working software against real scenarios, so the people who know the operation can spot gaps before they become expensive assumptions.
04 / Operate
The scope of ongoing support is agreed explicitly. Where we continue together, I remain involved in maintenance, monitoring and improvements—with the context of why the system was built this way in the first place.
Before we start
No. A description of the current process, where it breaks down and why it matters is enough to start. We can work out the requirements together.
As an indication of fit, new custom builds generally start around AUD $15,000. The actual scope and investment are agreed after understanding the problem. Advisory work, integrations and ongoing support can be scoped separately.
Yes. The first step is to understand its architecture, condition, documentation and operational responsibilities. That assessment informs whether to improve it incrementally, address a specific risk, or consider a larger change.
It depends on the workflows, integrations, data and level of change involved. I will discuss a realistic delivery approach after scoping; a reliable estimate needs more than a short feature list.
We agree the ongoing responsibilities and support scope rather than assuming them. Continued development, maintenance and technical ownership are available as a separate arrangement.
Start with the problem
Tell me where things get complicated. You don't need a specification, a technology choice, or all the answers.