Software
CRM, portals, workflows, mobile apps and automation combined, one system on one database, built around your business.
Superstack builds custom business systems NZ companies use instead of a stack of subscriptions that never quite connect. One system on one database: your CRM, quotes, jobs or bookings, staff app, customer portal, invoicing and dashboards, built around how your business already runs. We build it in phases, so the first part is live and in use while the rest is still being planned.
eight subscriptions and no system
custom business systems on one database
A custom business system is the whole Superstack stack assembled for one business: CRM, portals, jobs or bookings, mobile apps, automation, dashboards and integrations, all reading and writing one database. We do not build it all at once. We map the whole thing, then build it in phases, each one live and in use before the next begins.
01 of 8
Everything starts with one data model: customers, sites, contacts, staff, jobs, bookings, invoices and documents, each defined once and linked. A customer with several sites is one record with several sites, not three spellings in three tools. When a receptionist updates a phone number, the technician's app, the invoice and the portal show the new one, because there is only one.
02 of 8
Leads, pipeline, quotes and follow-ups live in the same system as the jobs they turn into. A salesperson quotes from the real price list, sees the customer's job history, and when the quote is accepted the job appears on the operations board without anyone re-entering it. Sales and operations stop arguing about what was promised, because both read the same record.
03 of 8
Each group gets its own door into the same system. Customers log in to accept quotes, see visit reports and pay invoices. Staff see their roster, their jobs and their forms. Contractors see only the work assigned to them, upload evidence and submit invoices. A security company runs all three from one system, with each person seeing what their role allows.
04 of 8
The operational heart: jobs for trades and cleaning, bookings for clinics and fitness, with the workflow your business follows. A job moves from scheduled to on site to complete to invoiced, and each step can require a form, a photo or a sign-off. Rosters, checklists and approvals sit in the same flow, so a completed job already has everything the invoice needs.
05 of 8
Field staff work from a phone app that is part of the system, not a separate product. A cleaner opens tonight's run, checks in at each site, ticks the checklist, photographs the finished floor and flags a broken fitting, offline if the basement has no signal. The office sees it as it happens, and the client report writes itself.
06 of 8
Because everything is in one place, automation is a rule, not an integration project. Job complete creates the invoice. Quote unanswered for a week triggers the follow-up. Certificate expiring next month emails the contractor. AI sits on top where it earns its place: triaging enquiries, drafting replies, reading supplier invoices into the system, with a person approving anything a customer will see.
07 of 8
With the data already in one place, reporting needs no export and no spreadsheet. The owner opens one screen and sees revenue by service line, jobs completed against scheduled, overdue invoices and staff utilisation, all live. A franchisor sees every site side by side. Reports go out to clients and managers on a schedule, from the same numbers everyone else sees.
08 of 8
One system does not mean an island. Your accounting software stays your accounting package: invoices, bills and payments flow both ways. Stripe and GoCardless take payments from the portal. Twilio, SendGrid and your email carry the SMS and messages the system sends. Anything else you rely on, from a supplier catalogue to a payroll tool, connects by API.
A lead comes in and becomes a quote. The customer accepts it in the portal, which makes them a customer and the quote a job. The job lands on the roster and in the staff app. The technician completes it on their phone, with photos and a signed checklist as evidence. The invoice is built from the job and sent through your accounting software. The customer sees the invoice, the photos and the report in their portal. The owner's dashboard shows the day's revenue. Nobody typed anything twice. The only decisions people made were pricing the quote and doing the work.
Your accounting software stay as your ledger: the system sends invoices, bills and contacts, and reads back payments, so the portal and the dashboard know the moment an invoice is settled. Stripe and GoCardless take card and direct debit payments. Google Workspace and Microsoft 365 sync email and calendars. Twilio sends SMS, Shopify passes orders in, HubSpot data migrates across, and any other tool 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 the system runs without it. It earns its place here because everything sits on one database. Read how we use AI and how it fits into business process automation.
The enquiry, the job, the invoice and the report sit together, so every AI step works from the same facts.
New enquiries sorted by type and urgency and matched to the existing customer record.
Replies, quotes and client reports drafted in your tone, for a person to approve.
Supplier invoices, signed forms and certificates read straight into the right fields.
A plain-language note on what moved this week, from the dashboard data.
A phone assistant that takes an after-hours booking or enquiry straight into the system.
The office runs the business from the web app: pipeline, scheduling, rosters, invoicing, approvals and dashboards in one place, with roles so the receptionist, the scheduler and the owner each see their own view of the same system.
Staff and contractors work from the mobile app: today's jobs or bookings, checklists, photos, signatures and time on site, with offline support for basements and rural jobs. Managers approve quotes and see the day's numbers from wherever they are.
Customers accept quotes, book, see reports and photos, download invoices and pay, without emailing anyone. All three share one database, so when a cleaner ticks the last item on their phone, the customer's portal and the owner's dashboard both change in the same second.
Contracts, sites, rosters, audits and client reports together.
TradesQuote, job, invoice and the technician's phone on one record.
Property and securityPatrols, maintenance, contractors and owner reporting together.
FitnessMemberships, bookings, payments and the member app.
Childcare and activitiesEnrolments, rolls, parent portal and invoicing.
Healthcare adminReferrals, appointments, recalls and clinician notes.
CareClient plans, rosters, visit records and funder reporting.
HospitalityBookings, functions, staff rosters and supplier ordering.
RecruitmentCandidates, clients, placements and timesheets to invoice.
Professional servicesProposals, engagements, time and billing.
DistributionCustomers, orders, stock and deliveries.
FranchisesEvery site on one system, reported centrally.
Quickest start
We customise an existing Superstack module, usually the one that hurts most, such as jobs or CRM, and build it on the shared data model so the next modules slot in later.
Most common
We combine modules into one platform: CRM, jobs, portals, staff app, automation and dashboards, built in the order that pays back first. This is what most people mean by an all-in-one business system.
Fully bespoke
A fully bespoke end-to-end business platform for a company whose process, data or rules do not fit any existing module, designed from a blank page on the same phased approach.
No, not in the sense of a boxed package with endless settings. It does the job people want from a custom ERP for small business: one database, one view of the customer, the job and the money, and processes that run end to end. It is built around your workflow, not a generic one. Call it an integrated business management system NZ businesses can actually run.
No. We map the whole system first, then build it in phases. Phase one is usually the module that removes the most pain, such as jobs and invoicing, running on the full data model from day one. Your team uses it for real, and what they learn shapes phase two. The business keeps running throughout, and each phase pays back before the next starts.
Tool by tool, in the order the phases need them. Each subscription gets an export: customers, jobs, invoices, documents and history. We match that data to the new model, fix the duplicates three tools always create, and load it into a staging copy your team can check. When they are satisfied, the live migration runs and that tool is switched off. Nothing is cancelled until its replacement has proven itself.
Start by adding up what you pay now: every per-seat licence and the hours spent retyping between tools. A custom system is mostly an upfront build, phased so each part pays back before the next, followed by hosting and support. There are no per-user fees, so hiring does not raise the bill. Bring your subscription list to the first conversation and we put the two totals side by side.
Yes. The code, the database and the documentation are yours, on terms we agree before the build starts. It is business operating system software you own rather than rent, so nobody can raise the price per seat, retire a feature or hold your data. We host and support it, and another developer can take it on at any time.
Support is an ongoing arrangement: monitoring, fixes, platform updates and a person who knows your system to call. The roadmap is the list of phases we agreed, reordered as your business changes. After each phase goes live we review what your team actually uses and what they ask for, and that feeds the next phase. The system keeps improving because someone owns it.
Yes, and most businesses do. The trick is that the first module is built on the full data model, so a CRM built in phase one already knows what a job, a site and an invoice are, even before those modules exist. Adding jobs later is a matter of switching the module on and migrating that tool, not rebuilding the customer records.
It depends on how many phases, and a full system is a programme of releases rather than one launch date. The first phase is small and goes live early. We give you a phase plan with a range for each one, and we only commit to dates for the phase we are building. Nothing stops while we build: your current tools stay until their replacement is live.
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.
Send us the list of software you pay for each month. We'll show you what one system would replace, and in what order.
We use cookies to see which pages help people. Nothing runs until you say yes. Read the privacy policy.