Claude for Small Business — Deployed Right.

What we do.

A five-phase engagement: discovery to map your connector footprint and staff profile; configuration to wire the right connectors and turn off the ones that don't belong; governance design to build your approval gate map and acceptable use policy; a staff orientation session so your team starts confident; and a documented handoff so the configuration doesn't live only in someone's head.

Discovery: Connector inventory, staff profile, policy baseline, infrastructure check — which tools are live, who will use it, what data handling rules need to be in place before anyone touches a workflow.

Configuration: Enable Claude for Business on your tenant, wire active connectors (up to 3), disable or restrict out-of-scope connectors, verify integrations are working and not over-permissioned.

Governance design: Approval gate map (which workflows staff can run autonomously vs. which require sign-off), an acceptable use policy in plain language specific to your tool stack, and a data handling rules document (what goes into Claude, what stays out).

Staff orientation: A 1–2 hour session with all users — what it does, what it doesn't, what they can do, what they need to flag. Not a product demo. A practical briefing.

Handoff: Full documentation package and a 30-day check-in call.

What you walk away with.

A configured Claude for Business environment wired to your active tools. An approval gate map so your staff knows what they can do without asking. An acceptable use policy they've actually read — written for your operation, not a generic template. A data handling rules document. A staff orientation on record. And a 30-day check-in call to surface anything that came up after go-live.

What you receive across the engagement.

• Connector configuration — Active connectors wired, tested, and verified. Out-of-scope connectors disabled or restricted. Auth reviewed for least-privilege.
• Workflow approval gate map — Document specifying which built-in workflows staff can run autonomously and which require a review step before execution. Specific to your operation and team structure.
• Acceptable use policy — Plain-language document your team will actually read. Covers what Claude is for, what it isn't for, what data can and can't go in, and what to do when something doesn't look right.
• Data handling rules — Specific rules for your environment: which data categories are permitted in Claude, which are conditional, which are prohibited. Written against your actual tool stack and data types — not generic AI policy language.
• Staff orientation session — 1–2 hour session with all users before go-live. Covers what Claude for Business does, what it doesn't, what's in bounds, what's not, and what the escalation path is.
• Configuration documentation — Full written record of the connector setup, approval gate decisions, and policy rationale — so the configuration doesn't live only in the implementer's head.
• 30-day check-in call — 30-minute call four weeks after go-live to surface anything that came up in practice and confirm the governance design is holding.

Here's the kind of governance decision this engagement surfaces before it becomes a problem:

How pricing works.

Fixed fee: $6,500–$8,500. Scope is confirmed at the kickoff scoping call — the fee is set at that point and doesn't change based on hours. Exact amount within the range depends on the number of active connectors and team size.

Payment: 50% at kickoff, 50% at handoff. No ongoing retainer included — ongoing AI governance routes to the vCIO Retainer if you want that relationship after delivery.