{
  "docId": "019f6b8f-703a-73b2-9ce7-4c20d37b9d2c",
  "docSlug": "jarvis-the-ultimate-guide-to-arr",
  "documentTitle": "The Ultimate Guide To ARR",
  "authorId": "the-ultimate-guide-to-arr",
  "authorName": null,
  "documentKindSlug": "deck",
  "documentKindLabel": "Deck",
  "sourceTypeSlug": "investor_relations",
  "sourceTypeLabel": "Investor relations",
  "presentationDate": null,
  "orientation": null,
  "aspectRatio": null,
  "pageNumber": 63,
  "pageCount": 72,
  "prevPage": 62,
  "nextPage": 64,
  "slideType": "other",
  "function": "illustrate_case",
  "density": "dense",
  "nDataPoints": 0,
  "notes": "The slide uses a narrative structure to explain how a specific technical issue (email throttling) led to broader strategic insights about the signup process.",
  "elementsJson": null,
  "metadataConfidence": 0.9,
  "imagePath": null,
  "slideHref": "/slides/019f6b8f-703a-73b2-9ce7-4c20d37b9d2c/63",
  "deckHref": "/decks/019f6b8f-703a-73b2-9ce7-4c20d37b9d2c",
  "deckJsonHref": "/decks/019f6b8f-703a-73b2-9ce7-4c20d37b9d2c.json",
  "deckAnchorHref": "/decks/019f6b8f-703a-73b2-9ce7-4c20d37b9d2c#slide-63",
  "components": [
    {
      "bbox": {
        "h": 0.15,
        "w": 0.6,
        "x": 0.2,
        "y": 0.11
      },
      "kind": "paragraph",
      "text": "number of new active users was the cause. They broke that down further and investigated all sorts of different cross-cuts. Was it certain geographies? Different demographics? Had they introduced a bug, etc.? The investigation actually found that one of their email providers was throttling confirmation emails.",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "16ec881b-80cf-46ce-95be-9b85a0a651df",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.2,
        "w": 0.6,
        "x": 0.2,
        "y": 0.43
      },
      "kind": "paragraph",
      "text": "However, the real insight came from seeing that confirmation emails were a critical step in the signup process. Previously, that step was taken for granted. But from here, the opportunity to improve actually became quite clear—and it was revealed by something being broken. So, the team started to ask a bunch of different questions that they had never considered previously. How can we make confirmation emails go out faster? How can we make them clearer? Do we even need them in the first place? All of which was in the spirit of being able to grow faster.",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "328c0058-bf9f-4973-8955-00f895cc12be",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.15,
        "w": 0.66,
        "x": 0.17,
        "y": 0.67
      },
      "kind": "paragraph",
      "text": "We love this lesson because it speaks to the importance of setting up a great system. That system is what lets you play great defense. You can play great defense by building a system that gives you clear visibility into your ARR and business processes—consistently and at scale. The question then becomes how can you take that defense and turn it into great offense? What’s the equivalent in your business for confirmation emails, and how can you not just fix the problem but turn it into an opportunity to grow?",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "47cddab5-e0fc-45a3-8dd4-a7338cc292a8",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.15,
        "w": 0.6,
        "x": 0.2,
        "y": 0.27
      },
      "kind": "paragraph",
      "text": "When someone signed up for Facebook, they’d click join, but then they’d have to go back to their inbox to click through a confirmation email to confirm it was actually them. Yahoo was apparently throttling those emails, which was the cause of lower new signups. Ok, that makes sense. They had the systems in place to detect that problem. And the easy answer from there was to work with Yahoo! to prevent any throttling moving forward.",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "daa860ad-a971-451f-be44-72b0d9323e82",
      "frameworkName": null,
      "frameworkSlug": null
    }
  ],
  "metrics": [],
  "tools": [],
  "frameworks": [
    {
      "name": "metaphor-analogy",
      "slug": null,
      "matchId": "ac0af1ef-9d7b-4616-a342-9edd8534f29f",
      "evidence": "Uses the sports metaphor of 'defense' vs 'offense' to describe business operations and growth.",
      "confidence": 0.9
    }
  ],
  "arcBeats": [
    {
      "to": 63,
      "from": 44,
      "beatId": "7976f1fb-7ca9-4a2c-bfd0-864fe8dff526",
      "arcName": "Monroe's Motivated Sequence",
      "arcSlug": "monroes-sequence",
      "beatName": "Satisfaction",
      "beatSlug": "monroes-sequence-satisfaction",
      "evidence": "The document provides a detailed guide to building ARR, acting on ARR, and benchmarking ARR to satisfy the reader's need.",
      "position": 2,
      "confidence": 0.7,
      "parentBeatName": "Turn",
      "parentBeatSlug": "turn"
    }
  ],
  "loops": [
    {
      "to": 72,
      "from": 10,
      "name": "Logic Chain",
      "slug": "01-logic-chain",
      "bestFor": "Skeptical audiences, controversial recommendations, rigorous analysis",
      "matchId": "e8faec0b-9f7e-48c0-9872-9bc2ef4cc4c5",
      "evidence": "The document presents a logical sequence of information, starting with the components of ARR and building up to benchmarking.",
      "position": 0,
      "objective": "To understand the components of ARR and how they relate to each other.",
      "structure": "Premise 1 (Accepted truth) -> Premise 2 (Observed fact) -> Therefore... (Inevitable conclusion)",
      "confidence": 0.6,
      "description": "Build an airtight chain of logic where each premise leads inevitably to the conclusion"
    },
    {
      "to": 63,
      "from": 57,
      "name": "Cost Of Inaction",
      "slug": "27-cost-of-inaction",
      "bestFor": "Urgent budget requests, compliance, risk mitigation",
      "matchId": "ecf51a40-5bf0-4f9d-9194-96e995e005b5",
      "evidence": "The document emphasizes the need for businesses to take action based on ARR metrics.",
      "position": 1,
      "objective": "To highlight the importance of acting on ARR metrics.",
      "structure": "The Status Quo -> The Hidden Costs Accumulating -> The Future State of Inaction -> The Tipping Point",
      "confidence": 0.5,
      "description": "Quantify what happens if the audience does nothing"
    }
  ],
  "imagePathAlt": null,
  "thumbSrc": null,
  "thumbSrcAlt": null,
  "locked": true
}