Solo UnicornFrom Side Project to Full-Time — My Decision Framework for Leaving Big Tech
From Side Project to Full-Time — My Decision Framework for Leaving Big Tech
On March 14, 2025, I submitted my resignation letter. Senior Member of Technical Staff, Generative AI division, total compensation with salary and equity coming in at close to $300K.
In the 48 hours before resigning, I felt no excitement whatsoever — just a strange calm. Because I had spent 18 months validating this decision with data. It wasn't an emotional choice; it was a rational judgment backed by quantitative analysis.
Many people ask me "how did you muster the courage to quit," as if this were a question about bravery. It wasn't. It was a question about information and probability. This article breaks down my decision framework — no motivational fluff, just a replicable methodology.
Background: What Happened During the Side Project Phase
In late 2023, I started building ArkTop AI (an AI tool for luxury retail) in my spare time. The motivation was straightforward: my MBA at NYU Stern gave me exposure to the retail industry, my CS PhD background let me build products myself, and I wanted to see how far one person could go.
Here's the timeline:
- Dec 2023 – Jun 2024 (Exploration phase): Invested 10–15 hours per week, working my day job while coding at night. Built MVPs in three different directions — two failed, one gained traction.
- Jul 2024 – Dec 2024 (Validation phase): ArkTop AI acquired its first 10 paying customers. Simultaneously launched JewelFlow (a jewelry industry SaaS) after an ArkTop customer asked if I could build a jewelry recommendation tool. Monthly revenue went from $0 to $2,800.
- Jan 2025 – Mar 2025 (Decision phase): Combined monthly revenue from both products reached $4,200. I started seriously evaluating the feasibility of going full-time.
Note the timeline: from first line of code to resignation, a full 15 months. This wasn't "had a great idea and quit my job" — it was "proved viability with data, then quit."
The Three-Dimensional Decision Framework
Dimension 1: Financial Runway — How Much Time Do You Have to Make Mistakes?
This is the most fundamental dimension, and the one most people overlook. The biggest risk of quitting to start a company isn't "the project doesn't work out" — it's "running out of money and being forced to find a job." The difference between being forced back and choosing to go back: the former leaves you with no negotiating leverage.
My calculation:
Monthly survival cost: In New York, my minimum monthly expenses were $4,800 (rent $2,400 + food $600 + insurance $450 + everything else $1,350). Note this was a trimmed-down figure — after resigning, I moved from Manhattan to Brooklyn, cut unnecessary subscriptions, and reduced dining out by 60%.
Runway calculation: Before resigning, I had 18 months of survival savings ($86,400). Combined with product revenue of $4,200/month, the actual runway was longer. But I used conservative assumptions — assuming post-resignation income drops to zero (in case something goes wrong with the products), pure savings would last 18 months.
Stop-loss line: I set a clear rule for myself — if monthly revenue doesn't reach $6,000 (enough to cover 125% of survival costs) within 12 months of resigning, I go back to a regular job. No vague "let me push through a bit longer." The stop-loss line was written on paper, and when the date came, I'd execute.
What actually happened: I resigned in March 2025, and by September my monthly revenue reached $8,700. The stop-loss line was never triggered. But having that "bumper" reduced my resignation anxiety by at least 70% — because I knew exactly what the worst-case scenario looked like, and it was one I could accept.
Dimension 2: Capability Validation — What Did You Prove During the Side Project Phase?
Many people quit to start companies because "I have a great idea." Ideas are cheap. What matters is whether you validated three core capabilities during your side project phase:
1. Can you build something people will pay for?
ArkTop AI and JewelFlow had 26 paying customers before I resigned, generating $4,200/month. This isn't "someone said your product is nice" — it's "someone swipes their credit card every month to pay for it." The gap between these two is wider than most people imagine.
2. Can you handle the entire chain from product to delivery on your own?
My CS PhD let me write code; NYU Stern training enabled market analysis and pricing. But the biggest takeaway from the side project phase was discovering I could also handle customer support, marketing content, legal, and accounting — not perfectly, but well enough. A solo company doesn't need you to score 90 on everything. A passing grade of 60 is enough to keep things running.
3. Can you sustain output without team support?
Big tech has product managers defining requirements, colleagues for brainstorming, and infra teams handling deployment. When you're on your own, every decision is yours to make, every problem yours to solve. Fifteen months of side project work was a 15-month stress test — I proved I could sustain output without organizational support.
All three questions had data-backed answers. That was the prerequisite for resigning. If the answer to any one of them had been "uncertain," I would have stayed at my job and kept building on the side.
Dimension 3: Opportunity Cost — What Do You Lose by Staying?
Most people only calculate the cost of quitting (foregone salary). They don't calculate the cost of staying.
Time cost: I worked 9 hours per day at my big tech job (including commute), leaving only 12–15 hours per week on evenings and weekends for the side project. After resigning, that became 50–60 hours per week. The productivity gain isn't a simple multiple — the focus of full-time work is vastly superior to fragmented side-project time. One feature for ArkTop AI took two months as a side project; after going full-time, a feature of similar complexity took a week and a half.
Market window: The jewelry industry SaaS market where JewelFlow operates had limited competition in early 2025. But I spotted at least three seed-funded teams pursuing similar directions. If I continued at side-project pace, the market window might close before I was ready.
Personal well-being: Juggling a full-time job and two products was degrading my health — sleeping 5–6 hours a day, no weekends off, golf completely abandoned. This pace wasn't sustainable. I either had to go all-in on the products or drop them and return to a normal rhythm. Trying to have it both ways was the worst option.
Risk Assessment Checklist
Before resigning, I created a risk checklist and assessed each item:
| Risk | Probability | Impact | Mitigation |
|---|---|---|---|
| Product revenue stagnates or declines | Medium | High | Stop-loss: find a job if monthly income < $6K within 12 months |
| Health insurance costs spike | Low | Medium | New York State Marketplace plan, $450/month already budgeted |
| Psychological isolation | High | Medium | Solo Unicorn Club + monthly scheduled socializing |
| Technical skills atrophy | Low | Low | Building my own products is the best technical practice |
| Doors back to big tech close | Low | Medium | CS PhD + senior-level experience, re-entry isn't hard |
| Visa/immigration issues | N/A | N/A | Resolved (green card) |
The point of this checklist isn't to eliminate risk — you can't. The point is to transform "vague fear" into "specific problems," then prepare a response plan for each one. Fear comes from the unknown. Once you quantify every risk, it becomes much less frightening.
Actual Results: One Year After Resigning
March 2026 — exactly one year since I resigned. Here are some numbers for comparison:
| Metric | Before Resigning (Mar 2025) | Now (Mar 2026) |
|---|---|---|
| Monthly Revenue (Products) | $4,200 | $18,500 |
| Monthly Expenses (Tools + Living) | $4,800 | $5,200 (tools increased) |
| Paying Customers | 26 | 143 |
| Number of Products | 2 | 2 + Solo Unicorn Club |
| Weekly Working Hours | 55h (job + side projects) | 45h |
| Sleep | 5–6h/day | 7–7.5h/day |
| Golf | Completely stopped | Every two weeks |
The revenue numbers aren't the point — what matters is the quality-of-life change. Working 10 fewer hours, sleeping 1.5 more hours, golf is back. Not because full-time entrepreneurship is easier, but because I no longer have to context-switch between two identities.
Lessons Learned the Hard Way
Mistake 1: Productivity actually dropped in the first two months after resigning
I expected efficiency to skyrocket immediately after going full-time. In reality, the first two months were disorienting — without external structure (showing up at the office at 9 AM), my time management fell apart. Sleeping until I woke naturally, then puttering around, and by the end of the day feeling like I'd accomplished nothing.
Solution: I imposed strict time blocks — 8:30 AM to noon for product development, noon to 1 PM for exercise, 1 PM to 5 PM for customer work and operations, nothing after 5 PM. The same fixed rhythm as a day job, just with different content. Productivity was back within two weeks.
Mistake 2: Underestimating the impact of social deprivation
No matter how intense big tech gets, you still have someone to chat with at lunch. Going full-time as a solo company, I sometimes went entire days speaking fewer than 10 sentences (conversations with AI don't count). By month three, the isolation was palpable.
Solution: The Solo Unicorn Club went from "a community I run" to "my own social network." Weekly coffee chats with 2–3 members, monthly in-person meetups. This time investment doesn't generate direct revenue, but the return on mental health is immense.
Mistake 3: Saying yes to customers too easily
After resigning, there's a subtle psychological shift: without a steady paycheck as a safety net, every customer request triggers an instinct to say "sure, might as well — it's revenue." The result: in the first three months, I took on too many custom requests, and my product roadmap got pulled off course.
Lesson: A solo company's scarcest resources are your time and attention. Saying no to requests that don't align with your product direction matters more than closing one more deal.
For Those Thinking About Going Full-Time
Step 1: Get to "$1,000/month" during the side project phase first.
Not $100. Not "someone said they'd buy it." Consistent, repeatable $1,000/month in revenue. The number itself isn't what matters — what matters is what it represents: proof that people are willing to continuously pay for your product. Until you hit this milestone, don't seriously consider quitting.
Step 2: Calculate your "true runway."
Monthly expenses x the longest period of zero income you can tolerate = savings you need. I recommend at least 12 months of runway. Don't model the "everything goes well" scenario — model the "income drops to zero" scenario.
Step 3: Talk to people who've actually done it.
Not reading articles (including this one) — finding people who actually quit their jobs to run a solo company. Everyone's situation is different, but the pitfalls overlap heavily. The Solo Unicorn Club has over 30 full-time solo founders whose experience is more valuable than any framework.
Final Thoughts
Resigning isn't a decision about courage; it's a decision about information sufficiency.
When your financial runway is long enough, your capabilities have been validated through side projects, and you've clearly calculated the opportunity costs — quitting transforms from a "gamble" into a "data-backed strategic adjustment."
I don't encourage anyone to quit impulsively, nor do I encourage anyone to stay in the "safe zone" doing side projects forever. Between these two extremes lies a sweet spot, and finding it isn't about gut feeling — it's about data.
Where are you in your side project journey? If you haven't started yet, don't worry about whether to quit — first, get your first paying customer.