We offer fixed-price startup prototype development for Auckland founders who need a working first version, clear costs before committing and ownership of their code. You don’t need a technical brief to begin.
Prototypes starting at NZ$5,000
Our projects start at NZ$5,000 as at October 2026, with a clear scope and fixed quote before you commit. The starting price is a baseline, rather than a flat fee for every prototype.
Our 14-day delivery offer covers design, build, testing and launch within an agreed scope. We work through the features, integrations and release requirements with you first, so the delivery plan matches the software you’re commissioning.
A focused first version gives users something concrete to try. The scope should make clear what they can do, what you want to learn and what belongs in a later build.
What fits into two weeks
A two-week prototype needs one defined problem, a focused user journey and the working components needed to test that journey. A broader product idea needs to be narrowed before we can agree the build.
A prototype and a minimum viable product (MVP) can answer different questions. Business.govt.nz describes an MVP as a first working version that gives potential customers enough value to use it and provide feedback. A prototype may test a narrower part of that experience.
A focused first version
A useful starting point is a task you can observe: can a customer submit a request and understand its status? That gives design and development a clear boundary.
NZ Digital Government’s alpha guidance recommends narrowing scope and assessing prototypes through measures such as task completion and user satisfaction. Those principles help separate essential functionality from features that can wait.
Integrations belong in that discussion from the start. A screen that depends on another business system needs more scope consideration than its appearance alone suggests. There is no universal feature allowance attached to our starting price.
Work needing a larger scope
A fuller operational service can require repeated user testing, accessibility checks, security testing, analytics, documentation and support arrangements. NZ Digital Government’s beta guidance identifies these as work involved in developing a prototype into a sustainable service.
The intended use determines the depth of that work. A limited trial and a public service handling live customer activity need different scope decisions.
Design, build, testing, and launch
Our delivery process gives you visible progress, an opportunity to try the software and one revision round before launch. You can assess the agreed functionality before putting the first version in front of its intended users.
Design and engineering
We design around the user journey agreed during scoping. The screens and interactions should help someone complete that journey without adding unrelated features.
AI assists development. Our engineers handle the custom logic, integrations and checks that make the software fit your needs. For example, a request form’s appearance is only part of the work; the rules governing what happens after submission also need engineering attention.
Your revision round provides an opportunity to refine the build before launch. Any additions are priced and agreed with you first.
Testing and release
Technical checks and user feedback answer different questions. Engineers check the software, while trying the agreed journey helps you assess whether users can understand and complete the task. User feedback alone does not establish readiness for every release environment.
At launch, we show you or your team how to use the software. The release route also matters: completing development and obtaining public app-store approval are separate milestones.
Apple reviews submissions to App Store Connect. Incomplete information or placeholder content can prevent approval.
For personal developer accounts created after 13 November 2023, Google Play requires at least 12 testers opted in continuously for 14 days before applying for production access. Google says that application review usually takes seven days or less, but can take longer.
What we need from you
We need a plain-language description of the problem, the people using the software and the task you want them to complete. You don’t need to turn your idea into a technical specification first.
Also tell us what the prototype must help you learn. Usability, appeal and willingness to pay are separate questions. Someone can understand a demonstration and still have no intention of buying.
The University of Auckland’s Centre for Innovation and Entrepreneurship treats customer discovery as finding customers, testing an idea’s appeal and investigating whether people would pay. Choosing that question early helps us scope functionality that will produce useful feedback.
SurgReady’s early Auckland prototype
SurgReady provides an independent Auckland example of a focused prototype preceding a fuller product. The venture was founded by Ronan Payinda; it was not a Good Phase project.
The University of Auckland’s July 2025 profile described an early-stage prototype with a login system and clinician dashboard, while the team worked towards an MVP.
The wider concept involved helping patients prepare for surgery through personalised guidance and reminders. The profile did not establish that every proposed capability was already part of the prototype.
For a founder deciding what to commission, the useful distinction is between the wider product ambition and the functionality built at that stage. A prototype can make a defined part of an idea tangible while further development remains ahead. That boundary should be explicit in your own scope.
Your code and hosting choices
You own the source code and choose where your software is hosted. After launch, you can run the software yourself or choose ongoing hosting, support and development. You do not have to commit to continuing services.
Code ownership, hosting and ongoing support are separate decisions. Choosing help with hosting does not mean you need to commission the next set of features. Owning the code leaves you free to decide how future development is handled.
Think about who will look after the software once people start using it. You may want your team to manage day-to-day use and someone else to handle technical support. Your next step can reflect that division of responsibility.
Get your fixed-price scope
Start your scoping enquiry by telling us what you want to build or improve and who will use it. Include the main task, any systems involved and the question your prototype needs to answer.
Send your name, email address and project description. Your business name or website is optional. We reply by email to work through the details, define the features and integrations, and prepare your scope and fixed-price quote.
You can begin with a problem description rather than a finished feature list. We’ll help turn that description into a defined first build.
Send your project description through our enquiry form so we can scope the version you want to put in users’ hands.
Get a fixed-price quoteWritten by Good Phase