A few months ago I watched a YouTube video of a carpenter demonstrating a $90 framing hammer.

I expected a product review. What I got was one of the clearest product design lessons I've seen in years — and it had nothing to do with software.

It's not really a hammer. It's a workflow tool.

The carpenter didn't open by talking about the hammer. He opened by talking about what a framer actually does all day.

He talked about stud spacing. Plate layout. Squaring lumber. Pulling nails. Marking angles. The repetitive, physical rhythm of framing a wall.

Then he picked up the hammer and showed how almost every feature on it was designed to eliminate a step in that workflow.

That reframe — from "what does this product do" to "what does the customer do all day" — is the whole lesson.

He demonstrates jobs.

The hammer has fourteen distinct features. The carpenter didn't list them. He demonstrated each one by showing the job it replaced.

Hammer Feature	Actual Job It Solves	SaaS Equivalent
16-inch overall measurement	Quickly find standard stud spacing	Built-in workflow logic that eliminates a separate calculation or tool
14.5-inch center spacing	Measure framing gaps without grabbing a tape	Automatically calculating or pre-populating information users normally look up
90-degree square	Square lumber without carrying another tool	Embedded functionality that replaces another app or workflow step
1.5-inch and 3-inch reference points	Rapid plate layout	Templates, presets, and smart defaults
45-degree reference	Quickly mark an angle	Contextual shortcuts for common user tasks
Rip claw	Demolition and prying as well as nail removal	Expanding around an adjacent job the same user regularly performs
Anti-ring rib	Reduce annoying noise during repeated use	UX improvement that may not change core functionality but makes repeated use better
Stronger, wider claws	More durability under real-world use	Reliability, uptime, scalability, and resilient infrastructure
Magnetic nail starter	Start nails one-handed	Automation that removes a repetitive manual step
Hexagonal face	Better access in tight spaces	UI or functionality optimized for edge cases users repeatedly encounter
Side nail puller	Easier nail removal in certain situations	An alternate workflow for cases where the primary interface is inefficient
14.5-inch straightedge	Draw a line without finding scrap lumber	A built-in utility that replaces an external workaround
Tether hole	Prevent dropping the hammer at height	Security, permissions, backups, and safeguards
Saw-blade wrench	Remove the need to grab another tool	An integration or adjacent capability that eliminates context switching

Every feature is a job. Not a capability. A job.

"A feature by itself is just a capability. A feature tied to a job becomes a reason to care."

The feature is not the job.

This is where most SaaS product teams get stuck.

They build features. They ship capabilities. They write release notes that describe what the product now does.

But the customer doesn't care what the product does. The customer cares what they no longer have to do.

The hammer's magnetic nail starter doesn't exist because someone thought "what if we added a magnet?" It exists because starting a nail one-handed is a real job that framers do hundreds of times a day, and doing it two-handed is slower and occasionally dangerous.

The question the designer asked wasn't "how many features can we fit into a hammer?"

"How many features can we fit into a hammer?"

The question was: "What else does a carpenter need to do while the hammer is already in their hand?"

"What else does a carpenter need to do while the hammer is already in their hand?"

That's a completely different question. And it produces completely different products.

Where does your customer put your product down?

Here's a question worth asking about your own product.

Where does your customer put your product down?

Not when they're done for the day. During the job. Mid-task. What makes them stop, switch to something else, and come back?

Every one of those moments is a friction point. And friction points are either product opportunities or product failures, depending on how you look at them.

"Where does your customer put your product down?"

The carpenter almost never puts the hammer down during a framing sequence. The hammer was designed so he wouldn't have to.

Most SaaS products are not designed that way.

Workflow compression may be more valuable than feature expansion.

Here's what the hammer's workflow looks like in practice:

Physical workflow: Hammer → Tape Measure → Hammer → Square → Hammer → Straightedge → Hammer → Wrench

SaaS workflow: SaaS Product → Excel → SaaS Product → Slack → CRM → SaaS Product → ChatGPT → SaaS Product

The carpenter's hammer compressed that first sequence. The tape measure, the square, the straightedge, the wrench — they're all still there, but they're built in. The workflow got shorter.

Most SaaS products do the opposite. They add steps. They require context switching. They create new places where the customer has to put the product down.

"Where are we unnecessarily interrupting the job they came here to do?"

Workflow compression — reducing the number of times a customer has to leave your product to complete a job — may be more valuable than adding new features.

This is different from feature bloat.

Feature bloat is adding capabilities that don't map to real jobs. It's the product equivalent of adding a bottle opener to a hammer because someone thought it would be clever.

Workflow compression is different. It's identifying the jobs that surround the job your product already does — the things your customer does immediately before, during, and after using your product — and asking which of those you could absorb.

The hammer didn't become a Swiss Army knife. It became a better hammer by understanding the full workflow a framer actually lives in.

The question isn't "what can we add?" The question is "what can we remove from the customer's work?"

"What can we remove from the customer's work instead of what can we add to our product?"

The product feature is not the marketing story.

Here's where this gets interesting for product marketers and GTM teams.

The carpenter never led with features. He led with jobs.

He didn't say "this hammer has a 14.5-inch center spacing reference." He said "you can measure stud gaps without grabbing a tape." The feature is the mechanism. The job is the story.

This distinction matters enormously in how you position and sell a product.

Feature vs. Job — four examples:

---

SaaS Feature: Automated Lead Routing

Customer Job: Stop making someone manually decide who owns every new lead.

---

SaaS Feature: AI-Powered Reporting

Customer Job: Stop making me spend two hours every Friday assembling the same report.

---

SaaS Feature: Multi-Account Management

Customer Job: Let me manage 50 clients without opening 50 tabs.

---

SaaS Feature: CRM Integration

Customer Job: Stop making my team enter the same information twice.

---

The feature is what you built. The job is why anyone should care.

"Don't show me everything your product does. Show me how it changes the things I already do."

Most product marketing leads with the feature. The best product marketing leads with the job.

It is also an almost perfect product demo.

The carpenter's video is, structurally, a product demo. And it's one of the best I've seen.

He doesn't start with specs. He starts with context — the world the customer lives in, the work they do, the friction they feel.

Then he introduces the product. Then he demonstrates each feature by showing the job it eliminates. Then he lets the viewer do the math on whether the product is worth it.

There's no hype. No superlatives. No "game-changing" or "revolutionary." Just: here's the job, here's how this solves it, here's what that means for your day.

That's a template worth stealing.

Then the price changes without changing.

The hammer costs $90. That's a lot for a hammer.

But by the end of the video, you're not thinking about the price of a hammer. You're thinking about the price of a tool that replaces a tape measure, a square, a straightedge, a wrench, and a nail starter — and eliminates the time and friction of switching between them.

The price didn't change. The frame did.

This is what good product marketing does. It doesn't justify the price. It reframes what the customer is actually buying.

A $90 hammer is expensive. A workflow tool that compresses a framer's daily routine and reduces the number of times they have to put it down? That's a different conversation.

The best products become invisible.

The carpenter said something near the end of the video that stuck with me.

He said the best tools become invisible. You stop thinking about the tool and start thinking about the work.

That's the goal. Not a product that impresses. A product that disappears into the workflow.

The hammer doesn't ask the carpenter to adapt to it. It adapted to the carpenter.

That's the standard worth building toward.

---

The hammer is only half the lesson.

The product designer understood the job. The seller turned those product decisions into a story built around the customer's work. That same idea carries directly into field marketing, sales plays, demand generation, event booths, customer dinners, advocacy, and the broader GTM flywheel.

Next: What This Hammer Demo Can Teach Field Marketing