Working for Yourself

I’m losing some faith in the corporate path, and being my own boss sounds good in the way things sound good before you’ve priced them out. I’ve done contract work before (BigHammerGarage was one), but never as the plan. These are my notes on five videos about making it the plan.

They run in a rough order. Freelancing sells your time, so it starts fast and caps out. A product sells without you, so it starts slow and doesn’t. The first video is a freelancer’s one-week launch; the next three are about building something that sells on its own; the last is the MBA arithmetic that decides whether either one pays. It’s a synthesis of other people’s claims, and I’ve marked where I trust them less.

#IdeaFrom
1Sell a solved problem, priced from a floorA freelancer of 16 years
2Test the idea before you build itA founder, with caveats
3Make quality the strategyHow Linear took on Jira
4Find the toll on something freeA free stock-footage site
5Know your break-evenAn MBA in 25 minutes

1 · Sell a solved problem

Jamie, a freelancer for sixteen years with clients from Google and Netflix down to boring B2B companies that “pay better than those big guys,” starts with the mistake most new freelancers make: naming a skill. “I do graphic design” sounds replaceable. Business is money exchanged for solved problems, so the offer should be one sentence you could say at a bar: I solve this problem for these people to get this result. “I write launch emails for new SaaS products to help drive early traction.”

Pick the lane by asking which of your skills makes someone money, saves them time or removes risk, where you’ve already done that (a day job counts), and which people you naturally understand. Industries over-represented in your own network grow fastest. Then give your process a name, like a “brand clarity sprint,” because a named process sounds owned.

Jamie’s pricing rule is the part I’d never heard. Don’t price from the market or from what you need to survive. Price from what it would cost you to subcontract the job, plus your margin, so the work could run without you. The worked example: $80K a year across 40 projects with a 25% buffer means no project under $2,500. When a client pushes on budget, negotiate the scope, never the fee.

Live · your floor price per project
$80,000 ÷ 40 projects, plus a 25% buffer: no projects under $2,500.
The first three fields are Jamie's worked example, which lands on $2,500. The actual rule is the fourth field: price what it would cost to hire someone at your level to do the job, plus your margin. When you fill it in, the floor is whichever of the two is higher. That combination is mine.

The rest of the week is short enough to keep as a table:

DayBuildThe move that matters
1A laneProblem first; check Upwork for who’s paying and the words they use
2An offerThe one-sentence offer, a floor price, a named process
3A processOnboarding, pre-production sign-off, a midpoint check-in, a delivery email that pitches the next project
4A portfolioTwo or three spec projects, labeled as spec, each with a one-paragraph case study
5Your networkTen handwritten messages: what you do, for whom, “feel free to forward this”
6Job boardsSearch by problem; a three-sentence pitch ending in a call or a Loom
7A launch postWhat you offer, who it’s for, what to do next

Two lines from that week stuck. Iterate “on the cheap side of the project,” while it’s still a sketch, because changes get expensive once it’s built. And the trophy is the repeat client, which is why delivery ends with a pitch for the next job.

2 · Test it before you build it

Freelancing caps at the hours you have. The million-dollar video, from a founder who says they sold their last company for $110 million, argues for a “high-leverage” business instead: recurring revenue, margins around 70%, growth through software instead of headcount, and a product you own. I’m taking that video with some salt. It quotes statistics I couldn’t trace, so I’ve kept only the ideas that stand without its numbers. Its “no agencies, no consulting” rule also clashes with section 1, and I read it as where to end up.

What holds up is the insistence on selling before building: recruit a “customer advisory board” of ten real prospects who sign a letter of interest before you write code, then build a “black car product” that solves one problem only, after Henry Ford’s any-color-so-long-as-it’s-black. The sales order is what, how, who: what change they want, how you’ll deliver it, and why you’re the one to trust. Prospects liked the founder’s product and didn’t buy until the pitch added slides about the team.

The cheapest test is a fake door. A chef with a cooking blog adds a “buy my book” page that just collects emails, and checks the clicks two weeks later. The video’s math turns those clicks into $12,000 a month. All of it rests on one borrowed guess about how many clickers would actually buy.

Live · the fake-door test, and how much rides on one guess
6,000 clicks a month × 10% × $20 = $12,000 a month.
The defaults are the video's chef example: 30,000 visits and 3,000 clicks every two weeks, and a 10% purchase rate borrowed from Amazon book pages. The slider is my addition. Everything downstream scales with that one borrowed number, so test it before you trust it.

3 · Make quality the strategy

The Linear video is the one I found most convincing. In 2019 three Finnish founders went after issue tracking, a market Atlassian’s Jira owned so thoroughly that collaborating with another team usually meant using Jira. Their wedge was speed and focus, against a tool developers mostly try to avoid.

They scoped the first version by user instead of by feature: small startups like their own, with enterprise leads turned away. They let in about ten new users a week, took no funding until investors came to them, and the video says they were profitable within two years. Early on they spent six months on a sync engine that makes every change feel instant. The lesson the narrator draws is to invest early in infrastructure a competitor can’t copy without rewriting everything, not to build a sync engine “for your horse Tinder project.”

The process is the part I’d steal. No A/B tests; taste and real users decide. Prototypes ship in three to five days behind a feature flag, first to the team, then to beta users, then to everyone. Bugs beat features, with an internal one-day fix target. And no customization that helps a middle manager’s reports at the expense of the person who lives in the tool. The video is honest about survivorship bias: the founders came from Uber, Airbnb and Coinbase, and their first waitlist followed them from there.

4 · Find the toll on something free

The shortest video is the most specific. Getty Images charges $400, its lowest license, for a three-second clip of General Patton that comes from a public domain film on archive.org. The narrator built a free site that pulls the public domain FedFlix collection from archive.org, cuts each film into individual shots automatically, and makes them searchable by what’s in the picture. It holds over 40,000 shots, each linked to its source, with no sign-up, paywall or ads.

It isn’t a business; it runs at a loss on donations. But the shape of the opportunity is worth keeping. When an incumbent charges for convenience on top of something free, the convenience is the whole product, and cheap tools can rebuild it.

5 · Know your break-even

The MBA video tries to fit a year of business school into 25 minutes, and nearly every sentence is a definition worth keeping. It deserves a page of its own someday. For working alone, these are the ideas that matter most.

Cash is not profit. Accrual accounting books revenue when it’s earned, so a January sale paid in July makes you profitable in January and broke until summer, and a profitable company can still run out of cash. Working capital (current assets minus current liabilities) is whether you can pay the bills.

Price has four common bases: cost plus markup, the value you create, what competitors charge, and how hard buyers flinch when the price rises. The video’s rule underneath all four is that if price is less than cost, you are a charity. Everything else falls out of contribution margin, the price minus the cost of each unit, which pays down your fixed costs:

Live · break-even, and why the gap between price and cost decides it
Each unit contributes $7.00 toward fixed costs. Break-even: 300 units a month.
Break-even units = fixed costs ÷ contribution margin, where contribution margin = price − variable cost. The numbers are illustrative. Drag the variable cost toward the price and watch the break-even run away, which is the video's warning made literal.

The finance half adds the time value of money: a dollar today is worth more than a dollar later, so future cash gets discounted, and a project is worth doing when its discounted returns beat what it costs (positive net present value). Payback period is the fast-food version, quick and filling and blind to anything after the money comes back.

The plan

Read in order, the five videos describe a path more than a choice:

  1. Write the one-sentence offer and set a floor price before the first call.
  2. Freelance in that lane, with a real process, and watch for the problem clients keep paying to have solved.
  3. Before building a product for it, put up a fake door and line up people who’ll sign something.
  4. Build the black car: one problem, for one kind of user, at a quality the incumbents can’t be bothered with.
  5. Know the break-even, and keep enough cash to survive the gap between earning money and receiving it.

Source

Five videos, watched in October 2026. Everything above is my synthesis of their arguments, and the figures (Atlassian’s and Linear’s valuations, the $110 million sale, the $400 license, the freelancer’s client list) are the speakers’ claims. I’ve treated the million-dollar video with the most caution, because its statistics come without sources. Two narrators aren’t named in the transcripts, and the founder’s name and the footage site’s address are garbled by the captions, so I haven’t guessed them.