Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问许可证需确认审计通过

b2b-saas-workflow-strategyB2B SaaS 工作流程策略

Agent Skill

b2b-saas-workflow-strategy 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

315

周安装

13

GitHub Stars

23

下载量

103
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:b2b-saas-workflow-strategy(B2B SaaS 工作流程策略)
来源仓库:https://github.com/samarv/shanon
仓库路径:skills/b2b-saas-workflow-strategy
安装命令:
npx skills add https://github.com/samarv/shanon --skill b2b-saas-workflow-strategy
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/samarv/shanon --skill b2b-saas-workflow-strategy

简介

B2B SaaS Workflow Strategy 通过二维矩阵预测高增长产品路径,识别独角兽诞生区。

  • 适用于评估产品是否处于‘日常习惯’象限(高频+全员使用),决定资源投入优先级。
  • 框架基于 Oji Udezue 模型,横轴为用户广度,纵轴为执行频率,划分四个战略象限。
  • 输出包含当前定位诊断、迁移路径建议与对应组织能力建设要点。
  • 需企业提供详细工作流程描述,否则难以准确映射至战略坐标系。

SKILL.md

This framework, developed by Oji Udezue, provides a predictive model for B2B SaaS success by mapping workflows across two dimensions to identify where "unicorns" are born and how to navigate toward high-growth territory.

The Strategic Quadrant

Map your product's core workflow based on two axes:

  1. Breadth (Who does it?): Does the workflow apply to a single department (Niche) or every department in a company (Everyone)?
  2. Frequency (How often?): Is the workflow executed daily/multiple times a week (High) or once a month/quarter (Low)?

The Four Quadrants

  • High Frequency / Everyone: The "Daily Habit" tools (Email, Slack, Calendaring, Notion). This is the most profitable but hardest to enter as it is dominated by incumbents like Microsoft and Google.
  • High Frequency / Niche (High-Ni): The "Sweet Spot" for B2B SaaS. Specialized tools used daily by specific roles (Jira for developers, Salesforce for sales, HubSpot for marketers). These frequently become billion-dollar companies.
  • Low Frequency / Everyone: "Necessary Evils" (Expense reporting, Form building, HR portals). Users must use them, but they don't live in them.
  • Low Frequency / Niche: "Administrative Tasks" (FP&A planning tools, specialized compliance audits). These are often the hardest to scale without moving into another quadrant.

The "3X Zone of Benefit" Rule

To successfully displace a status quo or competitor in any quadrant, your solution cannot just be "better." It must reach the Zone of Benefit:

  • The 3X Threshold: The solution must be at least 3x faster, cheaper, or more productive than the current workflow for a user to notice and care.
  • Workflow Compression: Draw the current "before" workflow as a horizontal line and the "after" workflow using your product. If the line isn't 2-3x shorter, it is not a "sharp" enough problem.
  • The "Whites of the Eyes" Test: When describing the workflow compression to a target customer, look for dilated pupils or an immediate "When can I pay?" response. A simple "that’s cool" is a failure signal.

Execution Steps

1. Identify Your Current Quadrant

Analyze your product's primary use case. If you are in a "Low Frequency" or "Niche" quadrant, identify the "ceiling" of your current market.

2. Move Toward "High-Ni" or "Everyone"

Strategic growth involves navigating between quadrants:

  • From Low Frequency to High Frequency: Find a specific sub-segment of your users who view your tool as mission-critical. For example, moving from a general survey tool (Low Frequency Everyone) to a lead-gen tool for marketers (High Frequency Niche).
  • From Niche to Everyone: Use a wedge in one department to expand horizontally. (e.g., Atlassian moving from Jira for devs to Confluence for all departments).

3. Validate the ICP (Ideal Customer Profile)

Your best ICPs are the people whose workflow you compress the most.

  • Calendly example: Don't target "anyone who has meetings." Target recruiters and salespeople whose lifeblood is external scheduling.
  • Typeform example: Target marketers who need "human" customer-facing interactions that reflect their brand.

Examples

Example 1: Strategic Pivot

  • Context: A company makes a form-building tool used occasionally by various employees (Low Frequency Everyone).
  • Application: To increase growth, they pivot to focus on "Interactive Quizzes for eCommerce Marketers."
  • Result: They move into the High Frequency Niche (High-Ni) quadrant, as marketers now use the tool daily to drive their core revenue-generating workflow.

Example 2: Market Evaluation

  • Context: A founder is pitching a new "Internal Employee Feedback" tool.
  • Input: Employees give feedback once a quarter (Low Frequency Everyone).
  • Application: The founder applies the 3X rule. They realize that unless they can make the feedback loop 3x more impactful or faster than the current "Email + Spreadsheet" method, users will stay with the status quo because the frequency is too low to justify learning a new tool.

Common Pitfalls

  • Solving a "Sharp Idea" instead of a "Sharp Problem": A sharp idea is clever; a sharp problem is a pain point that steals time, money, and focus. If the customer doesn't feel the pain daily, they won't pay for the solution.
  • Underestimating the "Everyone" Quadrant: Trying to build a new email or chat app without massive resources. These are "Everyday" tools; to win, you must be exponentially better because the switching cost is highest here.
  • Synthetic Virality vs. Real Value: Adding "Invite your friends" buttons to a product that doesn't solve a sharp problem. Oji notes that if the product sucks, synthetic virality just helps it fail faster. Build a 3X workflow first; virality is "customer-augmented marketing" that follows value.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.24%
按下载量换算35

Claude

28.28%
按下载量换算29

Cursor

18.59%
按下载量换算19

Gemini CLI

9.07%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills