In an emerging category, your fiercest competitor rarely wears a logo. It's the spreadsheet your prospect already built, the intern who compiles the weekly report, or the flat decision to keep doing nothing. A Jobs-to-Be-Done competitive analysis maps every option customers currently hire to get the job done — including inaction.
Your real competitive set in a new category isn't the two or three funded startups chasing the same customer. It's every workaround already doing the job today: spreadsheets, manual processes, outsourced help, and doing nothing at all.
Why Named Competitors Are the Wrong Starting Point in New Categories
Traditional competitive analysis starts with a list of vendors selling something similar to yours. In an emerging category that list is short, misleading, or empty — while the real alternative, a manual workaround, quietly serves 80-90% of the addressable market. Naming rivals before naming the job is backwards.
Clayton Christensen built an entire theory of disruption around this blind spot. His research, later formalized through the Christensen Institute, argued that the biggest growth opportunities sit in non-consumption — the mass of people and companies who currently solve a job with nothing, or with something so crude it barely counts as a solution. A feature-comparison grid against two other funded startups tells you nothing about that market.
Christensen's own field research makes the point concrete. In the well-known milkshake study he conducted with Bob Moesta for a fast-food chain, researchers discovered that a large share of morning milkshake sales were competing against boredom, bagels, and bananas on a commute, not against a rival chain's milkshake.
Christensen and his co-authors later detailed this reasoning in the Harvard Business Review piece "Know Your Customers' Jobs to Be Done" (2016), written with Taddy Hall, Karen Dillon, and David Duncan. The chain's real rival for that morning job was anything else a commuter could grab one-handed, including nothing.
This matters even more for founders and PMs in categories that don't have an established name yet — "vertical AI copilots," "workflow orchestration," "revenue intelligence," whatever the analysts are calling it this quarter. If prospects can't easily name what you are, they also can't name who else does it. They can only tell you what they currently do — and that "do" is your actual battlefield.
Signs you're only competing against named rivals
A few tells suggest your competitive analysis is missing the bigger battlefield:
- Your win-loss notes only ever say "chose Competitor X" or "chose us," with no "stuck with their current process" option.
- Your sales deck opens with a logo-versus-logo comparison slide instead of a "what are you doing about this today" question.
- Your churn interviews never surface "we went back to the spreadsheet."
- Nobody on the team can describe, in detail, what a prospect's Tuesday looks like without your product.
The three faces of your real competitive set
Most emerging-category teams eventually discover their competition breaks into three buckets, not one:
- Named rivals — other funded or bootstrapped products chasing the same buyer.
- Manual workarounds — spreadsheets, shared docs, a trusted intern, an agency, a Slack thread.
- Non-consumption — the job simply doesn't get done, or gets done so rarely it barely registers as a process.
Ignore the second and third buckets and you'll build a roadmap that wins feature comparisons against rivals nobody was choosing between in the first place.
Redefining the Competitive Set: Everyone Hired for the Job
A JTBD competitive audit starts from the job, not the category. Theodore Levitt's famous line — people don't want a quarter-inch drill, they want a quarter-inch hole — is the whole method in one sentence. Anything that produces the hole is a competitor, drill or no drill.
This is the same lens behind our complete guide to Jobs-to-Be-Done: define the progress a customer is trying to make, then ask what they currently hire to make it, rather than what they'd buy if your product already existed in their mental map of options. "Hire" is deliberately broad. A person, a habit, and a piece of software can all be hired for the same job.
Writing the job down in a disciplined format matters here, because a vague job statement produces a vague competitive set. Following a structured approach — the kind covered in how to write a JTBD job statement — forces you to separate the job ("understand why weekly signups dropped") from the solution category ("analytics software"), which is exactly the separation that surfaces workarounds as real competitors.
Jobs also aren't purely functional. The pull to keep asking a trusted colleague instead of adopting new software is often emotional (fear of being wrong in front of leadership) or social (looking capable and in control) as much as it is functional (getting a number). A competitive audit that only inventories functional substitutes misses why the emotional and social "competitors" are so hard to displace.
| Traditional competitive analysis | JTBD competitive analysis |
|---|---|
| Starts from category ("BI tools," "project trackers") | Starts from the job ("know if we hit the number this week") |
| Competitor list = funded companies with similar positioning | Competitor list = anything currently hired for the job |
| Benchmarks features and pricing | Benchmarks time-to-progress, trust, and switching cost |
| Blind to "no solution" as an answer | Treats non-consumption as the largest single competitor |
| Wins by matching or beating rival feature sets | Wins by beating the job of doing it manually or not at all |
Case in Point: The Analytics Tool Losing to "We Just Ask the Data Team"
Consider a common pattern in early-stage analytics tools: the roadmap is built against Looker, Tableau, and Mode, but the deals that stall aren't lost to any of them. They're lost to a Slack message that says "hey, can you pull this for me?" That message is the real competitor.
This is a composite scenario, not a single case study, but it repeats often enough to be worth walking through in detail. A team building self-serve analytics for ops and revenue leaders assumed their competitive set was other self-serve BI vendors. Win-loss interviews kept surfacing something else: buyers weren't choosing a rival tool, they were choosing to keep asking their internal data team for the number.
That workaround wins for reasons no feature comparison would ever surface:
- Zero setup cost. The relationship with the data analyst already exists; no procurement, no onboarding, no new login.
- Trust is pre-loaded. The requester already trusts the person, so they don't have to trust a new tool's methodology.
- The job is rare, not constant. If the question only comes up twice a month, the "cost" of asking a person feels lower than learning software.
- Social cover. Asking a colleague spreads accountability for a wrong number; a self-serve dashboard puts it entirely on the requester.
Applying Forces of Progress to the workaround
Bob Moesta and the JTBD practitioner community frame switching decisions with four forces: push away from the status quo, pull toward a new solution, anxiety about the new option, and habit with the old one. Mapping "ask the data team" against those forces explains the stalled deals better than any feature grid.
| Force | What it looks like with "ask the data team" |
|---|---|
| Push | Waiting two days for an answer; the analyst is a bottleneck during crunch weeks |
| Pull | Promise of an instant, self-serve number whenever it's needed |
| Anxiety | Fear of misreading a chart, defining a metric wrong, or looking foolish in front of leadership |
| Habit | The Slack thread is comfortable, familiar, and already part of the weekly rhythm |
Read this way, the team's real objection wasn't "your dashboard is missing a feature." It was "your dashboard hasn't yet out-weighed my anxiety and habit enough to justify the switch." That reframed the roadmap, and the shift shows up clearly when you line up what the team was building before against what they prioritized after:
| Roadmap item under feature-parity thinking | Roadmap item under the JTBD reframe |
|---|---|
| Add more chart types to match Tableau | Cut time-to-first-answer to a few minutes |
| Build a more flexible dashboard builder | Embed pre-answered metrics directly into Slack, where the request already happens |
| Match a competitor's semantic layer | Pre-certify trusted metric definitions so users stop double-checking with the data team |
| Add more export formats | Compress onboarding from a multi-week rollout to a single guided setup |
The competitor was never a company. It was comfort — and comfort has a roadmap of its own once you know where to look.
Running a JTBD Competitive Audit, Step by Step
A JTBD competitive audit is a repeatable exercise, not a one-time insight. It works best as a structured sequence: write the job, inventory every hire for it, map the current journey, score the opportunity, and pressure-test that the findings survive contact with engineering. Skipping steps is how teams slide back into feature-grid thinking.
- Write the job statement precisely. Use the job statement format so the job is stated as customer progress, not as a product category — this alone rules out "compete with Tableau" as a strategy, and it gives every later step a stable unit of analysis.
- Inventory every current hire for that job. List named vendors, manual processes, outsourced help (an agency, a consultant, "the intern"), and explicit non-consumption. Interview recent buyers about what they did before they found you, not just what other tools they demoed, and ask them to walk you through the last time they actually did the job.
- Map the current journey against the workaround. Plot the emotional highs and lows of the existing process using something like the approach in the customer journey guide; the moments of friction in that journey — waiting, second-guessing, re-work — are where a new entrant has leverage.
- Score the opportunity per desired outcome. Tony Ulwick's Outcome-Driven Innovation (ODI) method scores outcomes by importance minus satisfaction, and the opportunity score formula turns that into a rankable backlog instead of a gut-feel list, with workarounds scored on the same outcomes as named rivals.
- Check that findings survive the handoff. Insights about "why the spreadsheet wins" die quietly in a slide deck unless they're translated into statements engineering can build against — see how job statements survive the handoff to engineering for a way to keep the workaround's advantages visible all the way to the sprint board.
- Look for the systemic forces protecting the status quo. Manual workarounds often persist because of a self-reinforcing loop (a trusted analyst plus a low-volume request plus organizational habit); the systems thinking guide is useful for spotting the loop before you design a fix for a single symptom that the loop will simply route around.
A quick self-check
If your competitive analysis document doesn't have a row for "spreadsheet," "manual process," or "does nothing about it," it's incomplete — not because those are strong products, but because they're strong incumbents.
From Competitive Map to Roadmap: What Non-Consumption Tells You to Build
Once non-consumption and workarounds are on the competitive map, prioritization changes shape. Instead of asking "what feature beats Rival X," the question becomes "what reduces the switching cost below the comfort of the status quo." That's a roadmap about trust, setup time, and habit — not about parity checkboxes.
CB Insights has repeatedly cited "no market need" as among the most common reasons startups fail in its postmortem analyses of shut-down companies — a directional signal, not an exact figure, but a consistent one across years of their reporting. A large share of that failure mode isn't an absence of demand; it's demand that's already satisfied by a workaround the team never benchmarked against.
Three practical shifts follow from taking non-consumption seriously:
- Prioritize time-to-first-value over feature depth. If the workaround is "ask a person," your product has to beat that person's response time, not just their functionality.
- Design for the moment the workaround breaks. Manual processes fail at specific volumes, headcounts, or complexity thresholds — target the roadmap at that breaking point, not at an abstract persona.
- Sell against comfort, not against competitors. Positioning that argues "better than Tool X" is often irrelevant to a buyer whose actual alternative is a familiar habit, not a rival vendor.
In practice this changes the sales narrative as much as the roadmap. Instead of "we're better than Competitor X," the honest and more persuasive claim is "we're faster than waiting on the data team" or "here's what this costs you in hours versus the spreadsheet you already have."
Analyst commentary on shadow IT and shadow BI — the spreadsheets, personal databases, and one-off scripts that Gartner and Forrester have both flagged for years as running alongside official tooling — is a useful, if directional, reminder of just how entrenched the workaround usually is before you show up.
Where a tool like Prodinja fits
This is exactly the reframe Prodinja's Customer Jobs tool is built around: it walks you through the job statement, Ulwick-style opportunity scoring, and Forces of Progress in one flow, so the "competitor" field in your analysis isn't limited to named rivals. By framing competitors as anything hired for the same job, it helps you scope opportunity against workarounds and non-consumption — not just the two other startups in your Series A deck.
Key Takeaways
- Your competitive set in an emerging category includes manual workarounds and non-consumption, not just named vendors — and the workaround is usually the larger share of the market.
- Clayton Christensen's non-consumption concept and Theodore Levitt's "quarter-inch hole" framing both point to the same discipline: define the job, then find everything hired to do it.
- Bob Moesta's Forces of Progress (push, pull, anxiety, habit) explain why comfortable workarounds beat feature-rich new tools even when the new tool is objectively better.
- A JTBD competitive audit is a sequence — job statement, hire inventory, journey map, opportunity score, handoff check — not a single workshop.
- Roadmaps built against non-consumption prioritize time-to-first-value, trust, and the workaround's breaking point over checkbox feature parity.
- Prodinja's
Customer Jobstool operationalizes this by scoping opportunity against workarounds and non-consumption, not only named rivals.
Frequently Asked Questions
What is a JTBD competitive analysis?
A JTBD competitive analysis identifies every option — vendors, manual processes, outsourced help, and doing nothing — that customers currently "hire" to make progress on a specific job, then compares them on switching cost and trust rather than feature lists alone.
How do you compete against "doing nothing"?
You compete against non-consumption by lowering the cost of getting started (setup time, learning curve, risk of a wrong answer) below the cost of continuing to do nothing, since for most non-consumers the job feels too rare, risky, or low-priority to justify any solution at all.
Isn't non-consumption just another way of saying there's no market?
No — non-consumption usually means demand exists but is being met by an informal substitute (a spreadsheet, a colleague, a manual habit), which is a real, addressable market once you identify what's currently being hired and why it's "good enough" for now.
How do I find out who my real competitors are in JTBD terms?
Ask recent buyers what they did in the weeks before they found you, not which other products they evaluated; their honest answer — a spreadsheet, an intern, a consultant, or nothing — is your actual competitive set, and it should show up directly in your job statement work.
What's the practical difference between JTBD and traditional competitive analysis?
Traditional competitive analysis starts from a product category and lists similar vendors; JTBD competitive analysis starts from the customer's job and lists everything hired to do it, which routinely surfaces manual workarounds and non-consumption as the biggest competitors a new entrant actually faces.