Seventeen years as a migration agent. An OMARA investigation. Eight years building the tool no one else built. Every agent we've spoken to since recognises this story as their own.
If this is you
You're a registered migration agent. Your compliance could be tighter. Your records might not survive real scrutiny. You haven't found a tool built for how this work actually runs. Keep reading.
Jan Bejcek registered as a migration agent in 2009. The work was meaningful: helping people navigate the system, reunite families, open pathways. But the infrastructure was a mess.
Spreadsheets for cases. Email folders for documents. Handwritten notes for records. Separate tools for invoicing, intake, and compliance. Nothing was designed for an agent.
Every available tool was built for another industry and jammed into a migration context. Generic CRMs. Document platforms with no audit logic. Compliance that meant "keep a folder and hope."
The gap was obvious. The question was who would fill it.
Ten clients is manageable. Fifty isn't. As the practice grew, the improvised systems started to fail. Not all at once. Quietly. A missing file note. A deadline in an email no one found. A staff member who left and took the knowledge with them.
Then came the CRICOS college. Jan founded it, ran it, and later sold it. Now there were two regulatory regimes running at once. OMARA and ESOS. Two audit frameworks. The same broken tools for both.
This wasn't a product roadmap. It was operational necessity. Every feature was built because the practice needed it. Tested on real clients, real compliance obligations, real stakes.
No one expects the letter. Even agents who keep records, advise carefully, and take their Code of Conduct seriously. An OMARA investigation is a different kind of experience.
It requires evidence across every matter under review. Correspondence, file notes, advice records, documents, billing history, timeline of actions. Everything. Produced on demand.
The investigation closed without adverse findings. But it changed everything about what Educli was being built to do. Not a practice management platform. An evidence engine. A system that produces proof by default.
The PROOF Engine was redesigned from scratch. Not to pass an audit. To make the audit irrelevant.
"Every RMA we've spoken to since says the same thing. They didn't know their records weren't good enough until they had to prove it. That gap is exactly what Educli was built to close."
After years of running the practice on Educli, the evidence was in. Cases processed cleanly. Staff onboarded without chaos. Compliance records that held up. A practice that ran whether Jan was there or not.
Other agents kept asking the same question. What system do you use? How are you not drowning?
The miracle wasn't one moment. It was the realisation that every other RMA was still solving the same problems Jan had solved years earlier. Educli wasn't just Jan's OS. It was the one the whole profession needed.
The breakthrough wasn't technical. It was a naming decision. What had been built wasn't just tools. It was a standard for how to run a migration practice. Regulatory-Ready by design. Unified across operations. Navigable by anyone on the team.
That standard is RUN™. The platform exists to make it achievable for every registered migration agent in Australia.
Not written by a marketing team. Made undeniable by seventeen years in practice, an OMARA investigation, and thousands of client files.
Not because you worked harder. Because the system does what used to live in your head. Files clean before anyone asks. Team knows what to do. You take a week off and nothing falls apart.
That's what Built to RUN™ looks like. That's what we're building toward for every registered migration agent in Australia.
Start with the Practice Maturity Index. Ten minutes. Instant results. No email required.