Service 01

Software development

We build software that fits how your organisation really works, and that the next developer will be glad to inherit.

Overview

Useful software is mostly clear decisions.

Most software projects do not struggle because of the programming language. They struggle because the problem was never quite agreed, the risky parts were left until last, or the first version was too large to learn from.

We start by finding the smallest version that can do real work, then build it in short cycles with your people involved. Automated tests, code review and repeatable deployment are there from the first week, because they are far more expensive to add later.

You own what we build. The code, the infrastructure definitions and the documentation sit in your accounts, so continuing with us remains a choice and never a dependency.

What we do

From a first version to long-lived platforms.

  • Web applications and portals

    Customer portals, booking and ordering systems, dashboards and multi-tenant SaaS products, with attention to accessibility and performance on real devices.

  • APIs and backend services

    Well-documented REST and event-driven services with versioning, authentication, rate limits and useful error handling.

  • Mobile applications

    Cross-platform and native applications, with offline behaviour and secure storage designed in from the beginning.

  • Internal tools and automation

    Replacing fragile spreadsheets and repetitive manual steps with simple tools that keep a proper record of who did what.

  • Legacy modernisation

    Gradually replacing ageing systems while the business keeps running, using characterisation tests and staged cut-overs in place of big-bang rewrites.

  • Data and reporting

    Sensible schemas, pipelines and reporting that give people figures they can trust, along with clear lineage and retention rules.

  • Applied AI features

    Search, summarisation and assistive workflows, where they genuinely help, with evaluation, human review and careful handling of private data.

  • Code and architecture review

    An independent reading of an existing system, with a prioritised list of what matters and what can safely wait.

How it runs

How a software engagement runs.

  • 01

    Discovery

    We meet the people who will use the system, map the current process and agree the outcomes that matter.

  • 02

    Slice

    We choose a thin end-to-end version that tests the riskiest assumptions early.

  • 03

    Build

    We work in short cycles with working software to review, using tests, code review and automated deployment.

  • 04

    Launch

    We release in stages with monitoring, rollback plans and data migration rehearsals.

  • 05

    Evolve

    We support the system in use, watch how it behaves, and hand over at the pace your team prefers.

What you receive

Everything needed to run it without us.

  • Source code in your own repository, with a readable history
  • Automated test suite and continuous delivery pipeline
  • Infrastructure defined as code
  • Architecture notes recording the important decisions and why they were made
  • Runbooks for deployment, recovery and common operational tasks
  • A dependency and licence inventory

A good fit when

When this service tends to help.

  • You have outgrown spreadsheets or an off-the-shelf product
  • An important system has become slow or risky to change
  • You need a first version in users' hands, to learn from it
  • Your own developers need additional senior capacity for a period
  • You inherited a codebase and want an honest opinion on it

Questions

Things people usually ask

Do you work with our existing developers?
Yes, and we often prefer it. We can join your repository, tools and rituals, or lead a piece of work and hand it over to your team.
Who owns the code?
You do, once the agreed fees are paid. The specific terms are written into each statement of work, and open-source components stay under their own licences.
Should we rewrite our old system?
Usually not all at once. Replacing it piece by piece is slower to announce, but far safer. We explain the reasoning in our article on modernising legacy systems.
Can you give a fixed price?
For well-understood work, yes. For uncertain work, we suggest a short paid discovery first so that any later estimate rests on evidence.

Start a conversation

Tell us what you are trying to do.

A few plain sentences are enough. Send us the problem, the deadline if there is one, and what has already been tried. We will tell you honestly whether we are the right people to help.

Get in touch support@vnet.nz