How I work
No surprises.
Here’s what happens between “I’ve got an idea” and launch, what I’ll need from you, and — because every job is bespoke and I don’t publish prices — an honest explanation of what actually drives the cost.
The six steps · 01
Discovery
A conversation — in person if you’re in Canberra, otherwise a call. I want to understand what you’re trying to achieve, who it’s for, and what you’ve already got. Then I write it up as a one-page brief and send it to you. If we don’t agree on the brief, nothing else happens. This step is free.
Scope and quote
From the brief, I define a first release — the smallest version that does the job properly — and quote it. The quote is fixed for that scope. If the scope changes, the quote changes, and I’ll tell you before it does.
Design
Structure first (the pages, the screens, how they connect), then look and feel. You review at each step. Nothing gets built until the design is agreed.
Build
In short cycles — usually two weeks. At the end of each you see working software: a TestFlight build for an app, a staging site for a website. Feedback goes in before the next cycle.
Launch
App Store submission or site go-live, with the redirects, analytics, search setup and store listing handled. I stay on it until it’s actually live, not just submitted.
After
I’ll fix any bugs in the first 30 days at no charge. After that you can choose a support pack for on-going enhancements.
What I’ll need from you · 02
- A decision-maker. One person who can say yes. Committees double the timeline.
- Content. Words, photos, logos, product data — or a decision to have me produce them.
- Access. Domain registrar, hosting, existing accounts, Apple Developer Program if you have one.
- Time. Roughly two hours a week during design and build, for reviews and answers.
How quoting works · 03
I don’t publish prices, because I’ve never built the same thing twice. But I’m not going to make you guess, either. These are the things that move the number:
| Driver | Why it matters |
|---|---|
| Number of screens or pages | Each one is designed, built and tested. |
| Data and integrations | An app that stores data needs a backend. An app that talks to your existing system needs an integration. Both are real work. |
| Accounts and sync | Sign-in, password reset, syncing between devices — invisible when it works, substantial to build. |
| Content creation | Do you have the words and images, or am I producing them? |
| App Store handling | Listing, screenshots, privacy declarations, review. I include it; it isn’t free. |
| Ongoing support | A care plan is separate from the build, and optional. |
After discovery I’ll give you a quote and, if it’s more than you’d budgeted, a smaller first release that fits. The right first version is almost always smaller than the first idea.
Timelines, roughly · 04
4–8
weeks · small-business website
3–6
weeks · redesign
8–16
weeks · iPhone app, first release
3–5
weeks · brand identity
Questions · 05
Do you take a deposit?
Yes — a portion on signing, the rest at milestones. The schedule is in the quote.
Do you work with clients outside Canberra?
Yes, across Australia. Everything works over video; the only thing you miss is the coffee.
Can I see a contract before we start?
Of course. It’s short, and written in English.
Next step
Got something to build?
Tell me what you’re trying to do and I’ll tell you honestly whether I’m the right person for it — and if not, who might be.
Canberra-based · working with clients across Australia · replies within one business day