Skill Tracer
Skills › Knowledge Work Plugins › smb-onboard › gotchas.md

gotchas.md

111 lines · small-business/skills/smb-onboard/reference/gotchas.md at 2574e29

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1# Gotchas
2
3## Gotcha: Skipping the prove-value step when a connection takes too long
4
5**Why it matters:** If the owner connects a tool but Claude moves straight to the interview, the "aha" moment never lands. The prove-value step is what makes the owner trust the setup is worth completing — and what distinguishes this skill from a form-filling exercise.
6

Gotcha: Skipping the prove-value step when a connection takes too long

Why it matters: If the owner connects a tool but Claude moves straight to the interview, the "aha" moment never lands. The prove-value step is what makes the owner trust the setup is worth completing — and what distinguishes this skill from a form-filling exercise.

Raw lines 3 to 6
7### ✗ Bad
8
9> "Great, QuickBooks is connected! Now let me ask you a few questions about your business."
11Skips the recipe entirely. Owner leaves not knowing what they just enabled.

✗ Bad

"Great, QuickBooks is connected! Now let me ask you a few questions about your business."

Skips the recipe entirely. Owner leaves not knowing what they just enabled.

Raw lines 7 to 12
13### ✓ Good
15> "QuickBooks is live. Let me pull your last 30 days of cash flow — takes about 10 seconds."
16> *[runs cash-flow-snapshot, shows results]*
17> "That's what we can do anytime you want a number check. Now, a few questions about your business…"
19The demo runs before the interview, every time, without exception.
21---

✓ Good

"QuickBooks is live. Let me pull your last 30 days of cash flow — takes about 10 seconds." [runs cash-flow-snapshot, shows results] "That's what we can do anytime you want a number check. Now, a few questions about your business…"

The demo runs before the interview, every time, without exception.


Raw lines 13 to 22
23## Gotcha: Dumping all five interview questions at once
25**Why it matters:** Five questions presented together feel like a form, not a conversation. Owners either skim-answer or drop off. Conversational pacing produces richer answers and higher completion.

Gotcha: Dumping all five interview questions at once

Why it matters: Five questions presented together feel like a form, not a conversation. Owners either skim-answer or drop off. Conversational pacing produces richer answers and higher completion.

Raw lines 23 to 26
27### ✗ Bad
29> "To get you set up, I need: (1) What kind of business do you run? (2) How many employees? (3) What are your top headaches? (4) What tools do you use? (5) How often do you want check-ins?"

✗ Bad

"To get you set up, I need: (1) What kind of business do you run? (2) How many employees? (3) What are your top headaches? (4) What tools do you use? (5) How often do you want check-ins?"
Raw lines 27 to 30
31### ✓ Good
33Ask each question, receive the full answer, then ask the next. Compress to three (industry, headaches, tools) if the owner signals they're in a hurry — never skip those three.
35---

✓ Good

Ask each question, receive the full answer, then ask the next. Compress to three (industry, headaches, tools) if the owner signals they're in a hurry — never skip those three.


Raw lines 31 to 36
37## Gotcha: Writing context without showing the profile first
39**Why it matters:** Silent writes feel intrusive and remove the owner's chance to correct misheard answers. Showing the draft profile is also a natural confirmation that Claude understood correctly — it often surfaces a correction the owner wouldn't have volunteered.

Gotcha: Writing context without showing the profile first

Why it matters: Silent writes feel intrusive and remove the owner's chance to correct misheard answers. Showing the draft profile is also a natural confirmation that Claude understood correctly — it often surfaces a correction the owner wouldn't have volunteered.

Raw lines 37 to 40
41### ✗ Bad
43> "Got it, I've saved your business profile!"
45No preview, no approval — owner doesn't know what was written.

✗ Bad

"Got it, I've saved your business profile!"

No preview, no approval — owner doesn't know what was written.

Raw lines 41 to 46
47### ✓ Good
49> "Here's what I'm about to save as your business profile — let me know if anything needs fixing:"
51> ```
52> Business: Lakewood Hardware — retail hardware store
53> Size: 4 people (including owner)
54> Top headaches: cash flow gaps · slow-paying contractors · scheduling part-timers
55> Connected tools: QuickBooks, Gmail
56> Country: US
57> Currency: USD
58> Financial year end: 31 December
59> Weekly cadence: weekly check-in every Monday
60> Onboarded: 2026-04-23
61> ```
63> "Look right? I'll save it once you confirm."
65Show the block, wait for approval, then write.
67---

✓ Good

"Here's what I'm about to save as your business profile — let me know if anything needs fixing:" `` Business: Lakewood Hardware — retail hardware store Size: 4 people (including owner) Top headaches: cash flow gaps · slow-paying contractors · scheduling part-timers Connected tools: QuickBooks, Gmail Country: US Currency: USD Financial year end: 31 December Weekly cadence: weekly check-in every Monday Onboarded: 2026-04-23 `` "Look right? I'll save it once you confirm."

Show the block, wait for approval, then write.


Raw lines 47 to 68
Involves a person wait for approval :65
69## Gotcha: Pitching the platform instead of the capability
71**Why it matters:** Owners already know what HubSpot, QuickBooks, Gmail, and Calendar do. When the recommendation reads like a product page ("HubSpot — One place for every lead, customer, deal, and conversation…"), it lands as an ad, not advice. The owner tunes out exactly when we need their attention.

Gotcha: Pitching the platform instead of the capability

Why it matters: Owners already know what HubSpot, QuickBooks, Gmail, and Calendar do. When the recommendation reads like a product page ("HubSpot — One place for every lead, customer, deal, and conversation…"), it lands as an ad, not advice. The owner tunes out exactly when we need their attention.

Raw lines 69 to 72
73### ✗ Bad
75> "1. HubSpot (CRM) — One place for every lead, customer, deal, and conversation. Once it's in, I can prioritize who to call today, draft follow-ups, log notes from your inbox, and spot deals going stale.
77> 2. Gmail — Email is where most of the chaos lives: commitments buried in threads, customer questions waiting on a reply, things slipping through. Connecting your inbox lets me surface what actually needs an answer…"
79Reads like marketing for HubSpot and Gmail. The owner is being sold to.

✗ Bad

"1. HubSpot (CRM) — One place for every lead, customer, deal, and conversation. Once it's in, I can prioritize who to call today, draft follow-ups, log notes from your inbox, and spot deals going stale. 2. Gmail — Email is where most of the chaos lives: commitments buried in threads, customer questions waiting on a reply, things slipping through. Connecting your inbox lets me surface what actually needs an answer…"

Reads like marketing for HubSpot and Gmail. The owner is being sold to.

Raw lines 73 to 80
81### ✓ Good
83> "For customer follow-up, the two pieces I'd want are a CRM and your inbox.
85> What do you use for a CRM today?"
87> *(Owner: "Pipedrive.")*
89> "Got it — we don't have a Pipedrive connector yet. Two ways to go: I can connect Pipedrive through Zapier, which takes about ten minutes of setup and then lead scoring and drafted follow-ups work from inside it. Or you can export your leads as a CSV whenever you want a call list, and I'll work from that. Which do you prefer?"
91States the function, asks what the owner uses without naming a vendor, offers the Zapier connection and the fallback with the trade-off in one line each, and leaves the decision with the owner. It never suggests switching to a CRM we happen to support. If the owner asks "which CRM should I get?" — that's an explicit invitation; describe what each connector in the category unlocks, alphabetically and in the same number of words, and let them choose.
93---

✓ Good

"For customer follow-up, the two pieces I'd want are a CRM and your inbox. What do you use for a CRM today?" (Owner: "Pipedrive.") "Got it — we don't have a Pipedrive connector yet. Two ways to go: I can connect Pipedrive through Zapier, which takes about ten minutes of setup and then lead scoring and drafted follow-ups work from inside it. Or you can export your leads as a CSV whenever you want a call list, and I'll work from that. Which do you prefer?"

States the function, asks what the owner uses without naming a vendor, offers the Zapier connection and the fallback with the trade-off in one line each, and leaves the decision with the owner. It never suggests switching to a CRM we happen to support. If the owner asks "which CRM should I get?" — that's an explicit invitation; describe what each connector in the category unlocks, alphabetically and in the same number of words, and let them choose.


Raw lines 81 to 94
95## Gotcha: Recommending a vendor because it is the one we have
97**Why it matters:** The plugin is neutral. An owner on Xero told to "connect QuickBooks first" hears that their tool is second-class, and an owner with no bookkeeping tool told to get a specific one hears an ad. Both are wrong. The rule is `../../../shared/connector-neutrality.md`.

Gotcha: Recommending a vendor because it is the one we have

Why it matters: The plugin is neutral. An owner on Xero told to "connect QuickBooks first" hears that their tool is second-class, and an owner with no bookkeeping tool told to get a specific one hears an ad. Both are wrong. The rule is ../../../shared/connector-neutrality.md.

Raw lines 95 to 98
99### ✗ Bad
101> "Let's connect QuickBooks first — that lets me pull your cash position anytime."

✗ Bad

"Let's connect QuickBooks first — that lets me pull your cash position anytime."
Raw lines 99 to 102
103### ✓ Good
105> "Let's start with your bookkeeping — what do you use?"
107> *(Owner: "Xero.")*
109> "Xero it is. Here's how to authorize the connection…"
111Ask the category, connect what they name. If they have nothing in the category, say what the zero-connector path gives them and name the category — "once you have a bookkeeping tool connected, this gets deeper" — not a product.

✓ Good

"Let's start with your bookkeeping — what do you use?" (Owner: "Xero.") "Xero it is. Here's how to authorize the connection…"

Ask the category, connect what they name. If they have nothing in the category, say what the zero-connector path gives them and name the category — "once you have a bookkeeping tool connected, this gets deeper" — not a product.

Raw lines 103 to 111