Every new client,cleared for takeoff.

A CRM — HubSpot or GoHighLevel (it works with either) — for the signed deal, and Google Drive, where the client folder and draft docs get staged. Google Calendar is optional, for drafting the kickoff invite. You bring your own accounts and connect them to Claude via MCP; the Runway is the orchestration layer on top — it never includes or resells your CRM or storage.

It scores a six-item onboarding checklist — signed agreement, deposit/first payment, scope confirmed, access & credentials, primary contact, kickoff scheduled — each rated 0–5 on readiness, with weights that sum to 100. That yields a 0–100 score and one verdict: GO (≥ 80, every blocker locked), ALMOST (55–79), NOT READY (< 55), or HOLD KICKOFF. The honest part is the blocker gate: a blocker — contract, deposit, or scope — below READY forces HOLD KICKOFF no matter how high the score. In the worked example everything's ready except the deposit, so it scores 76 but still reads HOLD KICKOFF; collect the deposit and it clears to GO at 87. The checklist, weights, and blocker flags are all yours to edit.

No — and that's deliberate. It reads your CRM and Drive and drafts the onboarding kit, and it may stage unshared drafts in your own Drive (like an unsent draft email). It never shares a doc with or grants the client access, never sends the welcome or an intake request, never edits or moves a live deal, and never deletes anything. Sharing, sending, granting access, and updating the CRM are yours to do after you review.

That kit is a content library of SaaS-style activation email sequences — welcome, activation, adoption — for getting a self-serve user to an activation milestone. The Runway is a connected workflow for agencies and service businesses onboarding a signed client: it reads the deal, scores kickoff-readiness, and drafts the whole intake-and-setup packet into your stack. Different audience, different scope, different mechanism — they're complementary. You could run the Runway to start the engagement and borrow the Sequence Kit's email patterns inside it.

Four Claude Skills (readiness scout, kickoff-packet architect, workspace setup drafter, onboarding tracker), a runnable Python scoring engine with the worked sample, the same scorer as an Excel workbook, a kickoff-packet template, and two playbooks — the onboarding workflow and a CRM + Drive MCP setup-and-safe-onboarding guide. You supply the CRM and Drive accounts.

No on both. It surfaces what's ready, what's a gap, and what's blocking the kickoff — but a clean start still depends on you and the client, and outcomes are never guaranteed. And the GO/HOLD verdict is operational kickoff-readiness, not legal or financial advice: use your own contracts, counsel, and judgment for anything contractual or financial.