{
  "docId": "019dd923-5f69-752d-a9b7-6d2c4b70ae04",
  "docSlug": "Q47LFqjHFbOgTsaiAp6n",
  "documentTitle": "This serial founder thinks pitch decks are passé. Here's what his startup used instead to raise $45 million in new funding.",
  "authorId": "Pitchdecks",
  "authorName": "Rippling",
  "documentKindSlug": "pitchdeck",
  "documentKindLabel": "Pitch deck",
  "sourceTypeSlug": "strategy_consulting",
  "sourceTypeLabel": "Strategy consulting",
  "presentationDate": null,
  "orientation": "portrait",
  "aspectRatio": 0.773,
  "pageNumber": 6,
  "pageCount": 11,
  "prevPage": 5,
  "nextPage": 7,
  "slideType": "product_demo",
  "function": "present_solution",
  "density": "overcrowded",
  "nDataPoints": 0,
  "notes": "This slide uses a narrative format to explain the 'identity' concept in the context of IT/HR integration.",
  "elementsJson": [
    "paragraph",
    "screenshot"
  ],
  "metadataConfidence": 0.95,
  "imagePath": null,
  "slideHref": "/slides/019dd923-5f69-752d-a9b7-6d2c4b70ae04/6",
  "deckHref": "/decks/019dd923-5f69-752d-a9b7-6d2c4b70ae04",
  "deckJsonHref": "/decks/019dd923-5f69-752d-a9b7-6d2c4b70ae04.json",
  "deckAnchorHref": "/decks/019dd923-5f69-752d-a9b7-6d2c4b70ae04#slide-6",
  "components": [
    {
      "bbox": null,
      "kind": "callout",
      "text": "If you could speak to your IT systems in terms of HR concepts like someone’s department, or role, or work location, you could just add that department to the email list.",
      "attrs": null,
      "subkind": null,
      "toolName": "Visual emphasis",
      "toolSlug": "visual-emphasis",
      "confidence": null,
      "componentId": "019dd952-a28d-7358-81d7-538ed7d3f417",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.16,
        "w": 0.74,
        "x": 0.117,
        "y": 0.51
      },
      "kind": "image",
      "text": "Rippling UI showing email list configuration with HR attributes",
      "attrs": null,
      "subkind": "screenshot",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "c5a3e783-97bd-4022-afcc-ad64f04880f7",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.08,
        "w": 0.36,
        "x": 0.117,
        "y": 0.31
      },
      "kind": "paragraph",
      "text": "If you could speak to your IT systems in terms of HR concepts like someone’s department, or role, or work location, you could just add that department to the email list. And this, in turn, would dramatically simplify the administration of those systems.",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "3dae5e1c-3c2d-4efb-ad44-cdd30101d1a3",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.06,
        "w": 0.36,
        "x": 0.117,
        "y": 0.07
      },
      "kind": "paragraph",
      "text": "back to the original meaning of the word “identity” — would be inseparable from information about each employee’s role, department, and function within a company. In other words, a company’s HR data.",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "a3f007af-2520-4627-9b90-024ec5cc62d5",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.15,
        "w": 0.36,
        "x": 0.117,
        "y": 0.145
      },
      "kind": "paragraph",
      "text": "One small example of this: In many companies, IT is responsible for maintaining company email lists. A hypothetical company, Acme Co, might have 56 people on the email list ‘engineering@acme.com.’ Current IT systems will all treat the 56 people on the list as “users,” without understanding anything about their underlying role within the business. But these aren’t 56 random individuals! They’re engineers, in the engineering department.",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "b126a4f2-4f38-4082-bafb-0bfaa49644e6",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.08,
        "w": 0.36,
        "x": 0.117,
        "y": 0.405
      },
      "kind": "paragraph",
      "text": "One of my favorite parts of a Rippling demo is when I show prospects how you can add not only individuals, but also HR concepts like the “Engineering Department,” or a particular work location, or all managers in the company, to an email list in Rippling:",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "bb7897eb-9d7f-4afa-9ef5-ec53104aec46",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.12,
        "w": 0.36,
        "x": 0.5,
        "y": 0.19
      },
      "kind": "paragraph",
      "text": "And, taking that one step further: When you hire someone in Rippling and you tell us this person is in the engineering department, that changes everything about how Rippling sets them up in your systems: It changes what systems they’ll have access to — AWS and GitHub perhaps, but not Salesforce. It changes what email lists they are subscribed to. It changes what software is installed on their computer.",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "de8aeb94-9761-4900-8b58-4d4f49ccaaf1",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.08,
        "w": 0.36,
        "x": 0.5,
        "y": 0.34
      },
      "kind": "paragraph",
      "text": "And when someone’s role within an organization changes, Rippling isn’t just changing payroll and HR systems — we’re reconfiguring the systems they have access to, the email lists they are subscribed to, and the software and level of access they have on their work computer.",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "e03b8bcc-b73a-44c7-a1cf-25c009695222",
      "frameworkName": null,
      "frameworkSlug": null
    },
    {
      "bbox": {
        "h": 0.11,
        "w": 0.36,
        "x": 0.5,
        "y": 0.07
      },
      "kind": "paragraph",
      "text": "The neat thing about this is that Rippling isn’t just going back and adding all of the individuals in those buckets to that email list in GSuite or Office365. Rippling will also maintain the fidelity of that data going forward — so that the next time you hire an engineer, or the next time someone gets promoted to be a manager, they’re going to be added to that email list.",
      "attrs": null,
      "subkind": "paragraph",
      "toolName": null,
      "toolSlug": null,
      "confidence": null,
      "componentId": "f5219d87-2530-426a-b754-341707f69602",
      "frameworkName": null,
      "frameworkSlug": null
    }
  ],
  "metrics": [],
  "tools": [
    {
      "name": "Metaphor & Analogy",
      "slug": "metaphor-analogy",
      "agent": "Storyteller",
      "layer": "slide",
      "matchId": "ff005d4f-3a50-4e26-b594-dd03c6cc5f63",
      "evidence": "back to the original meaning of the word “identity” — would be inseparable from information about each employee’s role, department, and function within a company. In other words, a company’s HR data.",
      "confidence": 0.8
    }
  ],
  "frameworks": [],
  "arcBeats": [
    {
      "to": 6,
      "from": 5,
      "beatId": "f836cbd6-28fe-4ee0-b082-9d7ce2a73836",
      "arcName": "The Sequoia Pitch",
      "arcSlug": "sequoia-pitch",
      "beatName": "Product",
      "beatSlug": "sequoia-pitch-product",
      "evidence": "Slides 5 and 6 demonstrate the product",
      "position": 1,
      "confidence": 0.7,
      "parentBeatName": "Evidence",
      "parentBeatSlug": "evidence"
    }
  ],
  "loops": [
    {
      "to": 11,
      "from": 1,
      "name": "Quick Win Big Bet",
      "slug": "47-quick-win-big-bet",
      "bestFor": "Transformation planning, 100-day plans, resource allocation",
      "matchId": "734f52d8-53e7-4cf0-ac00-a7170275fc4f",
      "evidence": "The document presents a clear and innovative approach",
      "position": 1,
      "objective": "Present a compelling investment opportunity",
      "structure": "The Full List -> Quick Wins (Low effort, High impact) -> Big Bets (High effort, High impact) -> Sequenced Roadmap",
      "confidence": 0.6,
      "description": "Separate initiatives into immediate wins and longer-term strategic bets"
    }
  ],
  "imagePathAlt": null,
  "thumbSrc": null,
  "thumbSrcAlt": null,
  "locked": true
}