Custom web apps & portals
-
Updated

What does a fixed price for a web app actually cover?

At Applicable a fixed price covers the scope written down before the build starts: one number from NZ$6,999, with anything added later quoted separately. A fast, simple build is enough when the app is standalone and roughly right will do. Scope it first when it talks to your other systems, when customers will use it, or when getting it wrong costs you money.

What does a fixed price for a web app actually cover?

What a fixed price covers

A senior engineer scopes what you want built and puts one number on it in writing, from NZ$6,999 for a business application and NZ$8,999 for a customer portal or booking service. Then a build measured in weeks, with something clickable in the first week and your team testing it with real work well before launch.

Fixed means the deliverables are written down and priced before anything is built, and that Applicable builds exactly that. Nothing gets added without your say-so, and anything extra is quoted separately. The number you are given is the number on the invoice.

Not every project needs that, though. The first question worth answering is how much certainty you actually need.

When a fast, simple build is enough

  • The app is internal, standalone and simple: a form that feeds a list, a basic CRM, a dashboard over a spreadsheet.
  • It does not need to talk to your accounting package, your job system or your customers' logins.
  • If it is roughly right on the first release, that is good enough, and you can iterate on a monthly plan.
  • You are a founder testing whether anyone wants the thing at all.

In those cases the cheapest route that works is the right one, and Applicable will tell you so on the first call rather than scoping something you do not need.

When scoping it first is the right answer

  • Customers or staff will use it every day, and getting a flow wrong costs you money or trust.
  • It has to integrate: Xero or MYOB, a job management system, a payment gateway, a CRM, an existing database.
  • There are rules in it: approvals over a value, trade pricing for some customers, a job that cannot close until a checklist is complete.
  • It replaces something that is already running, so the migration is part of the work.
  • You need to know the total cost before you sign, and hold someone to it.

Scoping it properly costs you a conversation, not a fee, and it is what lets someone put one number on the work. That is cheaper than finding out what the system had to do from a live app your customers cannot use.

What the price covers

WhatAt Applicable
Before you commitA senior engineer scopes it and puts one number on it in writing
Business applicationFrom NZ$6,999, live in weeks
Customer portal or booking serviceFrom NZ$8,999, live in weeks
IntegrationsScoped and quoted per project, checked against your systems
After launchFree self-host, or managed from NZ$249 a month
Who you deal withThe founder and the people who build it
What you ownThe code, the hosting accounts, the data, the documentation

All prices are in New Zealand dollars. The full guide is on the process page.

How to decide in one conversation

Tell any vendor three things: who will use it, what it has to connect to, and what happens when it goes wrong. If the honest answers are "just us", "nothing" and "we fix it next week", the fastest build that works is fine. If any answer involves customers, another system or money, have the work scoped before you commit. Ask Applicable and you will get a straight answer, including that a simpler option is fine for this.

Common questions

For a simple, standalone tool, yes: a form, a list, a dashboard, a basic CRM. What a fast build does not cover is a portal that customers log into, integrated with the systems you already run, tested by your staff and supported for years. Ask any vendor which of the two they are quoting for.

Because scoping is where the price becomes fixed. A senior engineer turns your brief into a scope both sides can read, and puts one number on it. Nothing gets added without your say-so, and anything extra is quoted separately.

It should mean the same thing: the repository, the hosting accounts and the data are in your name. Ask any vendor to put it in the agreement, and ask who can rebuild it if they disappear. Code produced mainly by AI with a thin review is harder for the next developer to pick up; ask to see a handover document, and see what vibe coding leaves you to finish.

Sometimes. If the cheap build proves the idea, the rebuild is a normal project. If the cheap build is in front of customers and breaking, the rebuild is a rescue, and rescues cost more than starting properly. Applicable will look at what you have and say which it is.