Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Red Team

Red Team

How to Succeed By Thinking Like the Enemy
Can your organization find its blind spots before an adversary does?
by Micah Zenko 2015 336 pages
3.74
500+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Stop grading your own homework on high-stakes decisions

Self-assessment has blind spots. Red teaming is a structured way to examine an organization or decision from a perspective its usual routines may exclude. Its distant ancestor was the Catholic Church’s Devil’s Advocate, an official assigned to challenge evidence for a candidate’s sainthood. The point was not reflexive negativity, but a formal check on enthusiasm and hearsay.

Separate facts from choices. In 2007, two independent teams examined evidence that Syria’s Al Kibar facility was a nuclear reactor. One tried to confirm the claim; the other searched for alternatives. Both concluded the reactor explanation was strongest, but neither found evidence that it was part of a weapons program. President Bush accepted the assessment of the facility while declining to treat that finding alone as grounds for an American attack.

Analysis

The case shows why challenge is most valuable when it separates questions that confidence tends to blur. Is the building a reactor? Is it part of a weapons program? Does that justify military action? Each question demands different evidence and carries different consequences. Independent review cannot eliminate uncertainty, but it can stop a persuasive answer to one question from quietly answering all the others. The method also depends on leaders being willing to preserve that distinction when political pressure favors a simpler story.

A warning ignored is not a successful test

Discovery is only half the job. The Federal Aviation Administration’s red team repeatedly found weak airport security before the September 11 attacks. During a 1996 exercise at Frankfurt airport, its members tried 44 times to smuggle simulated bombs through screening. Not one attempt was detected. The team documented failures, but had no reliable way to learn whether managers corrected them, and similar weaknesses kept appearing.

Warnings need owners. The team lacked clear authority, its findings were not consistently tracked, and its managers did not make lasting improvements a priority. An investigation later found that the program had been badly managed and had created a serious danger to public safety. A probe that exposes a flaw without a path to repair it produces reports, not protection.

Analysis

This is a powerful distinction between diagnostic accuracy and institutional effectiveness. A test can be technically excellent and still fail its purpose if no one is accountable for acting on the result. Organizations often celebrate audits and assessments because they create evidence of oversight; the harder measure is whether a named owner closes the gap and verifies the fix. The FAA case also warns against treating repeated findings as fresh information. When the same vulnerability recurs, the failure may be less about detection than incentives, authority, or follow-through.

Choose the right challenge: simulate, probe, or reanalyze

Three tools answer different questions. A simulation rehearses how a plan may unfold among actors with competing goals. A vulnerability probe imitates an adversary trying to defeat a defense. An alternative analysis reexamines evidence or assumptions through a different process or team. Calling all three “red teaming” can conceal the fact that each exposes a different kind of weakness.

Match method to risk. The Navy SEAL raid on Osama bin Laden’s compound was rehearsed against possible complications, including the loss of a helicopter. Security testers, by contrast, try to enter buildings or networks without authorization. Intelligence teams might instead ask whether evidence supports a competing explanation. A rehearsal cannot establish whether intelligence is true, and a network penetration test cannot tell executives how a competitor will respond to a new product.

Analysis

The framework is useful because it turns a broad aspiration, “think differently,” into a choice of method. It also discourages a common category error: mistaking a successful exercise for proof that a strategy is sound. Simulations test interactions under selected assumptions; probes test defenses under defined rules; alternative analyses test interpretations. Every method has boundaries, so the strongest review makes its question explicit before work begins. Otherwise, a polished exercise can create reassurance about precisely the issue it never examined.

Place challengers near power, but outside its assumptions

Independence needs access. A red team kept far from decision-makers may lack information and influence. One absorbed into the regular hierarchy may adopt the very assumptions it should question. Effective teams occupy a middle ground: close enough to understand the organization and reach senior leaders, yet independent enough to disagree.

Design the engagement deliberately. Leaders need to define what is being examined, who can access the relevant information, how long the work lasts, and what the team must deliver. Members need both analytical courage and the communication skill to make criticism usable. A probe should not humiliate staff or damage the system being tested. Above all, senior leaders must signal support and protect honest findings, or the team becomes a decorative office or a source of unwanted friction.

Analysis

This is a boundary-design problem, not simply a hiring problem. Independence without access becomes uninformed commentary; access without independence becomes conformity. The most productive arrangement gives challengers protected channels to authority while keeping them connected to the people who must implement changes. Tone matters for the same reason: tact is not a demand to soften the finding, but a way to keep attention on the evidence rather than the messenger. Still, good communication cannot compensate for leaders who punish unwelcome conclusions.

A game is worthless when the referee scripts the winner

The rules reveal the real test. In the 2002 Millennium Challenge, a costly US military exercise, retired Marine general Paul Van Riper led a simulated opposing force. His team used unconventional tactics and quickly sank 19 virtual US ships. Exercise controllers then restored the ships and restricted further attacks so the planned training events could continue. The final report acknowledged that the opposition’s freedom was eventually constrained until the outcome favored the US side.

A simulation is not a pageant. The exercise produced some useful lessons, but it could not honestly validate the concepts it was designed to test once the rules protected the preferred result. A credible simulation needs realistic constraints, a capable opposing side, and permission for the plan to fail. Otherwise, participants rehearse the institution’s expectations instead of encountering the challenge those expectations may have missed.

Analysis

The episode illustrates how a model’s rules can quietly encode the answer its sponsors hope to find. That does not make every controlled exercise dishonest; simulations must simplify reality to be usable. The key is to distinguish necessary boundaries from outcome protection. Participants should know what the exercise can and cannot establish, and controllers should document interventions that change the contest. The more consequential the decision, the more dangerous it is to present a managed demonstration as independent evidence.

Make dissent structured, specific, and harder to silence

Permission alone is weak protection. People may stay quiet when rank, reputation, or career advancement is at stake, even when leaders claim to welcome disagreement. Red Team University taught practical ways to reduce that pressure, including writing ideas before discussion, gathering anonymous feedback, and preventing any one person from dominating the conversation.

The method can change whose ideas win. During a review of a draft military concept, facilitators collected suggestions anonymously and had participants score them. The strongest proposals came from an Air Force major, while none of the senior participants’ ideas made the top group. The result does not prove that junior staff are generally wiser. It shows how a process can temporarily keep status from deciding which ideas receive attention.

Analysis

Structured participation helps because it alters the conditions under which people contribute, rather than merely asking them to be braver. Anonymity, precommitment, and turn-taking can surface ideas that would otherwise be crowded out by confidence or seniority. But these techniques are not substitutes for a safe working culture. If participants expect retaliation after the meeting, they may still self-censor, or offer only harmless criticism. The goal is not to flatten expertise, but to keep authority from being mistaken for evidence.

Fresh eyes must test assumptions, not arrive with a preloaded answer

Opposition can be biased too. In 1976, outside experts known for hard-line views on the Soviet Union challenged the CIA’s estimates of Soviet power. The exercise, called Team B, lacked clear objectives, became politicized, and was perceived as designed to reach a preferred conclusion. Its controversy damaged trust in alternative analysis for years.

Independence requires relevant expertise. In 1998, the United States destroyed Sudan’s Al Shifa pharmaceutical factory based on weak claims that it was tied to Osama bin Laden and chemical weapons. Relevant specialists had doubts, but their assessment was not sought in time. In contrast, separate teams reviewed the evidence about bin Laden’s Abbottabad compound in 2011, bringing fresh perspectives to a consequential estimate. Red teaming works when it tests a claim, not when it merely argues the opposite.

Analysis

The contrast reveals two distinct dangers: a challenge team can be captured by the institution, or captured by the agenda of its sponsors. Neither is genuine independence. A useful test asks whether the team has the expertise to assess the evidence, can state its uncertainty, and is allowed to reach an inconvenient conclusion in either direction. Assigning someone to disagree is not enough. The design must make honest revision more attractive than performance for a political audience.

Probe the route an adversary would actually take

Visible defenses can be misleading. Vulnerability probes imitate plausible attackers to test buildings, procedures, or computer systems. Government investigators, for example, successfully carried simulated bomb components into airports and federal buildings. Physical access can be gained through inattentive staff or weak visitor procedures, while cyber access may come from reused passwords or a convincing message to an employee.

A real probe can expose the unexpected. A private security team examining a Verizon femtocell, a small device that extends cell-phone coverage, gained deep access and could capture calls, messages, and other phone data. The team notified Verizon and allowed time for a software fix before making the findings public. The lesson is not that every system can be perfectly secured, but that defenses should be tested against realistic human and technical pathways, not just checked against a compliance list.

Analysis

This approach treats security as an adversarial relationship rather than a collection of visible safeguards. A camera, badge reader, or password policy matters only insofar as it changes an attacker’s options. The emphasis on realistic methods also limits theatrical testing: a spectacular stunt may impress an audience while revealing little about ordinary vulnerabilities. There is an ethical boundary, too. Authorization, careful scoping, and responsible disclosure help ensure that a test improves security without creating the breach or panic it claims to prevent.

Run the review early, track the fixes, and stop before paralysis

Timing determines influence. A military review of a major concept document came so late that its recommendations were unlikely to change the finished draft. A red team needs enough time to affect a decision, but repeated challenges can also exhaust staff and leave no room to implement improvements. How often to test depends on how quickly the environment changes and how severe the consequences of failure could be.

Turn findings into work. Assign owners, prioritize corrective steps, set deadlines, and check whether changes actually work. A red team can advise, challenge, and expose; it should not take over the decision. Nor should leaders commission one as a ceremonial stamp of approval. If the organization is unwilling to hear and act on the results, the exercise may create false confidence instead of learning.

Analysis

The practical standard is not maximum scrutiny, but useful scrutiny. An organization needs enough challenge to detect drift and enough stability to respond to what it learns. Tracking remediation closes the loop between diagnosis and performance, while explicit limits prevent red teams from becoming an alternate command structure. This also clarifies accountability: experts can identify risks, but leaders must decide which risks to accept and explain why. A report without an owner is a warning that has been filed, not answered.

Use red teaming to restart stalled strategies, not replace political will

Success can hide a plateau. A global campaign against polio reduced cases by 99 percent, from about 350,000 in 1988 to roughly 3,500 in 2000. By 2009, cases had fallen further, but progress toward eradication had stalled. Many officials assumed the strategy that achieved the early gains simply needed to be applied more forcefully.

A different perspective reopened the debate. After a red-teaming session challenged the campaign’s assumptions, staff at the Gates Foundation pressed harder questions about proposed plans. The process helped unsettle rubber-stamp agreement, but it could not solve the remaining barriers: political instability and resistance to vaccination in some places. Red teaming can reveal when a familiar approach has stopped working. It cannot create the political commitment or local cooperation needed to make a better approach succeed.

Analysis

This case offers a useful corrective to both complacency and tool worship. Early progress can make a strategy feel self-validating, even when the conditions behind its success have changed. A challenge session can reopen inquiry and change what decision-makers notice, but it cannot substitute for resources, trust, or authority on the ground. The broader lesson is to treat a strong track record as evidence, not immunity from review. A method that worked remarkably well may still need revision at its hardest edge.

Analysis

The book’s central contribution is to treat institutional self-criticism as a designed capability rather than a virtue leaders can announce into existence. Its cases show that people inside organizations face predictable pressures: expertise narrows attention, hierarchy shapes what can safely be said, and shared routines make existing arrangements feel natural. Red teams create a temporary counterweight by changing who asks questions, what perspective they adopt, or how a challenge is conducted.

The comparative structure is especially effective. The Al Kibar assessment shows independent review improving confidence while preserving uncertainty about intent. Al Shifa and the FAA aviation-security program show that important doubts can remain unheard or unacted upon. Millennium Challenge shows how a nominal test loses value when its controllers protect the desired outcome. Together, these cases establish that a red team’s value depends less on contrarian flair than on institutional design, access, scope, and response.

The book is also careful to resist turning red teaming into a cure-all. A challenge team can be biased, misused, ignored, or mistaken. The Team B episode demonstrates that ideological opposition is not the same as analytical independence. The cautions about timing, frequency, and decision authority matter because constant challenge can distract or demoralize, while excessive deference makes the process ceremonial.

One limitation is that many cases are vivid institutional narratives rather than controlled comparisons. The benefits are difficult to quantify, and the absence of disaster cannot prove that a red team prevented it. That uncertainty does not invalidate the method, but it argues for evaluating the process through observable measures: whether assumptions were surfaced, findings reached decision-makers, corrective actions had owners, and those actions were verified. The book’s lasting insight is therefore procedural and political: build an honest route for bad news, then make leaders accountable for what they do with it.

Summary in 30 Seconds
Independent challenge can expose assumptions that routine review misses, but it must reach decision-makers without inheriting their biases. Choose a method suited to the risk: rehearse competing moves, probe defenses, or reassess evidence. Credible tests allow the plan to fail. Give findings owners, deadlines, and follow-up checks. At airports in 1996, simulated bombs passed all 44 screening attempts, yet repeated warnings did not ensure lasting fixes.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.74 out of 5
Average of 500+ ratings from Goodreads and Amazon.

Red Team receives mixed reviews, with an average rating of 3.71/5. Readers appreciate its comprehensive coverage of red teaming across various sectors and the practical insights it offers. Many find the case studies informative, though some feel they're overly detailed. The book is praised for its exploration of best practices and pitfalls in red teaming. However, some readers criticize it for being dry, repetitive, and lacking in-depth "how-to" guidance. Overall, it's considered a solid introduction to the concept of red teaming, particularly valuable for those in security, military, or leadership roles.

Your rating:
4.24
314 ratings
Want to read the full book?

Glossary

Red teaming

Structured independent challenge

A structured process for examining an organization, plan, or potential competitor from perspectives that ordinary analysis may miss. It can use simulations, vulnerability probes, or alternative analyses to reveal assumptions, blind spots, and weaknesses. A red team informs decision-makers; it does not replace their authority or guarantee that its findings will be correct.

Simulations

Rehearsals of possible events

Exercises that model how plans may unfold through interactions among actors with differing goals and capabilities. They include military war games, business strategy exercises, and emergency-response tabletops. A useful simulation exposes participants to plausible developments and constraints. Its lessons depend on realistic assumptions and rules that do not secretly protect a preferred outcome.

Vulnerability probes

Tests of defensive weaknesses

Authorized tests in which a team acts as a plausible adversary to determine whether a facility, network, procedure, or organization can be breached or disrupted. Good probes are realistically scoped, based on likely threats, and designed to avoid unnecessary harm. Their purpose is not merely to demonstrate access, but to support practical improvements.

Alternative analysis

Independent review of interpretations

Analysis that differs from an organization’s routine products in its people, process, or conclusions. It challenges assumptions, tests competing explanations, and examines outcomes that conventional analysis may overlook. It can be performed by a separate team or through structured techniques. It should broaden decision-makers’ understanding, not be mistaken for authoritative policy or a guaranteed prediction.

Institutional capture

Adopting the target’s assumptions

The process by which a team meant to challenge an organization becomes shaped by its culture, incentives, routines, or leadership preferences. Captured teams may lose independence, repeat accepted assumptions, or produce findings their sponsors prefer. Red teams therefore need enough access to understand the institution, while retaining sufficient distance to question its prevailing judgments.

Liberating structures

Facilitated methods for wider participation

Semi-structured group methods used to encourage divergent thinking, surface assumptions, and reduce barriers created by hierarchy or habitual discussion patterns. Examples include collecting individual ideas before group discussion and using facilitated rounds so that one person does not dominate. These methods can improve participation, but they do not by themselves ensure that leaders will act on what emerges.

Red Cell

CIA alternative-analysis unit

The CIA’s semi-independent unit for producing unconventional analyses that challenge prevailing assumptions and prompt officials to consider unexpected possibilities. Created after the September 11 attacks, it differs from units focused solely on imitating an adversary. Its products are explicitly not authoritative assessments, and its value lies in offering policymakers a fresh analytical perspective.

FAQ

What's Red Team: How to Succeed By Thinking Like the Enemy about?

  • Focus on Red Teaming: The book delves into red teaming, a method of simulating adversarial perspectives to enhance decision-making and performance across military, intelligence, and corporate sectors.
  • Historical Context: It traces the evolution of red teaming from the Vatican's Devil's Advocate to modern military and intelligence applications, highlighting its role in preventing failures.
  • Practical Applications: Micah Zenko provides case studies and best practices for implementing red teaming, emphasizing its importance in identifying vulnerabilities and challenging conventional wisdom.

Why should I read Red Team: How to Succeed By Thinking Like the Enemy?

  • Enhance Decision-Making: The book offers insights into improving organizational decision-making by incorporating alternative perspectives and critical thinking.
  • Real-World Examples: Zenko uses compelling case studies from various sectors to demonstrate the effectiveness of red teaming.
  • Practical Guidance: Readers receive actionable advice on implementing red teaming, making it a valuable resource for leaders and decision-makers.

What are the key takeaways of Red Team: How to Succeed By Thinking Like the Enemy?

  • Importance of Dissent: Organizations must encourage dissenting opinions to avoid groupthink and blind spots.
  • Best Practices: Zenko outlines six best practices for effective red teaming, including leadership buy-in and maintaining objectivity.
  • Flexibility in Approach: Red teaming should be adaptable and tailored to an organization's specific needs, not a rigid set of rules.

What are the best quotes from Red Team: How to Succeed By Thinking Like the Enemy and what do they mean?

  • “You cannot grade your own homework.”: Highlights the need for external perspectives to identify organizational shortcomings.
  • “The boss must buy in.”: Emphasizes the necessity of leadership support for successful red teaming initiatives.
  • “Red teaming is not only about using a devil’s advocate.”: Suggests red teaming is a strategic tool for significant decisions, not just routine evaluations.

How do red teams function according to Red Team: How to Succeed By Thinking Like the Enemy?

  • Three Core Techniques: Red teams use simulations, vulnerability probes, and alternative analyses to assess strategies.
  • Independent Perspective: They operate independently to provide unbiased assessments and challenge assumptions.
  • Engagement with Stakeholders: Effective red teams engage with stakeholders to ensure findings are relevant and actionable.

What are the six best practices for red teaming mentioned in Red Team: How to Succeed By Thinking Like the Enemy?

  • Leadership Buy-In: Senior leaders' support is crucial for the success of red teaming efforts.
  • Objective and Aware: Red teams should maintain objectivity while understanding the organization's culture.
  • Fearless Skeptics: Team members should be critical thinkers unafraid to challenge the status quo.

How does Red Team: How to Succeed By Thinking Like the Enemy illustrate the failures of organizations without red teaming?

  • Case Studies: Examples like the FAA's red team before 9/11 show ignored vulnerabilities leading to catastrophic outcomes.
  • Cognitive Biases: Discusses how biases prevent leaders from recognizing shortcomings, highlighting the need for external scrutiny.
  • Consequences of Ignoring Findings: Failing to act on red team findings can result in significant risks and failures.

What role does red teaming play in military operations as described in Red Team: How to Succeed By Thinking Like the Enemy?

  • Strategic Assessment: Red teams evaluate military strategies, providing alternative perspectives for better decision-making.
  • Training and Preparedness: They conduct simulations to prepare personnel for real-world scenarios, enhancing readiness.
  • Historical Examples: Details exercises like Millennium Challenge 2002 to illustrate red teaming's importance in understanding adversarial tactics.

How can organizations implement red teaming effectively based on Zenko's advice?

  • Establish Clear Objectives: Define the scope and goals of red teaming efforts to align with strategic priorities.
  • Foster a Culture of Openness: Encourage an environment where dissenting opinions are valued and assumptions are challenged.
  • Regularly Review and Adapt: Continuously evaluate and refine red teaming approaches to stay relevant and effective.

What challenges does red teaming face according to Red Team: How to Succeed By Thinking Like the Enemy?

  • Resistance to Change: Organizations may resist red teaming due to entrenched hierarchies and reluctance to accept criticism.
  • Scope Limitations: Improperly scoped red teams can produce irrelevant findings, diminishing their impact.
  • Misunderstanding of Purpose: Some expect red teams to make decisions rather than inform and challenge existing policies.

What is the definition of red teaming in Red Team: How to Succeed By Thinking Like the Enemy?

  • Structured Process: Red teaming is a structured process to understand interests, intentions, and capabilities through simulations and analyses.
  • Methods Used: Involves simulations, vulnerability probes, and alternative analyses to challenge assumptions.
  • Goal-Oriented: Aims to enhance organizational effectiveness and security by identifying blind spots and vulnerabilities.

How does Red Team: How to Succeed By Thinking Like the Enemy address the future of red teaming?

  • Integration of Technology: Future red teaming may involve more automation and technology for enhanced assessments.
  • Evolving Practices: As threats change, red teaming practices must adapt with new methodologies and tools.
  • Continued Relevance: Red teaming remains critical for organizations navigating complex environments and making informed decisions.

About the Author

Micah Zenko is an accomplished author and researcher specializing in national security, foreign policy, and conflict prevention. He is a Senior Fellow at the Council on Foreign Relations and has held positions at Harvard University's Kennedy School of Government and the Brookings Institution. Zenko has written extensively on international relations, with his work appearing in prestigious publications such as Foreign Policy and The Atlantic. His expertise in strategic planning and risk assessment is evident in his book "Red Team," which draws on his extensive research and interviews with red team practitioners across various fields. Zenko's background in policy analysis and his ability to synthesize complex information make him a respected voice in the field of security studies.

Download PDF

To save this Red Team summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.42 MB     Pages: 20

Download EPUB

To read this Red Team summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.42 MB     Pages: 25
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...