Who it's for
Small businesses and larger companies whose software runs, or should run, on AWS: a platform that outgrew its server, a legacy system nobody dares touch, a bill that grew faster than the business, or an acquisition that came with technology nobody on the buyer's side has seen. Most of my clients are growing Australian businesses in agriculture, finance and technology, and the decision-maker is an executive who needs it done right, not explained in acronyms.
How an engagement works
- A free 30-minute call. You explain where the business needs to go; I ask the questions that change the design.
- A written proposal with a fixed price. What I'll build, how, what it will cost to run, and the price for each piece of work, before anything starts.
- I build it. With tests, telemetry and infrastructure as code from the first day, and a running system you can see at every step.
- You keep it, or I run it. Everything is in your AWS accounts and your repositories, documented, so your team can take it over or I keep it running.
What it costs
The first call is free, and so is the written proposal that follows it. The proposal breaks the work into pieces, each with a fixed price set from its scope: what gets built, the systems it touches, and the risk in changing them. You approve each piece before it starts, and the price doesn't move once it's agreed. That's our default, not a rule: if a retainer or hourly billing suits your project better, we'll work that way.
Why me
You talk to the engineer. There's no account manager and no junior team: I design the system, write it with Claude Code under my review, ship it and keep it running. I've been building software for two decades, the last 15 years of them in the cloud, and I've run three businesses of my own, so I start from the business problem, not the brief.
What I build with, and why, is public: The Stack lists every AWS service I use or avoid, with prices and the gotchas that bit my clients. The projects below are real, with the client described rather than named.
Questions
Do you only work with Sydney companies? No. I'm in Sydney and most clients are in Australia, but the work is remote-first, and AWS regions are the same from anywhere.
Can you work with our team rather than instead of it? Yes. I often design and build the hard parts, then hand over a codebase, the infrastructure as code and the runbooks, and coach the team to ship with Claude Code or Codex.
What does it cost? It depends on the work, so the first step is the free call, then a written proposal with a fixed price for each piece. You know the cost before you commit.