It Doesn't Have to Be Like That | Real Minds AI

A founder told me that technology was “not her thing.”

She’d built a services organisation from the ground up. Incredible team, meaningful work, real impact on people’s lives. Carer Solutions does something genuinely rare — it’s the only service in Australia that supports people living with disability, or their nominees, to directly employ support workers they already know and trust. Payroll, compliance, the whole employer load — they carry it so participants don’t have to.

But the back office had grown around her, not with her. Multiple platforms, years of accumulated files, a compliance load that kept expanding.

She didn’t need someone to tell her it was complex. She knew.

What we actually found

I’ve spent 35 years walking into organisations and mapping how the work actually flows. The pattern is almost always the same: the problem isn’t inside any one system. It’s in the spaces between them — where data doesn’t move, where a human carries context by hand, where the workaround became the process so long ago that nobody remembers it’s a workaround.

At Carer Solutions, here’s what the discovery phase turned up:

  • More than 400,000 files scattered across SharePoint and OneDrive, with no structure holding them together
  • Folders nested 19 levels deep, navigated purely by muscle memory
  • An expensive project management tool everyone hated but couldn’t escape, because two years of compliance knowledge was buried in its tickets
  • 35-plus disconnected systems, none of them documented
  • An “everyone sees everything” permission model — in an organisation handling participant data
  • An NDIS audit on the horizon, with no clear picture of the compliance exposure

Their Head of People & Culture, Corey Tonkin, put it better than any consultant’s report could: “When Dennis and Tracy showed us we had hundreds of thousands of files in SharePoint, I realised it was like those reality TV shows about hoarders — piles of stuff everywhere with no clear system.”

None of this happened because anyone did anything wrong. It happened the way it always happens: a good team kept delivering for clients while the systems quietly grew around them. Every workaround made sense at the time. The 32 people in that business were exceptional. The plumbing was not.

The path she didn’t take

The conventional answer to a mess like this is a clean-up project. Six to twelve months of sorting 400,000 files, a recommendations deck, probably another piece of software on top of the 35 systems already in the stack. Most of the advice she could have bought would have started exactly there — and her team would have carried that project on top of their actual jobs the whole way through.

That’s the version of “transformation” most organisations have learned to dread, and fair enough. It’s months of construction debris in the middle of your operations, and at the end you’ve often paid for a map of the problem rather than a fix.

What she needed was someone who’d actually sort it out without pulling her team away from the work they were there to do.

What we built

So we made the opposite call. Rather than spending a year cleaning up 400,000 files, we built a completely new digital environment and migrated only what mattered.

Over 90 days, that became:

  • A SharePoint intranet built around how they actually work — ten interconnected sites matching the real shape of the business, not the org chart from three restructures ago
  • A knowledge management system — one source of truth for policies, processes and procedures, with version control and a review cadence built in from day one
  • A compliance centre — seven compliance registers with full audit trails preserved from the legacy systems, audit-ready from the moment it went live
  • The hated project tool, gone — we extracted two years of compliance knowledge from its tickets, turned that history into structured FAQs and procedures, and eliminated the annual licence cost entirely
  • A security overhaul — from “everyone sees everything” to proper role-based access with 20 security groups, so participant data is seen by the people who should see it and nobody else
  • A licence audit — 35 Salesforce licences analysed, with significant ongoing annual savings identified

The rhythm matters as much as the list. Weeks one to three were discovery — mapping all 35-plus systems and analysing the 400,000 files to work out what actually mattered. Weeks four to eight were architecture and build. Weeks nine to eleven were migration and training, six teams’ worth. Week twelve was go-live.

And here’s the part I care about most: her team didn’t live through a renovation. They walked into a finished system on day one — populated with their data, configured to their structure, staff trained and live. No construction debris. No six-month internal implementation grinding away next to the day jobs.

90 days, against a traditional estimate of six to twelve months. The investment recovered 64–121% of its cost in year one, and it had started paying for itself before the first year was out.

Her executive advisor, Peter Lochert, called it “a textbook example of getting it right.” But the bit that stuck with me was the go-live meeting. Watching the team realise they could actually find what they needed, without the workarounds they’d been carrying for years.

What the team does now

This is the question I wish more people asked about transformation projects — not “what did you build?” but “what does Tuesday look like now?”

Tuesday now looks like this: a staff member needs a policy, and they find the current version, first try, in the knowledge management system — not the third-newest copy in a folder nested 19 levels deep. A compliance question comes in, and the answer is in a register with an audit trail behind it, not in someone’s memory of a ticket from 2024. The NDIS audit stopped being a looming unknown, because the evidence is organised and the registers are current. And nobody is paying for a project management tool the whole team was quietly working around.

None of that is glamorous. That’s rather the point. The glamorous version of AI is a demo on a stage. The useful version is a 32-person disability services provider whose people stopped spending their days hunting through folders and started spending them on the participants they exist to serve.

Why it matters

That’s the thing about operational complexity. People adapt. They build muscle memory around broken things. The 19-level folder structure didn’t feel absurd to the people inside it — it felt like Tuesday. The workaround you’ve been doing for four years doesn’t feel like friction. It feels like the job.

And then when you take the friction away, there’s this moment of “oh… it doesn’t have to be like that.”

I’ve watched that moment land in every engagement we’ve run, and it never gets old. It’s not really about the technology — the founder who told me technology was “not her thing” was right, and she didn’t have to make it her thing. She needed the plumbing fixed and her team switched on, in that order. AI is what let us do the diagnostic and the build in 90 days instead of a year — it’s the accelerant, not the product.

If your back office has grown around you rather than with you, the mess is not a character flaw and it is not permanent. It’s plumbing. Plumbing can be fixed — faster than you think, and without pulling your team off the work that matters.

How to tell if you’re there too

You don’t need a consultant to diagnose this. Three questions will do it.

The new-starter test. When someone joins your team, how long before they can find things without asking? If the honest answer is “months”, your filing system lives in people’s heads, not in your systems. That knowledge walks out the door every time someone resigns.

The muscle-memory test. Pick a routine task — finding the current version of a policy, pulling evidence for an audit question, working out which spreadsheet is the real one. Now ask: could you write down the steps? If the steps only exist as “Sharon knows”, you’re navigating by muscle memory, exactly like a 19-level folder tree.

The audit test. If a regulator asked you tomorrow to show your compliance evidence, would that be a request or a crisis? The gap between those two is the gap Carer Solutions closed in 90 days.

If you failed two of the three, you’re who we built this for. The entry point is deliberately small: a free discovery conversation, or a $400 AI Starter Session if you want a structured look at where you stand before committing to anything. A bite-sized chunk, not a transformation pitch.


Carer Solutions, founded by Jane Morell in 2011, provides the only service in Australia that supports people living with disability (or their nominees) to directly employ people that they already know and trust as disability Support Workers. As payroll and compliance experts, they partner with the Participant (or their Nominee) to ensure they have all the tools and support they need to fulfil their responsibilities as an employer.

Read the full Carer Solutions case study — the 90-day timeline, what we delivered, and the numbers behind the 64–121% first-year ROI.


Got questions about this?

How We Work Proof Talk to us
How We Work Proof Talk to us
Ask us anything