The Hook Model is a four-phase loop from Nir Eyal's book Hooked that explains how products form user habits. A trigger prompts an action, the action delivers a variable reward, and the user makes an investment that stores value and sets up the next trigger. Over repeated cycles, users stop needing external prompts and return on their own.

Product and growth teams reach for it because it names something most roadmaps ignore: the reason a customer opens your product on a Tuesday afternoon when nobody asked them to. Acquisition gets people in. A habit is what brings them back. And for a B2B SaaS product, a returning user is the difference between a renewed contract and a quiet churn.

Key Facts: The Hook Model

The loop has four phases: trigger, action, variable reward, and investment. (Nir Eyal, How to Manufacture Desire)

Triggers come in two kinds. External triggers come from the product itself; internal triggers are associations with routines and emotions that form through repeated use. (Nir Eyal)

Eyal groups variable rewards into three types: rewards of the tribe, the hunt, and the self. (Nir Eyal, Variable Rewards)

The Habit Zone is where a behavior occurs often enough, and is rewarding enough to the user, to become the default. (Nir Eyal, TechCrunch, September 2012)

The Fogg Behavior Model states that behavior happens when motivation, ability, and a prompt converge at the same moment (B=MAP). (BJ Fogg, behaviormodel.org)

The Manipulation Matrix asks two questions: would you use the product yourself, and does it materially improve users' lives? (Nir Eyal, TechCrunch, July 2012)

What the Hook Model Is (and What It Isn't)

The Hook Model describes how a product can become a default response to a recurring feeling. It isn't a growth hack, a gamification checklist, or a guarantee. It's a diagnostic lens: for any feature you care about, does it complete a loop, or does it just sit there waiting for the user to remember it exists?

Eyal's argument is that a company's value increasingly depends on the habits it creates, not only on how many users it has signed up. That's a useful frame for subscription software, where revenue arrives monthly and depends on repeated use. A product that people open out of habit is easier to renew than one they open out of duty.

The model also has limits worth stating early. It fits products with a naturally frequent use case: messaging, task management, dashboards, inboxes, collaboration tools. It fits poorly where the underlying need is rare, such as annual tax software or a once-a-quarter compliance tool. And it says nothing about whether your product solves a real problem. A flawless loop around a pointless behavior is still pointless.

The Four Phases of the Hook Model

Each phase has a design question you can ask of your own product.

Phase	What it does	Design question	B2B SaaS example (illustrative)
Trigger	Cues the behavior, externally or internally	What prompts the user to start, and what feeling sits behind it?	A weekly digest email, then later the urge to check pipeline status before a Monday meeting
Action	The simplest behavior done in anticipation of a reward	How few steps stand between the cue and the payoff?	One click from the notification into the exact record that changed
Variable reward	A payoff the user can't fully predict	What does the user hope to find, and does it vary?	A feed showing new comments, new activity, or an unexpected insight
Investment	The user puts something in that improves the next pass	What does the user leave behind that makes tomorrow's visit better?	Saved filters, imported data, teammates invited, a customized dashboard

Phase 1: Trigger

A trigger is the cue that starts the loop. Eyal separates two kinds. External triggers are prompts that live in the product or around it: an email, a push notification, an app icon, a link a teammate sends you. Internal triggers are different. They're associations the user builds between a feeling and your product, such as boredom leading to a specific app.

The goal is a hand-off. Early on, you pay for attention with external triggers. As the loop repeats, the user begins to connect a routine or an emotion to your product, and the internal trigger starts doing the work for free. In B2B, the internal trigger is rarely boredom. It's usually uncertainty: "Where does this deal stand?", "Did the client reply?", "Is the campaign on track?" If your product reliably answers an anxious recurring question, that question becomes the trigger.

Phase 2: Action

The action is what the user does in anticipation of the reward. Eyal's guidance is to make it as easy as possible while raising motivation. This is where the Hook Model borrows from BJ Fogg's work, which the next section covers.

The practical test is friction counting. Take your most common return path and count the clicks, fields, logins, and decisions between the trigger and the first reward. Every one of them is a place the loop can break. Single sign-on, deep links that land on the exact item, and defaults that pre-fill the next step are unglamorous and work well.

Phase 3: Variable Reward

A reward that arrives the same way every time stops creating desire. Eyal ties the effect to B.F. Skinner's work on variable schedules, which he describes as intermittent reinforcement: lab mice pressed a lever more eagerly when the payoff was unpredictable than when it was identical each time. The reward in a product is rarely a treat, but the principle carries over to feeds, inboxes, and activity streams where what you'll find changes.

Eyal sorts variable rewards into three families:

Reward type	What the user seeks	Product patterns	B2B SaaS illustration
Rewards of the tribe	Feeling accepted, important, and included	Comments, mentions, recognition, shared wins	A teammate reacts to your update, or your name appears in a launch announcement
Rewards of the hunt	The satisfaction of searching and finding	Feeds, search results, deal alerts, curated content	A prioritized list of accounts showing buying signals today
Rewards of the self	Mastery, control, and completion	Progress bars, inbox zero, streaks, cleared queues	A task board you clear to zero before end of day

Most B2B products lean on hunt and self. Tribe rewards appear wherever collaboration is a core use case. The trap is mistaking variety for value: a random surprise with nothing useful in it teaches the user to stop checking.

Phase 4: Investment

Investment is the user contributing something that makes the next cycle better: time, data, effort, social capital, or money. Eyal's point is that these investments make the product more valuable to the user over time and improve what they see on the next pass. The popular shorthand is stored value: the longer someone uses a product, the more it holds that they'd lose by leaving.

In B2B SaaS, investment is concrete. Imported contacts, built automations, trained teammates, configured integrations, and accumulated history are all stored value. They're also the real moat. A competitor can copy your interface in a quarter, but it can't copy two years of your customer's configured workflows.

Investment should also load the next trigger. When a user sets a reminder, follows a project, or invites a colleague, they're scheduling their own future prompt. That's how the loop closes: the investment creates the external trigger for next time.

The Fogg Behavior Model Behind the Action Phase

BJ Fogg, who founded the Behavior Design Lab at Stanford, built a model that says behavior occurs when three things converge at the same moment: motivation, ability, and a prompt. His formula is written B=MAP. If a behavior doesn't happen, at least one of the three is missing.

Map that onto the Hook Model and the structure becomes clear. The trigger is the prompt. The action phase is where motivation and ability meet. Eyal points to motivation and ability as the two levers designers pull inside the action. So when a hook underperforms, B=MAP gives you a fast diagnosis:

No prompt: the user never gets cued, so nothing starts.
Low ability: the path is too slow or confusing, so the cue is ignored.
Low motivation: the path is easy but the expected reward isn't worth it.

Fix the weakest of the three first. Teams usually reach for more motivation (discounts, copy, urgency) when the real problem is ability (too many steps).

Hook Model vs Other Growth Frameworks

The Hook Model gets confused with other frameworks because they all deal with retention. They answer different questions.

Framework	Core question	Unit of analysis	Best used for	Weakness
Hook Model	How does a user come back without being prompted?	One user's behavior loop	Designing habit-forming features	Assumes a frequent use case
Fogg Behavior Model (B=MAP)	Why did this behavior happen or not?	A single behavior at a moment	Diagnosing a failing step	Doesn't design a full loop
Growth loops	How does one cohort's output feed the next cohort's input?	A system of users and inputs	Compounding acquisition. See in-product growth loops	Says little about individual habit
AARRR (pirate metrics)	Where in the funnel do we lose people?	Funnel stages	Measuring and finding the leak	Describes stages, not mechanisms
HEART	How do we measure user experience quality?	Experience metrics	Choosing product KPIs. See the HEART framework	Measures; doesn't prescribe design

A simple way to hold them together: use AARRR to find where retention leaks, B=MAP to diagnose a specific behavior, the Hook Model to redesign the loop around it, and HEART to measure whether it worked. The Hook Model sits close to product-led growth because in a product-led motion the product itself has to carry the habit.

The Habit Zone: Is Your Product a Candidate?

Before building a loop, check whether the underlying behavior can become a habit at all. Eyal's Habit Zone plots two variables: frequency (how often the behavior occurs) and perceived utility (how rewarding the user finds it). The zone is where both are high enough that the behavior becomes the default.

The two variables can trade off in principle: frequent use with modest payoff, or rare use with a large payoff. A behavior that's both rare and low-value won't reach the zone. Run the check honestly for each core workflow:

Workflow	How often does the need arise?	How valuable does the user find it?	Habit Zone verdict (illustrative)
Checking a shared task board	Daily or more	Moderate	Likely in the zone
Reviewing deal pipeline before a forecast call	Weekly	High	Plausible, with a good trigger
Updating a quarterly report template	Quarterly	Moderate	Unlikely; design for ease, not habit
Approving a large purchase	Rare	High	Not a habit; make it clear and fast

If a core workflow falls outside the zone, don't force a loop on it. Look for an adjacent behavior that happens more often and attach the value to that. This is also where user activation and onboarding time to value matter: the first loop a new user completes sets the pattern for every one after it.

How to Apply the Hook Model: Step by Step

Here is a working sequence for a product team.

Pick one behavior. Choose the single recurring behavior you most want users to repeat, such as logging in to review a dashboard or updating a record. One loop at a time.
Run the Habit Zone check. Estimate frequency and perceived utility using real usage data. If it fails, choose a different behavior.
Name the internal trigger. Interview five to ten active users and ask what they were thinking or feeling just before they opened the product. Write the answer in the user's words.
Map the current external triggers. List every email, notification, and link that currently prompts the behavior. Note which ones are noise.
Count the friction in the action. Walk the path from trigger to first reward and list each step. Remove or pre-fill what you can.
Audit the reward. Decide which type (tribe, hunt, self) the product delivers and whether it varies. If it's identical every time, add legitimate variety, such as new activity or fresh recommendations.
Design the investment. Identify what the user can leave behind that improves the next visit, and make it a natural byproduct of the action rather than a chore.
Close the loop. Connect the investment to a future external trigger, such as a reminder, a follow, or an invitation.
Run the ethics check. Apply the Manipulation Matrix below before you ship.
Test it. Treat the loop as a hypothesis and run it through a growth experimentation framework: one change, a defined metric, a written result.

Hook Model Template

Copy this table into a doc and fill one row per loop you're designing.

Field	Your answer
Target behavior
Target user segment
Habit Zone check (frequency / perceived utility)
Internal trigger (the feeling or question, in the user's words)
External triggers in use today
Action (simplest behavior, steps from trigger to reward)
Friction removed or to remove
Variable reward (tribe / hunt / self, and what varies)
Investment (what the user adds, and how it improves next time)
Next trigger loaded by the investment
Manipulation Matrix result (facilitator / peddler / entertainer / dealer)
Primary metric and review date

Hook Model Examples by Business Function

These are illustrative patterns for B2B SaaS, not case studies of specific companies.

Function	Internal trigger	Action	Variable reward	Investment
Sales	"Which deals need me today?"	Open a prioritized task list	New buyer activity and replies, different each day	Logged notes, tuned scoring rules, saved views
Marketing	"Is the campaign working?"	Open a live performance view	Fresh results, wins, or surprises by channel	Connected ad accounts, saved reports, annotations
Customer success	"Which accounts are at risk?"	Open the health dashboard from an alert	Newly flagged accounts or improved scores	Playbooks configured, health rules tuned
Operations	"Is anything blocked?"	Scan the workflow board	Cleared queues and new exceptions	Built automations, templates, approval rules
HR	"Who needs my attention this week?"	Open the team inbox	New requests and completed approvals	Policies encoded, forms customized
Finance	"Are we on budget?"	Check the budget vs actual view	Variance shifts and flagged items	Mapped categories, scheduled reports

Notice what's common. The trigger is an anxious recurring question, the action is one step, and the investment is configuration that gets more valuable as it accumulates. That pattern is also why habit and churn reduction are connected: stored value is hard to walk away from.

The Manipulation Matrix and Ethics

Eyal wrote the Manipulation Matrix as a check for makers of habit-forming products. It asks two questions: will you use the product yourself, and will it materially help users improve their lives? The answers sort a product into four categories.

Category	Would the maker use it?	Does it materially improve users' lives?	Eyal's view
Facilitator	Yes	Yes	The healthiest position: you're helping people form good habits
Peddler	No	Yes	Tends to fail because the maker lacks insight into the user
Entertainer	Yes	No	Fun or art, but often fades quickly
Dealer	No	No	Exploitation

The matrix isn't a moral verdict on a business. It moves the question from "can we hook users?" to "should we?" For B2B SaaS, the working test is simple: if your best customer saw exactly how your trigger, reward, and investment mechanics work, would they feel helped or handled? Notifications that exist to hit an engagement number rather than to inform, rewards that create compulsion without value, and investments that make leaving punishing rather than staying useful all fail that test.

Build loops that make the user better at their job. Keep export tools honest. And remember that a habit that serves the customer is also the one that survives a renewal conversation.

Do's and Don'ts

Do	Don't
Start with a behavior that already has natural frequency	Force a daily loop onto a quarterly workflow
Name the internal trigger in users' own words	Rely on notifications as a permanent substitute for it
Cut steps between trigger and first reward	Add motivation tricks to cover a high-friction path
Vary the reward with genuinely useful content	Add random surprises that contain nothing useful
Make investment a byproduct of useful work	Make users do setup chores for their own sake
Use investment to schedule the next trigger	Let investments pile up with no link to a future visit
Run the Manipulation Matrix on every loop	Treat engagement time as the success metric by itself
Test the loop as a hypothesis	Roll out all four phases at once and guess which one worked

Frequently Asked Questions about the Hook Model

What is the Hook Model in simple terms?

It's a four-step loop (trigger, action, variable reward, investment) that Nir Eyal describes in his book Hooked. Each pass through the loop makes the next one more likely, until users return out of habit instead of because they were reminded.

What is the difference between internal and external triggers?

External triggers are prompts that come from the product or around it, like an email, a notification, or an icon. Internal triggers are associations in the user's mind between a feeling or routine and your product. Good loops hand off from the first to the second over time.

How does the Fogg Behavior Model relate to the Hook Model?

Fogg's B=MAP says behavior happens when motivation, ability, and a prompt coincide. The trigger in a hook is the prompt, and the action phase is where motivation and ability meet. Use B=MAP to diagnose which element is weakest when a loop underperforms.

What are the three types of variable rewards?

Eyal calls them rewards of the tribe (social acceptance and recognition), rewards of the hunt (finding something valuable through search), and rewards of the self (mastery, control, and completion). Most B2B products lean on hunt and self rewards.

What is the Habit Zone?

It's the area where a behavior occurs often enough, and is rewarding enough to the user, that it becomes their default. You assess it by plotting frequency against perceived utility. A behavior that is both rare and low-value won't reach it.

Does the Hook Model work for B2B SaaS?

It works where the product has a recurring use case, such as pipeline review, task management, or reporting. It fits poorly for rare workflows. The strongest B2B investments are configured data, automations, and teammates, which raise the cost of switching naturally.

Is the Hook Model manipulative?

It can be, which is why Eyal published the Manipulation Matrix. The test is whether you would use the product yourself and whether it materially improves users' lives. If both answers are yes, you're facilitating a useful habit rather than exploiting one.

About the author

Harry Nguyen

Sales Operations Practice Lead

Harry Nguyen is Sales Operations Practice Lead at Rework with a growth marketing focus on Asia-Pacific markets. Harry writes about ecommerce growth and the growth frameworks teams use to decide where to invest next, connecting marketing activity to the sales operations that turn demand into revenue.

View full profile LinkedIn