Skip to content

Web app development

When a spreadsheet, a shared inbox and a lot of double-handling are holding a process together, a small custom application usually pays for itself faster than another subscription. We build the tool that fits the way you already work.

What it is

Web app development, in plain terms

A web app is software you use in a browser rather than a program you install. Staff sign in from any computer or phone, the data lives in one place, and there is nothing to update on individual machines.

The ones we build are usually not ambitious in scope. A booking system that matches how your bookings really work. A client portal where customers see their job status without ringing you. A quoting tool that produces the same document every time. An internal dashboard that pulls numbers you currently copy between spreadsheets.

We build with the same technology used for large commercial products, but sized to the job. That matters when the thing is still running in five years and needs a change.

Why it matters

Why your business needs this

Most businesses reach a point where an off-the-shelf product does eighty per cent of what they need, and the missing twenty per cent gets handled by hand. That manual gap is where the errors, the delays and the wasted hours live.

Manual handling costs more than it looks

Twenty minutes a day rekeying data between two systems is roughly two working weeks a year, every year, plus the mistakes. Custom software is often cheaper than the labour it removes.

Spreadsheets stop scaling at exactly the wrong time

A shared spreadsheet works until two people edit it at once, a formula gets pasted over, or the person who built it leaves. By then the business depends on it.

Subscriptions add up and still do not fit

Paying per user per month for four tools that each do part of the job is common. One application that does the actual job usually costs less over its life.

Customers expect self-service

Letting clients check a booking, see a job status or download an invoice themselves removes a pile of phone calls from your week.

Why through us

One team instead of four suppliers

Custom software is where the multi-supplier problem bites hardest. A developer who only writes code will hand you an application and leave you to find hosting, arrange a domain, sort out sign-ins, and work out who to call at two in the morning when it stops responding. That handover is where most small business software projects quietly die.

We build it, host it, connect it to the domain and email you already have with us, and keep it running afterwards. If your app needs to send email, it sends through the Microsoft 365 or Google Workspace account we set up, configured properly so the messages arrive instead of landing in spam.

And because we also run your IT support, the staff using the app can raise a problem the same way they raise any other problem. They do not need to know whether an issue is the app, the network or their laptop. That is our job to work out.

What you get

What is included

Scoping before quoting

We sit with the people who will use it and map the process as it really runs, including the exceptions everyone works around.

A working version early

You use something real within weeks, not at the end. It is far easier to say what is wrong with a working screen than with a document.

Sign-in and permissions

Staff accounts with the right access levels, and single sign-on with your Microsoft 365 or Google account where that makes sense.

Integration with what you already run

Connections to accounting, payments, email or whatever else the process touches, so data stops being retyped.

Hosting, backups and monitoring

Run on infrastructure we manage, backed up daily, with alerts that reach us before they reach you.

Documentation and handover

Written instructions your staff can follow, and the source code, so you are never locked in to us.

How it runs

From first call to done

You will always know what stage the work is at and what happens next.

  1. Map the process

    We watch how the work is done now and write it down, including every step someone does by hand.

  2. Agree the smallest useful version

    We identify what has to exist for the tool to be worth using, and deliberately leave the rest for later.

  3. Build in short stages

    You see progress regularly and can redirect it. Nothing goes six months without you looking at it.

  4. Test with real staff and real data

    The people who will use it every day try it before launch, on their own devices.

  5. Launch and keep improving

    We put it live, watch how it gets used, and make the adjustments that only become obvious once people rely on it.

Common questions

How much does a custom web app cost?

It depends entirely on scope, which is why we scope before we quote rather than after. Small internal tools are considerably cheaper than most people expect. We will tell you early if an off-the-shelf product would do the job for less, because sometimes one will.

Should I just buy existing software instead?

Often, yes, and we will say so. Custom is worth it when the existing options force you to change how you work, when you are paying for four tools to cover one process, or when the missing piece is being done by hand.

What happens if we stop working together?

You get the source code and the data. We will help move it to another provider. There is no scenario where your own business software is held over you.

Can it connect to Xero, MYOB or our booking system?

Usually. Most business software has an integration interface, and we check what is possible during scoping so there are no surprises later.

Will it work on phones?

Yes. Anything staff or customers use away from a desk is built for a phone screen first.

Got a process held together by a spreadsheet?

Tell us what you have now and what is not working. We will come back with a straight answer on what it takes and what it costs.