One Person, Right Tools

There’s this assumption that serious software requires a team. Product manager, designer, three backend developers, two frontend, a DevOps person, QA. Sprints. Standups. Retrospectives. Jira boards.

I built an iOS app with physics-modeled audio synthesis, localized it to 16 languages, deployed it across 14 markets, and run an automated outreach pipeline. All by myself. Not because I’m special. Because the tools changed.

What “solo” actually means

It doesn’t mean I do everything manually. It means I build systems that do the work.

Translation: I don’t sit there translating strings into Korean. I built agents that take English content, understand the context (not just the words), and produce culturally adapted translations in 15 languages simultaneously. The Korean version references K-wellness trends. The French version avoids words that trigger regulatory scrutiny. The Italian version leads with physics because Italian consumers are skeptical of wellness claims.

Research: I don’t read papers one by one. I built a pipeline that ingests academic textbooks, chunks them into searchable paragraphs, and lets me query across 30+ books in seconds. “What does Fletcher & Rossing say about modal frequencies in metal plates?” Answered in 2 seconds with page references.

Deployment: I don’t manually upload builds. Push to git, everything builds and deploys. The iOS app, the website, the admin dashboard, the API. Different platforms, same workflow.

The economics

A traditional setup for what I built would look like: 2 iOS developers (HKD 80K each), 1 backend developer (HKD 70K), 1 designer (HKD 50K), 1 project manager (HKD 60K). That’s HKD 340,000 per month. Four million per year. Before office space, equipment, insurance.

I spend about HKD 200 per month on infrastructure. Cloudflare (free tier covers most of it), a couple of API subscriptions, R2 storage. The expensive part is my time. But my time is one salary, not five.

This isn’t a flex. It’s an observation about where we are. The tools exist. The question is whether you’re using them or paying five people to do what one person with the right setup can do faster.

What this means for you

You probably don’t need to go full solo. But you probably have a team of 8 doing work that 3 people with better tools could handle.

The pattern is always the same: identify the repetitive parts, automate them, let humans do the parts that require judgment and creativity. That’s it. That’s the whole methodology.

The iOS app plays audio based on Bessel functions and damped harmonic oscillators. That’s the creative, judgment-heavy part. A human (me) had to understand the physics and make it sound right. Everything around it (translation, deployment, outreach, monitoring, admin) is automated. Not because it’s less important. Because it’s predictable.

The uncomfortable truth

Most companies aren’t slow because the work is hard. They’re slow because the workflow is hard. Approvals, handoffs, context switches, meetings about meetings. Remove the workflow friction and suddenly a small team moves faster than a large one.

I’ve seen 50-person companies ship slower than a solo developer with good infrastructure. Not because the 50 people are bad at their jobs. Because the coordination cost is real and nobody accounts for it.

If you’re building something: start small, automate early, grow the team only when you’ve run out of automation options. You’ll be surprised how far you get.