Frequency-Based Strategy: Why Booking.com Tactics Kill Amazon

Every day I see companies making the same mistake. They see Booking.com’s success with aggressive countdown timers and scarcity messages. They watch Amazon dominate e-commerce. Then they draw the wrong conclusion: “We should copy both.”

But here’s what they’re missing — the single most consequential variable in behavioral design isn’t which Core Drives you use. It’s not whether you use Dark Patterns or the Octalysis Framework. It’s something deeper: how often your users encounter your product.

Purchase frequency determines whether Black Hat tactics build a sustainable business or destroy it entirely.

And when I say frequency, I do not just mean how often someone pays you. I mean how often they re-enter the same decision environment and re-experience the emotional residue of your design. That is why the same urgency mechanic can feel helpful in one context and exhausting in another.

Author Credibility: Yu-kai Chou

Yu-kai Chou created the Octalysis Framework after studying gamification since 2003 — years before the term entered mainstream vocabulary. As a Human-Systems Architect & Behavioral Designer, his framework has been applied by LEGO, Microsoft, Porsche, Coca-Cola, Salesforce, and MrBeast, impacting over 1.5 Billion Users.

Chou has taught the Octalysis methodology at Harvard, Stanford, Yale, Tesla, Google, BCG, and IDEO.

His work has been cited by Harvard, Stanford, MIT, Forbes, Wall Street Journal, Wired, US Department of Energy, NIST, NSF, NCBI, US Department of Education, ClinicalTrials.gov, and Google Scholar — with 3,700+ more academic publications. Explore his books here.

TEDxLausanne · Gamification to Improve Our World17 min

The Frequency Spectrum Changes Everything

Think about the products you buy. You’ll notice they fall into three patterns:

One-Time or Low Frequency (yearly or less)

Insurance premiums, car purchases, hotel bookings — these happen maybe once or twice a year. By the time a customer returns to Booking.com six months later, the stress from yesterday’s countdown timer has evaporated. The emotional manipulation worked. They booked. They forgot about the pressure. When they return, they’re psychologically reset.

This is why Black Hat tactics dominate low-frequency categories. “Only 2 tickets left!” creates urgency that actually moves the needle. The cost of that urgency — buyer’s remorse, frustration, eroded trust — hasn’t accumulated yet because there’s no next purchase in sight.

Medium Frequency (weekly to monthly)

Grocery delivery apps, fitness platforms, subscription services. These companies live in the sweet spot. They can layer White Hat fundamentals — real value, genuine personalization, authentic community — and then sprinkle in Black Hat mechanics for specific moments. A well-timed “Flash Discount: 2 hours only” works because the baseline experience is solid. Users don’t feel abused; they feel they caught a good deal.

High Frequency (daily or multiple times per week)

Social media, e-commerce platforms, news apps. Here’s the hard truth: Black Hat tactics accumulate. Every countdown timer, every fake urgency message, every artificial scarcity adds another brick to a wall of distrust. What works once becomes abuse the second, third, tenth time. Users start feeling manipulated instead of motivated.

If you are new to Octalysis, think of each Core Drive as a different motivational lever. The mistake most teams make is assuming one lever works equally well at every cadence. Frequency changes how those levers feel over time.

The Core Example: Booking.com vs Amazon

Let me tell you why Booking.com and Amazon can’t use the same playbook.

Booking.com built an empire on Black Hat mechanics. Their interface screams urgency: countdown timers, “20 people viewing this property right now,” “Only 3 rooms left at this price.” These tactics work because customers book in intense but infrequent bursts. The pressure generates a booking. The customer moves on. Months later, the stress is gone, so the tactic does not keep compounding in memory the way it would in a daily environment.

Amazon could theoretically use the exact same approach. But here’s where it breaks: my wife buys three different juicers, tries all of them, and returns two. That behavior — testing, comparing, optimizing — is pure Core Drive 2 (CD2): Development & Accomplishment. She doesn’t feel manipulated. She feels smart. She feels she’s making the best decision.

If Amazon plastered every product page with “Only 1 item left in stock!” and countdown timers, my wife would start feeling abused. She’d buy fewer items. She’d trust the platform less. She’d spend more mental energy questioning whether she’s being pressured into bad decisions.

So what does Amazon do? They reserve the heavy Black Hat arsenal for specific moments: Lightning Deals, Prime Day events, seasonal promotions. These are scarcity windows that customers expect. They’re opt-in. They happen infrequently enough that they generate excitement instead of fatigue.

The lesson every company wants to ignore: You can’t copy Booking.com’s tactics just because you’re in e-commerce. Frequency determines whether those tactics build or destroy your business.

The Value Gap Problem

But frequency creates another challenge: the value gap.

Insurance companies typically have only two critical touchpoints with customers per year: renewal and claims. That’s a problem. How do you build engagement when your product only demands attention twice annually?

The companies that solve this don’t try to force more transactions. They expand the value narrative. Instead of just selling insurance, they sell lifestyle. AAA does this brilliantly — they layer monthly coupon books from partner restaurants, stores, and attractions. Suddenly, your annual insurance service becomes a monthly touchpoint of value. You check those coupons. You use them. You feel like your membership is actively improving your life.

The mechanic? Weekly lifestyle promotions that align with your brand’s actual promise. For adventure-focused insurance: skydiving deals, rock climbing guides, expedition partnerships. The message isn’t about the product. It’s “Because you work with our insurance, you get to live more freely.”

That’s Core Drive 2 (CD2): Development & Accomplishment — packaged as a reason to stay engaged between renewal cycles.

Another pattern I’ve observed: booster-based renewal strategies. Customers accumulate status, badges, or exclusive benefits throughout the year. By renewal time, they’ve built psychological investment. They can’t leave without feeling the sunk cost loss (Core Drive 8). The system doesn’t pressure them to renew — it makes them unwilling to give up what they’ve built.

The Discovery Phase Formula

Whether you’re designing for monthly engagement or annual renewals, the initial onboarding follows a predictable Discovery Phase pattern:

Core Drive 7 (CD7): Unpredictability & Curiosity draws attention. Be different. Break the pattern. Make them wonder what comes next.

Core Drive 5 (CD5): Social Influence & Relatedness establishes safety. Show them others like them have succeeded. Demonstrate early wins.

That sequence also explains why many teams overuse urgency. Urgency creates motion fast, but it does not automatically create confidence. If your users are going to see you again tomorrow, confidence matters more than adrenaline.

Core Drive 2 (Development & Accomplishment) provides the actual value. Clear progression, meaningful improvement, tangible growth.

Get this sequence right, and you’ve built intrinsic motivation. Skip Core Drive 5, and users feel isolated. Skip Core Drive 2, and the curiosity expires. You need all three in order.

The White Hat vs Black Hat Organizational Tension

Here’s a friction point that almost every company experiences:

White Hat activities, helping users grow, teaching them skills, celebrating their progress, create zero urgency. A user doesn’t need to sign up today to improve themselves tomorrow. The value is always there.

Black Hat mechanics, deadlines, notifications, fake scarcity, create immediate urgency. And because urgency drives conversions, the pressure always wins internally. The sales team loves deadlines. The growth team loves notifications. The designers love countdown timers.

I’ve seen this play out at dozens of companies. The tension becomes organizational. White Hat advocates say, “We need to stop manipulating users.” Black Hat advocates say, “But the numbers show it works.” Both are right. Both are also incomplete.

There are two main solutions:

Solution 1: The Retreat Model

Remove all competing Black Hat mechanics. If your users are confused by conflicting urgency messages, they disengage. Sometimes the answer is to strip away the pressure entirely and let Core Drives 2 and 5 do the heavy lifting. This works for high-frequency products but requires absolute discipline. The moment you backslide and add one deadline, the entire experience becomes mixed messages.

Solution 2: Add Black Hat to White Hat (More Practical)

Keep the White Hat foundation strong and add controlled Black Hat mechanics as optional overlays. Scarcity windows, social proof badges, optional participation mechanics that create Fear of Missing Out (FOMO) without pressure, these can enhance engagement without feeling abusive.

The key word is optional. If the Black Hat layer is something users can ignore and still get full value, you’ve preserved trust while creating behavioral triggers.

I built Octalysis Prime around this principle. We created a scarcity window, 6 months for a specific cohort to enroll, but embedded it within a Black Hat-resistant experience. Why? Because the membership itself is high-frequency. Once someone joins, they interact weekly. A heavy-handed sales page would destroy the experience of members who look at the waitlist later.

The 6-month enrollment window creates urgency. The 3-day early-bird discount creates urgency. But the underlying product doesn’t rely on deadline pressure. That’s the balance.

FAQ

How do I determine my product’s purchase frequency?

Calculate the average time between repeat purchases or engagement sessions for your active users. Daily or weekly = high frequency. Monthly or quarterly = medium. Annually or less = low. Your strategy should match this frequency, not your aspirational frequency.

Can I use both high-frequency and low-frequency tactics?

Yes, but segment them. Use urgency tactics for users in active purchase mode and loyalty-building tactics for users between purchases. The mistake is applying one strategy uniformly across all user states.

What if I want to increase my product’s purchase frequency?

Start by creating reasons to return between purchases. Content, community, and progress mechanics fill the value gap. But don’t force frequency with Black Hat tactics — that creates resentment. Build genuine value that makes users want to return more often.

Why do Booking.com’s tactics feel acceptable but similar tactics on Amazon feel manipulative?

Context and frequency. Hotel shoppers often make decisions inside a short, genuinely time-sensitive booking window, but they do not revisit that pressure every day of the year. Amazon shoppers browse constantly without the same urgency. The same tactic can feel useful in one environment and manipulative in the other.

How does this apply to SaaS products?

SaaS products are high-frequency by nature (daily or weekly usage). Focus on Core Drive 3 (CD3): Empowerment of Creativity & Feedback and Core Drive 2 (Development & Accomplishment) for sustained engagement. Use Core Drive 7 (Unpredictability & Curiosity) sparingly for feature discovery. Avoid heavy Black Hat tactics — users who feel pressured by their daily tools will switch to competitors.

The Decision That Changes Everything

I think about this framework constantly when working with companies in different verticals. Fintech platforms, SaaS products, subscription services, they all think their situation is unique. But once we map frequency, the strategy becomes obvious.

The companies winning aren’t necessarily the ones using the most advanced behavioral design. They’re the ones asking the right question first: “How often will this actually happen?”

From that question, everything else follows.

The practical version is even simpler. Map how often users buy, how often they browse, and how often they live with the emotional aftertaste of your tactics. When those cadences are high, design for trust. When they are low, you have more room for urgency, but only if the urgency still helps the user make a real decision.

Related Reading

• Octalysis Framework: The Complete Motivation Model
• Black Hat vs White Hat Behavioral Design
• Core Drive 4: Ownership & Possession
• Core Drive 7: Unpredictability & Curiosity
• Onboarding Design: The First Five Minutes

WOULD YOU LIKE YU-KAI CHOU TO WORK WITH YOUR ORGANIZATION?