Jobs to Be Done Examples for Indie Hackers (No Jargon)

Jobs to be done is one of those frameworks that sounds academic until you see it applied to one real complaint, at which point it becomes the most practical lens you have.

The idea is simple: people do not buy products, they hire something to make progress in a situation. Your job as a founder is to find the situation and the progress, not the demographic.

What jobs to be done actually means

Forget the personas. A person is not their age or their job title; they are a set of situations they are trying to get out of.

The classic example: nobody wants a quarter-inch drill bit. They want a quarter-inch hole. Go one step further and they do not want the hole either; they want the shelf up before guests arrive. The job is have the shelf up in time, and the drill is only one way to hire for it. A handyman, a bracket-free shelf, or a friend with a drill all compete for the same job.

That reframe matters because it changes who your competition is and what your product must promise.

Examples that make it click

• Invoicing software. The job is not “send invoices”. It is “get paid without chasing people”, or “look professional to a client who is deciding whether to trust me”.
• A project tracker. The job is not “organise tasks”. It is “stop dropping the ball on the one client who matters”, or “show my manager I am on top of things”.
• A scheduling tool. The job is not “book meetings”. It is “avoid the back-and-forth that makes a client think I am disorganised”.

Read a few one-star reviews and you will find the job stated almost literally: people describe the progress they wanted and the wall they hit. That is the raw material for review mining, read through a jobs lens.

Run a switch interview

The best way to find jobs is to reconstruct a switch: the moment someone moved from one solution to another. Ask about a past decision, in order:

1. First thought. What made you realise the old way was not working?
2. Search. What did you try, and what did you find?
3. Decision. What tipped you to finally switch (or to give up)?
4. Anxiety. What worried you about changing?
5. Aftermath. What can you do now that you could not before?

The anxieties are gold. A product that removes the fear of switching often beats a product with more features. This is a special case of customer discovery interviews: same discipline, sharper focus on one decision.

Turn jobs into a product decision

Once you have a job statement, use it to cut scope:

• Write it as progress. “When [situation], I want to [progress], so I can [outcome].”
• List the competitors for that job, including the non-software ones.
• Find the underserved step. Most products serve four of the eight steps in a job; the gap is often at the edges you do not own.
• Build the smallest thing that removes the friction at that step. Not the whole job, just the wall.

That last move is where jobs to be done pays off. You stop building features and start removing a specific obstacle in a specific situation, which is exactly how a complaint becomes a tight feature spec.

FAQ

Is jobs to be done just another word for pain points?

It is pain points plus situation plus desired progress. Pain alone tells you something hurts; the job tells you what the person is trying to reach, which is what you promise in your headline.

How many jobs does a product serve?

Usually more than the founder expects. Most small products get hired for two to four distinct jobs. Knowing them changes your messaging and your roadmap.

Do I need formal interviews to find jobs?

No, but they help. You can start from public complaints and reviews, where people describe switches out loud. Interviews just let you follow up on the interesting sentence.

What if two jobs conflict?

Pick the one tied to the most urgent situation and price it accordingly. Serving two jobs badly is the fastest way to serve none.

How do I start with no customer access?

Read the reviews and complaints of the product your buyer already uses. When enough people describe the same switch for the same reason, you have a job. To shortlist jobs fast, run a report for 2.99 EUR and read clustered problems, then write the job statement for the strongest one.