The €125k Lesson I Almost Learned Too Late: Why Unit Economics Should Be Your First Calculation, Not Your Last

The Dinner That Changed Everything

Two nights ago, I'm sitting at this fancy gala dinner at Idea Lab (got invited as their development partner, which still feels surreal). Across from me is the CEO and founder of Jokr, a company that raised over $260 million.

Between courses, I'm pitching him on fastpal, explaining our pricing model, how we're building an MVP to test with a small pilot group. I'm getting excited, talking about our AI sales supervisor, the real-time coaching, all the features we're building.

Then he stops me cold.

"Before you build anything, before you write a single line of code, you need to look at your unit economics. Will it even work? Selling and marketing is the easy part. But if your unit economics don't work, you don't have a business."

I nodded along, but inside I'm thinking: Shit. We're already months into development.

The Truth About Where We Are

Here's the honest truth: Moritz and I have been so focused on building the perfect product that we forgot to ask the fundamental question every business needs to answer: For every customer we acquire, will we make more money than we spend?

Sure, I've done some napkin math. We're targeting a 3:1 LTV to CAC ratio, which sounds good on paper. But when I really dig into our current situation, the cracks show:

• We're spending weeks talking to potential partners who aren't converting
• Our sales cycle is dragging on forever (B2B reality check: it's nothing like the instant dopamine hit of B2C sales)
• We're burning through our own funds with no clear timeline to profitability
• We got one pre-sale, which proves interest exists, but interest doesn't pay the bills

The worst part? I studied Business Administration with a focus on Finance at Frankfurt School. I know how to build financial models. I just... didn't. We got caught up in the builder's trap: if we just add this one more feature, then people will definitely buy.

What Unit Economics Actually Means (And Why You Should Care)

After that dinner, I went deep into research mode. Here's what every founder needs to understand:

Unit economics is the P&L statement of a single customer. It answers one question: Can you generate more value from a customer over their lifetime than what you spend to acquire them?

For SaaS businesses like fastpal, this breaks down into two critical metrics:

1. Customer Lifetime Value (LTV)

This is the total profit (not revenue!) a customer generates over their entire relationship with you. The formula that actually matters:

LTV = (ARPA × Gross Margin %) / Revenue Churn Rate

Where:

• ARPA = Average Revenue Per Account
• Gross Margin % = What's left after you subtract all costs to serve that customer
• Revenue Churn Rate = The percentage of revenue you lose each month

2. Customer Acquisition Cost (CAC)

The FULL cost to acquire a customer. And I mean everything:

• Ad spend
• Sales team salaries and commissions
• Marketing tools and software
• Even a portion of your office rent for the sales team

CAC = Total Sales & Marketing Expenses / Number of New Customers

The Magic Ratio

If your LTV:CAC ratio is:

• < 1:1 - You're literally paying people to use your product
• 1:1 to 3:1 - You're treading water
• > 3:1 - You have a real business
• > 5:1 - You're probably under-investing in growth

But here's the kicker: even a great LTV:CAC ratio means nothing if your payback period is 30 months and you only have 6 months of runway.

What I Would Do Differently (My Brutal Honest Retrospective)

If I could go back to Day 1 of fastpal, here's exactly what I'd change:

1. Start with the Economics, Not the Idea

Before writing any code, I'd build a detailed financial model answering:

• How much can we realistically charge?
• What will it cost to acquire each customer?
• How long before we get our money back?
• What churn rate kills the business?

2. Sell Before You Build

We spent months perfecting features nobody asked for. Instead, I should have:

• Created mockups and a sales deck
• Actually tried to close 10 deals
• Used those conversations to understand real willingness to pay
• Only then started building

3. Track Everything From Day One

I built a finance tracking sheet, but too late. Every founder should track:

• Time spent per lead
• Cost per sales activity
• Conversion rates at each stage
• Actual vs projected metrics weekly

4. Be Ruthless About Lead Quality

We're talking to everyone who will listen. Wrong approach. Better to have 10 conversations with perfect-fit customers than 100 with randoms who "might be interested."

The Framework You Need (So You Don't Make My Mistakes)

Here's your pre-launch checklist:

Step 1: Research Your Pricing

• Analyze 10 competitors' pricing pages
• Interview 20 potential customers about their current spend
• Use the Van Westendorp Price Sensitivity Meter (ask these 4 questions):
  • At what price is this too expensive?
  • At what price is this too cheap to be good?
  • At what price does it start getting expensive?
  • At what price is this a bargain?

Step 2: Model Your CAC

• Map out your planned acquisition channels
• Research industry benchmarks for each channel
• Add up ALL costs (don't forget salaries!)
• Build three scenarios: optimistic, realistic, pessimistic

Step 3: Forecast Churn

• SMB SaaS: Plan for 3-7% monthly churn
• Enterprise SaaS: 0.5-1% monthly churn
• Early stage reality: Could be 10-15% until product-market fit

Step 4: Stress Test Everything

• What if CAC is 50% higher?
• What if churn is double?
• What if sales cycle is 3x longer?
• At what point does the business break?

The Hard Truth Nobody Tells You

Here's what that Jokr CEO understood that I'm only now learning: Growth without profitable unit economics isn't growth, it's just death at scale.

You can raise money, hire people, and build features all day long. But if you're losing money on every customer, you're just digging a prettier grave.

The good news? Once you understand this, you can fix it. For fastpal, this means:

• Shorter sales cycles (no more endless partner discussions)
• Higher prices for enterprise clients
• Ruthless focus on customers who actually pay
• Building only what directly impacts conversion or retention

Your Move

Don't wait until you're months into development like I did. Don't assume that because there's interest, there's a business model.

Start with the economics. Build your model. Test your assumptions. Then, and only then, start building.

Because at the end of the day, the market doesn't care about your perfect product. It cares about one thing: do the numbers work?

Mine didn't at first. But now I know what to fix.

What about yours?

P.S. - If you want the detailed framework and calculations I'm using now, I've put together a simple spreadsheet template. No email required, just grab it here. Learn from my expensive mistakes for free.

Currently building fastpal.com and learning these lessons in real-time. Follow the journey on Twitter where I share the brutal truths of building a SaaS startup.