Pricing
Scope decides cost.
We do not publish fixed prices, because scope decides cost and a number without a scope is a guess. Tell us what you are trying to change and we will tell you what it takes.
Described by shape and fit, not by a figure.
The levels
Three shapes of engagement.
Most projects land in one of these. Which one is a question about how many moving parts there are, not about how much you intend to spend.
- 01
Focused Build
For a defined website or a specific improvement
A clear brief with a known shape: a new site, a rebuild, a performance or accessibility fix, a single automation.
Work that fits
Defined scope and schedule · Design and build · Launch and handoverWhat moves the scope
Mostly how much of the design and content already exists, and whether anything has to be brought across from an old site.
Next step
Send the brief. A defined piece of work can usually be scoped from a written description and one conversation.
- 02
Growth System
For a website plus automation and integrations
Where the site is one part of a working system: the surface, the workflows behind it, and the tools it has to talk to.
Work that fits
Process mapping · Website and automation together · Integrations with your existing tools · Ongoing maintenanceWhat moves the scope
How many systems are involved, and how willingly each one gives up its data. A tool with a clean API is a different job from one without.
Next step
Book the conversation. Which systems are in play decides most of this, and that is quicker to establish by talking than by typing.
- 03
Custom Platform
For applications, AI systems and infrastructure
Longer engagements where the software is the business operation: custom applications, agents with real access, and the infrastructure under them.
Work that fits
Architecture and discovery · Application and AI development · Cloud infrastructure and security · Monitoring and continuous improvementWhat moves the scope
How much of your domain has to be modelled from scratch, how strict the access and audit requirements are, and how much existing data has to come with you.
Next step
Book a conversation. Work at this scale starts with discovery, and the first thing worth establishing is whether that is the right next step at all.
What it depends on
Five things move the number.
- 01
Complexity
How many distinct things the system has to get right, and how many of them are unusual. Ten ordinary pages are less work than one screen that has to reconcile three sources of truth.
- 02
Integrations
Every tool the system has to talk to adds work, and how much depends entirely on the tool. A documented, modern API is straightforward; an older system without one is a project of its own.
- 03
Content readiness
Whether the words, images, product data and legal copy already exist, or have to be written, gathered and organised as part of the build. This is the single most common reason a project takes longer than expected.
- 04
Data migration
Moving existing records into a new system is rarely a copy. Old data usually needs cleaning, mapping and checking first, and how much of that is needed only becomes clear once we look at it.
- 05
Ongoing support
Whether monitoring and maintenance continue after launch, and at what depth. Agreed with the rest of the scope rather than assumed in either direction.
The configurator
Guidance, not a quote.
The configurator recommends an engagement level by applying fixed rules to your answers. It is guidance, not a quote, and it commits neither of us to anything. A real number needs a scope, and a written scope is what the first phase of delivery produces.
The sensible next step
The fastest way to a real number is a scope.
Tell us what you are trying to change and we will tell you what it takes. If it is not worth building, that is an answer you can have for free.
Free 30-minute project conversation - online meeting, no obligation.
Or email hello@needyahmate.com.au