About
A digital studio that came out of running real operations.
- Based in
- Griffith, NSW, Australia
- Working across
- Griffith and the Riverina and regional New South Wales
- Sectors
- Hospitality, events and entertainment, trades and services, multi-site operators
Why we build what we build
The problems came first. The software came after.
Running events and working inside venues means seeing the administration up close: the stock order placed by text message, the incident written on a form that took a week to reach a manager, the ticket sales handed to a platform that kept the customer list, the roster and the till and the compliance folder that never agreed with one another.
None of that is a technology problem to start with. It is a process problem that technology can fix once someone has actually understood the process. That is the order we work in, and it is why discovery is a paid stage rather than an unpaid sales call — it is where the value is.
Being based in Griffith matters for the same reason. A business in the Riverina is not a smaller version of a business in a capital city; it has different staffing, different margins and different tolerance for software that needs a specialist to operate. Everything here is built for that.
How we work
Six things we will not trade away.
These are the commitments that decide what we take on and how it is priced. They are also the ones most likely to cost us a job, which is rather the point.
- 01
Understand the process before proposing software
Most bad software is a correct solution to a misread problem. We start by watching how the work is done today, by the people who actually do it, before anyone draws a screen.
- 02
Price what can be priced, quote what cannot
Websites and support have published prices. Applications and automation get a paid discovery and a fixed-scope proposal. A confident number given before the data model is understood is a guess with a decimal point.
- 03
Say no when the answer is no
Sometimes an integration is not possible, a listing cannot be claimed the way somebody hoped, or the process should be fixed before it is automated. We would rather lose the sale than be the reason a project fails halfway.
- 04
Build so somebody else could take over
Boring, well-supported technology. Code you own, in a repository you control, on infrastructure in your name. If you ever want another developer, the handover is a folder, not a negotiation.
- 05
The audit trail is a by-product, not a chore
If a system requires people to record what they did, the record will be wrong. We build so that doing the work produces the evidence.
- 06
Accessible and fast are not upgrades
Keyboard navigation, visible focus, colour contrast, reduced motion and a performance budget are part of the base build. They are not a line item and they are not optional.
Honest limits
Who we are not the right studio for.
Every studio has work it should turn down. Saying so up front saves everyone a consultation.
- Businesses looking for the cheapest possible template site
- Projects where the brief is fixed and discovery is not welcome
- Anyone wanting guaranteed search rankings, which nobody can promise
- Work that requires acting on a Google listing without the owner's authorisation
- Automations designed to remove a decision that genuinely needs a person
If that sounds like the way you want to work, let’s talk.
A consultation is a conversation about your process, not a pitch. You will leave it knowing whether there is a project here.