Software
Full custom software development from concept through launch, web, mobile, portals and automation, built by a NZ team around the way you work.
This page is for owners and managers who need software nothing off the shelf provides, and who want to see exactly how a project runs before they sign anything. Superstack runs custom software development NZ and Australian businesses can watch step by step, from discovery to support, and hands over tailored business software you own outright.
when the tools run the business
custom software development from discovery to support
Custom software is a process, not a product. Every build we do, whether it is a web app, a mobile app, a CRM or portal or an automation, runs through the same nine steps, so you always know what happens next.
01 of 9
Discovery is a few sessions with the people who do the work, not just the owner. We watch a job move from enquiry to invoice, ask what gets retyped and what gets lost, and write it down as a plain-language requirements document. The cleaning company that asks for a job app often finds rostering at the top of the list.
02 of 9
Architecture is the plan for how the pieces fit: which data lives where, what talks to your accounting software, what the mobile app does when the signal drops, and what stays out of scope for now. You get it as a one-page diagram and a written, priced proposal. When a franchise wants head office reporting later, the plan allows for it from day one.
03 of 9
Design means your team's screens, in your team's words. We draw the dispatcher's board, the technician's job sheet and the customer's booking page as clickable mock-ups, then put them in front of the people who will use them. A receptionist who says the cancel button is in the wrong place saves a change that costs far more once code exists.
04 of 9
We build in short sprints, and every sprint ends with working software you can log in to, not a status report. Sprint one is the core record, a job, a client or a booking, and its office screen. The mobile app and the customer portal follow on the same database, so a job updated from a ute shows in the office at once.
05 of 9
Your customers, jobs, invoices and history come across from the old system, the spreadsheets and the shared drive. We pull the data out, strip duplicates, match old fields to new ones and load a trial copy your team checks before the real move. When old job numbers matter to your customers, they survive, so an old invoice still matches its job.
06 of 9
Integration means each piece of information is typed once. A quote accepted in your system raises the invoice in your accounting software, the payment shows back against the job, and the customer's SMS reminder goes out through Twilio without anyone copying a phone number. We connect to anything with an API and write down what each integration moves, when, and in which direction.
07 of 9
We test every sprint before you see it, and your team tests it again on real work. UAT means your dispatcher runs Monday's jobs through the new system alongside the old one and tells us what is wrong, missing or slower. We fix that before launch, not after. Nothing is signed off until the people using it agree.
08 of 9
Launch happens at a quiet time you choose, with the final data move done the night before and us close by while the first real jobs go through. Training is by role: the office team learns their screens, field staff learn the app in the yard, and managers learn the reports. Short written guides stay inside the system for whoever joins next year.
09 of 9
After launch you get a support agreement that says who to call, how fast we respond and what is included. We fix bugs under it. Bigger changes go on a roadmap we review with you regularly, so the next module, a customer portal or a reporting dashboard, is planned rather than bolted on. Hosting, backups and updates sit with us or with your own IT.
Discovery and the proposal come first, and you can stop there with a document any developer can build from. Sprints turn the agreed screens into working software, and each one ends with a demo you log in to. UAT is your team on real work, with sign-off against the requirements. Launch moves the data and the people. Support keeps it running, and the roadmap decides what comes next. You choose at the end of every sprint whether to continue, change direction or pause. The process runs on rails. The decisions stay with you.
Your accounting software take invoices and customer records from the system and send payment status back. Stripe and GoCardless handle card and direct debit payments. Google Workspace and Microsoft 365 provide sign-in, email and calendars. Twilio sends SMS. Shopify passes orders through. HubSpot and Salesforce sync contacts and deals if your sales team stays in them. Anything else with an API connects the same way.
Any system with an API connects. Click a logo to visit them.
Xero
MYOB
Stripe
Google Workspace
Microsoft 365
Twilio
Shopify
HubSpotAI is optional, and on many builds it is a small part or none at all. We decide during discovery whether an AI step earns its place, by asking what it saves and what happens when it is wrong. Read how we use AI and how it fits into business process automation.
A summary of a job's history before the technician arrives, drafted replies your staff edit, classification of incoming requests, extraction from supplier invoices, search across old job notes, and voice for answering routine calls. Never bolted on for the sake of it, and always with a person checking the result.
The office, managers and admin staff work in the web app: the job board, quoting, rostering, approvals and reports, in any browser, with a role for each person. It is usually built first, because it is where the data is created and checked.
Field staff, carers, drivers and contractors use the mobile app for the parts of the job that happen away from a desk: job sheets, photos, signatures, timesheets and checklists, working offline and syncing when the signal returns. See mobile app development.
Customers, clients, members or franchisees log in to a portal to book, approve quotes, pay, download documents and see progress without ringing the office. All three run on one database, so the office, the field and the customer see the same record.
Contracts, sites, rosters and quality audits in one system.
TradesQuotes, job sheets and invoicing from the van.
Property and securityProperties, patrols, inspections and incident reports.
FitnessMemberships, class bookings, waivers and check-ins.
Childcare and activitiesEnrolments, attendance, programmes and parent updates.
Healthcare adminReferrals, intake forms and appointment reminders.
CareVisit schedules, carer notes and family updates.
HospitalityFunctions, rosters and supplier orders.
RecruitmentCandidate pipelines, placements and contractor timesheets.
Professional servicesProposals, engagement letters and client portals.
DistributionStock, orders, delivery runs and a dealer portal.
FranchisesEvery site on one system, with reporting for head office.
Quickest start
We customise an existing Superstack module, such as a CRM or a job app, to your process, your words and your integrations. It is the quickest route to a first system, and it still gets discovery, UAT and training.
Most common
We combine several modules into one platform: quotes feeding jobs, jobs feeding invoices, a portal on top. Most projects on this page land here, because the value is in the joins.
Fully bespoke
Bespoke software development from a blank page, for a process or product nothing existing covers. Same lifecycle, same ownership, with more time in discovery and design because there is nothing to adapt.
The number of screens, the number of things it connects to, and how much of your data has to move. A job app with an office screen and your accounting software link costs far less than a platform with a customer portal, several integrations and years of history to migrate. Discovery pins those down before anyone quotes, so our proposals are priced against a written scope, not a guess.
Yes, both, and most projects use each at a different stage. Discovery and the first version are usually quoted as a fixed price against the agreed scope, so you know what you are committing to. After launch, changes and new modules run in sprints you approve one at a time, once you know the system and want to steer it. Either way, you see the price before the work starts.
It depends on how many modules are in the first version and how much data comes across, so the timeline is in the proposal, not on this page. You are using part of the system before the whole thing is finished, because sprints deliver working software from the first one, and you can pause at the end of any sprint with something that works.
Standard, widely used web and mobile technology, not a niche platform only we understand. Web apps run in any modern browser. Mobile apps are built for iPhone and Android, from one codebase where that makes sense. The data sits in a mainstream database. That matters because another developer can pick the system up, and the parts underneath keep getting security updates. The proposal names the specific choices in plain language.
Yes. The code, the database and the documentation are yours, and we put ownership in writing before the build starts. You are not renting a licence. If another developer or an in-house team ever takes over, they get the code, the hosting access and the documentation. Where a build starts from an existing Superstack module, the same agreement spells out what is yours and what you keep the right to use.
Yes. Superstack is a custom software company New Zealand businesses can meet in person. The people you meet in discovery are the people who do the software development. Christchurch is home, and we work with businesses across New Zealand and Australia. The software developers NZ clients deal with are the ones who build the system, which matters when you need a change explained on the phone.
We start with a short review of what exists: the code, the database, the documentation and whatever the previous developer left behind. Then we tell you plainly which path fits: finish it, rebuild parts of it on the same data, or start again and migrate what is worth keeping. Half-finished projects often have a usable database and screens nobody trusts, so the answer is rarely all or nothing.
A written support agreement that says who to contact, how quickly we respond and what is included. Bugs and small fixes are covered. Hosting, backups, monitoring and security updates are handled by us, or by your own IT if you prefer. Bigger changes go on the roadmap and run as sprints you approve. The people who built the system are the ones answering the phone.
Built around the way you work.
Your business shouldn't have to fit someone else's software. Tell us how your business works. We'll show you what Superstack can build around it.
Tell us where your business is stuck. We'll tell you whether software fixes it, and what kind.
We use cookies to see which pages help people. Nothing runs until you say yes. Read the privacy policy.