Welcome to this week’s edition of The Bootstrap Insider (Thoughts of the Week). If you’re new here, subscribe to ensure you receive my next piece in your inbox. If you want to read more of my posts, check out my archive.

Hi {{first_name}},

thank you for being part of this newsletter.

As I mentioned before, the main goal of The Bootstrap Insider is simple: to help you find equity-free prize money and opportunities that actually move your startup forward. That's the hard business side.

But on Sundays, I do something different.

Bootstrapping can be a lonely game. While everyone else is celebrating fake VC-funding rounds on LinkedIn, we are the ones actually figuring out how to survive on cash flow.

That’s why Sundays are for the unglamorous reality. I share the behind-the-scenes learnings, the roadblocks, and the raw stories of what it actually takes to build a business without a safety net.

It’s a new format, and I want to make sure it hits the mark for you.

Do me a quick favor: Hit "reply" and just say "Yes" if you want more of the unpolished behind-the-scenes stuff—or tell me what your biggest headache was this week. I read every single one.

Best,

Bartosz

Last week, I introduced you to a concept that completely shifted how I look at startups: We need to stop building products for static demographics (like "Klaus, 42, Manager") and start building for the specific roles people are playing at the exact moment they need help.

But what I didn’t tell you is that understanding the "role" is only half the battle. There is a second layer to this concept. And to be honest, missing this second layer is exactly why so many founders build products packed with amazing features... that absolutely nobody wants to pay for.

Here is the missing link: How do we translate a "Role" into actual Entrepreneurship?

Last week, we established that a role (like "Head of Department" or "Freelance Designer") is basically a costume we wear. But sociology tells us that every costume comes with heavy, invisible expectations.

There are strict rules for every role:

When a person feels the pressure of these expectations, they look for help. They don't wake up wanting to buy a SaaS subscription—they wake up needing to "hire" a tool (a prop) to help them fulfill their role's expectations. They have a "Job" to do.

And this is where the JTBD (Jobs-To-Be-Done) framework comes in.

When I look at the JTBD infographic on my office wall, there is a section with three interlocking gears that perfectly explains how these expectations break down. It reminds me of one of my biggest conceptual errors in product development.

In the past, I always focused solely on the pure function of a product.

Let's say you are building an invoicing tool for freelancers. The obvious goal is: "My tool helps them create and send invoices faster."

That is the Functional Job (the top gear). It is the rational, practical baseline. But here is the hard truth: A purely functional product is just a "vitamin." It’s nice to have, but it’s completely replaceable by a free Excel template.

The real breakthrough happens when you realize that every customer role simultaneously drives two much more powerful, invisible gears:

❤️ The Emotional Job (The Inner State): They don't just want to send an invoice faster. They want to get rid of that knot in their stomach at the end of the month. They want to avoid the panic of making a tax mistake. They want to feel safe and in control of their chaotic freelance business.

🎭 The Social Job (The Stage): They want to look good in front of their clients. They don't want to look like an amateur who sends messy Word documents. They want to be perceived as a highly professional, established business owner.

That is the magic! When you realize this, you stop selling software features. You start selling relief, peace of mind, and status.

These reflections led me straight down the rabbit hole to the Jobs-To-Be-Done (JTBD) Framework. It is the only logical consequence.

Features and functions get you into the game, but the Emotional and Social jobs are the true triggers that actually close the sale.

So, how do you apply this to your startup today?

There is a magic formula I use to force myself to combine these three gears into one razor-sharp value proposition. Before you write your next landing page, email campaign, or sales pitch, fill in these blanks:

Example: "When the end of the month approaches (Situation), I want to generate flawless invoices in 2 clicks (Functional Job), so I look like a top-tier professional to my clients (Social Job) and can finally sleep soundly without worrying about my cash flow (Emotional Job/Outcome)."

Stop selling the top gear. Start selling the bottom gears. That is how you build a painkiller.

P.S. Let’s do a quick reality check on your own product. It's easy to list features, but much harder to nail the psychology.

Hit "Reply" to this email and tell me in one short sentence: What is the core Emotional Job your product solves for your users? What inner pain does it take away?

I read every single one!

P.P.S. This is only Part 2 of my deep dive into the JTBD framework. Keep an eye out for Part 3 and Part 4 in the coming weeks, where we will uncover the invisible psychological forces that actually stop people from clicking "buy"—even if your product is perfect.

Let's get to work!

([email protected])