A customer makes two separate hiring decisions, and most retention dashboards only track the first one. The little hire is the purchase or sign-up, where money or a credit card changes hands. The big hire is what happens after, when the product either delivers real progress on the job someone brought to it, or it doesn't. Churn almost always starts in the gap between the two.
Quick Answer: The little hire is buying or signing up; the big hire is actually using the product to make progress on the job. High conversion measures the little hire, while retention measures the big hire — and a product can win the first while quietly losing the second.
What "Hiring" a Product Really Means in JTBD
In Jobs to Be Done language, customers don't buy products, they hire them to make progress on a specific job in a specific circumstance. Bob Moesta, who co-developed the JTBD interview method alongside Clayton Christensen, separates that hiring into two distinct moments. Missing the difference is why so many teams optimize the wrong funnel stage.
Moesta's framing, laid out across his work on demand-side sales and in Christensen's 2016 book Competing Against Luck, treats "hiring" as a two-part transaction:
- The little hire — the customer commits money, time, or attention. A trial starts, a card gets charged, a form gets submitted.
- The big hire — the customer actually puts the product to work and it either makes the desired progress happen or it doesn't.
Christensen's original milkshake study is the clearest illustration. People "hired" the milkshake at the register (little hire), but the job it needed to do — make a boring commute more interesting and hold them over until lunch — only got proven or disproven once they were driving and drinking it (big hire). If it goes down too thick or too fast, the milkshake gets fired next time, no matter how smooth the checkout was.
For a deeper foundation on the framework this article builds on, see this complete guide to Jobs to Be Done, which covers the underlying causal structure of a job: the push of the current situation, the pull of the new solution, and the anxieties that slow the decision down.
Why the Distinction Gets Lost in SaaS
SaaS teams have a structural reason to conflate the two hires: the little hire is easy to instrument, and the big hire is not. Sign-up forms, checkout events, and trial starts all fire clean analytics events. Whether someone actually made progress is fuzzier, slower, and often invisible until a cancellation or a support ticket surfaces it weeks later.
That asymmetry is why conversion-rate dashboards get built first and progress dashboards get built last, if at all.
The Four Forces Behind Each Hire
Moesta and Chris Spiek's "Four Forces" model explains why the little hire happens before the big hire is ever tested. Two forces push the customer toward buying, and two forces hold them back — but none of the four forces actually require the product to work yet.
- Push of the situation — the current approach has become painful enough to act on.
- Pull of the new solution — the alternative looks appealing, at least in theory.
- Anxiety of the new choice — doubts about switching, learning curve, or risk.
- Habit of the present — comfort with the existing (even if flawed) way of doing things.
Push and pull can win the little hire on their own, especially with a persuasive trial offer or a well-run demo. Whether the product actually resolves the push is a question only the big hire can answer, which is exactly why so many teams discover the mismatch only after the money has already changed hands.
The Little Hire: The Moment Money and Attention Change Hands
The little hire is the transaction — sign-up, checkout, trial activation, or the first click past a paywall. It is necessary but never sufficient, because it only proves someone was interested enough to try, not that the product delivered anything. Optimizing it in isolation is how teams end up with a funnel that looks healthy and a retention curve that doesn't.
Everything that lives in a typical growth or marketing dashboard belongs to the little hire:
- Landing-page conversion rate
- Trial sign-up rate
- Checkout completion rate
- Free-to-paid conversion rate
- Cost per acquisition
These numbers are real and worth improving. But they describe intent, not outcome. A prospective customer who signs up has told you they believe your product might do the job. They haven't told you it did.
A clean little hire is a promise. A clean big hire is a receipt.
Push and pull forces get resolved at the little hire. The customer has decided the pain of their current approach (push) and the appeal of your solution (pull) outweigh the anxiety of switching and the habit of the status quo. That's a real cognitive event, but it happens before the product has proven anything about the job itself.
Writing that reasoning down as a clear job statement is what keeps teams from confusing "why they signed up" with "why they'll stay." This guide on writing a JTBD job statement walks through the format.
The Big Hire: The Moment Progress Either Happens or Doesn't
The big hire is the first real use of the product against the actual job, and it's where the product either earns its keep or gets quietly fired. This is the moment activation metrics are meant to capture, though most teams define activation around product actions (created a project, invited a teammate) rather than around whether the underlying job got done. That gap between "did the action" and "made the progress" is where retention leaks.
A useful test: the big hire is complete when the customer would be upset if you took the product away, because it's now doing something they'd have to replace. Sean Ellis built an entire product-market-fit survey around a version of this question ("how would you feel if you could no longer use this product?"), precisely because it separates people who tried the product from people who depend on it.
Three signals tend to mark a completed big hire:
- Repeat, unprompted use — the customer comes back without a nudge email.
- A named outcome — they can describe what changed for them, not just what feature they touched.
- Behavior change elsewhere — they've stopped using the old workaround, spreadsheet, or competitor.
Reforge and other growth-research communities built around Brian Balfour's work describe this as the shift from "activation" to "habit" — the point where the new behavior competes with, and beats, the old one. Until that shift happens, the big hire is still pending, no matter how polished onboarding felt.
The Big Hire Has a Deadline, Even If You Haven't Named It
Every job has an implicit clock. Wes Bush, whose Product-Led Growth work is widely cited in PLG circles, argues that customers carry an expectation of how quickly value should show up, and that expectation is set by the job, not by the vendor. A scheduling tool might need to prove itself in one meeting; a data-migration tool might reasonably get a few weeks.
Two consequences follow directly from that deadline:
- If the big hire doesn't happen inside the window the job implies, the customer starts shopping for a replacement — often quietly, well before a support ticket or cancellation shows up.
- Teams that only track a generic "week-1 retention" number without asking what window the specific job actually demands will misread how much time they really have.
A SaaS Example: When Great Sign-Up Conversion Hides a Broken Big Hire
Picture a project-management SaaS tool with a strong top of funnel: a 45% visitor-to-trial rate and a 30% trial-to-paid rate, both comfortably above typical benchmarks. Every little-hire metric says the product is winning. Then look one layer deeper, at what paying customers actually do in week two, and a different story can show up.
Say cohort data shows that most new paying accounts create a single project, invite no teammates, and never open the tool again after day three. The little hire — the purchase decision — worked. The big hire, using the tool to actually coordinate a team's work, never got proven.
Nothing here is a claim about a real customer; it's the shape of a failure mode. OpenView Partners' SaaS Benchmarks research has repeatedly flagged the gap between conversion and durable activation as one of the more persistent blind spots in product-led growth.
| Signal | Little-hire read | Big-hire read |
|---|---|---|
| Trial-to-paid conversion is high | Product looks compelling at the point of decision | Tells you nothing about whether the job got done |
| Single project created, then silence | Onboarding checklist "complete" | Progress likely never started |
| No second teammate invited | Account is technically active | The collaboration job — the actual reason teams buy — is unhired |
| Cancels at renewal with no support tickets | No obvious "failure" signal beforehand | Classic sign the big hire silently failed weeks earlier |
This is exactly why a churn conversation after the fact is too late. The failure happened at week two, not at the cancel button. Whatever the tool's actual job was — say, "help me stop chasing status updates across five channels" — the product never delivered visible proof that the job was done, so the customer had no reason to build a new habit around it.
The Diagnostic Question
When conversion is strong but early retention is weak, the diagnostic question isn't "how do we get more signups." It's: what did the customer expect to be true one week after paying, and did the product make that visible to them? If the answer is fuzzy internally, it will be fuzzy for the customer too.
Turning the Two Hires into Metrics You Can Actually Track
Little-hire and big-hire moments map to two different metric families, and treating them as one blended "growth" number is what lets a broken big hire hide behind a healthy little hire. Splitting them into a real reporting structure is the fix, not a slogan.
| Hire moment | What it proves | Typical metrics |
|---|---|---|
| Little hire | Someone believed the product could do the job | Visitor-to-trial rate, trial-to-paid rate, checkout completion, CAC |
| Big hire | The product actually did the job | Activation rate (job-based, not action-based), time-to-first-value, week-1/week-4 retention, feature depth per active account |
A few practical moves make this split usable instead of theoretical:
- Define activation as a job outcome, not a product action. "Created a project" is a little-hire-adjacent action; "coordinated a real deliverable with a teammate inside the tool" is closer to the actual job.
- Set a time-to-value target and instrument it. If the job usually needs to show progress inside 3-7 days to stick, measure exactly that window, not an arbitrary "week 1 active" flag.
- Score the job's opportunity, not just the feature backlog. Tony Ulwick's outcome-driven innovation work, and the opportunity-score formula explained here, gives a way to rank which unmet outcomes are worth building toward next, based on importance and satisfaction gaps rather than gut feel.
- Write the job statement down before you build the fix, and check that it can survive contact with an actual sprint — this piece on making job statements survive the handoff to engineering covers how a clear statement keeps the big hire in scope when a feature gets scoped down.
- Look for the systemic cause, not just the symptom. A stalled big hire is frequently a downstream effect of an upstream loop — a confusing default setting, a missing integration, an incentive that rewards sign-ups over usage. This guide to systems thinking is useful for tracing a retention symptom back to its structural cause rather than patching the symptom.
Rule of thumb: if your activation metric can be satisfied by clicking through an onboarding checklist without ever touching the actual job, it's measuring the little hire wearing a big-hire costume.
Where the Two Hires Show Up on a Customer Journey Map
The cleanest way to see the gap between the little hire and the big hire is to plot emotion against time, from first contact through weeks of real use, rather than looking at a single conversion funnel. A journey view makes the moment progress stalls visible in a way a funnel report can't, because a funnel only shows drop-off, not the emotional flatline that precedes it.
This is precisely the gap Prodinja's Customer Journey tool is built to surface: it lets you plot an emotion curve across a customer's actual timeline, so the spike of relief at checkout (the little hire) and the moment progress either continues or plateaus afterward (the big hire) show up as two distinct points instead of one blurred "onboarding" phase. Seeing them separately is what turns "our activation is low" into a specific, addressable moment — the week-two silence, the never-invited teammate, the checklist that was completed but changed nothing.
Used this way, a journey map isn't a retrospective nicety; it's a diagnostic for exactly the failure mode this article describes. For the fuller method behind that emotion-curve view, this complete guide to mapping the customer journey covers how to plot it stage by stage.
Key Takeaways
- The little hire is the purchase or sign-up moment; the big hire is the moment the product actually delivers progress on the job it was hired for.
- A high conversion rate only proves the little hire worked. It says nothing about whether the big hire did.
- Bob Moesta and Clayton Christensen's JTBD work, including the milkshake study, is the clearest grounding for this distinction.
- Activation metrics should be defined around job outcomes, not product actions, or they'll quietly re-measure the little hire.
- Churn usually starts at a silent, un-instrumented big-hire failure weeks before the cancellation event, not at the cancel button itself.
- Mapping emotion across the full timeline — not just the funnel — is what makes the gap between the two hires visible before it turns into churn.
Frequently Asked Questions
What is the difference between the little hire and the big hire?
The little hire is the transaction — signing up, checking out, starting a trial — where money or commitment changes hands. The big hire is what happens next: whether the customer actually uses the product to make progress on their job. One is a decision; the other is a result.
Why does a high sign-up or trial conversion rate not guarantee retention?
Conversion rate only measures whether someone believed the product could help, which is a little-hire signal. Retention depends on whether the product delivered the progress the customer expected, which is the big hire — a separate event that conversion data can't see.
How do you measure the big hire in a SaaS product?
Measure it as a job outcome rather than a product action: whether the customer reached a meaningful, repeatable result (not just clicked through a checklist) within the time window the job actually demands. Week-1 or week-4 retention tied to a specific behavior, not a generic "logged in," is a closer proxy.
Is the big hire the same thing as product activation?
They overlap, but most activation metrics are looser than the big hire. Activation is often defined around a shallow action (created an account, uploaded a file); the big hire requires that action to have actually produced the progress the customer was hiring the product for.
What usually causes a broken big hire even when onboarding looks smooth?
Most often, the product never made the customer's progress visible — the job got partially done, or done invisibly, so the customer had no evidence to build a new habit around. Tracing that back to its structural cause, rather than patching the onboarding flow, is where a systems-thinking pass on the customer journey pays off.