Frequently asked questions

The questions we get asked most often, answered straight. If yours is not here, ask us — it costs nothing and we would rather you knew.

What happens after our software launches?

We do not treat launch as the end of an engagement. Support, maintenance and further development are agreed as part of the work rather than bolted on afterwards, and the shape of that depends on whether you have a team to hand over to or would rather we kept running it. We build and operate our own products, so running software in production is ordinary work for us rather than something we hand off and forget.

How long does a typical project take?

It depends on what you are trying to achieve. A prototype meant to prove an idea, or to put something in front of investors, is usually a matter of weeks. A full build is measured in months, and depends on scope, how much is already decided, and how quickly decisions can be made on your side. We would rather stage a longer build into useful releases than disappear for six months and hope.

You are based in New Zealand. Does that work if we are not?

Yes. We work with clients worldwide and have done for years, so distributed delivery is normal for us rather than an experiment. Overlap hours are something we agree at the start of an engagement rather than discover halfway through, and the time difference is often an advantage: work continues while your own team is asleep.

Can you work alongside our existing team?

Often that is exactly the arrangement. We work as an extension of an in-house team as readily as we work on our own, and we are comfortable inside a codebase somebody else wrote. If what you need is a second opinion rather than more hands, we also review software and hardware independently for usability, functionality and code quality.

Do you only build new software, or work on what we already have?

Both. A good proportion of our work is extending, stabilising or rethinking software that already exists and already has users. That is a different discipline from starting on a blank page, and it rewards being careful rather than being fast.

What technologies do you use?

Whichever ones fit your problem. We deliberately do not advertise a stack, because choosing the technology before understanding the problem is how projects end up carrying decisions nobody can defend two years later. What we will do is talk through the realistic options for your situation, including what each one will cost you to live with once we are gone.

Do you work with start-ups?

Yes, and we structure the engagement to suit. For start-ups and early stage technology companies we offer equity-based payment structures depending on the opportunity, conditions apply. The point is to give a good idea a route to a real build before the funding exists.

What kinds of problems do you work on?

Primarily business software — the systems a company runs on. We build custom CRM, ERP, personnel management, fleet management and operations software. Between that and our own products, our work also covers time tracking and billing, field operations, asset management and inspections, venue and facility booking, and start-up MVPs. If you are not sure whether yours fits, ask.

How does a project usually start?

With a conversation, virtually or over coffee. From there it is usually a short discovery to pin down scope and constraints, and then either a prototype or a staged build depending on how much certainty you already have.

How do we know whether we are a good fit?

The honest answer is that a conversation settles it faster than a web page can. An obligation-free chat costs you nothing and usually resolves it in half an hour, including the cases where we tell you that you do not need us, or that somebody else is better placed to help.