Tactical insights for first-time founders to outsmart the burn, the churn & the breakdown.

Hey Founder,

You know the Monday meeting.

You’re back from dinner, an event, or a conversation with another founder, convinced you’ve found the next opportunity:
“Why don’t we add another segment?”
“What if we go after B2C?”
“This customer will sign if we build it.”

The opening is real, and the excitement makes sense.

But “can we do this” and “can we do this on top of everything else” are not the same questions.

This issue is about evaluating the commitment before you make it: what it requires, where the capacity comes from, and whether it creates leverage or just more load.

Let’s dive in. 

When you evaluate an opportunity, the upside usually has a number: contract value, customers, projected revenue.

The real question is what the company has to be able to do to earn it.

A large customer may need implementation, security reviews, reporting, and support you don’t yet provide. A new segment may require a different sales process, product changes, and expertise your team hasn’t built.

These aren’t extra tasks; they change what the company must deliver.

The mistake is treating the opportunity as extra revenue when it’s also extra work. You’ve planned for the win, not for what the win demands.

Growth creates problems worth solving, but it only creates room for the next opportunity if you solve them faster than they pile up.

In his conversation with David Senra, Travis Kalanick described the rule simply:
Rate of problem-solving ≥ Rate of problem-creation

When problem-solving pulls ahead, you build capacity. When problem-creation wins, each new commitment piles onto unfinished work. 

Uber’s expansion into China shows how familiar work can hide unfamiliar requirements. Uber knew how to launch markets, but China required different mapping systems, local knowledge, and local relationships while competing with Didi on its home turf.

What looked like another market launch required capabilities its existing playbook didn’t provide. After a costly fight, Uber sold its China operations to Didi. 

Baremetrics hit the same mismatch on a smaller scale.

In 2015, it introduced a free plan. Over 11 weeks, more than 1,000 free accounts signed up and 53 upgraded, adding nearly $5,000 in MRR.

But data volume doubled. Performance deteriorated, support suffered, and product development slowed. Paying customers saw downtime, delayed data, and inaccurate metrics.

Baremetrics lost nearly 60 customers, revenue churn doubled, and the free plan was replaced with a time-limited trial. 

The acquisition offer worked, but weakened the company’s ability to serve existing customers.

Uber faced requirements beyond its launch playbook. Baremetrics faced more load than its operation could absorb.

Different businesses, same question: what does this opportunity require that the company isn’t yet equipped to provide?

“Can we launch it?” is not enough. You also need to know what remains after launch, and who carries it. 

A new opportunity is tempting when the business has paying customers but growth isn’t repeatable.

Customers need help getting started, renewals take work, and deals still depend on you. Fixing that means reopening decisions you thought were settled: who you target or how onboarding works.

A new segment, partner, or feature feels more attractive because it offers fresh revenue instead of pulling you back into old problems.

But building a partner integration isn’t simplifying onboarding, and selling to a new buyer takes attention away from reducing founder dependence in the core.

So the core stays hard to run because the work that would make it easier keeps getting displaced. 

Then it misses its growth target again, giving you another reason to chase something new. You judge the core by results while taking away the resources needed to improve them.

That’s the no-man’s-land: the core pays the bills, but attention follows whichever opportunity looks most promising next.

Before adding another path, ask what it does to the core. Does it strengthen what you have, add a separate commitment, or replace part of the business?

If it’s an addition, name the capacity that will carry it. If it’s a change of direction, make sure you’re responding to evidence, not avoiding the harder work of fixing what exists. 

Having capacity for an opportunity is one question. Whether the work creates more capacity is another.

Some effort leaves reusable answers; some becomes an obligation you carry.

Uber’s city launches show the difference. Before London, Kalanick describes spending eight to ten hours on pricing calls. Once the playbook improved, later calls took five minutes, and he no longer needed to attend.

Ask whether your opportunity leaves behind:

Or will the next customer need custom work and founder involvement?

The first delivery may look similar either way. The difference is what no longer needs doing next time.

Ask: “If we did this ten more times, what would the tenth inherit from the first?”

Then make sure you want that tenth customer. Getting faster at serving the wrong segment still pulls you away from the core.

One-off work can be worthwhile. Just price it that way if every customer needs a fresh build. 

“Not yet” feels risky because you can picture the lost opportunity. “Yes” feels safer because the capacity problem comes later.

But postponing the decision doesn’t remove it; it makes the promise harder to change.

Give “not yet” a condition: “until someone owns implementation” or “until we agree which commitment this replaces.”

That turns “not yet” into a decision rule, not a delay. 

Before approving the opportunity, map what it takes to win, deliver, and scale delivery.

Don’t assume the third is just more of the second. A founder onboarding one customer and a team implementing ten may need different capabilities, not more hours.

Put an owner and effort estimate beside each requirement, then mark what exists and what you need to learn, build, or hire. You’re looking for the point where “we can do this” becomes “we need to change how the company operates.” 

For each responsibility, record: 

If the core is funding the move, show that contribution. Borrowed people and founder time count as investment.

Adjust the commitments or targets affected by that transfer. If the answer is “we’ll hire,” include the start date, onboarding time, and who carries the work until then. An open role cannot run an implementation.

If delivery should get easier, write down why.

Which integration becomes reusable? Which decisions stop coming back to you? What should the next delivery no longer require?

Then test those assumptions against the next customer. Custom work is easy to call a “platform investment”; the second customer tells you whether it really is.

If the work stays bespoke, revise the economics before selling more of it. Change the price, scope, or staffing assumption instead of budgeting for efficiencies you haven’t achieved.

Make sure the reuse helps you serve the customers you want. 

Once a month, review initiatives consuming meaningful capacity and give each one a decision:

For each decision, name what comes off someone’s workload.

“Still a priority” is not a decision. Neither is “let’s keep an eye on it.”

The review should change what the company does next week. Otherwise, you’ve added another meeting to discuss why nobody has time.

A founder wrote:

I’d split this into two buckets:

1. Things that fill your cup.

Running, art, singing, whatever you enjoy. Find a local group where you can show up without pitching, networking, or explaining how the company is going. When so much of your week depends on the business, it helps to belong somewhere that doesn’t.

2. Founder groups where you can tell the truth.

Look for small, recurring forums with thoughtful member selection, confidentiality, and no pitching. You want people you can tell “I don’t know what to do” without worrying it becomes gossip or a sales opportunity. Prioritize founders who listen, ask useful questions, and follow up.

Before joining, ask: “When you were having a difficult time, what did the group actually do?”

Events can still be useful for introductions, but don’t expect a room built for meeting people to create the trust of a group that knows you. 

Send it my way, just hit reply.

A few great reads this week:

Before you go…

Go back to your last big yes.

What did you expect it to require? What is it actually taking, and how much of the difference has quietly become your job?

That’s where I’d look before the next one. Not just for work to hand over, but for something to fix once so you don’t keep carrying it.

That’s the real moat.

See you next Thursday,

— Mariya

Hit reply and let me know. I read every single one (for real).

1. Early stage? Start with one of my practical finance guides.

2. Stuck on something specific? Book a 1:1 and we’ll work through it together.

3. Past $2M ARR? Work with me and the team at FounderFirst to run your CFO function.

Hey, I’m Mariya, a startup CFO and founder of FounderFirst. After 10 years working alongside founders at early and growth-stage startups, I know how tough it is to make the right calls when resources are tight and the stakes are high. I started this newsletter to share the practical playbook I wish every founder had from day one, packed with lessons I’ve learned (and mistakes I’ve made) helping teams scale.

Mariya Valeva

Find me on LinkedIn