All sprints
Completed 8 August 2026 Sprint 01 · Allied Health (Physical Therapy) · Sydney

Notes from one Saturday inside a working clinic.

A clinic opened up how it really runs. Then the room built.

The business was Wally’s Health, a physiotherapy and chiropractic practice. The day opened with the owners telling a room of builders how it actually works. Insurance invoices that go out and come back on the insurer’s schedule. Forms written up in the evening after a full day of patients, and patient conversation scattered across three accounts. Every team demoed live by close, and four of the five are still taking what they started to market.

A builder sits with a laptop showing the clinic journey mapped across five colour-coded stages, with the seated room out of focus beyond.
Mapping the clinic, stage by stage.
The business
Wally’s HealthPhysiotherapy and chiropractic clinic
Teams
5
Builders
12
Product demos
5All live, all same day
Going to market
4 teamsStill pursuing it after the day
The day
5 hoursNoon to five, and people stayed on

The opportunity

A large market that software has barely reached.

Physical therapy is one of the busiest corners of Australian healthcare, with hundreds of thousands of appointments a week and steady demand from an ageing population. A market that big with software this thin doesn’t come up often. Most of it still runs on tools that were never shaped around how these clinics work.

~$5.7bn Combined annual market
16,000+ Independent clinics
45,000+ Registered practitioners
Open field No dominant software player

Sources: IBISWorld (2025); Australian Physiotherapy Association; AHPRA.

The method

Five stages, run against a business with patients booked in.

The Sprint Method is the same wherever it runs. The stages exist to get a room of outsiders oriented fast, and to keep ideas moving before anyone commits to one. Understand the problem the way the business actually experiences it, and the boundaries of a workable answer show up alongside it. Here’s what each one looked like with a working clinic in the room.

A moment from the day.

Prime

The business owner took the stage first, answering questions about how the practice really runs. What makes someone book, what makes them stay, where the work stops paying. He was candid about the parts of the business that run on memory instead of measurement.

The session was supposed to end and didn’t. The questions kept coming, and a second practitioner, this time from the audience, added her own read on the same ground.

Four things surfaced and then stayed up for the rest of the day. How patients find the clinic at all, and how little of that is measured. The paperwork that trails a workers compensation patient, which lands in a clinician’s evening. Insurance invoices that go out and come back whenever the insurer feels like it, sometimes not at all, while the practitioner has already been paid for the session. And patient conversation spread across accounts, email and text, which is quietly the difference between someone rebooking and someone drifting off.

A seated room listens as one person speaks, viewed from among the audience.
The owner taking questions from the room.

Frame

Frame runs on the 5 E’s, a customer-journey model that works through a business one stage at a time, from how a patient first hears about the clinic to what brings them back years later.

In an open conversation the interesting parts crowd out the rest. Take the stages one at a time and every stage has to produce an answer, so the whole journey ends up laid out side by side and comparable.

The owners walked the room through their own business, from both sides of the partnership, and came out with a map of what they run. Where the value is made, and which of the moments that matter most to a patient is worth putting effort behind first. Underneath the stages sit three questions the owner is always asking. Where does the clinic lose time, money, quality or patients. Where does the experience lean too heavily on one practitioner. And what gets harder as the business grows.

Every build below came off that map. The front door, the paperwork, the money, and the conversation that decides whether a patient comes back.

The five stages of the clinic journey, Entice, Enter, Engage, Exit and Extend, each with a short description and a patient quote. The problems and the potential value listed under each stage are deliberately obscured.
Scroll sideways to see all five stages.The 5 E’s mapped onto an allied health clinic. Working through the detail is what a sprint does in the room.

Build

After ninety minutes of that, each team chose a problem and checked the direction with the owners before committing to it. The owners stayed at the tables. A question about insurance or patient communication or clinical risk got answered in a minute, so nobody had to guess and then build on the guess.

Putting a real business in the room and keeping the people who run it there is the whole bet the format makes. By the demo, every team had something concrete enough for the owners to challenge, extend or recognise.

Builders at tables around the room, working on laptops in small groups, with the street visible through floor-to-ceiling windows.
Heads down, with both owners still in the room.

Demo

Every team demoed live, and the owners reacted in the room. One team learned on the spot that the shared invoices inbox needed triaging before anything downstream would help, which hadn’t been in their build an hour earlier. Another had already folded in something an owner told them, and got to watch him recognise his own words in the working product. A third had gone as far as connecting to a trial account of an existing practice management system, so what the room saw ran end to end.

The room gathered in a wide circle of chairs and tables, laptops open, watching a demo.
Demoing via video call due to technical difficulties (oops).

Grow

The day closed with judging, and over $1,000 in Codex credits went to the teams to help them get what they built to market.

The builds

What got built, and what the owners said when they saw it.

In the order they were demoed. Nobody handed out a brief; each team picked its own problem.

Build 01

Cash flow for a business that gets paid by insurers

The claims dashboard, showing outstanding, overdue and expected collections, with an aging snapshot beside it. Sample data.

Insurance invoices go out and come back whenever they come back. There was nowhere to look to see what was owed, so chasing happened from memory, in a batch, at the end of the week.

The team built a dashboard that pulls what already sits in Cliniko into one view. Outstanding, overdue, due in the next seven days, and what the clinic can expect to actually collect. Nothing on the screen was invented. It’s the shape of the clinic’s own data, arranged so chasing becomes something you plan instead of something you remember. Around it they put rules for keeping invoices moving, with a person approving anything that goes out, a view of which payers actually pay on time, and separate screens for an owner and for a receptionist.

The owner said it made the job easy. Then he asked for something the demo hadn’t covered: could it triage the invoices inbox as well.

Build 02

AI-driven compliance for allied health

The treatment request tool, stepping through the sections of the form and totalling the services requested. Sample data.

Every workers compensation and CTP patient needs an Allied Health Treatment Request. It’s a PDF, and it gets edited by hand. A new one has to be written to request each new block of sessions, and it takes somewhere between 40 and 60 minutes. A clinician seeing 16 to 18 people a day doesn’t have that hour, so it happens in the evening or at the weekend.

Their generator reads the notes a clinician already has and fills the form out: current presentation, the compensable injury, risk screening, capacity for work, outcome measures, barriers to recovery, treatment plan. Nothing goes straight to a PDF. The clinician works down the form field by field, checking each one against the notes, and the tool only exports the document once every field is confirmed.

The treatment request is one form of several. The same evening job, turning clinical notes into a compliance document by hand, repeats across the rest of the paperwork allied health runs on.

Build 03

The reconciliation layer between a clinic and its insurers

Remittances from each insurer matched back to the invoices and sessions they cover. Sample data.

When an insurer finally pays, a remittance lands in the clinic’s accounts inbox and someone has to work out which sessions it covers. One payment can cover several sessions across several patients. So it’s a matching problem, and that’s why the clinic batches it up and loses an hour to it at the end of the week.

They built the whole loop. An invoice goes to the insurer, the remittance comes back into the app, and the practice manager checks the money actually landed in the bank before confirming it and settling the sessions.

They talked to the owners for the best part of an hour before writing anything, and what they built after that was deliberately rough. Enough of the loop to find out whether they had the problem right, and no more.

Build 04

Patient acquisition for practices Salesforce was never built for

The landing page built for the clinic, with the customer system sketched behind it.

One team went at the other end of the journey: how a practice gets found at all, and how it keeps track of the people it has already met.

The landing page they built had real branding and search visibility in mind, and they sketched a customer system designed for a medical practice. Salesforce is the wrong shape for a clinic with a handful of practitioners. A clinic needs one channel for contact, for follow-up, and for bringing a patient back.

They also put a question to the room that nobody else had asked: what would it take for an AI assistant to recommend this practice when a patient asks it where to go.

Build 05

The relationship layer between visits

Patient conversation is spread across the practice management system, email and text. Keeping up with even one of those is more than a full day of back-to-back appointments leaves room for. The cost of switching between them lands on the practitioner, usually at home in the evening.

This team spent their time with the owners first and built afterwards. They ended up with one surface for messages from existing patients. A check-in comes in, the assistant drafts the reply, and the patient’s treatment history sits beside the conversation, so whoever answers already has the context in front of them. When a question carries clinical risk it stops and asks a person to review and approve before anything goes out. In this industry you can’t leave that part out.

The demo ran against a real Cliniko integration while the room watched, on a trial account with test patient notes rather than the clinic’s own system or anyone’s real records.

The Hackathon was able to showcase how individuals from different expertises, skillset with the aid of tech tools can effectively provide solutions for day-day challenges faced by small businesses. As clinicians, this event has given us the live opportunity to witness the potential of working cohesively across different industries. We are motivated to nurture this relationship whilst on our journey to upscale our practice. The horizon to expand ideas into reality is limitless.

Wally’s Health

After the day

What happened once everyone went home.

This was the first sprint, and the clinic and the room were testing the same thing: whether a day is enough for outsiders to understand a business well enough to build something its owners recognise.

Four of the teams are still pursuing what they started, and three of them are doing it with the Wally’s Health team. Two are carrying on with what they demoed: the compliance document tool, which turns a clinician’s unstructured notes, across as many sessions as a claim runs, into a treatment request draft, and the patient messaging platform, which handles the routine questions a clinic fields all day and gives practitioners a way to stay in contact with patients they’ve already treated. The third built the claims dashboard and is now working with the clinic on something else in the same space. So is the fourth team, minus the clinic.

Where a team keeps going, the business can choose to stay involved as a design partner while the first version takes shape, or to leave it at the demo, and that choice is theirs. The builders own what they build, and a business that stays involved gets a say in it and early use of it.

Three teams picked the same insurance problem, and nobody pointed them at it. Put a room of outsiders in front of a business and they agree quickly about where the money is going. For Wally’s Health that turned a recurring cost into a clear priority with several approaches to compare. For a builder it sets up the next test, which is whether the same approach holds up beyond one clinic.

We didn’t get a verdict, just a pattern. The teams that spent the most time understanding the business were the ones most likely to carry the idea on afterwards, and that mattered more than the stack they picked or how early they started building. Access to the people who run the business was the scarce part, and the format is what created it.

At least two teams integrated an external system inside the day. One went into the clinic’s practice management software, one into a language model API doing the document work. Neither the plumbing nor the interface turned out to be the constraint. Several teams didn’t use the whole build window. They put more than half their time into the owners and still had something working in half an hour to forty five minutes.

None of that depends on the industry. Sprint 02 will run the same method against a different business, and different things will fall out.

The next sprint is being planned.

The date for Sprint 02 is coming soon. Both sides of the room are being lined up now, and putting your name down is how you’ll hear it first.

Businesses

Bring something you want to grow

You already know the part of your business that loses hours, or leaves revenue sitting with someone else for months, or lets a good customer quietly go. Bring that. You get a room of product builders on it for a day, and an honest read on whether software would move it or whether the answer is something simpler. Free to take part, and nothing gets published about your business without your say-so.

Bring a business opportunity
Builders

Get inside a business before you build

Spend a day with the people who run it. Ask the questions you can’t ask from behind a screen, then demo what you built before you go home. The hard part of building something people want was never the building. Free to take part.

Register your interest as a builder

Not ready for either? One email per sprint: what ran, what got built, and what happened next.