Skip to content
Superstack

Automation

Business Process Automation

Remove repetitive manual work, automations you own, built into your systems, with AI where it actually helps.

Review request sentJust now

Superstack builds business process automation NZ owners use to get hours back every week. If your team retypes enquiries into the CRM, chases quotes by memory and builds documents by hand, we find the tasks that cost the most, automate them inside the systems you already run, and add AI only where a rule is not enough. You own the result, not a subscription.

The problem

the admin that eats the week

  • Our office manager spends most of Monday copying last week's job sheets into invoices and the same names into three systems.
  • Every time details get pasted from one system to another, something changes. Wrong price, wrong address, and the customer tells us.
  • We send the quote and mean to follow up on Thursday. Then a busy week happens and the job goes to whoever called back.
  • The Zapier and Make bills climb every time we add a step, and one chain quietly stopped. Nobody knew for a fortnight.
  • The whole onboarding process lives in one person's head. When they are on leave, new customers wait.

What Superstack builds

business process automation you own

We start by counting. Every repetitive task gets a name, a time cost and a frequency, so you can see what a week of admin is actually worth. Then we automate the expensive ones first, inside your CRM, job system and accounting, as software you own rather than a chain of subscriptions.

Example workflow

An enquiry lands in the inbox. AI reads it, tags it as a quote request, and creates the lead in the CRM. The customer gets a reply saying who will call. The system drafts the quote from your price list. The salesperson checks it and sends it. Follow-ups go out on the days you set and stop the moment the customer replies. When the quote is won, the job is created, the accounting invoice is raised, and a review request goes out. The salesperson made one decision. The rest ran on its own.

  1. 1
    Enquiry email arrives
  2. 2
    AI classifies it
  3. 3
    Lead created in the CRM
  4. 4
    Auto-reply sent
  5. 5
    Quote drafted
  6. 6
    Follow-ups scheduled
  7. 7
    Won
  8. 8
    Job and Invoice created
  9. 9
    Review request sent

Integrations

Your accounting software receive the invoices and contacts your automations create, and report payments back so follow-ups stop when money arrives. Stripe and GoCardless take payments. Google Workspace and Microsoft 365 supply the inbox and calendar triggers watch. Twilio and SendGrid carry SMS and email. HubSpot and Shopify supply leads and orders, Slack and Microsoft Teams carry alerts and approvals, and your own systems connect by API.

Any system with an API connects. Click a logo to visit them.

Add AI when it actually makes sense

AI is optional. Most of what saves time here is plain rules. AI automation NZ businesses can trust has one principle: a person approves anything that reaches a customer. See how we use AI and everything else under automation.

Web app, mobile app and customer portal

Web app

The office team uses the web app to see every automation, what it ran today, what is waiting on a person and what failed. They adjust a rule, change a template or pause a workflow themselves. The ROI map lives here too.

Mobile app

Approvals and alerts reach the mobile app. A manager approves a quote from the ute, a technician gets the job change, and the owner sees the day's summary on the way home. Anything the automation needs a human for is one tap away.

Customer portal

Customers are on the receiving end of most automations: the quote to accept, the document to sign, the invoice to pay. In the portal they do each one, and their action triggers the next step. All three share one database, so nothing is copied.

Build options

FAQ

Anything that follows a rule: if this happens, do that. Creating the invoice when a job closes, chasing a quote after a set number of days, filing a signed form against the right customer. You can automate business processes that need a little judgement too, with AI classifying or drafting and a person checking. What we do not automate is the decision itself: pricing an unusual job or handling a complaint.

Zapier and Make are fine for linking two apps in an afternoon. The workflow automation NZ businesses come to us for is different: it runs inside your own system, holds your data, waits for approvals, and does not bill you per task. Their chains break quietly and cost more with every step. We often replace a tangle of them with one automation you own.

Reliable for the jobs we give it. Classifying an enquiry, pulling a total from an invoice or drafting a reply are tasks where AI is usually right and a wrong answer is cheap to catch. So anything AI produces for a customer waits for a person, and anything it was unsure about goes to a queue. AI never sends anything on its own.

In hours, then in dollars. Discovery gives every task a time cost and a frequency, so the ROI map states what each one costs your business a month. After go-live the platform counts the runs, so the same map shows hours actually saved against hours expected. If an automation is not paying back, the numbers say so and we change it.

Fast, because we choose it for speed. Automation for small business NZ owners is judged on payback, so the first one is usually the most expensive task on the ROI map with the simplest rule: job closed, invoice sent. It goes live on its own, before the rest is built, so your team sees hours coming back while discovery on the bigger workflows is still under way.

Yes. The platform, the rules, the templates and the data are yours. They run on hosting we manage, and you can move them to your own hosting or another developer at any time, with the documentation to do it. There is no per-task fee and no plan to upgrade when you add a workflow. A subscription tool's automations exist only while you keep paying.

The automation stops that record, not the whole workflow, and tells someone. A failed step retries on its own first, since most failures are a system briefly unavailable. If it still fails, the person who owns that workflow gets an alert saying which record, which step and why, with a retry button. Nothing is silently skipped, and the log lets you trace any invoice or email.

Yes, and most of the useful ones do. An approval step pauses the workflow until a named person says go: a manager approving a large quote, an owner signing off a purchase order, a clinician checking a letter before it reaches a patient. The request arrives on their phone, one tap approves or rejects, and if nobody answers in time it escalates. Every decision is logged.

Talk to Superstack

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.

List the three tasks your team repeats most. We'll come back with what each one costs and how to automate it.