Back to Details

smb-onboard

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

SMB Onboard

中小企业（SMB）入门指南

Quick start

快速入门

Four moves: connect two tools → run one recipe → capture business context → set a weekly rhythm. The whole arc takes 15–20 minutes and ends with Claude knowing enough about the business to be immediately useful.
User: "get me started"
→ Assess what's already connected; pick the best 2 tools to connect first
→ Guide connection of each tool (one at a time)
→ Run one recipe against live data to prove value
→ Ask 5 business questions one at a time; store answers to persistent memory
→ "Each Monday, say 'weekly check-in' — I'll pull your numbers and flag anything urgent."
四个步骤：连接两个工具 → 运行一个流程（recipe） → 捕获业务上下文 → 设定每周节奏。整个流程耗时15-20分钟，结束后Claude将充分了解企业情况，可立即提供有效帮助。
User: "get me started"
→ Assess what's already connected; pick the best 2 tools to connect first
→ Guide connection of each tool (one at a time)
→ Run one recipe against live data to prove value
→ Ask 5 business questions one at a time; store answers to persistent memory
→ "Each Monday, say 'weekly check-in' — I'll pull your numbers and flag anything urgent."

Tone for connectors

工具连接的沟通语气

Whenever a connector comes up — recommending one, naming what to try next, or clarifying mid-flow — describe what Claude will be able to do once it's connected, not what the platform itself is or sells. Owners already know what HubSpot, QuickBooks, Gmail, and Calendar do; they don't need a product pitch from us.
  • Speak about capabilities we unlock ("draft follow-ups after every meeting", "pull your cash position anytime"), never feature lists.
  • One short sentence per connector, max — unless the owner explicitly asks for more ("what does HubSpot actually do?"), in which case answer that directly.
  • This rule applies to every step below.
每当提及工具连接时——推荐工具、说明下一步尝试方向，或是在流程中进行澄清——都要描述连接完成后Claude能实现的功能，而非平台本身的定位或销售卖点。企业主已经了解HubSpot、QuickBooks、Gmail和Calendar的用途，不需要我们进行产品推销。
  • 聚焦我们能解锁的能力（如“每次会议后自动草拟跟进邮件”、“随时查看现金流状况”），绝不要罗列功能清单。
  • 每个工具的描述最多用一句话——除非企业主明确询问更多信息（如“HubSpot到底能做什么？”），此时再直接作答。
  • 此规则适用于以下所有步骤。

Workflow

工作流程

  1. Welcome and assess. Greet the owner briefly. Check which connectors are already active. If a 
    ## Business context
    block already exists in the owner's CLAUDE.md or memory, read it first — then skip to the return-session path: show the existing profile, ask what's changed, update only the fields that changed. Do not re-interview from scratch.
  2. Pick two functions, then check what the owner uses. Ask: "What are your biggest day-to-day headaches — money, customers, scheduling, or getting organized?" Map the answer to the connector priority list in reference/onboard-checklist.md.
    Name the two functions we want (e.g. "a place to track customers and deals" and "your inbox") — not the platform features. One short sentence each, max. Then ask whether the owner uses a supported tool for each.
    For each function, branch:
    • Owner uses a supported connector (e.g. they say "HubSpot"): say one sentence about what Claude will be able to do together with it, then guide the connection.
    • Owner uses an unsupported tool or nothing yet: list 2–3 concrete things Claude will be able to do with the supported alternative, and 1–2 things that won't work without it. Then let the owner decide whether to switch or add it. Do not push.
    Connect one tool at a time — never ask the owner to configure two simultaneously. See reference/gotchas.md for the failure pattern this replaces.
  3. Run one recipe to prove value. Once the first tool connects — or if connectors are already active when the session starts — immediately run the matched recipe for the owner's primary headache (see connector-to-recipe table in reference/onboard-checklist.md). Narrate what Claude is doing and why — this is the "aha" moment. Do not skip it to get to the interview faster. For a worked example of the full arc, see reference/examples/happy-path.md.
  4. Interview the owner. Ask the five questions from reference/onboard-checklist.md, one at a time, conversationally. Wait for the full answer before moving to the next. If the owner seems pressed for time, compress to three: industry, headaches, tools — but never fewer.
  5. Store context. Show the owner the full profile before writing. Wait for explicit approval. Write the block to the Cowork session memory directory under the heading 
    ## Business context
    using the exact format in reference/onboard-checklist.md. If a memory file already exists, update only the 
    ## Business context
    section — do not touch other content. Confirm: "Saved. Every skill from here will know your business."
  6. Set the weekly cadence. Propose: "Each Monday, just say 'weekly check-in' and I'll pull a snapshot of your numbers, flag anything urgent, and remind you what's due." If they prefer a different phrase or day, store it in the profile. If tools are connected, name one skill the owner can try right now. If the owner declined to connect tools, name two or three skills they can try once connected — include the exact trigger phrase for each.
  1. 欢迎与评估。向企业主简要问候。检查已激活的工具连接情况。如果企业主的CLAUDE.md或内存中已存在
    ## Business context
    板块，先读取该内容——然后跳转到返回会话路径：展示现有资料，询问是否有变化，仅更新有变动的字段。不要从头重新进行访谈。
  2. 选择两项核心功能，确认企业主的使用工具。询问：“你日常工作中最大的痛点是什么——资金管理、客户维护、日程安排，还是事务统筹？” 根据reference/onboard-checklist.md中的工具连接优先级列表，将答案对应到相应工具。
    说明我们需要的两项功能（如“客户与交易追踪工具”和“收件箱”）——而非平台特性。每项描述最多用一句话。然后询问企业主是否使用支持的工具来实现这些功能。
    针对每项功能，分情况处理：
    • 企业主使用支持的工具（如他们提到“HubSpot”）：用一句话说明Claude与该工具结合后能实现的功能，然后引导完成连接。
    • 企业主使用不支持的工具或尚未使用任何工具：列出2-3项Claude与支持工具结合后能实现的具体功能，以及1-2项没有该工具则无法实现的功能。然后让企业主决定是否切换或添加该工具，不要强行推荐。
    一次仅连接一个工具——绝不要让企业主同时配置两个工具。可参考reference/gotchas.md了解此做法避免的错误模式。
  3. 运行一个流程以证明价值。完成第一个工具连接后——或是会话开始时已存在活跃的工具连接——立即针对企业主的核心痛点运行匹配的流程（详见reference/onboard-checklist.md中的工具-流程对应表）。讲解Claude正在执行的操作及原因——这是让用户“恍然大悟”的时刻。不要为了加快访谈进度而跳过此步骤。完整流程的示例可参考reference/examples/happy-path.md。
  4. 访谈企业主。逐个询问reference/onboard-checklist.md中的五个问题，保持对话式语气。等待完整回答后再进行下一个问题。如果企业主时间紧张，可精简为三个问题：行业、痛点、使用工具——但不能再少。
  5. 存储上下文信息。在写入前向企业主展示完整的资料草稿。等待明确的批准后，按照reference/onboard-checklist.md中的精确格式，将该板块写入Cowork会话内存目录，标题为
    ## Business context
    。如果内存文件已存在，仅更新
    ## Business context
    部分——不要修改其他内容。确认告知：“已保存。此后所有功能都将了解你的业务情况。”
  6. 设定每周跟进节奏。提议：“每周一，只需说‘weekly check-in’，我就会为你提取数据快照，标记紧急事项，并提醒待办任务。” 如果他们偏好不同的表述或日期，将其存入资料。如果已连接工具，告知企业主当前可尝试的一项功能。如果企业主拒绝连接工具，告知他们连接后可尝试的2-3项功能——包括每项功能的触发语。

Approval gates

审批要求

  • Show context before writing. Display the full owner profile draft before storing it. Wait for explicit approval.
  • Never overwrite existing context silently. If a 
    ## Business context
    block already exists, show current vs. proposed before writing any changes.
  • Never connect a tool on the owner's behalf. Guide; do not act. Connector auth is always owner-initiated.
  • 写入前展示上下文。在存储前先展示完整的企业主资料草稿。等待明确的批准。
  • 绝不静默覆盖现有上下文。如果已存在
    ## Business context
    板块，在写入任何更改前先展示当前内容与拟更新内容的对比。
  • 绝不代企业主连接工具。仅提供引导，不要直接操作。工具授权始终由企业主自行发起。

Reference

参考资料

  • reference/onboard-checklist.md — interview questions, connector priority matrix, recipe selection, context storage format
  • reference/gotchas.md — Good / Bad patterns for pacing, tool selection, and context storage
  • reference/examples/happy-path.md — worked example: retail shop owner, first session end-to-end
  • reference/onboard-checklist.md —— 访谈问题、工具连接优先级矩阵、流程选择、上下文存储格式
  • reference/gotchas.md —— 节奏把控、工具选择、上下文存储的正确/错误模式
  • reference/examples/happy-path.md —— 完整示例：零售店店主的首次会话全流程