{
  "kind": "briefGuide",
  "slug": "when-switching-friction-is-killing-momentum",
  "title": "When switching friction is killing momentum",
  "summary": "Use a Decision Friction Brief when the product case looks credible, but migration cost, workflow disruption, or replacement risk still feels larger than the upside in the buyer's mind.",
  "canonicalUrl": "https://archive.citrusgate.com/brief/when-switching-friction-is-killing-momentum",
  "markdownUrl": "https://archive.citrusgate.com/brief/when-switching-friction-is-killing-momentum.md",
  "jsonUrl": "https://archive.citrusgate.com/api/public/brief/when-switching-friction-is-killing-momentum.json",
  "publishedAt": "2026-04-09",
  "tags": [
    "switching-friction",
    "migration-risk",
    "buyer-friction",
    "brief-fit"
  ],
  "policy": {
    "canonicalUrl": "https://archive.citrusgate.com/about",
    "markdownUrl": "https://archive.citrusgate.com/about.md",
    "author": {
      "name": "Ivan Golovach",
      "title": "Founder and brief lead",
      "summary": "Ivan Golovach built and operates the CitrusGate workflow, holds the release stop-line on the private memo, and answers fit questions directly. The service is sold on inspectable work, clear boundaries, and one accountable operator."
    },
    "entity": {
      "name": "CitrusGate LLC",
      "summary": "The operating entity behind the site, the Stripe checkout, and the private brief release."
    },
    "editorialBoundary": {
      "summary": "CitrusGate publishes public proof, not raw company notes. The site shows how the diagnosis thinks without exposing the company-specific correction that belongs in private delivery.",
      "bullets": [
        "Public pages show public-safe proof, dated recurrence, and blocker framing.",
        "They do not show raw company notes or the private next move for one team.",
        "Published counts refer to the current public release, not every private company the workflow has touched.",
        "The first commercial product is the fixed-scope Decision Friction Brief."
      ]
    },
    "privacyBoundary": {
      "summary": "If a piece of information only makes sense when the reader knows the exact company, contact, or outreach context, it stays private. CitrusGate does not repurpose client-specific brief detail onto the public site unless it has been fully abstracted and made public-safe.",
      "bullets": [
        "Private data bundles, admin routes, and raw company-level research stay out of the public layer.",
        "Only public-safe artifacts that become clearer after abstraction belong in the machine-readable corpus."
      ]
    },
    "usage": {
      "publicReadOnly": true,
      "searchDiscoveryAllowed": true,
      "trainingAllowed": false,
      "vendorAccess": {
        "googleSearch": true,
        "googleExtended": true,
        "bingSearch": true,
        "openAiSearch": true,
        "openAiUserFetch": true,
        "openAiTraining": false,
        "anthropicSearch": true,
        "anthropicUserFetch": true,
        "anthropicTraining": false,
        "perplexitySearch": true,
        "perplexityUserFetch": true
      },
      "writeActionsAvailable": true,
      "privateResearchExposed": false,
      "publicAskAvailable": true,
      "mcpAvailable": false
    }
  },
  "timestamps": {
    "machineGeneratedAt": "2026-05-02T21:38:17Z",
    "canonicalLastModifiedAt": "2026-04-09",
    "publishedAt": "2026-04-09"
  },
  "body": "# When switching friction is killing momentum\n- Published: 2026-04-09\n- Tags: switching-friction, migration-risk, buyer-friction, brief-fit\n- Canonical: https://archive.citrusgate.com/brief/when-switching-friction-is-killing-momentum\nUse a Decision Friction Brief when the product case looks credible, but migration cost, workflow disruption, or replacement risk still feels larger than the upside in the buyer's mind.\n## Short answer\nA strong product case does not matter if the replacement path still feels too risky. The brief helps when the team needs to know whether switching friction is the real blocker, what sequence belongs first, and which broader change can wait.\n## What this usually means\nTeams often keep selling upside while the buyer is still pricing exposure, disruption, or internal change cost. The result is a deal that sounds interested but never reaches a clean comparison.\n- The buyer likes the category promise, but replacement anxiety keeps returning in different forms.\n- The team is talking about value while the buyer is still trying to picture risk and disruption.\n- Internal responses are getting broader before anyone has narrowed the most believable de-risking step.\n## What teams often misread first\nSwitching friction usually looks like product doubt from the seller side. In reality, the buyer is often still evaluating exposure, sequence, and fallback risk.\n- Feature proof gets treated as the missing piece even when replacement risk is still the real decision.\n- Migration fear is read as generic conservatism instead of as an unsequenced change path.\n- Teams keep expanding the upside story while the first believable low-risk move is still missing.\n## What to check next before you add more proof\nClarify the smallest believable replacement step first. If that step is not credible yet, broader persuasion will not fix the pace of the deal.\n- Name the first migration or replacement step that would reduce exposure fastest.\n- Check whether buyer questions are really about disruption, rollback, or operator-hours rather than product capability.\n- Find out whether the team is forcing the whole migration story before the first credible step exists.\n## Why the brief is the right first move\nThis is a sequencing problem more than a persuasion problem. The brief is useful when the team needs to know what smallest believable move lowers exposure first and what should stop being pushed all at once.\n- You need a bounded diagnosis of the replacement path, not another general migration narrative.\n- You want to know which de-risking step belongs first for one live deal.\n- You want the team to stop forcing the whole migration story before the first credible step is clear.\n## Check these before you react\nIf these show up together, switching friction is probably shaping the pace of the deal already.\n- The team cannot name the smallest believable migration or replacement step that would reduce exposure fastest.\n- Buyer questions keep returning to disruption, change management, or rollback risk rather than feature gaps.\n- The first proposed response is more product proof, not clearer sequencing.\n## Do not use this page as your answer\nA brief is not the first move if the migration sequence is already clear and the only work left is execution.\n- Do not use this if the team already knows the exact rollout path and just needs implementation support.\n- Do not use this if the blocker is mainly proof friction or pricing interpretation instead.\n- Do not use this if there is no real live replacement decision to diagnose.\n## Public proof behind this situation\nThis page is backed by one blocker page, one supporting note, and one specimen brief that shows how replacement risk can outrun product proof if sequence stays fuzzy.\n- Recurring blocker: In this cohort, switching risk eased when the first wedge was narrow. (https://archive.citrusgate.com/themes/switching-friction)\n  - Why it matters here: The blocker page keeps the recurring switching-friction pattern canonical instead of reducing it to a one-off objection.\n- Supporting note: Switching cost kills momentum before product fit (https://archive.citrusgate.com/notes/switching-cost-kills-momentum-before-product-fit)\n  - Why it matters here: The note shows how switching cost can kill momentum before product fit is even judged cleanly.\n- Specimen brief: Fix deployment framing before procurement defines the deal (https://archive.citrusgate.com/example/deployment-framing-before-procurement)\n  - Why it matters here: This specimen brief shows how deployment-path and diligence sequence can decide a deal before a broader value story has any chance to land.\n## Additional trust paths\n- FAQ: https://archive.citrusgate.com/faq\n- About the operator: https://archive.citrusgate.com/about\n## Next step\nIf migration anxiety is outrunning the product case, start with the brief. If you want proof of the diagnosis standard first, use the specimen briefs.\n- Primary action: Read the brief scope (https://archive.citrusgate.com/brief)\n- Secondary action: Read the specimen briefs (https://archive.citrusgate.com/example)",
  "sections": [
    {
      "title": "Short answer",
      "body": "A strong product case does not matter if the replacement path still feels too risky. The brief helps when the team needs to know whether switching friction is the real blocker, what sequence belongs first, and which broader change can wait."
    },
    {
      "title": "What this usually means",
      "body": "Teams often keep selling upside while the buyer is still pricing exposure, disruption, or internal change cost. The result is a deal that sounds interested but never reaches a clean comparison.",
      "bullets": [
        "The buyer likes the category promise, but replacement anxiety keeps returning in different forms.",
        "The team is talking about value while the buyer is still trying to picture risk and disruption.",
        "Internal responses are getting broader before anyone has narrowed the most believable de-risking step."
      ]
    },
    {
      "title": "What teams often misread first",
      "body": "Switching friction usually looks like product doubt from the seller side. In reality, the buyer is often still evaluating exposure, sequence, and fallback risk.",
      "bullets": [
        "Feature proof gets treated as the missing piece even when replacement risk is still the real decision.",
        "Migration fear is read as generic conservatism instead of as an unsequenced change path.",
        "Teams keep expanding the upside story while the first believable low-risk move is still missing."
      ]
    },
    {
      "title": "What to check next before you add more proof",
      "body": "Clarify the smallest believable replacement step first. If that step is not credible yet, broader persuasion will not fix the pace of the deal.",
      "bullets": [
        "Name the first migration or replacement step that would reduce exposure fastest.",
        "Check whether buyer questions are really about disruption, rollback, or operator-hours rather than product capability.",
        "Find out whether the team is forcing the whole migration story before the first credible step exists."
      ]
    },
    {
      "title": "Why the brief is the right first move",
      "body": "This is a sequencing problem more than a persuasion problem. The brief is useful when the team needs to know what smallest believable move lowers exposure first and what should stop being pushed all at once.",
      "bullets": [
        "You need a bounded diagnosis of the replacement path, not another general migration narrative.",
        "You want to know which de-risking step belongs first for one live deal.",
        "You want the team to stop forcing the whole migration story before the first credible step is clear."
      ]
    },
    {
      "title": "Check these before you react",
      "body": "If these show up together, switching friction is probably shaping the pace of the deal already.",
      "bullets": [
        "The team cannot name the smallest believable migration or replacement step that would reduce exposure fastest.",
        "Buyer questions keep returning to disruption, change management, or rollback risk rather than feature gaps.",
        "The first proposed response is more product proof, not clearer sequencing."
      ]
    },
    {
      "title": "Do not use this page as your answer",
      "body": "A brief is not the first move if the migration sequence is already clear and the only work left is execution.",
      "bullets": [
        "Do not use this if the team already knows the exact rollout path and just needs implementation support.",
        "Do not use this if the blocker is mainly proof friction or pricing interpretation instead.",
        "Do not use this if there is no real live replacement decision to diagnose."
      ]
    },
    {
      "title": "Public proof behind this situation",
      "body": "This page is backed by one blocker page, one supporting note, and one specimen brief that shows how replacement risk can outrun product proof if sequence stays fuzzy.",
      "items": [
        {
          "title": "Recurring blocker: In this cohort, switching risk eased when the first wedge was narrow.",
          "body": "The blocker page keeps the recurring switching-friction pattern canonical instead of reducing it to a one-off objection."
        },
        {
          "title": "Supporting note: Switching cost kills momentum before product fit",
          "body": "The note shows how switching cost can kill momentum before product fit is even judged cleanly."
        },
        {
          "title": "Specimen brief: Fix deployment framing before procurement defines the deal",
          "body": "This specimen brief shows how deployment-path and diligence sequence can decide a deal before a broader value story has any chance to land."
        }
      ]
    }
  ],
  "related": {
    "themes": [
      {
        "title": "In this cohort, switching risk eased when the first wedge was narrow.",
        "canonicalUrl": "https://archive.citrusgate.com/themes/switching-friction",
        "markdownUrl": "https://archive.citrusgate.com/themes/switching-friction.md",
        "jsonUrl": "https://archive.citrusgate.com/api/public/themes/switching-friction.json",
        "summary": "In the selected cohort, switching-friction evidence appeared across 254 companies and 256 signals. In selected cases, buyers were more willing to advance when adoption could coexist with current systems before a broader replacement decision."
      }
    ],
    "notes": [
      {
        "title": "Switching cost kills momentum before product fit",
        "canonicalUrl": "https://archive.citrusgate.com/notes/switching-cost-kills-momentum-before-product-fit",
        "markdownUrl": "https://archive.citrusgate.com/notes/switching-cost-kills-momentum-before-product-fit.md",
        "jsonUrl": "https://archive.citrusgate.com/api/public/notes/switching-cost-kills-momentum-before-product-fit.json",
        "summary": "Migration anxiety can overpower a strong product case long before buyers say so directly. In the current 334-company cohort, 56 of 334 companies made it the main blocker, while 254 of 334 showed at least one public signal for it."
      }
    ],
    "examples": [
      {
        "title": "Fix deployment framing before procurement defines the deal",
        "canonicalUrl": "https://archive.citrusgate.com/example/deployment-framing-before-procurement",
        "summary": "A public-source specimen brief built from a developer-facing platform with both managed and self-hosted paths. The core issue was not feature doubt. It was the wrong deployment model being evaluated first."
      }
    ],
    "core": [
      {
        "title": "Decision Friction Brief",
        "canonicalUrl": "https://archive.citrusgate.com/brief",
        "markdownUrl": "https://archive.citrusgate.com/brief.md",
        "summary": "The fixed-scope commercial page for the Decision Friction Brief."
      },
      {
        "title": "Decision Friction Brief FAQ",
        "canonicalUrl": "https://archive.citrusgate.com/faq",
        "markdownUrl": "https://archive.citrusgate.com/faq.md",
        "summary": "Common buyer questions about scope, timing, delivery, and fit."
      },
      {
        "title": "About CitrusGate",
        "canonicalUrl": "https://archive.citrusgate.com/about",
        "markdownUrl": "https://archive.citrusgate.com/about.md",
        "summary": "Who runs CitrusGate, what the brief is for, and where the public boundary sits."
      }
    ]
  }
}