Services · Custom Apps & Business Software
I design and build business tools, client portals and apps around the people who use them. We start with the job the software needs to do, then build a useful first version you can try, improve and grow.
Replace awkward steps between spreadsheets, inboxes and existing systems with a clearer way to manage the work.
Turn a product idea into an app people can use, with essential features worked through before the build grows.
Job boards, bookings and workflows shaped around how your team works.
A clear place to sign in, share information, follow progress and complete important tasks.
Views and exports built around the questions you regularly need to answer.
Integrations that reduce repeated entry and move relevant information between tools.
Software designed for where people use it, with mobile app builds where they are useful.
Access planned around what each person needs to view or change.
We agree the features, platforms and integrations around the work you need to do.
Built while employed at Tyre General
The job board that runs fleet call-outs across a South Island tyre group.
Read the case study →A product of my own
My World Cup companion: live scores, a bracket that fills in, local kick-off times and ten languages, on the web and the App Store.
Read the case study →We map what happens now, where it gets stuck and what a better result looks like.
We decide what the first release must do, then work through the key screens and tasks.
You try the software as it develops, so decisions are based on something real.
We check important tasks, prepare the rollout and agree how the software will be maintained.
The agreed source code sits in your repository, with project accounts and data under your control. Handover explains how the software fits together and what another developer needs to maintain it.
Hosting, third-party services, maintenance and future changes are agreed before release.
That is part of the first conversation. We look at the work and the available options before deciding whether a custom build is worthwhile.
Yes. We agree the essential first release, then add to it based on what people actually need.
Often, but the detail matters. I review the available access and integration options before committing to a scope.
Yes. The approach depends on how people use the product. Web, iOS and Android delivery can be included where they fit the brief.
The proposal sets out the stage, price and schedule, including dependencies that may affect delivery. We agree hosting, maintenance and support responsibilities before release.
What would make the work easier?
Tell me about the process that is getting in the way, or the product you want to build.
Talk about your software