December 18, 2025·6 min read

Solo Studio: Organization, Tools, Reality

How a one-person development studio actually works. Tools, methods, and real challenges of a developer managing multiple projects at once.

TL;DR

My solo setup: Obsidian for tracking (bye Linear), Git + automated CI/CD, AI for pair programming, and a strict rule of 2 projects max in parallel. The hardest part is the discipline of prioritization.

Jungle Labs has been around since mid-2023. Two and a half years solo, no co-founder, no employees. What surprised me the most: the code is the easy part. The real difficulty is everything else -- prioritization, admin, marketing, support.

The Tech Stack of a Solo Studio

Development Environment

My current setup runs on a Mac Studio with an Innocn external display at 1920x821. Why these details? Because when you're on your own, every bit of friction matters. A screen that's too small means hours lost juggling between windows.

Editors:

Xcode for Inner Gallery (Swift/SwiftUI)
VS Code for everything else (Flutter, NestJS, Next.js)
Terminal native macOS with Zsh

No over-optimization. I tried Neovim for months, but in the end VS Code with the right extensions saves me more time than it costs.

Docker everywhere: Every project has its docker-compose.yml. Databases, Redis, external services -- everything runs locally with a simple docker-compose up. It avoids the "works on my machine" problem and lets me switch between projects without pollution.

My best investment: automating the dev setup. New project = 5 minutes to have a complete environment.

Knowledge Management

Obsidian is my external brain. Two separate vaults:

Jungle Obsidian: technical documentation, ADRs (Architecture Decision Records), code notes
Cortex Obsidian: business strategy, marketing, market analysis

This separation isn't trivial. When I'm coding, I don't want to be distracted by business considerations. And conversely, when I'm thinking strategy, technical details are noise.

Git as a timeline: All my projects are versioned with descriptive commits. Not for teamwork, but for me in 6 months. Commit messages become my progression documentation.

Monitoring and Observability

As a solo studio, I need to monitor multiple projects simultaneously:

Uptime monitoring with UptimeRobot for my apps in production
Error tracking with Sentry for Inner Gallery and Coachy
Analytics with Plausible (lighter than Google Analytics)

What matters: alerts that don't spam you. It's better to miss a minor bug than to ignore all notifications out of fatigue.

Multi-Project Organization

The Context Method

I have three types of days:

Technical focus: I work on a single project, usually the one that requires the most architectural thinking. Phone on airplane mode, notifications off. These days are rare but precious.

Maintenance: I go through the ongoing projects. Fix a bug on Inner Gallery, test a feature on Coachy, update dependencies. Less rewarding but necessary.

Business: Prospecting, accounting, strategy, tech watch. Not a single line of code gets written. These days remind me that being a solo developer also means being an entrepreneur.

Ruthless Prioritization

With multiple projects, the art is saying no. My rule: if a project doesn't progress for a month, I either stop it or figure out why and fix it.

Inner Gallery is currently my #1 priority. Native iOS app, local encryption with CryptoKit. App Store launch planned soon.

Coachy is in active development. The architecture with Event Sourcing + CQRS is taking shape, the AI Coach is showing promising results. Launch planned during 2026.

Freelance work funds it all. Mostly NestJS and Next.js, a stack I know well.

The Tools That Make a Difference

Communication

Telegram for client emergencies. WhatsApp for prospects. Email for everything else. This segmentation prevents context mixing.

Loom for client demos. Rather than explaining a feature in 10 paragraphs, 2 minutes of video is worth more.

Finances

Freebe for invoicing (French solution, GDPR-friendly). Qonto for the business account. Notion for cash flow tracking and forecasts.

The golden rule: automate as much as possible. I spend 2 hours per month on admin, no more.

Deployment

GitHub Actions for CI/CD. Railway for hosting NestJS APIs. Vercel for Next.js frontends. TestFlight for distributing Inner Gallery.

Every push to main triggers deployment. Zero downtime, easy rollback. This infrastructure costs me about 50 euros/month but saves me hours.

In a solo studio, your time is worth more than infrastructure. Always prioritize automation.

The Reality of Working Solo

The Advantages

Velocity: No meetings to validate a technical decision. If I think a refactor will improve maintainability, I do it.

Consistency: All my projects follow the same code conventions, the same architecture, the same tools. Switching between them is seamless.

Learning: I touch everything. Backend, frontend, mobile, DevOps, design, marketing. This versatility is a huge competitive advantage.

The Challenges

Technical solitude: No colleague to challenge your decisions. You can spend hours on a problem that a 5-minute discussion with a peer would have solved.

Bottleneck: If I get sick or go on vacation, everything stops. This personal dependency is a real business risk.

Cognitive overload: Juggling between Swift for Inner Gallery, Flutter for Coachy, and NestJS for client work requires constant mental effort.

Impostor syndrome: When you're alone, it's hard to validate that your technical choices are sound. You sometimes develop overengineered solutions from lack of feedback.

Mistakes to Avoid

The Magic Tool

I lost months looking for the perfect setup. Notion vs Obsidian, VS Code vs Neovim, PostgreSQL vs MongoDB. In the end, productivity comes from mastering your tools.

Over-Splitting

Creating 15 micro-services for an app with 100 users. Architecture should serve the product.

Total Isolation

Refusing all external collaboration. Even as a solo studio, you need feedback, mentorship, and a network. Communities like IndieHackers or local meetups are invaluable.

Tips for Getting Started

Start with One Project

Don't launch 5 projects at the same time. Master managing a single product from A to Z first. You'll add complexity later.

Automate from Day One

Deployment scripts, automated tests, monitoring. These investments seem costly at first but pay off by the second project.

Document Everything

Not for others, for yourself in 6 months. How do you start the project? Where are the credentials? How do you debug the classic problem X?

Keep a Safety Net

3-6 months of cash reserves minimum. Being solo means accepting financial uncertainty, but not irresponsibility.

Possible Evolution

A solo studio isn't necessarily an end goal. It might be a stepping stone toward:

A 2-3 person studio: keeping agility while adding complementary skills
Fully automated products: focusing on SaaS that runs without intervention
Premium consultancy: selling high-level expertise rather than time

For my part, the current goal is to achieve financial independence through my products. After that, we'll see.