Manual

A guide to working with me. Read this before we start.

What I Bring

Design to full-stack. I started as a designer, moved to front-end, then full-stack. I think in design systems, not just code. This means products that look right and work right from day one.

15+ years building products. From leading front-end development for a national e-government service at 19, to startups and enterprises across three continents. I've shipped at every scale and seen what actually works.

AI-augmented execution. I use AI tools to move faster without sacrificing quality. What takes agencies months, I ship in weeks. You get senior expertise at startup speed.

Working Style

Async-first. I prefer written communication over calls. A well-written message beats a meeting. I'm in different time zones constantly, so async keeps things moving without scheduling gymnastics.

Direct. I'll tell you what I think, not what you want to hear. If something won't work, I'll say so early. Sugar-coating wastes everyone's time.

Fast iterations. I'd rather ship something imperfect and improve it than spend weeks planning the perfect solution. Real feedback beats hypothetical optimization.

Documentation over memory. I write things down obsessively. Decisions, context, rationale—all of it. This means I can pick up projects after gaps and you get a clear audit trail.

Communication

Best ways to reach me: Email for new inquiries. Telegram or Slack for active projects. I check messages in batches, not continuously.

Response time: Usually within 24 hours on weekdays. Faster for urgent project issues.

Meetings: I keep them short and rare. If we need a call, I'll come with an agenda and leave with action items. Most things can be resolved in writing.

Updates: I proactively share progress. You shouldn't have to ask "what's the status?" If you're asking, I've already failed.

Values

Sovereignty

Own your platform, your data, your decisions. Don't build on rented land.

Simplicity

Remove until it breaks. The best solution is usually the one with fewer parts.

Boring Technology

Proven beats cutting-edge. I'll choose PostgreSQL over the new database every time.

Time Freedom

The point of work is to buy back your time. Every system should serve this goal.

What Clients Can Expect

Fixed scope, clear deliverables. I don't do open-ended retainers or hourly billing. We agree on what success looks like upfront, and I deliver that.

Honest assessment. If I'm not the right fit for your project, I'll tell you and point you to someone who is. I'd rather lose a deal than take on work I can't nail.

Transfer of knowledge. I build things you can maintain without me. No lock-in, no mysterious black boxes, no "you need me forever" dynamics.

Opinionated recommendations. You're not paying for someone to nod along. I'll push back when I disagree and explain why.

How I Make Decisions

First principles. I start from "what are we actually trying to achieve?" not "what does everyone else do?" Sometimes the conventional approach is right. Often it isn't.

Reversibility. For reversible decisions, I move fast and adjust. For irreversible ones, I slow down and think hard. Most decisions are more reversible than they feel.

Asymmetric bets. I look for high upside, low downside situations and repeat them. Small experiments that could pay off big, even if most fail.

Known Limitations

I won't babysit process. If you need someone to attend daily standups and manage a team's tickets, that's not me. I work best with autonomy and accountability.

Limited capacity. I take on fewer projects to deliver better results. This means I'm selective about what I commit to—but when I commit, I deliver.

I'm blunt. Some people find this refreshing. Others find it abrasive. If you need someone diplomatic and careful with words, we might clash.

Kuan
Kuan

Shipped infrastructure to 10M+ users. Built systems behind $B+ exits. Remote since 2014, 30+ countries.

Still interested?

See the different ways we can work together, or schedule a discovery call.

Free Resource

Technical Decision Framework

Evaluate tech decisions without writing code.

5 questions that reveal everything
Red flags checklist + vendor matrix

No spam · Instant download

You're all set!

Your Technical Decision Framework is ready.

Open Technical Decision Framework