How I got here
I trained as a doctor, and what I loved most was the research: the evidence, the method, the discipline of ruling things out before committing to a finding, and of saying plainly when something isn't certain. Medicine also taught me that process exists for a reason and you follow it.
That love of evidence is what rerouted me into data. I studied data science, then moved from analysis into building the platforms underneath it: pipelines, data models, reporting. Along the way I kept meeting financial data and wanted to be sure I was handling it correctly, so I trained in accounting as well. I wanted the numbers I produce to hold up with the people who sign them off. Learning is the constant; everything I do is built on it.
What this means for you
Every claim on this site is backed by experience and training. I have trained deeply in the Microsoft data platform and hold its certifications, I have delivered for clients across industries, and I run projects end to end: discovery, integration, modelling, reporting, governance and handover, with one person accountable throughout. Medicine gave me precision and the habit of working to a standard. Accounting means your reporting reconciles to your books, line by line. Years of delivery across industries mean I've seen most of the ways reporting goes wrong, and fixed them.
What I bring
Deep Microsoft training. Certified across Fabric and Power BI and continuously trained on the platform as it changes: lakehouse, pipelines, semantic models, Purview, DevOps. I learn each new capability before a client needs it.
Client work, not theory. Years of hands-on delivery across hospitality, local government, healthcare, SaaS and professional services. I've worked inside clients' tenants, with their data quality and their politics, not in demos.
End-to-end ownership. I run the whole project: discovery, scope, integration, modelling, reporting, governance, training and handover. One person accountable from the first conversation to the last sign-off.
Method, not improvisation. Our procedures and steps are guided by the established bodies of knowledge for this work: Kimball for dimensional modelling, the DAMA DMBOK for data management and governance, and BABOK for requirements and business analysis. In practice that means conformed dimensions in every model, a data dictionary and stewardship model on governance work, and structured requirements before any build.
Clean, documented, traceable. Every engagement ships with detailed technical documentation, version-controlled code and lineage from the report back to the source record. Trust in a number comes from being able to show where it came from, and that is designed in, not added at the end.
What I care about
Systems that work seamlessly. The best reporting is the kind nobody has to think about: it refreshes, it agrees with the ledger, and the meeting starts with the decision rather than the number. That's what I build towards, and why I'm exacting about the details that make it hold.
Learning, since forever. Medicine, data science, accounting, and now whatever Microsoft ships next. I'm a member of the DAMA Australia chapter, part of the international data management association, and I test new platform features on my own time before they go near a client. The field notes on this site are the result.
Problem solving under pressure. Building a second career while raising a family taught me resilience and how to keep delivering when the plan changes. Clients notice that when requirements move, the work moves with them.
Explaining things clearly. I'm an active Toastmasters member and serve as Vice President of Public Relations for my club. I love public speaking, and it shows in how I hand over: your team gets an explanation they can repeat, not a deck they have to decode.
The problem I solve
With one system, reporting is reading off a screen. With six that don't talk to each other, it becomes an argument. Each system was set up at a different time for a different job and defines things slightly differently, so the same word means a different number depending on which one you open. I fix the cause rather than the symptom: each measure is defined once, across every system, so revenue, costs and reporting finally line up.
How I work
I'm the founder, and I scope and lead every engagement and stay hands-on through to handover. Larger builds bring in additional engineers under my direction; your point of contact and the person accountable never change. Based in Canberra, onsite in the ACT, and remote for clients across Australia, New Zealand and the United States.
The fair question is what happens if I'm not around. So I build things you don't depend on me for: every change is tracked and reversible, the design is written down rather than kept in my head, and your team is trained to run it. Your reporting doesn't live on my laptop.
