Custom software case studies from Australian businesses
Cena Advisory builds custom software and mobile apps for Australian businesses. These case studies show the kinds of problems we solve for operators, practices, and teams. The three write-ups below are live: stock control, appointment booking, and an operational dashboard.
The hub
What these case studies are
This is the hub for Cena Advisory case studies. A case study here is a real problem a business brought to us, what we built to solve it, and what changed for the people who use it day to day. We build custom software and mobile apps, including custom business software, so most of these sit in one of three lanes: internal tools and web apps, phone apps for iOS and Android, and operational dashboards that join systems that otherwise do not talk to each other.
The examples below are anonymised. We describe a Melbourne retailer, a regional healthcare practice, and a logistics operator without naming them. If you are weighing up whether we are a fit, the shape of the work matters more than the logo on the sign. A retailer drowning in stock spreadsheets and a practice double-booking appointments are closer to your world than a named reference account would be. Read the About page for who you would be working with, or tell us about the project if you want to talk through your own.
Each write-up will follow the same shape. First, what the business was doing before, and why it was slow or risky. Then what we shipped, in plain language rather than a feature list. Then what is different now for the staff and customers who live with it. We keep the code, the spec, and the conversation in the same hands, so the case study reflects work we actually delivered, not a sales summary written after the fact.
Method
How we scope a case study
Before we write anything, we need to understand the work. That usually starts with a conversation, described on How we work, and sometimes a two-week discovery that turns a fuzzy problem into a written spec. A case study is built from that same understanding: what the business was doing before, what we shipped, and what is different now. We do not publish a write-up until the client has seen it and is comfortable with what it says.
We only state an outcome number when the client has confirmed it. Where a write-up would normally show a saving or a time reduction, we leave a TODO placeholder until the client signs it off. That means the early versions of these pages will read as honest rather than polished, and that is the point. If you want to know whether we can help with a problem like yours, the faster route is to tell us about the project than to wait for a finished case study. We will not invent a metric to fill the space, and we will not name a client who asked to stay quiet.
Examples
Three shapes of work, with live write-ups
Retail inventory app
Stock control for a Melbourne retailer with several shops. We replaced a spreadsheet-and-memory routine with one view of what is on the shelf, what is in the back room, and what needs to be reordered. The detailed write-up is live.
Healthcare booking app
Appointment scheduling for a regional healthcare practice. Patients book online, the front desk sees the day at a glance, and double-booking stops being a daily problem. The detailed write-up is live.
Logistics dashboard
An operational dashboard for a logistics operator. The team tracks jobs, vehicles, and exceptions from one screen instead of three systems and a wall of email. The detailed write-up is live.
Questions
Buyer questions
Do you publish client names in these case studies?
No. The work shown here is anonymised. We describe a Melbourne retailer, a regional healthcare practice, and a logistics operator without naming them. If a client wants a public write-up with their name attached, that is their call. Most prefer to stay quiet, and we respect that. You can read more about the studio on the About page.
What kinds of work are these case studies?
They are the three shapes of job Cena Advisory does most: custom software development for internal tools and web apps, mobile app development for iOS and Android when the phone is the right surface, and operational dashboards that join systems that do not talk. A case study here is a real problem, what we built, and what changed for the business.
Can I see something like my industry?
The examples below cover retail stock control, healthcare scheduling, and logistics operations. If your work is close to one of those, start with the retail inventory app, healthcare booking app, or logistics dashboard write-up. We do not lock the work to a single industry; the same point is on the FAQ. If it is not a close match, tell us about the project and we will talk through whether the shape fits. We work across Australian industries from Melbourne and take meetings and calls.
How do you measure the outcome in a case study?
Honestly, and only with numbers the client has confirmed. Where a case study would normally state a saving or a time reduction, we leave a placeholder until the client signs it off. We will not invent a percentage or a dollar figure to make the page look better. The How we work page explains how a project is scoped before any numbers are discussed. More answers sit on the FAQ.
Contact
Want a call?
Tell us about the project on the contact page, or email Felix. We take meetings and calls from Melbourne.