waterfall-blueprint

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Waterfall Blueprint Skill

Waterfall Blueprint Skill

When to Use

适用场景

  • Building contact/company enrichment workflows across multiple providers.
  • Updating fallback rules after provider outages or cost shifts.
  • Documenting waterfall logic for RevOps + engineering handoffs.
  • 构建跨多个服务商的联系人/企业数据增强工作流。
  • 在服务商故障或成本变动后更新降级规则。
  • 为RevOps与工程团队的交接记录瀑布流逻辑。

Framework

框架

  1. Goal & Constraints – define enrichment type, data requirements, credit ceiling, SLA.
  2. Provider Catalog – list eligible providers with success %, latency, compliance notes.
  3. Routing Logic – determine sequence, branching, and retry intervals.
  4. Safeguards – set throttles, dedupe checks, and exception triggers.
  5. Versioning – log changes, approvals, and effective dates.
  1. 目标与约束 – 定义数据增强类型、数据要求、额度上限、服务水平协议(SLA)。
  2. 服务商目录 – 列出符合条件的服务商,包含成功率、延迟、合规说明。
  3. 路由逻辑 – 确定序列、分支和重试间隔。
  4. 保障措施 – 设置限流、重复数据检查和异常触发机制。
  5. 版本管理 – 记录变更、审批信息和生效日期。

Templates

模板

  • Waterfall diagram (sequence, inputs, outputs, fallback paths).
  • Routing table (provider, criteria, cost, notes).
  • Change log with owners + rationale.
  • 瀑布流图(序列、输入、输出、降级路径)。
  • 路由表(服务商、判定条件、成本、备注)。
  • 包含负责人及变更理由的变更日志。

Tips

技巧

  • Keep sequences short for real-time use cases; reserve long chains for batch mode.
  • Use A/B tests to validate new providers before full rollout.
  • Pair with
    provider-scorecard
    to continuously optimize routing.

  • 实时场景保持序列简短;批量模式可使用长链路。
  • 在全面推广前使用A/B测试验证新服务商。
  • 搭配
    provider-scorecard
    持续优化路由策略。