Software, robotics and websites, built to fit.

Most businesses bend themselves around tools that nearly fit.

It starts with a conversation about what is actually going wrong. Then we build the thing that fixes it, and stay on to run it.

Start a conversationSee what we’ve built

Working with
More on each

What changes

Where you are now, and what you have instead.

Software

Now

Your process lives in a spreadsheet and three people’s heads.

Craig points to a line of code on a monitor while Simon looks on.
Instead

One system, built around how you actually work.

Off-the-shelf platforms make you work their way. We build to the process you already run, so nothing lives in a side spreadsheet, and when someone asks what happened, the system can show them.

Sounds familiar?See how it works

Robotics

Now

The places survivors are trapped are the places rescuers can’t safely go.

Instead

Robots that walk where wheels stop.

Each foot picks its own ground, so the robot can step over debris, keep its footing on loose material and carry its sensors into gaps people can’t safely reach.

Sounds familiar?See how it works

Websites

Now

Every change to your site is a quote and a fortnight.

The Nug General Store website: the NUG. wordmark over a photograph of the shopfront window, its gold lettering reading “Handmade pasta”, beside a sage panel reading “Ben makes everything himself. Ruxi looks after everyone.”
Instead

A site you can change yourself, the afternoon you decide to.

Fast, accessible and built for the people who use it. When the menu or the hours change, you change them, without a quote or a fortnight’s wait.

Sounds familiar?See how it works

Craig talks through code on a monitor while Simon types at the keyboard.

Why we work this way

Different work, the same complaint underneath it.

A platform that does eighty per cent of the job. A template site that fights you every time you edit it. A system specified by someone who had never had to run the place. Every one of them ends with the organisation bending to fit the tool.

Between us we have spent years running operations, not only building software for them — which is most of why we notice when a system has been specified by someone who has not. We make our own tools and run our own hardware, and the same small team does the whole job. That is why the answer is the same in all three: work out what is actually wrong, build to that, and stay on to run it.

Who we work with

Clients & partners

Client

A TGA-regulated medical device portal — front end, API, design system and hosting, built to IEC 62304.

Industry partner

Full industry partner with QUT, with student capstone teams working on live projects with us.

Client

Rebuilt a ten-year-old training platform, then added AI marking that runs on hardware we own in Australia, so student work never goes to a third-party AI service.

The team

Everyone you will actually deal with

Craig Schneider

Founder & Technical Director

Computer science, engineering, and two decades on site. Runs the shop.

Simon Hanmer

Lead Developer & UX

Designs it and builds it. Twenty years in kitchens before the degree.

Ronan Donahoe

Testing & Robotics

Finds it before the auditor does.

Asuka Hirai

Testing & Machine Learning

Tests it until he knows why it works — computer science, with a background in machine learning.

Tom Lee

Backend & Platform Developer

Backend, and the platform under it. Knows why it broke at 2am.

Read the longer version →

Tell us what you are trying to build.

Start a conversation