Back in 2018, our founder spent three months manually reconciling cash flow statements for a mid-sized retailer. Spreadsheets everywhere. Version control nightmares. And the sinking feeling that there had to be a better way.
That frustration sparked something. What if financial analysis tools actually worked the way accountants and analysts think?
We started baltheriqos in a shared office space in Bathurst with exactly that question.
Started with a simple cash flow forecasting tool. Our first version crashed if you imported more than 500 transactions. Not great when most businesses have thousands.
But we learned something important: people didn't want fancy features. They wanted reliability and speed. So we rebuilt everything from scratch.
The pandemic hit, and suddenly everyone needed better financial visibility. We added scenario planning features because clients kept asking "what if revenue drops by 30%?"
By mid-2021, we were processing over two million transactions monthly. Our servers handled it, barely. That's when we knew we needed to scale properly.
These days we focus on three things: making complex analysis simple, keeping data secure, and not adding features nobody asked for.
Our team has grown to twelve people. Still small enough that everyone knows what everyone else is working on. We like it that way.
Small team, big on solving actual problems. Everyone here has spent time working with financial data in some capacity, which means we understand the headaches firsthand.
Spent eight years building financial reporting systems for regional councils before joining us in 2020. She's the reason our interface doesn't look like a tax form.
Former backend engineer at a fintech startup in Sydney. Moved to Bathurst in 2019 and joined us a year later. He's obsessed with database query optimisation, which sounds boring but saves our clients hours.
Worked in corporate finance for six years before switching to software support. She answers probably 90% of our client questions and has an uncanny ability to explain complicated processes in plain English.
We don't have corporate values printed on posters. But we do have a few principles that come up in almost every product meeting or client conversation.
Financial analysis is already complicated enough. Our job is to make it clearer, not add more layers. That means saying no to features that sound impressive but don't actually help people make better decisions.
When someone asks if we can add a feature, our first question is always "will this make the existing tools harder to use?"
If something's not working, we tell you. If we can't solve a particular problem with our current tools, we'll say that too.
We've turned down clients before because our software wasn't the right fit. That probably sounds odd, but it saves everyone time and frustration in the long run.
