xbert-client-onboard

{
  "name": "xbert-client-onboard",
  "displayName": "XBert Client Onboard",
  "description": "Structured new-client onboarding with checklist, practice-owner gate, and approval-gated rules baseline assignment with rollback. v1 orchestrates the workflow; COA + opening-balance steps are checklist items the bookkeeper completes in the ledger.",
  "author": {
    "name": "XBert Intelligence",
    "email": "[email protected]"
  },
  "homepage": "https://intelligence.xbert.io/plugins/xbert-client-onboard",
  "license": "MIT",
  "keywords": [
    "onboarding",
    "new-client",
    "engagement",
    "checklist",
    "rules"
  ],
  "x-xbert": {
    "displayName": "XBert Client Onboard",
    "tagline": "Structured new-client onboarding with checklist, scope gate, and an approval-gated rules baseline that records its own rollback.",
    "audience": [
      "bookkeepers",
      "practice-managers"
    ],
    "categories": [
      "onboarding",
      "new-client"
    ],
    "prerequisites": [
      "XBert account",
      "Practice with templates configured for new-client tasks (workflow templates, rule baselines)",
      "Engagement letter signed off (gate-checked before configuration begins)",
      "v1 scope note: this plugin orchestrates the onboarding checklist and creates the workflow tasks — COA creation and opening-balance load are checklist items the bookkeeper does manually in the ledger"
    ],
    "screenshots": [],
    "demoVideo": null,
    "includes": {
      "skills": 1,
      "commands": 1,
      "mcpTools": 0
    },
    "longDescription": "New-client onboarding is the single biggest source of cleanup work downstream. Skip the engagement letter sign-off and you discover scope creep three months in. Skip the chart-of-accounts confirmation and the client's reports never reconcile to their old ones. Skip the rules baseline and every transaction needs manual coding. Each shortcut feels small at the moment; each one compounds into months of fix-up.\n\nXBert Client Onboard runs the four-phase onboarding lifecycle as a structured workflow — engagement, connection, configuration, go-live — with gate checks at each phase boundary that prevent skipping ahead. v1 orchestrates the checklist, creates the workflow tasks from your practice templates, and enforces the practice-owner gate. The COA-create and opening-balance-load steps remain checklist items the bookkeeper does manually in the ledger; v2 will automate those.\n\nThe rules baseline write (XBert rule pack the new client starts with) is **gated by an explicit approval prompt that names the resolved client and Connect tenants** — scope-confirm earlier in the flow is not authorisation to write. On approval, the plugin emits a rollback block recording every rule assigned and the previous state of any rule overwritten, so the configuration can be reverted in one paste-back.",
    "useCases": [
      {
        "title": "First-time client setup",
        "description": "Drive the new client through the four-phase onboarding with gate checks — no shortcut-taking, no missed steps."
      },
      {
        "title": "Mid-onboarding sanity check",
        "description": "Run mid-onboarding to confirm where the client is in the four phases and which items are still outstanding."
      },
      {
        "title": "Practice-wide onboarding consistency",
        "description": "Every onboarding goes through the same gates and creates the same workflow tasks from the same templates — no per-bookkeeper improvisation."
      },
      {
        "title": "Approval-gated rules baseline",
        "description": "The XBert rules baseline (which checks fire, which thresholds, which approvers) is assigned only after an explicit approval prompt that names the resolved client and Connect tenants. Scope-confirm alone is NOT authorisation to write."
      }
    ],
    "benefits": [
      {
        "icon": "GitBranch",
        "title": "Four-phase gated workflow",
        "description": "Engagement → connection → configuration → go-live. Each phase has explicit gate checks — no skipping ahead, no half-onboarded clients."
      },
      {
        "icon": "ShieldCheck",
        "title": "Practice-owner gate enforced",
        "description": "Engagement letter and scope confirmation are gate-checked before any configuration starts. The plugin won't proceed without sign-off."
      },
      {
        "icon": "Zap",
        "title": "Approval-gated rules baseline with rollback",
        "description": "Baseline assignment is gated by an explicit prompt naming the resolved client and Connect tenants — scope-confirm doesn't authorise the write. On approval, the plugin emits a rollback block recording every rule assigned and the prior state of any rule overwritten."
      }
    ],
    "workflow": [
      "Type /client-onboard in Claude Code or Claude Desktop",
      "Confirm the new client name, the Connect tenant, and the engagement scope",
      "Plugin checks current phase via the XBert MCP and presents the gated checklist",
      "Walk through each phase's gate checks; the plugin creates workflow tasks from your practice templates as you progress",
      "Phase 3 rules-baseline assignment is gated by an explicit approval prompt that names the resolved client + Connect tenants — on approval the plugin emits a rollback block recording every rule assigned. COA create + opening-balance load remain manual checklist items in the ledger (v1)"
    ]
  }
}