How a project runs at Applicable.
From problem
to live system
01. What you want to build.
The workaround, the old system, the half-finished AI app. Plain English is fine. You tell us what you are trying to build or fix, and we listen, ask questions and give you an early ballpark. If a website builder or an off-the-shelf product would do the job, we say so here.
02. Get the price in writing.
A senior engineer scopes it and puts one number on it. We size your app against the base every build starts from, check the integrations against the systems you already run, and write the result down before anything is built.
Nothing gets added without your say-so. Anything extra is quoted separately, so there are no surprises.
03. Test as we go.
Something clickable in days. Your team tries it with real work before we call it done, which is the cheapest way to find out what people will and will not do. You see working software, not status reports.
04. Go live.
We move your data across and hand over the code, the hosting accounts and the content system in your name. Then you choose how to run it: take the code and self-host it for nothing more, or go on a monthly plan.
Pricing, plainly Starting points, confirmed in writing before we start.
Every build starts with the same base: an app with user login, role based access control and user management, plus up to four main features across up to 15 screens. Think messaging, task management, payments, catalogues, notes, digital forms, admin and analytics. We size your app in the first briefing, and the time it needs sets the price.
One fixed price, written down before we start. Anything extra is quoted separately, so there are no surprises.
On the Managed plans, usage costs (compute, storage, AI/API tokens, bandwidth) are billed on top, based on your app usage and traffic. We estimate these up front.
Common questions
The deliverables are written down and priced before the build starts, and Applicable builds exactly that. Nothing gets added without your say-so, and anything extra is quoted separately. No surprise invoices.
They usually do a little. Small changes are absorbed; anything that changes the scope is quoted in writing and you decide. The build continues either way.
No. A senior engineer scopes what you want built and gives you one price in writing before any work starts. If you have an existing app you want looked at instead, the expert code review and remedy report is a fixed NZ$1,499 and you keep the report either way.
You get something clickable in the first week and your team testing it with real work well before launch. Most projects go live in weeks, and we tell you how many in writing before we start.
Integrations are scoped and quoted per project, because each one depends on the system at the other end. Xero, MYOB, payment gateways and most modern job, CRM and email platforms have APIs we work with.
Everything: code, hosting accounts, content system, data.