Built by analysts who actually use the tools
Back in 2018, a small group of financial analysts got tired of switching between seventeen different platforms just to complete one market report. So we started building something better.
How We Got Here
Starting from a shared office space in Bangkok to serving clients across Southeast Asia
The Spreadsheet Years
Three financial consultants met at a conference and spent two hours complaining about their analysis workflow. Instead of just venting, they decided to sketch out what a better system might look like. Those napkin drawings became our first prototype.
First Real Users
After months of testing with friends in the industry, we launched a beta version that actually worked. Twenty-three analysts signed up in the first week. Their feedback was brutally honest and incredibly useful.
Growing Beyond Ourselves
We hired our first employees who weren't founders. Turned out other people had even better ideas about what the software should do. The platform evolved faster in six months than it had in the previous two years.
Where We Are Now
Today we support over 400 financial professionals across Thailand and neighboring markets. The software has grown, but we're still that same group who believes analysis tools should help you think, not get in your way.
Who's Behind This
Meet one of the people who makes sure our software actually solves real problems
Chanarong Wattanapong
Spent twelve years working at financial institutions before joining us in 2021. He's the person who translates "wouldn't it be cool if..." into actual working features.
When analysts tell us about workflow problems they're facing, Chanarong usually already has three possible solutions sketched out. His background in both finance and software development means he understands what analysts need before they finish explaining it.
Outside work, he collects vintage calculation tools and has an impressive collection of slide rules that probably cost more than they should have.
What Matters To Us
These aren't aspirational values we printed on posters. They're the principles we actually use when making decisions.
Analyst First
Every feature starts with a real analyst's workflow problem. If it doesn't help someone do better analysis, we don't build it. Simple as that.
Data Privacy Seriously
Financial data is sensitive. We built our systems with security from day one, not as an afterthought. Your analysis stays yours.
Honest Feedback
When users tell us something doesn't work, we listen. Some of our best features came from blunt emails that started with "This is frustrating because..."
Continuous Improvement
Markets change. Analysis methods evolve. Our software needs to keep up. We ship updates based on what analysts actually need, not what looks impressive in demos.
How We Build Software
Our development process is pretty straightforward. Talk to analysts, build what helps them, test it with real workflows, then improve based on feedback.
Starting With Real Problems
We spend a lot of time in offices watching analysts work. Not in a creepy way — people volunteer to let us observe their workflow. You'd be surprised how much you learn just by watching someone struggle with a task that should be simple.
These observations turn into features that might not sound exciting but save hours every week. Things like automatic data formatting or intelligent chart suggestions that actually make sense.
Testing With Actual Work
Beta testing here means giving analysts pre-release features and asking them to use it for their regular work. Not test scenarios — real client reports and market analysis.
This catches problems that never show up in controlled testing. Like that time we discovered our chart export feature completely broke when dealing with Thai Baht symbols. Fixed before launch, thanks to real-world testing.
- Weekly feedback sessions with active users
- Direct communication channels between users and developers
- Bug fixes prioritized by impact on daily workflow
- Feature requests tracked and regularly reviewed
Supporting Long-Term Success
Software launches aren't finish lines. The interesting work happens after people start using it daily. We maintain regular contact with clients, not to sell them more stuff, but to understand how their needs evolve.
Sometimes this means adding features. Sometimes it means removing complexity. Often it means explaining existing capabilities better because we failed to communicate them clearly the first time.
Regional Market Understanding
Operating in Thailand means understanding local market dynamics, regulatory requirements, and business practices. We're not just translating software — we're building tools that work within the regional financial ecosystem.
This includes things like proper handling of regional data formats, compliance with local regulations, and integration with systems that Thai financial professionals actually use. Details that matter when you're doing real work.
