SOFTWARE DEVELOPMENT

The system that does not exist yet.

Automation connects the tools you already have. Software development builds the product itself: something other people log into and often pay for. This page covers what that involves and when it is worth doing.

SaaS in plain English

SaaS stands for software as a service. It means software you use through a web browser and pay for by subscription, instead of buying a licence and installing it. Xero is SaaS.

From the builder's side, SaaS has one defining feature: a single system serves many customer organisations at once, and each of them must only ever see its own data. Those organisations are called tenants. Getting the separation between tenants right is the first architectural decision on any SaaS build and the hardest one to change later, so it is the one we spend the most time on.

If you are thinking about turning your expertise into a product that other businesses subscribe to, this page is for you.

Off-the-shelf, custom software, or a SaaS product

These three get muddled, and choosing the wrong one is expensive.

Off-the-shelf software is a product someone else built and you subscribe to. Xero, HubSpot and your practice management system are examples. It is the cheapest and quickest option, and the price of that is that you adapt your way of working to the software.

Custom software is built for one organisation's own use. A quoting tool shaped around how your firm prices work, or a portal your clients use to upload documents to you. We cover this kind of build on our web apps and business systems page, because it has different needs from a product.

A SaaS product is software you build to offer to many organisations. That is what this page is about. The moment more than one organisation logs in, you need tenant separation, permissions inside each tenant, onboarding, billing, support and a release process that does not break anyone's working day.

Here is the difference between this page and the web apps page in one line. A web app runs your business. A software product is your business, or a new part of it.

When to build and when to buy

Buy, if you can. If an existing product does most of what you need and the rest is preference rather than advantage, subscribe to it and automate around the gaps. Our automation work exists largely for that situation.

Custom software earns its cost in a few situations:

  • the software is the thing you sell, or plan to sell
  • no product fits the regulatory shape of your industry, such as compliance rules that differ between New Zealand and Australia
  • your method is your advantage, and an off-the-shelf tool would force you to work like everyone else
  • you are paying for several products to do one job badly between them

If none of those apply, we will say so in the first conversation.

What we build

These are the kinds of software we can build. If yours fits none of them, ask anyway.

SaaS products

Multi-tenant platforms where many organisations share one codebase and one database, kept strictly apart. We decide the tenancy model, the permission structure inside each tenant and the audit trail before feature work starts.

Compliance and regulated-industry software

Systems where the rules are the product: employment law, health and safety, immigration. An audit trail is a feature rather than a log file, every rule records where it came from, and who saw what, and when, has to be answerable months later.

Practice and case management systems

Software for professional firms that run their work as matters or cases. Intake, documents, deadlines, client updates and billing sit in one place. Law firms, licensed immigration advisers and accounting practices each have a version of this problem, with their own rules.

Booking, scheduling and membership platforms

For businesses that sell time or access, such as clinics, tutors, studios and equipment hire. Calendars that follow your rules, online payment, reminders, waitlists and memberships, offered to your own customers or sold to other businesses like yours.

Marketplaces and directories

Platforms that connect two sides, such as homeowners and tradespeople, with profiles, search, enquiries and reviews. The hard part is usually trust: checking who people are, moderating what they post, and deciding what happens when a job goes wrong.

Reporting and analytics products

Dashboards and reports your clients pay to see, built on data you already hold. For example, an agency's client reporting product, or a benchmark comparing a business with its industry without exposing anyone's figures.

Clinical and health-adjacent tools

Software that handles health information, where privacy is a design constraint from the first commit rather than a review at the end. In New Zealand that means designing for the Health Information Privacy Code 2020 as well as the Privacy Act.

Prototypes to test an idea

A small first version, built properly, to put in front of real users before committing to a full platform. It tells you whether people will use it and pay for it, and if they do, it can become the foundation.

Client portals

A secure place where your clients log in to see their own documents, progress or invoices. When a portal is part of a product sold to other businesses, it belongs here. When it is for your own clients only, it is a web app.

Internal tools that become products

A tool built for one organisation, then reworked so it can be offered to others. The gap between those two things is mostly isolation, permissions and onboarding.

AI-powered applications

Software where a language model does a defined job inside a larger system, such as summarising notes or drafting a document from structured data. The model is one component, with checks around it and a person reviewing anything that matters. It is never the whole design, and when a plain rule would do the job more reliably, we will say so and use the rule.

Integrations

Connections between your product and the systems your customers already use. Xero is the obvious one for New Zealand businesses. Good integrations handle the unglamorous cases: expired connections, rate limits, and data that arrives in a shape nobody expected.

Mobile-friendly web apps

Software that works properly on a phone, in the browser, with no app store involved. For many business uses that is enough, and it skips app store review altogether. Whether you need a native iOS or Android app depends on what it has to do, such as working offline or using the phone's hardware. Tell us early, because it shapes the plan from the start.

The stack

We build in TypeScript, with React and Next.js for the interface and PostgreSQL for data. Where tenants share a database, row-level security in PostgreSQL enforces the boundary, so a forgotten filter in one query cannot expose another tenant's records. Integrations use each platform's official API.

Every release passes an automated test suite before it reaches production, including tests that drive the product in a real browser. Hosting is chosen per project and billed to you directly.

We pick boring, well-supported technology on purpose. Your product should outlive any one developer's enthusiasm for a new framework.

How a build runs, from idea to launch

  1. Discovery & Audit. Who will use it, what must be true on the first day, and what rules your industry imposes. We write this down and agree it with you.
  2. Strategy & Roadmap. Architecture, written first: the tenancy model, data isolation, sign-in and permissions, the release path and hosting. Retrofitting any of these later is close to a rewrite.
  3. Build & Integrate. One thin slice first, a narrow path that works from sign-in to saved data, which tells us early whether the architecture holds. Then the rest in slices, each tested, reviewed and released to a staging copy you can use. You see progress as working software, not status reports.
  4. Launch & Deploy. A pilot with real users: a small group uses it for real work, and their problems become the final list before launch. Launch brings monitoring, backups and a support route.
  5. Optimise & Scale. A plan for the first changes users will ask for, released the way the build was: tested, reviewed and staged first.

Security and privacy, designed in

In a product other organisations rely on, security is part of the architecture, not a review at the end.

Sign-in is handled by a proven service rather than code we invent, and administrators use two-factor authentication. Permissions inside each tenant follow roles, so a junior staff member and an owner see different things. Records that need to stand up later, such as audit entries, are written once and never edited. Backups are automatic and restoring one is tested, not assumed.

Your customers will ask where their data is stored, and with New Zealand and Australian clients the answer matters. Hosting regions are chosen deliberately and written down. Under the Privacy Act 2020 your customers are trusting you with their people's information, and the product has to make keeping that trust the easy path.

What drives the cost

We don't publish a starting price for software, because the range is too wide to be useful. What we can tell you is what moves it. The number of distinct user roles. How many outside systems it connects to. Whether it has to apply rules that differ by country or state. How much of it must be auditable. Discovery and architecture come first as a separate, smaller piece of work, so you know the shape of the build before committing to it.

Ownership and handover

Code ownership is agreed in writing before any build starts. Hosting accounts are in your name and billed to you directly. Handover includes documentation and a working setup that a developer who was not involved can run on their own machine.

After launch

Software needs looking after. Libraries get security updates, platforms change their APIs, and in regulated work the rules themselves change. In a compliance product, statutory figures move every year and someone has to update them on time.

You can keep us on to do that work, hand it to your own developers, or split it. Whichever you choose, the documentation is written so the decision is genuinely yours.

When custom software is the wrong answer

Often. If you have not yet sold the idea to anyone, a well-run spreadsheet and some automation may prove the demand far more cheaply than a platform would. If a product already covers the job, buy it. And if the main appeal is owning something shiny, that is a reason to wait.

Architecture

Three layers, decided before feature work starts.

Customer experiencePortal
Team operationsWorkspace
Connected dataIntegrations

A conceptual model, not a claim about a client build.

QUESTIONS

Frequently asked questions

What is SaaS, in plain English?

Software you use in a browser and pay for by subscription, like Xero. For the business building it, SaaS means one system serving many customer organisations at once, with each organisation seeing only its own data.

Should we build custom software or buy an existing product?

Buy if a product does most of what you need. Build when the software is what you sell, when no product fits your industry rules, or when your way of working is the advantage an off-the-shelf tool would take away.

Do we own the code?

Code ownership is agreed in writing before any build starts. Handover includes a working environment for a developer who was not involved in the build.

How is this different from your web apps service?

A web app runs your own business and has one customer: you. A software product is offered to many organisations, so it needs tenant separation, onboarding, billing and a careful release process from the start.

Can you take over an existing codebase?

Sometimes. It depends on the state of the code and whether its architecture supports where you want to go. We assess that before committing to anything, and we tell you if a rebuild would cost less than a rescue.

What happens after launch?

The product needs looking after: security updates, changes when connected platforms update their APIs, and in regulated software, rule changes such as new statutory figures. You can keep us on for that work, hand it to your own developers, or split it between us.

NEXT STEP

Talk it through before you commit to anything.

A scoping call is where we work out what the problem is and what, if anything, is worth building.