We Build Software Together
Started in 2022 with a simple idea — what if developers actually worked side by side instead of throwing code over walls? Turns out, it makes everything better.
How We Actually Work
Most development shops operate like assembly lines. Someone writes specs, passes them to developers, who pass to testers, who find problems, and the whole cycle repeats. It's slow and frustrating for everyone involved.
We ditched that model early on. Our teams sit together, work on the same problems, and catch issues before they become disasters. Last month we rebuilt a client's payment system in three weeks because both developers could debug in real time. Traditional approach? Probably two months minimum.
The Vietnam tech scene has grown fast, but many teams still follow outdated workflows. We're proving there's a better way — one that respects both code quality and human sanity.
What Keeps Us Going
Real Collaboration
Not scheduled meetings or status updates. We mean actual shoulder-to-shoulder problem solving where both people understand the full picture.
Code That Lives
Anyone can write code that works today. We write code that someone else can maintain two years from now without wanting to quit their job.
Honest Timelines
We'd rather tell you it takes six weeks than promise four and deliver eight. Surprises are great for birthdays, terrible for project deadlines.
Context Matters
Vietnamese businesses have unique needs — payment systems, local regulations, mobile-first users. We've been here long enough to understand the nuances.
This Plays Out Daily
Take our work with an e-commerce platform last fall. They needed inventory tracking across three warehouses in Hanoi, Da Nang, and Ho Chi Minh City. Different internet reliability, different staff tech literacy, different regional suppliers.
Instead of building one system and forcing it everywhere, we paired up our developers to visit each location. They spent time with warehouse staff, understood the actual workflows, then built something that worked for how people actually operate.
The Hanoi warehouse manager told us it cut their stock discrepancies by 80% in the first month. That's not because our code was magical — it's because we built what they needed instead of what we assumed they needed.
Finding Your Path Forward
Different projects need different approaches. Here's how we typically guide conversations based on what you're actually trying to accomplish.
Starting From Scratch?
New projects let us set proper foundations from day one. We spend extra time in the first two weeks getting architecture right, which saves months later when you need to scale or add features.
- We map out your core workflows before writing any code
- Choose tech stacks based on your team's capabilities, not just what's trendy
- Build in monitoring and debugging tools from the start
- Set up development environments that match production reality
Most new projects start properly in September 2025 or January 2026. That timing lets us dedicate senior developers without pulling them mid-project from existing clients.
Fixing Existing Systems?
Legacy code rescue is trickier but often more rewarding. We've inherited systems where the original developers disappeared, documentation never existed, and nobody quite knows why certain things work the way they do.
- First month focuses on understanding what's actually there
- We document as we go, building knowledge your team can use
- Prioritize fixes that reduce immediate pain points
- Gradually modernize pieces without breaking what works
One client came to us in March 2025 with a booking system held together by prayer and duct tape. Six months later, they're processing 10x the transactions without the 3am emergency calls.
Growing Your Team?
Sometimes you don't need us to build everything — you need us to work alongside your existing developers and help them level up their practices.
- We pair with your developers on real features, not toy examples
- Share techniques through actual work, not classroom lectures
- Help establish code review processes that actually improve quality
- Set up testing frameworks your team will actually use
This works best as 3-6 month engagements. Long enough to see real change, short enough that we don't become a crutch. Your team should be stronger when we leave, not dependent on us sticking around.
Who We Are
Small team, mixed backgrounds, shared frustrations with how software usually gets built. We've worked at agencies, startups, and enterprises — saw what worked and what didn't.
Thục Đoàn
Senior Developer
Spent five years building banking infrastructure before joining us. Still has nightmares about legacy COBOL systems. Believes most bugs come from unclear requirements, not bad code.
Liên Vương
Technical Lead
Started as a solo freelancer, learned the hard way that you can't scale by working longer hours. Now passionate about building systems that don't require heroic efforts to maintain.
What You Can Expect From Us
Clear Communication
We explain technical decisions in plain language. If you don't understand why we're recommending something, we haven't done our job explaining it properly.
Realistic Planning
Software estimates are notoriously bad. We build in buffer time and keep you updated when reality diverges from the plan — which it always does.
Long-Term Thinking
We optimize for code that's easy to change later, not just code that works right now. Your business will evolve, and your software should be able to keep up.
Local Context
We understand Vietnamese business realities — payment preferences, mobile usage patterns, infrastructure challenges, regulatory requirements that foreign teams often miss.
Let's Talk About Your Project
We take on a limited number of projects each quarter to maintain quality. Current availability starts August 2025 for new engagements.