Building Financial Clarity Through Better Organization
Started in 2019, webdevflux emerged from a simple observation: people weren't struggling with budgeting because they didn't care. They struggled because their financial tools made categorization tedious and confusing.
We're not here to revolutionize anything. Just make it easier to see where money goes and why that matters.
Why We Focus on Categories
Most budget apps treat categories like an afterthought. Pick from a dropdown, move on. But how you categorize spending shapes how you understand your financial habits.
Someone spending 800,000₫ at the supermarket might be buying groceries. Or household supplies. Or throwing a party. Each tells a different story about their budget priorities.
We built our platform around flexible categorization because financial life doesn't fit into neat boxes. Your rent might include utilities. Your transport costs might blur with food delivery. And that's fine—our system adapts to how you actually spend, not how some algorithm thinks you should.
After six years working with Vietnamese households and small businesses, we've learned that good categorization isn't about complexity. It's about giving people enough structure to spot patterns without making them accountants.
What Guides Our Decisions
We're not particularly philosophical about business, but these principles keep us focused
Practical Over Perfect
A categorization system that works for 90% of transactions beats one that demands precision for every single expense. We design for real usage patterns, not ideal scenarios.
Local Context Matters
Vietnamese spending habits differ from Western models. Street food, motorbike costs, extended family support—our categories reflect actual financial lives here, not imported frameworks.
Transparency in Limitations
We can't predict your financial future or guarantee savings. What we can do is help you see spending patterns clearly enough to make your own informed decisions.
Privacy as Default
Your financial data stays yours. We don't sell transaction information, build advertising profiles, or share category insights with third parties. That's non-negotiable.
Sustainable Growth
We grow by being useful, not by chasing viral features or venture capital milestones. Our business model depends on customers finding long-term value, which keeps us focused on actual improvements.
Support That Helps
When something breaks or confuses users, we fix it or explain it. No automated responses that don't address the actual question. Real people answering real concerns.
The People Behind the Platform
Our team of twelve works from a small office in Gò Vấp. Mix of developers, support specialists, and financial operations people who've spent years refining how categorization actually functions.
No rockstars or ninjas here. Just folks who care about solving a specific problem well.
Founded by Llewellyn Kavinsky after he spent three years managing accounts for small businesses across District 7 and noticed the same categorization headaches everywhere. Turned out building a better system required understanding both Vietnamese business practices and how people mentally organize spending.
Most of our team came from finance or accounting backgrounds before moving into product development. That perspective matters—we're not tech people trying to understand finance, we're finance people who learned to build software.
Team members across development and support
Years operating in Vietnamese market
Year we started fixing categorization problems
Support availability Monday through Friday
Llewellyn Kavinsky
Founder & Financial Systems ArchitectFormer accountant who got tired of watching clients struggle with inadequate categorization tools. Built webdevflux to fix that specific frustration.
How We Actually Build This
Our development process prioritizes reliability and user feedback over feature velocity
User Testing Before Launch
Every new categorization feature goes through at least four weeks of testing with actual users before we roll it out. Not friends or family—real customers managing real budgets.
This catches problems that internal testing misses. Like when we added subcategory nesting and discovered people wanted three levels, not two. Or when our "smart suggestions" kept miscategorizing bánh mì purchases as groceries instead of dining out.
Slower releases, fewer support tickets. That trade-off works for us.
Data-Informed Adjustments
We track how people use categories—not what they buy, but which organizational structures actually get adopted versus abandoned after a few weeks.
Turns out most users settle into 8-12 active categories regardless of how many options we provide. They want broad buckets with occasional subcategory detail, not elaborate taxonomies.
That insight shaped our entire interface design. Now we suggest starter categories based on common patterns but make customization straightforward for those who need it.
Continuous Refinement Cycle
We don't do annual overhauls or major version releases. Changes happen incrementally based on support conversations, usage analytics, and direct customer feedback.
Small improvements every few weeks beat dramatic redesigns that force everyone to relearn the system. People have enough to think about without their budget tool completely changing interface every year.
This approach requires discipline—resisting flashy features that look good in demos but don't solve real problems. But it keeps us focused on practical utility rather than novelty.
Want to See How It Works?
We're happy to walk through our categorization system and answer questions about whether it fits your financial management needs. No pressure, no sales pitch—just honest conversation about what we've built.
Get in Touch