{ "kind": "briefGuide", "slug": "when-to-use-a-decision-friction-brief", "title": "When to use a Decision Friction Brief", "summary": "Use a Decision Friction Brief when one live B2B software deal is slowing, the team can see symptoms but not the primary blocker, and a small private diagnosis is safer than a broader project as the first move.", "canonicalUrl": "https://archive.citrusgate.com/brief/when-to-use-a-decision-friction-brief", "markdownUrl": "https://archive.citrusgate.com/brief/when-to-use-a-decision-friction-brief.md", "jsonUrl": "https://archive.citrusgate.com/api/public/brief/when-to-use-a-decision-friction-brief.json", "publishedAt": "2026-04-09", "tags": [ "brief-fit", "service-selection", "decision-friction", "buyer-guidance" ], "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 to use a Decision Friction Brief\n- Published: 2026-04-09\n- Tags: brief-fit, service-selection, decision-friction, buyer-guidance\n- Canonical: https://archive.citrusgate.com/brief/when-to-use-a-decision-friction-brief\nUse a Decision Friction Brief when one live B2B software deal is slowing, the team can see symptoms but not the primary blocker, and a small private diagnosis is safer than a broader project as the first move.\n## Short answer\nThis is the right first step when you need one bounded diagnosis on one live buying decision. It is not the right first step when the blocker is already obvious, the team only needs execution capacity, or the real need is a broader research project.\n## What the brief is actually for\nThe brief exists to tell one team what is stalling one live buying decision before they change the wrong thing. It is designed for moments when the team can see drag, but cannot yet rank the blocker cleanly enough to react with confidence.\n- A deal or a small cluster of live deals is slowing, but the primary blocker still feels arguable.\n- The team is about to widen the response across pricing, proof, messaging, or rollout without a clean diagnosis first.\n- You want one private memo with one primary blocker, one false move to avoid, and one safer next move.\n## What teams often misread first\nWhen a live deal slows, teams often jump straight to a larger project, a wider rewrite, or a more visible internal sprint. That is usually too early.\n- A broader project gets treated as safer even though the first blocker is still arguable.\n- Teams assume more proof, more pricing work, or more messaging work is automatically more responsible.\n- The first purchase decision gets blurred with the broader strategy question that may belong later.\n## What to check next before you buy anything larger\nThe first useful check is whether one bounded diagnosis would already change the next move. If it would, a broader project is probably premature.\n- Name the one live decision you need clarified before anything else expands.\n- Check whether the team still disagrees on what should change first.\n- Ask whether one private memo with one blocker and one wrong move to avoid would already reduce the current confusion.\n## Why this format is different from a broader project\nThe Decision Friction Brief is intentionally small. It gives a team a bounded private answer in days so they can stop expanding the wrong response first.\n- Fixed scope: one private brief, not an open-ended engagement.\n- Fast answer: delivered in three business days after payment verification.\n- Operator-owned: one named operator reviews and releases the memo directly.\n## Use it when these are true\nThe brief is usually the right first purchase when most of these are true at the same time.\n- You need clarity on a live decision, not a general market narrative.\n- The team still disagrees on what should change first.\n- A broader project would be premature until the live blocker is narrowed.\n## Do not use it for these jobs\nThis is not meant to replace every adjacent service. The goal is diagnosis first, not to impersonate every strategy project.\n- Do not use it as a substitute for full win-loss research when the team needs broad market learning across many deals.\n- Do not use it for ongoing execution, implementation, or change-management work after the diagnosis is already clear.\n- Do not use it if there is no live buying decision to diagnose.\n## How this differs from a broader win-loss project\n### Best used when\n- Decision Friction Brief: One live buying decision is slowing and the team needs a bounded diagnosis first.\n- Broader win-loss project: The company needs broader learning across many losses, many stages, or many segments.\n### Output\n- Decision Friction Brief: One private memo naming the primary blocker, a wrong move to avoid, and the next move that belongs first.\n- Broader win-loss project: A larger body of market or buyer learning that informs a broader strategy.\n### Timing\n- Decision Friction Brief: Fast, fixed-scope answer in three business days.\n- Broader win-loss project: Longer project designed for breadth, not the smallest immediate answer.\n### Risk if chosen too early\n- Decision Friction Brief: Low risk when the live blocker is still unclear and the team needs bounded diagnosis.\n- Broader win-loss project: Higher risk when the team expands scope before it has isolated the first blocker.\n## Public proof behind this situation\nThis page is intentionally broad, but the fit still rests on one blocker page, one note, and one specimen brief so the recommendation stays inspectable rather than abstract.\n- Recurring blocker: In this selected cohort, no-action risk was the primary decision-drift pattern. (https://archive.citrusgate.com/themes/decision-drift)\n - Why it matters here: The blocker page shows one of the most common ways live deals keep drifting while teams argue over the wrong fix.\n- Supporting note: Decision drift stays broad until one stalled decision becomes primary (https://archive.citrusgate.com/notes/decision-drift-looks-like-noise-until-it-stalls-the-deal)\n - Why it matters here: The note keeps one compact public observation legible before you step into the larger blocker library.\n- Specimen brief: Fix the buying path before you widen the eval (https://archive.citrusgate.com/example/buying-path-before-bakeoff)\n - Why it matters here: This specimen brief shows what the private standard looks like when a live decision needs a bounded diagnosis instead of a broader project.\n## Related themes\n- In this cohort, the pricing blocker was often metric legibility. (https://archive.citrusgate.com/themes/pricing-ambiguity)\n- In this cohort, switching risk eased when the first wedge was narrow. (https://archive.citrusgate.com/themes/switching-friction)\n- In this cohort, trust proof often had to answer workflow governance. (https://archive.citrusgate.com/themes/proof-friction)\n## Related notes\n- Pricing ambiguity creates comparison fatigue (https://archive.citrusgate.com/notes/pricing-ambiguity-creates-comparison-fatigue)\n- Switching cost kills momentum before product fit (https://archive.citrusgate.com/notes/switching-cost-kills-momentum-before-product-fit)\n- Trust proof is deciding before product comparison (https://archive.citrusgate.com/notes/trust-proof-is-deciding-before-product-comparison)\n## Additional trust paths\n- FAQ: https://archive.citrusgate.com/faq\n- About the operator: https://archive.citrusgate.com/about\n## Next step\nRead the brief scope if you think the team needs a bounded diagnosis first. Read the specimen briefs if you want to inspect the standard before you buy.\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": "This is the right first step when you need one bounded diagnosis on one live buying decision. It is not the right first step when the blocker is already obvious, the team only needs execution capacity, or the real need is a broader research project." }, { "title": "What the brief is actually for", "body": "The brief exists to tell one team what is stalling one live buying decision before they change the wrong thing. It is designed for moments when the team can see drag, but cannot yet rank the blocker cleanly enough to react with confidence.", "bullets": [ "A deal or a small cluster of live deals is slowing, but the primary blocker still feels arguable.", "The team is about to widen the response across pricing, proof, messaging, or rollout without a clean diagnosis first.", "You want one private memo with one primary blocker, one false move to avoid, and one safer next move." ] }, { "title": "What teams often misread first", "body": "When a live deal slows, teams often jump straight to a larger project, a wider rewrite, or a more visible internal sprint. That is usually too early.", "bullets": [ "A broader project gets treated as safer even though the first blocker is still arguable.", "Teams assume more proof, more pricing work, or more messaging work is automatically more responsible.", "The first purchase decision gets blurred with the broader strategy question that may belong later." ] }, { "title": "What to check next before you buy anything larger", "body": "The first useful check is whether one bounded diagnosis would already change the next move. If it would, a broader project is probably premature.", "bullets": [ "Name the one live decision you need clarified before anything else expands.", "Check whether the team still disagrees on what should change first.", "Ask whether one private memo with one blocker and one wrong move to avoid would already reduce the current confusion." ] }, { "title": "Why this format is different from a broader project", "body": "The Decision Friction Brief is intentionally small. It gives a team a bounded private answer in days so they can stop expanding the wrong response first.", "bullets": [ "Fixed scope: one private brief, not an open-ended engagement.", "Fast answer: delivered in three business days after payment verification.", "Operator-owned: one named operator reviews and releases the memo directly." ] }, { "title": "Use it when these are true", "body": "The brief is usually the right first purchase when most of these are true at the same time.", "bullets": [ "You need clarity on a live decision, not a general market narrative.", "The team still disagrees on what should change first.", "A broader project would be premature until the live blocker is narrowed." ] }, { "title": "Do not use it for these jobs", "body": "This is not meant to replace every adjacent service. The goal is diagnosis first, not to impersonate every strategy project.", "bullets": [ "Do not use it as a substitute for full win-loss research when the team needs broad market learning across many deals.", "Do not use it for ongoing execution, implementation, or change-management work after the diagnosis is already clear.", "Do not use it if there is no live buying decision to diagnose." ] }, { "title": "Public proof behind this situation", "body": "This page is intentionally broad, but the fit still rests on one blocker page, one note, and one specimen brief so the recommendation stays inspectable rather than abstract.", "items": [ { "title": "Recurring blocker: In this selected cohort, no-action risk was the primary decision-drift pattern.", "body": "The blocker page shows one of the most common ways live deals keep drifting while teams argue over the wrong fix." }, { "title": "Supporting note: Decision drift stays broad until one stalled decision becomes primary", "body": "The note keeps one compact public observation legible before you step into the larger blocker library." }, { "title": "Specimen brief: Fix the buying path before you widen the eval", "body": "This specimen brief shows what the private standard looks like when a live decision needs a bounded diagnosis instead of a broader project." } ] }, { "title": "How this differs from a broader win-loss project", "body": "The question is not which tool is better in general. The question is which tool is the safer first move for the decision in front of you.", "items": [ { "title": "Best used when", "body": "Decision Friction Brief: One live buying decision is slowing and the team needs a bounded diagnosis first. Broader win-loss project: The company needs broader learning across many losses, many stages, or many segments." }, { "title": "Output", "body": "Decision Friction Brief: One private memo naming the primary blocker, a wrong move to avoid, and the next move that belongs first. Broader win-loss project: A larger body of market or buyer learning that informs a broader strategy." }, { "title": "Timing", "body": "Decision Friction Brief: Fast, fixed-scope answer in three business days. Broader win-loss project: Longer project designed for breadth, not the smallest immediate answer." }, { "title": "Risk if chosen too early", "body": "Decision Friction Brief: Low risk when the live blocker is still unclear and the team needs bounded diagnosis. Broader win-loss project: Higher risk when the team expands scope before it has isolated the first blocker." } ] } ], "related": { "themes": [ { "title": "In this selected cohort, no-action risk was the primary decision-drift pattern.", "canonicalUrl": "https://archive.citrusgate.com/themes/decision-drift", "markdownUrl": "https://archive.citrusgate.com/themes/decision-drift.md", "jsonUrl": "https://archive.citrusgate.com/api/public/themes/decision-drift.json", "summary": "In the manually reviewed cohort of 334 active companies, 331 profiles carried decision-drift signals. In selected cases, the buyer was not simply comparing vendors; the buyer was weighing whether renewal, tuning, internal build, or waiting was easier to defend than change." }, { "title": "In this cohort, the pricing blocker was often metric legibility.", "canonicalUrl": "https://archive.citrusgate.com/themes/pricing-ambiguity", "markdownUrl": "https://archive.citrusgate.com/themes/pricing-ambiguity.md", "jsonUrl": "https://archive.citrusgate.com/api/public/themes/pricing-ambiguity.json", "summary": "In the selected cohort, pricing-ambiguity evidence appeared across 276 companies and 286 signals. In these selected cases, the blocker was often not the price level itself; it was uncertainty about the metric, forecast, expansion trigger, or enterprise requirement that would define the real cost." }, { "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." }, { "title": "In this cohort, trust proof often had to answer workflow governance.", "canonicalUrl": "https://archive.citrusgate.com/themes/proof-friction", "markdownUrl": "https://archive.citrusgate.com/themes/proof-friction.md", "jsonUrl": "https://archive.citrusgate.com/api/public/themes/proof-friction.json", "summary": "In the selected cohort, trust-artifact evidence appeared across 328 companies and 432 signals. In selected cases, the blocker was not lack of pain; it was unclear permission, data-use alignment, approval ownership, or exception handling." } ], "notes": [ { "title": "Decision drift stays broad until one stalled decision becomes primary", "canonicalUrl": "https://archive.citrusgate.com/notes/decision-drift-looks-like-noise-until-it-stalls-the-deal", "markdownUrl": "https://archive.citrusgate.com/notes/decision-drift-looks-like-noise-until-it-stalls-the-deal.md", "jsonUrl": "https://archive.citrusgate.com/api/public/notes/decision-drift-looks-like-noise-until-it-stalls-the-deal.json", "summary": "Many quiet stalls are really future-state ambiguity problems rather than obvious losses. In the current 334-company cohort, 141 of 334 companies made it the main blocker, while 331 of 334 showed at least one public signal for it." }, { "title": "Pricing ambiguity creates comparison fatigue", "canonicalUrl": "https://archive.citrusgate.com/notes/pricing-ambiguity-creates-comparison-fatigue", "markdownUrl": "https://archive.citrusgate.com/notes/pricing-ambiguity-creates-comparison-fatigue.md", "jsonUrl": "https://archive.citrusgate.com/api/public/notes/pricing-ambiguity-creates-comparison-fatigue.json", "summary": "Pricing interpretation cost is quietly damaging otherwise promising evaluations. In the current 334-company cohort, 23 of 334 companies made it the main blocker, while 276 of 334 showed at least one public signal for it." }, { "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." }, { "title": "Trust proof is deciding before product comparison", "canonicalUrl": "https://archive.citrusgate.com/notes/trust-proof-is-deciding-before-product-comparison", "markdownUrl": "https://archive.citrusgate.com/notes/trust-proof-is-deciding-before-product-comparison.md", "jsonUrl": "https://archive.citrusgate.com/api/public/notes/trust-proof-is-deciding-before-product-comparison.json", "summary": "Trust proof is shaping more early decisions than many teams realize. In the current 334-company cohort, 96 of 334 companies made it the main blocker, while 328 of 334 showed at least one public signal for it." } ], "examples": [ { "title": "Fix the buying path before you widen the eval", "canonicalUrl": "https://archive.citrusgate.com/example/buying-path-before-bakeoff", "summary": "A public-source specimen brief built from an AI infrastructure platform selling into teams that already carry major cloud commitments. The commercial unlock was buying-path design, not broader product positioning." } ], "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." } ] } }