How a Build Works
A fixed fee, from A$4,500, for a defined piece of work made and handed over: an application or a site integrated with what the business already runs, a set of agreements and terms, a pricing or revenue model, a grant application or a raise pack. Everything is handed over in your own accounts with a written register of every asset and where it sits.
Most of the questions below were first asked about software, because software is where lock-in bites hardest. The answers apply to every Build, answered before the form rather than after it.
The Questions That Matter
Does Building in Days Mean a Template?
No. The speed comes from the stack and from one person making decisions, rather than from reusing a layout. The Perth clinic went from brief to live site in three days across thirty commits, and the slowest part of that job was waiting on photography.
Who Owns It When It Is Finished?
You do, and you own it from the first day rather than at handover. Domain, hosting, transactional email, lists, repository and analytics either start in your accounts or move to them, recorded line by line in a handover register. Nothing sits in an account you would have to ask for later.
What Happens If You Are Not Available?
One person is a single point of failure, and it would be dishonest to pretend otherwise. What reduces it: an ordinary, widely used stack in Next.js, Supabase and Vercel, with no proprietary framework to learn. Code in your repository. A handover register, so nothing load-bearing is undocumented. Another developer can take it on without reverse-engineering it first.
What If You Want Changes After It Is Live?
Two rounds, each as a single consolidated list, within fourteen days of the site going live. The consolidation matters more than the count, because two rounds agreed one message at a time becomes forty messages across three weeks, and that is where a fixed fee quietly stops being fixed. Defects are separate and never come out of those two rounds: if it does not do what was agreed, or it breaks, it is fixed for ninety days at no charge. The line is deliberately simple. A defect is a mistake in the build and a revision is a change of mind, and nobody should have to spend a round of their own on somebody else's mistake. The ninety days covers what was handed over, so once the code is edited by someone else it stops being covered.
Is There a Monthly Fee?
Not for the build. Nothing about it requires a retainer to keep running. Hosting and mail are paid directly, at cost, in your own accounts, because that is where they were set up. The commercial work that comes after is a separate tier called Growth, at A$2,000 a month, and it is a choice rather than a condition. Without it, the thing carries on working.
If AI Writes It, How Good Can It Be?
AI does the typing. The decisions and the review do not, and the decisions are what the fee is for. The multi-tenant booking product in the portfolio enforces per-tenant isolation in the database rather than in the application, and settles payments to each shop directly. That is a commercial and legal judgement before it is a technical one.
What Is Needed from You?
Decisions, which is the one hour that cannot be delegated. Access to the systems already in use. Copy and photographs, or a decision to have the copy written for you. Photography is the usual bottleneck on this kind of work, so it is worth starting before it is needed.
Systems, for Larger Companies
For companies with twenty to five hundred staff, and founders with funding behind them: AI agents that answer, qualify and follow up, automation that joins the CRM, inbox, payments and reporting, and internal applications with accounts, roles and a database behind them. A fixed fee, from A$30,000, and typically A$40,000 to A$120,000, quoted in Build units before work starts.
The same terms as every Build: an automated test suite, a release gate before anything reaches you, handover in your own accounts and a written manual for every asset and process. The architecture and the sign-off stay with one person; where the scope needs more hands, additional developers work under the same gate. Once it is live, the system can be run and improved monthly under Operator.
If a Revenue Share Suits You Better
Where the product already works and the only thing missing is distribution, there is a second way to do this that does not involve an invoice at all. The criteria are narrow, and they are stated before the form.
Start a Build
One paragraph is enough. What the business does, what needs to be made or fixed, and when you need it. If it is not a fit you will be told so in the reply, rather than booked onto a call to hear it.