Fixed scope. One clear quote.
We don't publish a rate card, because a rate card prices a guess. We price what we've agreed to build, after you've seen a prototype of it — and the number doesn't move unless the scope does.
A free prototype first
Before any quote, we build a clickable prototype of your core product. It costs nothing and carries no obligation — and it is what makes an accurate quote possible instead of a padded estimate.
Scope agreed in writing
Once the prototype is right, we write down exactly what is being built. That document is the scope, and the quote is priced against it.
One clear quote
A single number for the agreed scope. No retainers, no markups, no line items for overhead you did not ask for.
Changes are quoted, never charged silently
Anything beyond the agreed scope is quoted before it is built, so you decide. There are no change fees and no surprise invoices.
Four ways to pay for software
The question isn't only what software costs — it's who carries the risk when the estimate is wrong. Each model answers that differently.
Hourly billing
The final cost is unknown when you sign
- Slower work costs you more, which rewards the wrong thing
- Every scope question becomes a billing conversation
- Budgeting for it means padding for the worst case
Agency retainer
You pay monthly whether or not the month produced much
- Account managers and sales overhead are inside the rate
- Work is queued against other clients on the same retainer
- Leaving usually means leaving the code and accounts behind
Freelancer
Usually the lowest headline rate
- Availability and continuity depend on one person
- Design, build, testing, and deployment are rarely all covered
- Handover quality varies and is rarely part of the agreement
WizCodes
How we workScope and price agreed in writing before work starts
- One quote covering design, build, testing, and deployment
- You talk to the engineer building it, not an account manager
- Everything ships to your accounts — you own 100% from day one
Who you're actually choosing between
A prompt can generate a screen in seconds. It cannot sit with you, learn how your business actually earns, and build something that still works — and still has someone behind it — a year from now.
| Traditional agency | Freelancer | AI builder / one-prompt tool | WizCodes | |
|---|---|---|---|---|
| Understanding your business | Through account managers | Sometimes, if you brief well | It only reads your prompt | A real call before any code |
| What you end up with | A long engagement | One pair of hands | A generic template | A system built for how you operate |
| Automation & AI | Extra scope, extra cost | Rarely in scope | Surface-level at best | Designed in from the start |
| When something breaks | A ticket queue | If they are still free | Nobody to ask | The engineer who built it |
| After launch | A retainer | The engagement ends | You are on your own | You own it; we stay reachable |
None of these are bad choices in every case — a template really is enough for some jobs. The difference shows up when the software has to fit how your business already runs, and when something needs fixing six months later.
What the quote covers
Everything needed to get the product built and into your hands. There is no separate line for deployment, handover, or the things a build should include anyway.
- UI/UX design
- Engineering and testing
- Deployment to your own accounts
- App Store / Play Store submission where relevant
- SEO and performance work as standard
- IT consulting and technical support
- All code, repositories, credentials, and keys
Why it costs less than an agency
Not because the work is smaller. Because the price isn't carrying anything that isn't engineering. There are no account managers, no sales layer, no markups, and no retainers. Modern tooling and AI also let a senior team ship production-quality software considerably faster than the process most agencies still price for — and we pass that saving on instead of keeping it. Quality, security, and SEO are part of every build, not upsells.
If what you actually want to know is which parts of a project move the number, what drives the costranks the ten factors by impact — including the two that matter far less than people expect. There's also a longer breakdown of where software budgets go in what custom software actually costs.