WEB APPS & SYSTEMS

Your business, off the spreadsheet.

Portals, dashboards, booking and quoting tools, built around how your firm actually works and connected to Xero and the rest of what you use. These are systems for running your business, not products to sell.

What we mean by a web app

A web app, in the sense we use it here, is a private system your team uses in a browser. Sometimes your clients use part of it too. It runs on a laptop at the office and on a phone in a ute, holds your business's information in one structured place, and does the specific jobs your business needs done.

It has one organisation behind it: yours. That single fact shapes everything about how it is built.

How this differs from software development

We also build software products, and the two are easy to confuse. The difference is who the system is for.

A business system, the subject of this page, runs your own operations. Your staff, your clients, your rules. It can be shaped exactly around how you work and changed whenever your process changes, because nobody else depends on it.

A software product is offered to many organisations, each of which must be kept apart from the others. That needs tenant separation, onboarding, billing and a release process that cannot break anyone's day. It is a different engineering job, and it is covered on our software development page.

If you might one day sell the system to other firms like yours, tell us at the start. It changes the foundations, and changing them later costs far more.

The spreadsheet problem

Spreadsheets are brilliant. Nearly every business system starts life as one, and plenty should stay that way. The trouble begins when a spreadsheet quietly becomes the system the business runs on, and you can usually tell when that has happened:

  • several people edit it, and someone has overwritten someone else's work
  • there are copies called "final", "final v2" and "USE THIS ONE"
  • the formulas make sense to exactly one person, who would like to take a holiday
  • figures are copied from it into Xero by hand
  • nobody can say who changed a number, or when
  • client details get emailed around as attachments

That last one matters more than it looks. Under the Privacy Act 2020, personal information has to be protected by reasonable security safeguards. A spreadsheet full of client details sitting in half the team's inboxes is hard to defend, and if it leaks, it is hard to even work out who had a copy.

A web app replaces the spreadsheet with structured records, permissions and a history of changes. People see the parts they need, nothing more. Figures are entered once.

There is a fair test for when not to bother: if the spreadsheet works, is used by one person, and holds nothing sensitive, leave it alone.

What we build

Client portals

A secure place where your clients upload documents, see where their job or application is up to, and sign things off. It replaces long email threads with attachments in them. Each client sees only their own records, and you can see who accessed what. Immigration advisers, accountants and law firms are obvious fits, and our guide to automation for immigration advisers shows where a portal fits in that work.

Dashboards

One screen with the numbers you actually run the business on, drawn automatically from Xero, your CRM and your job system. The hard part is rarely the chart. It is agreeing what each number means, such as what counts as a lead or when a job is finished, and then making sure every source agrees with that definition.

Booking and quoting systems

A quote built from your own price list and rules, with your margins and minimum charges applied the same way every time. Prices are always calculated by rules you have approved, never estimated by AI. An accepted quote can become a job, the job can become a draft invoice in Xero, and a person approves the invoice before it is sent.

Job and workflow tracking

A board showing every job, who has it, what stage it is at and what is overdue. For a service business that moves work between people, this is often the first system worth building, because it is the one everyone looks at.

Internal tools

Onboarding checklists, compliance registers, equipment logs, staff rosters. Small systems that remove a weekly annoyance and give you a record you can rely on when someone asks what happened.

Connecting to Xero and the rest

Most New Zealand service businesses already run their finances in Xero, and a business system should work with it, not around it. Through Xero's API a system can create contacts, raise draft invoices and check whether an invoice has been paid. We have built a Xero integration into a production platform, so we know where the edges are.

Our rule is one source of truth for each kind of information. Financial records live in Xero. GST is worked out by Xero's own tax settings, not re-implemented in our code, and anything that feeds an IRD return stays in Xero where your accountant expects to find it. Our guide to automating Xero invoice processing covers which steps still need a person's sign-off.

Beyond Xero, systems commonly connect to MYOB, Microsoft 365 or Google Workspace calendars and email, payment providers, and whatever job or practice management tool you already use. Where a connection is simple, an automation workflow can be the better tool for it than custom code.

How a build runs

  1. Discovery & Audit. We look at how the job is done today and at every tab of the spreadsheet it depends on, including the ones nobody admits to.
  2. Strategy & Roadmap. We decide what the system holds and who sees what: the records, the fields, the roles and the permissions. This is written down and agreed.
  3. Build & Integrate. We build the screen that replaces the most-used tab. The first version does one thing well, with your real data in it.
  4. Launch & Deploy. For a period it runs alongside the spreadsheet, so you can check the new system agrees with the old one. Then you move over, and the spreadsheet is archived read-only, so history is kept and nobody keeps updating it out of habit.
  5. Optimise & Scale. The best requests come from people who have used the system for real work, so that is where the next changes come from.

A worked example

Take a hypothetical electrical contractor that quotes from a spreadsheet. The office manager copies the client's details in, picks items from a price list tab, adjusts the labour by hand and emails a PDF. Accepted quotes are retyped into the job board, and later into Xero.

The web app version starts with a quote form. The client is chosen from the records already in Xero, items come from the price list with the firm's own rules for margins and call-out charges applied automatically, and the quote is sent with a link the client can accept online. Acceptance creates the job, assigns it, and lists the materials to order. When the job is marked complete, a draft invoice appears in Xero for the office manager to check and approve.

Nobody types anything twice. The spreadsheet still exists, archived, for anyone who wants to look up an old quote.

What it costs to run

Building the system is one cost. Running it is another, and we tell you about it before you commit. Hosting, any third-party services it uses and its domain are billed to you directly, so nothing is marked up or hidden. Software also needs occasional care: security updates, and changes when a connected tool such as Xero updates its API. You can keep us on for that or hand it to your own developer.

Data, permissions and privacy

Every system we build has roles: who can see, who can edit, who can approve. Clients see their own records only. Changes are logged, and backups are part of the setup, not an afterthought.

We tell you where the data is hosted before anything goes live. And if something does go wrong, the Privacy Act 2020 requires a notifiable privacy breach to be reported to the Privacy Commissioner as soon as practicable. A system with access logs makes that far easier to assess than a spreadsheet that went who knows where.

Ownership and support

The system runs in accounts in your name, and the documentation is written for someone who wasn't there when it was built. Code ownership is agreed in writing before any build starts. You can keep us on to maintain and extend it, or hand it to your own developer. Both are normal.

Starting small

The first version of a business system should be smaller than you think. One screen that replaces the spreadsheet tab everyone uses, connected to the one tool it matters most to connect. Once that is in daily use, the next piece is usually obvious, and it is cheaper to build because the foundations are already there.

When a web app is the wrong answer

A product already does it. There are good job management and practice management products built for New Zealand businesses. If one fits, subscribe to it, and use automation for the gaps.

The spreadsheet only exists because two tools don't talk. Then the fix is connecting the tools, which is automation, not a new system.

Your process is still settling. Build once it has stopped changing every month.

You want to sell it. Then it is a product, and you need the software development approach from day one.

QUESTIONS

Frequently asked questions

What is the difference between a web app and your software development service?

A web app runs your own business and has one organisation behind it: yours. Software development builds products offered to many organisations, which need tenant separation, onboarding and billing. If you might sell the system later, say so at the start.

Can a web app replace our spreadsheets?

Usually, if the spreadsheet has become the system your business runs on. A web app gives you structured records, permissions and a history of changes. If a spreadsheet is used by one person and holds nothing sensitive, it is often fine as it is.

Does it connect to Xero?

Yes. Through Xero’s API a system can create contacts, raise draft invoices and check payment status. Financial records stay in Xero, GST is handled by Xero’s own tax settings, and a person approves invoices before they are sent.

Can our clients log in to it?

Yes, through a client portal. Each client sees only their own records, such as documents, job status or items waiting for their sign-off, and every access is logged.

Do we have to replace the tools we already use?

No. A business system works alongside Xero, your CRM and your practice management software, and fills the gaps between them. If an existing product already does the job, we will suggest using it.

How much does a web app cost?

It depends on how many screens, roles and connections it needs, so we quote after a scoping call rather than publishing a starting price. Running costs such as hosting are billed to you directly, and we tell you what they will be before you commit.

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.