Big Tech vs. Solo Founder: What Actually Transfers

Big Tech vs. Solo Founder: What Actually Transfers

I spent five years at Microsoft and another two at Amazon before going independent. Now I work with solo founders and small entrepreneurs. People ask me constantly what transfers from Big Tech to a one-person business, and the honest answer is: less than you'd think, but the things that do transfer are huge.

Let me try to make it concrete.

What doesn't transfer (and shouldn't)

The process overhead. A Senior PM at Microsoft has access to 12 partner teams, three legal reviewers, a privacy review board, a UX research budget, and a brand team. None of that exists when a founder is shipping their first SaaS. If you try to recreate even 10% of that machinery, you'll spend your first six months building process instead of product.

The "perfect launch" instinct. Big Tech launches are PR events. They're tied to keynotes, press cycles, partner announcements. Founder launches are not. A founder launch is just Tuesday. You ship something, it doesn't quite work, you fix it Wednesday. That iteration speed is the founder's main advantage. Every "let's get the launch story polished" instinct from Big Tech actively works against it.

The metric obsession. At Amazon I lived inside a metrics dashboard. Every decision had a quantifiable expected impact. That's the right model when you have 330 million users to A/B test on. It is the wrong model when you have 47 paying customers and you can call any of them on the phone. Talk to them. The dashboard can wait.

What does transfer (and matters more than people realise)

Customer obsession as a discipline. The single most useful thing I learned at Amazon was the literal habit of starting every doc with the customer problem, not the product idea. Founders skip this constantly. They start from "I'm building X" instead of "Y kind of person is suffering from Z, and here's what they currently do about it." The discipline forces clarity.

Writing things down. Microsoft and Amazon are written cultures — six-pagers, design docs, narratives. The reflex of writing a one-page spec before a build, even if the team is one person, is one of the best founder tools I know. It surfaces all the assumptions you didn't know you were making.

Dis­agree and commit. Founder teams (and their advisors) often confuse alignment with consensus. Not every decision needs everyone to agree. Most decisions need someone to make a call, the room to register their disagreement honestly, and then everyone to commit and move. Big Tech does this reasonably well. Founders should steal it.

The thing nobody warned me about

Going from a 50-person org to a 1-person business does something weird to your decision-making. At Microsoft, every decision was filtered through six other smart people before it became real. As a solo operator, you make a decision and it's just done. There's no friction.

That sounds great. It's a trap.

The first three months I freelanced, I made a lot of fast decisions that I would have caught if I'd had a peer review. The fix isn't to add bureaucracy. The fix is to manufacture a tiny amount of useful friction — a one-day pause on big decisions, a trusted second pair of eyes on important work, a habit of writing the decision down so future-you can see what past-you was thinking.

The discipline you absorb in a structured environment is real value. The trick is figuring out which 20% of it to keep, and which 80% to leave behind.