Technical Leadership · SaaS
From Sole Developer to a Product Team
Grew a SaaS guidebook platform from a single developer to a product engineering team while re-architecting the guest experience.
Professional case studyProblem
I joined as the only developer on a tightly coupled, server-rendered Django monolith (templates plus jQuery) with a large backlog of customer-requested features. One developer could not maintain the platform and build its next version at the same time.
Action
Stabilized the inherited codebase and cleared the backlog, then made the case for a team — defining profiles, interviewing, and closing full-stack and frontend hires in about two weeks each. I led three engineers through design, task breakdown, code review, and releases, and separated the guest-facing guidebook into an independent Vue.js app behind a Django REST Framework API, alongside Celery scheduling, a Redis-to-RabbitMQ move, and a reworked Stripe flow.
Outcome
Increased engineering throughput by at least 2x and supported approximately 2x product revenue growth over one year, delivering a fully separated, redesigned Vue.js guidebook with frequent, low-risk releases.
How it was measured: Throughput measured as sustained delivery output before and after growing from one developer to a team of three; revenue growth reported by the business over the same year.
Engineering takeaways
Reusable patterns from the work.
These notes focus on the judgment, tradeoffs, and working patterns behind the result.
- Built the team and the process, not just the code, to scale delivery.
- Used architecture decomposition to unlock independent frontend work and a full redesign.
- Balanced product bets, preserving a low-demand prototype while refocusing investment.
Stack