Part-Time vs Full-Time
| Part-time (alongside a job) | Full-time | |
|---|---|---|
| Financial risk | Low — salary covers living | High — burning savings or runway |
| Speed | Slow — nights and weekends | Fast — same-day iteration |
| Ability to raise | Hard — investors want full commitment | Expected precondition |
| Credibility | Weaker with enterprise buyers and early hires | Stronger |
| Burnout risk | High — two demanding jobs at once | Focused, but all-in pressure |
| Downside if it fails | Minimal — no income lost, no resume gap | Savings depleted, employment gap |
| Best used for | Validation, MVP, first paying users | Once traction is real and your time is the bottleneck |
The Pattern That Works
Section titled “The Pattern That Works”Stay part-time through validation. Go full-time only once there’s a clear signal — meaningful recurring revenue, or funding lined up.
Two failure modes to avoid:
- Going full-time on an unvalidated idea — the riskiest move available.
- Staying part-time after real traction arrives — execution speed becomes the binding constraint, and competitors move faster.
Strategies for Surviving the Split
Section titled “Strategies for Surviving the Split”- Fixed blocks, not leftover time. 90 min–2 hr protected windows beat “whenever I’m free” — reactive time gets eaten by fatigue.
- Batch by work type. Deep work on a dedicated weekend day; weekday evenings for async/admin only.
- Scope ruthlessly narrow. One core workflow, not a platform. Less surface area = less maintenance alongside a day job.
- Async customer development. Recorded walkthroughs, email surveys, community engagement — fits around a 9-to-5.
- Outsource selectively. Time is scarcer than money at this stage.
- Define your go/no-go trigger upfront. A specific number (MRR, or % of salary replaced) — not “I’ll know when.”
- Build in real recovery. Burnout, not lack of traction, is the most-cited reason side projects die. One full day off per week is a floor, not a luxury.
Next: Documents by Stage