People Don't Buy Products. They Hire Them for Jobs.

The founder had thirty integrations on slide four and the room was nodding on autopilot. Then the ops lead in the second row, a woman with a logistics badge on her lanyard, asked the only question that mattered: what happens to my exception queue on Tuesday morning after we sign?

The founder smiled, said onboarding would cover it, and opened slide five. Nobody in the room could describe her Tuesday. That silence is not a sales failure. It is a category error. Nobody buys your product. They hire something to make progress on a job in a specific circumstance, then fire it when progress stalls or a better hire appears. If your roadmap lists features instead of outcomes in her week, you are writing a CV for an object that will be unemployed by Q3.

You have sat in that room. The seller's language was SKU, module, and seat count. Your language was backlog, handover, and the hour you stop answering the same Slack thread. Or you subscribed to a tool you "should" use while still doing the job in a spreadsheet because the hire never started. AI copilots reframed every category review this year around one blunt question: what job does this replace in someone's actual week? The purchase was not possession. It was temporary employment with a performance review you never scheduled.

Feature Roadmaps Are HR Departments for Objects

The conventional view is simple and wrong in a useful way: we sell products, growth means more seats and more releases, and a healthy account expands. That story benefits vendors who earn expansion revenue when a module ships. It benefits agencies who sell integration statements of work that grow with every connector badge, analysts who sort firms into quadrants by feature breadth, and product managers whose promotion packet needs a visible widget in the sprint demo. Jobs are harder to commit to in Jira because they expire when context changes. A feature can sit on a roadmap for three quarters and still look like progress.

We measure the wrong instrument and call it health. Activation funnels, monthly active users, time-in-app: these track whether the object stayed on the payroll, not whether the job got done. A dashboard that glows while the exception queue grows is measuring attendance, not output. Incumbent SaaS still reports seat growth in earnings calls while customers describe the same spend as trying a wiki tool until someone actually uses it. That is the same wrong-instrument mistake as counting logins when the customer needed relief before lunch on Tuesday.

The Same Milkshake Hires Two Different Employees

Clayton Christensen's milkshake research, reported in Competing Against Luck (2016), found the same product hired for different jobs in the same day: a thick shake on the morning commute to kill boredom in traffic, a treat for a parent with a child in the evening. christensen-luck Same cup. Different employer, different success criteria, different substitute when the hire fails. Theodore Levitt made the earlier version in "Marketing Myopia" in the Harvard Business Review in July 1960: industries decay when they ship drills instead of holes. levitt I argued the buyer's side of that table in People Love to Buy: agency lives in naming the problem before anyone opens a deck. gaganmalik-love-to-buy

The competing hire is rarely your listed competitor. It is Excel, a shared inbox, an intern for a week, or the workaround someone built at midnight because the SaaS never matched how exceptions actually move. Procurement calls that evaluation. The ops lead calls it Tuesday. Every category review eventually returns to the same blunt question: what job does this replace, and what happens to the person still doing it manually?

Firing Is Not Churn. It Is the Performance Review.

Switching tools is not betrayal. It is HR. The customer fired the incumbent because progress stalled, the onboarding never transferred the job, or a cheaper hire appeared that actually cleared the queue. Churn charts record the exit interview after the decision was made. By the time renewal fails, the spreadsheet has often been doing the work for months. The vendor learns about the firing from a logo churn slide, not from the Tuesday when the ops lead quietly stopped opening the tab.

Demand, when it is real, is for the job done at economics that work, not for your SKU on the invoice. I wrote that shortage logic in Product Market Fit Is What Economists Call a Shortage: pull at a viable price means people want more of the outcome than you can comfortably deliver, not more of your feature map. gaganmalik-pmf-shortage A team still colour-coding exceptions at ten in the evening while the subscription renews is not a retention problem waiting for a win-back email. It is an employee who never showed up for the shift.

I Renamed the Epics. I Did Not Change the Metric.

I ran a jobs-to-be-done workshop at a client offsite once. Sticky notes lined the wall, each labelled "Job," and by the second coffee break I could see they were epics in disguise: "Streamline workflow," "Increase visibility," "Enable collaboration." Nobody wrote what changed in an ops lead's inbox before noon. I did not push. That was the brief. Challenging the success metric would have meant telling the VP of Product their quarterly target measured signup completion instead of job completion. I helped repackage the feature roadmap as outcome language anyway. I left with a workshop fee and a slide titled "Innovation." They left with the same dashboard.

Nadia is thirty-four, ops lead at a forty-person logistics startup in Bristol. She bought a project tool after a demo that showed kanban boards and automations. Her team never adopted it. The job still lives in a shared inbox and a colour-coded spreadsheet she updates when shipment exceptions pile up. Renewal auto-charged because cancel lived three screens deep under "Manage plan." She tried twice and got routed to a success manager offering training instead of an off switch. She is not lazy. She was asked to hire an employee who required a fortnight of configuration before Tuesday's queue looked any different. I gained a clean retro board photo. She did not gain a morning without the same Slack thread.

The Expensive Striker Still Gets Benched

You have watched a football match turn and felt the frustration before you had the vocabulary for it. Your club is losing. The manager benches the £50 million signing at the sixtieth minute and sends on a kid from the academy who has not scored in months. Nobody in the stand thinks loyalty to the transfer fee matters. The job tonight is to score. The asset is the player's CV. Expected-goals charts arrive on the phone later. Your stomach already knew at the hour mark.

That substitution is what your customer does when they reopen the spreadsheet. They are not being disloyal to your roadmap. They are losing, and you stayed on the pitch while the queue kept growing.

The Strongest Case for Selling the Product, Not the Job

Let me give the objection its fairest hearing, because the alternative is a workshop handout. Customers cannot articulate jobs in interviews. They lie, post-rationalise, and describe the product they already bought. Jobs-to-be-done can become retroactive storytelling after the fact. In enterprise software the purchase is often risk transfer: vendor balance sheet, SOC 2 certificate, latency SLA, the name on the contract when audit asks questions. Technical buyers genuinely hire specs, not feelings. Clayton Christensen acknowledged jobs shift when context shifts. Good product managers already track outcomes and north-star metrics. In categories where compliance is the job, selling "progress" sounds like marketing fluff next to a procurement matrix. If you wait for perfect job clarity, you never ship. The incumbent with the louder feature list wins by inertia.

The gap is not whether specs matter. It is whether your firm can state the job you are hired for before the customer writes the performance review for you. Clayton Christensen, Scott Cook, and Taddy Hall argued in "Marketing Malpractice: The Cause and the Cure" in the Harvard Business Review in December 2005 that segmentation by job, not demographic, predicts which innovations succeed, and that most companies cannot articulate the job they are hired to do. christensen-malpractice Alan Klement pushed the same line in When Coffee and Kale Compete (2018): customers pull products that help them make progress, not products that win feature comparisons on a slide. klement-coffee-kale The milkshake did not fail because commuters lacked vocabulary. It succeeded when the thickness matched the boredom job. Your integration count is not the job. Tuesday morning is.

Customers hire for progress and fire for stall. Until your success metric names the before-and-after in the customer's week, you are optimising a CV, not a hire. Nadia is still colour-coding shipment exceptions in a spreadsheet at ten in the evening while the SaaS invoice clears.