I didn't set out to build an app. But looking back, the path was probably inevitable.
I've always been drawn to knowledge that travels. A study abroad experience in my twenties made one thing clear: I deeply admired those who could bridge cultures through fluent, effortless language — it's a rare and powerful gift. But I also realized that my own path was different. I wasn't a linguistic natural.
I understood that for me to truly contribute in a global room, I needed to bring something that could cross borders as effectively as a second or third language. I needed a universal language of my own.
Accounting became that language. Not because I fell in love with the theory, but because I recognized it as a system of logic that the entire world runs on — one that, if you understood it deeply enough, allowed you to walk into any room, in any country, and have something real to offer.
That's why, when I joined a Big 4 firm, I sought out the international division. And it's why I found myself auditing Japanese companies with dual reporting obligations — Japanese GAAP and US SEC standards in parallel. International accounting wasn't an area of interest. It was the bridge I had chosen to build my world on.

Audit work demands precision, judgment, and an enormous amount of invisible effort. But one of its quieter realities is that the value you create is often structural — it supports trust in financial markets, protects stakeholders, upholds standards. The impact is real, but it is diffuse. It reaches people at a distance.
During one of Japan's first waves of internal control audits, I found myself buried in a repetitive, manual process — copy, paste, print, repeat across dozens of subsidiaries. My wife, an engineer, watched me one evening and said, matter-of-factly: "That's not work for a human."
So I learned VBA. Built a macro. Eliminated the repetition entirely.
The reaction was immediate — and unlike anything I had experienced before. Colleagues thanked me directly. The client felt the difference. The work I had done was visible, tangible, and useful in a way that landed right in front of me.
That feeling — of solving a real problem and watching someone's day get measurably better because of it — quietly redirected everything that followed. It was the moment I understood that I wanted to build things. Not instead of accounting, but with it.

I spent over a decade in financial consolidation — as a consultant, project manager, and eventually Product Manager building one of Japan's fastest-growing consolidation platforms.
Here's something most people outside Japan don't realize: in Japanese consolidation practice, subsidiaries worldwide report their financial data using IFRS as the common language. The deeper you go into Japanese consolidation, the deeper you go into IFRS — across jurisdictions, industries, and edge cases that textbooks don't cover.
And this is accelerating. More Japanese listed companies are now adopting IFRS at the consolidated level — making this knowledge not just useful, but increasingly essential.
I wasn't pulled into IFRS by accident. I moved toward it deliberately, for twenty years.

But here's what those years really taught me — and it wasn't accounting.
As a Product Manager, my job was to stand between two worlds: finance professionals who lived inside the complexity of IFRS, and engineers who had never opened an accounting standard in their lives. Every feature we built required me to take something genuinely difficult — an interpretation question, a recognition threshold, a disclosure requirement — and reconstruct it into something an engineer could implement precisely and a user could actually trust.
That process, repeated thousands of times over a decade, built something I didn't have a name for at the time: the ability to find the structure inside complexity. To know not just what IFRS says, but why it says it — and how to make that legible to someone encountering it for the first time.
That's the skill underneath everything I build now.

All those years talking to CFOs, controllers, finance teams — and engineers — I noticed the same pattern.
The questions were never really about the software.
They were about accounting. The system seems useful — but what's the correct accounting treatment here? What does IFRS actually require us to do?
Customers weren't asking for better features. They were asking for knowledge. The confidence to know they were doing it right.
That gap — between having a tool and understanding the standard — was the one nobody was filling.
I couldn't stop thinking about that.

IFRS-OneQ is my answer — a learning experience designed for anyone who wants to genuinely understand IFRS. Whether you are building a career through certification, deepening your practical knowledge as a finance professional, or approaching IFRS from a completely different field — the goal is the same: real understanding, not surface familiarity.
I built it alone. With AI as my co-developer, and two decades of IFRS practice as the content foundation. Every question is CPA-reviewed. The learning experience is designed to connect directly with what you read in IFRS Deep Dive.
It exists because the people who need IFRS knowledge the most are often too senior for textbooks and too busy for courses. They need something they can use in the margins of a working day.
That's what I tried to build.
🌐 Web App: http://ifrs-oneq.ifrs-labo.com/
📱 Android: https://play.google.com/store/apps/details?id=com.ifrslabo.ifrsoneq
📰Introduction: https://ifrs-labo.com/posts/ifrs-oneq