Turner Broadcasting System: A Media Giant’s Legacy

Get Your Unit Economics Right (Before You Scale)

Here’s the unsexy truth: you can’t scale a broken business model. I learned this the hard way with a SaaS venture that looked great on a spreadsheet. We had customers, revenue was coming in, and our growth metrics looked promising. Then I actually did the math on what it cost us to acquire each customer versus what they paid us.

The numbers were brutal. We were spending $1,200 to acquire customers who’d generate $800 in lifetime value. We could’ve grown that business to $10 million in ARR and still been hemorrhaging money on every single sale. That’s not a business. That’s a charity with delusions of grandeur.

Unit economics means understanding three things obsessively:

• Customer acquisition cost (CAC): Every dollar you spend to get a customer, divided by the number of customers you actually get. Be honest here. Include your time, ad spend, sales tools, everything.
• Customer lifetime value (LTV): How much a customer will realistically pay you over their entire relationship with your company. Not the theoretical maximum—the actual number based on churn and average contract value.
• The ratio: Most investors want to see an LTV:CAC ratio of at least 3:1. If you’re at 1:1, you’re in trouble. If you’re at 5:1, you can actually afford to scale.

The best part? You don’t need fancy software or a data science team to figure this out. A spreadsheet and brutal honesty will get you there. Track it monthly. Watch it obsessively. If it’s not working, fix it before you add more customers—not after.

This connects directly to your cash runway planning and whether you’re actually building something sustainable or just creating a faster way to burn through capital.

Build Your First Team Like You’re Bootstrapped

One of the biggest mistakes I see founders make is treating their first hire like they just closed a Series A. You haven’t. You’re scrappy. Act like it.

Your first hire should be someone who’s comfortable with ambiguity, can wear five hats simultaneously, and genuinely believes in what you’re building. Not because they’re getting rich quick—they’re not—but because they understand they’re helping to prove a concept that might change things.

Here’s what I look for in early team members:

• Bias toward action: They see a problem and start solving it without waiting for a meeting about having a meeting. They don’t need a spec doc or a detailed brief. They figure it out.
• Comfort with failure: Early-stage work is 70% failed experiments and 30% breakthroughs. If someone needs constant validation or perfect information before moving, they’ll slow you down.
• Genuine belief in the mission: I don’t care if they’re an expert. I care if they actually think this is worth their time. That matters when you’re asking them to work for less money and more uncertainty than they could get elsewhere.

Compensation should be honest. If you’re bootstrapped or pre-seed, don’t pretend you can pay market rate. Be transparent about equity, timeline, and what success looks like. The founders I respect most are the ones who say, “We can pay you $60K base plus 0.5% equity, and if we hit these milestones, we revisit it in 12 months.” That’s a conversation. That’s real.

Avoid the trap of hiring your friends or people you think will “figure it out.” I’ve seen that burn friendships and slow down progress. Hire people smarter than you in specific areas. Your job as a founder isn’t to be the best at everything—it’s to build something that works.

Customer Acquisition Isn’t Marketing Yet

This is where a lot of founders spend money they don’t have. They think customer acquisition means running Facebook ads or hiring a growth hacker. Sometimes it does. But not at the beginning.

In your first year, customer acquisition looks like talking to people. Lots of them. You’re figuring out who actually needs what you’re building, and you’re doing it manually. This is uncomfortable. Good.

Here’s the process I follow:

1. Identify who you think needs this: Get specific. Not “small businesses.” Which small businesses? What industry? What’s their annual revenue? What problem are they trying to solve right now?
2. Find them: LinkedIn, industry forums, local meetups, Twitter, wherever they actually hang out. You’re not running campaigns yet. You’re doing research.
3. Talk to them directly: Email, call, DM, whatever gets a conversation. Offer no sales pitch. Just ask questions. Learn. Take notes.
4. Identify patterns: After 20-30 conversations, you’ll start seeing repeating problems, objections, and desires. That’s your real market feedback.
5. Build for what you learned: Now you adjust your product, messaging, or positioning based on actual human feedback, not assumptions.

This is why knowing when to pivot versus push harder matters so much. You’re learning early, cheaply, before you’ve spent money scaling something that doesn’t work.

Once you have repeatable channels that work—meaning you can reliably get customers at a cost that makes sense—then you can think about scaling those channels. But that’s phase two. Phase one is proving the concept works at all.

External resources like SBA’s launch guide have good frameworks for early customer research, and Forbes has solid articles on customer acquisition strategy that go deeper into this.

The Cash Runway Reality Check

Cash is oxygen. You can have the best idea, the best team, and the best product, but if you run out of money, none of it matters. This is why understanding your burn rate and runway is non-negotiable.

Here’s what you need to know:

Burn rate: How much money you’re spending per month. Fixed costs (rent, salaries, tools) plus variable costs (customer acquisition, hosting, whatever scales with growth). Be aggressive in your estimates. If you think you’ll spend $10K, budget for $12K.

Runway: How many months you can operate before you’re out of cash. If you have $100K and burn $10K/month, you have 10 months. That’s your deadline to either find revenue, raise more money, or shut down. Plan accordingly.

Here’s the hard part: most founders are too optimistic about revenue timelines. They think they’ll be cash-flow positive by month six. Then month six hits, and they’re still spending money on customer acquisition without enough revenue to cover it. Then they panic.

Build a realistic model. Include:

• How many customers you need to break even (and be honest about how long it takes to get them)
• What your fixed costs are (the stuff you pay whether you have revenue or not)
• A buffer for surprises (there will be surprises)
• Multiple scenarios: best case, realistic case, worst case

If you’re raising money, investors want to see this. If you’re bootstrapping, you need this for yourself. Either way, know your numbers. Update them monthly. Watch them like a hawk.

A lot of founders I’ve worked with use Y Combinator’s resources on runway and burn rate to model this out properly. It’s worth the time.

When to Pivot vs. When to Push Harder

This is the question that keeps founders up at night, and there’s no perfect answer. But there are signals.

Most founders either pivot too early (they get scared after two weeks of slow traction) or they push too hard on something broken (they ignore the data and just work harder). The truth is somewhere in the middle.

Signals to pivot:

• You’ve talked to 30+ potential customers and they all say “interesting, but…” followed by a reason they won’t buy.
• You’ve been live for 3+ months with minimal revenue and no clear path to getting it.
• Your unit economics are terrible and you can’t see a way to fix them without completely changing your model.
• You’ve learned that the problem you’re solving isn’t actually a problem people will pay for.

Signals to push harder:

• You’re getting consistent interest from customers but your execution is sloppy. Fix the execution.
• You’ve found a repeatable way to get customers, but you’re not spending enough on acquisition to see if it scales.
• You’re early (under 3 months) and you’re still learning. Give yourself time.
• Your metrics are improving month-over-month, even if they’re not where you want them yet.

The hardest pivots I’ve seen are the ones where the founder finally admitted the original idea wasn’t working, but they’d learned enough to see a different opportunity. That’s not failure. That’s learning with intention. It’s why talking to customers early matters so much—you get the feedback before you’ve sunk a year and your entire emotional identity into one direction.

This is also where having a strong team around you helps. They’ll give you honest feedback when you’re too close to see clearly.

FAQ

How much should I pay my first hire?

Depends on your situation. If you’re bootstrapped and pre-revenue, be honest about what you can afford and what equity you’re offering. If you’ve raised money, you can pay closer to market rate but probably not quite there yet. Either way, the conversation should be transparent and realistic. Most early employees understand they’re trading some salary for upside.

What if I have a great idea but no co-founder?

That’s harder, but not impossible. You’ll move slower because you’re doing everything, but you can still get to product-market fit. Focus on outsourcing or finding a technical co-founder early if you’re not technical yourself. The thing that’ll kill you faster than being solo is being solo AND not executing on the core idea. Pick the one thing that matters most and get it done.

Should I raise money or bootstrap?

Depends on your market and your timeline. If you’re in a space where speed matters and capital requirements are high, raising makes sense. If you’re building something that can generate revenue quickly, bootstrap and keep control longer. There’s no universal right answer. Just be clear on the tradeoffs.

How do I know if my unit economics are actually good?

The rule of thumb is LTV:CAC of 3:1 or better. But that varies by industry. SaaS companies often aim for 3:1 or 4:1. B2B can sustain lower ratios if contracts are long. The important thing is tracking it obsessively and knowing whether you’re improving or getting worse.

What’s the most common mistake founders make in year one?

Spending too much time building features nobody asked for, and not enough time talking to customers. You’ll learn more from 20 customer conversations than from three months of coding in isolation. Talk to people. Let that inform what you build.