Applications, integration and automation · Auckland, New Zealand

Writing the software was never the hard part.

Deciding what is actually worth building. Proving it works. Releasing it without drama. Keeping it true for years, after everyone who chose it has moved on.

That is the difficult part of software, and it is the part Bits@Work is organised around.

We are not attached to any technology. We are attached to the result still standing in five years.

Start a conversation

How the quality actually happens

Six practices, in order
01
Understand the goal, not the request
We examine a requirement until the business problem underneath it is visible. Bits@Work would never recommend building a custom system where a simple one already exists — an answer that costs us the sale and saves you a decade.
02
Decide in writing
Every decision that shapes the system is recorded — what was chosen, what it cost, and the conditions under which it should be revisited. A year later nobody has to reconstruct the reasoning out of the code.
03
Choose the technology last
Platform, language and vendor are consequences of the problem, never preferences carried in from the last project. The right choice is the one you can still afford to run, staff and change in five years.
04
Prove it, rather than claim it
Nothing is finished because somebody says it is. It is finished when it has been tested, reviewed, written down, and demonstrated on the real system with real data.
05
Release on purpose
Environments, versions and cutovers are planned acts with a way back, not things that happen to you late on a Friday. You are told what is going out, when, and what changes for the people using it.
06
Own what is running
Monitoring, cost, incidents, the unglamorous maintenance. A system nobody is accountable for is a system quietly going wrong in a way you will find out about at the worst moment.

What “done” means here

Three conditions. All three, or it is not done.

It works

Demonstrated on the real platform with real data — and checked by someone other than the person who built it.

It is understood

Documentation written while the work happened, describing the system as it actually is rather than as it was once planned.

It can change

The next person can safely alter it without an archaeology project. That is what protects the investment.

Technology is a means. We match it to the goal.

Modern where modern earns its place; deliberately boring where boring is safer. What we are good at is choosing well — a system that is efficient to run, reliable under real load, and still supportable long after the fashion has moved on.

Cloud platforms
Microsoft Azure · Amazon Web Services
Mobile
iOS and Android, built to ship and to survive real use
Enterprise systems
The applications a business actually runs on
Data & analytics
Making what the business already knows usable
Artificial intelligence
In the product where it helps the user — and in the delivery, where it does the drafting a human then answers for

Work

Selected work
iOS · Speech & translation · Applied AI

Loquela

A voice back — in the person’s own language, on both sides of the conversation.

It listens, translates, speaks, and helps the person find the words when they cannot start. Bits@Work took it from the clinical problem through to a device in daily use: the product decisions, the app, the services behind it, the cloud it runs on, and every release since.

iOSMicrosoft Azure.NET servicesSpeech & translation
Beverages · Enterprise integration · Mobile

Suntory Beverage & Food

Core systems that finally talk to each other — and reach the people in the trade.

SAP at the centre, trade promotion management alongside it, and staff who need what is inside both, on a phone. Bits@Work built the connections and what sits on top of them: interfaces into SAP, trade promotion interfaces and dashboards, mobile applications, and a series of line-of-business automation platforms.

SAP integrationMobile applicationsTrade promotion managementAutomation platforms
Clients

Suntory Beverage & Food (formerly Frucor) · Insightful.Mobi · Business Mechanix · Avanti Finance · Crossware · Tanglin Consulting · DocumentOne · Pacific Horizon Motorhomes · Sheppard Center Australia

Community

Bits@Work supports and sponsors the Doina Community, the Romanian community in Auckland — managing their IT infrastructure, Microsoft 365, CRM, newsletter platform and public website.

If you have something that has to keep working for a long time, we should talk.

Tell us the problem before the solution. If Bits@Work is the wrong answer for it, we will say so.

info@bitsatwork.co.nz