Smb Onboard

# SMB Onboard

## 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 the interview 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." ```

## Workflow

1. **Welcome and assess.** Greet the owner briefly, then follow this decision order exactly — same inputs, same path, every time: 1. Check memory for a `## Business context` block **first**. If it exists, take the return-session path: show the existing profile, ask what's changed, update only the fields that changed, then go straight to the matched recipe or the cadence. Do not re-interview, and do not re-offer connector setup — if a useful connector is missing, mention the category in one line at most and move on. If the block predates the Country, Currency, and Financial year end fields, fill just those three (from the ledger if connected, otherwise one question) and nothing else. 2. Only if no context block exists: check which connectors are already active. This is a read-only inventory — **do not pull any business data during this step.** Count by product, not by registration: the owner's own `Trello` and the plugin's `small-business:trello` are one connected tool, and an unauthorized plugin copy beside a live owner copy is connected, not missing (`../../shared/connector-neutrality.md`, "One connector, two registrations"). Data pulls happen in step 3, after the owner has picked a direction, and nowhere earlier.

2. **Pick two tools.** Ask: *"What are your biggest day-to-day headaches — money, customers, scheduling, or getting organized?"* Map the answer to the two **categories** in [reference/onboard-checklist.md](reference/onboard-checklist.md), then ask what the owner already uses in each ("what do you use for bookkeeping?"). Connect what they name if we have the connector; offer `build-connector` if we don't; fall back to the recipe's zero-connector path if they'd rather not. Never recommend a vendor inside a category — the rule is `../../shared/connector-neutrality.md`. Guide connection one at a time — never ask the owner to configure two simultaneously.

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 the category-to-recipe list in [reference/onboard-checklist.md](reference/onboard-checklist.md)). If that first tool is a ledger, read the organisation record on the way in and fill Country, Currency, and Financial year end in the profile draft — the checklist says which call per connector. If it is a storefront and no ledger is connected, the shop record fills Country and Currency the same way. 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](reference/examples/happy-path.md).

4. **Interview the owner.** Ask the seven questions from [reference/onboard-checklist.md](reference/onboard-checklist.md), one at a time, conversationally. Wait for the full answer before moving to the next. Questions 6 and 7 (brand look and output format) run the `brand-style` skill's capture flow — that skill owns the logic, and the owner can call it again any time later ('update my brand') without re-onboarding. If country, currency, or financial year end were not read from a ledger or a storefront in step 3, ask the one locale question here; if a storefront filled country and currency, ask only for the financial year end. 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](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. **Deliver the welcome page.** At the end of onboarding, render a welcome page as an HTML artifact using the house artifact style (`../../shared/artifact-style.md`) — and apply the brand just captured, so the first page they ever see is already in their colors. This doubles as the brand preview: if it looks wrong, they say so once and it is fixed in the stored profile. It shows the owner's stack: the tools now connected, plus their s