Internal SOP • Client Production

Client Kickoff + Implementation Tracker SOP

This page moves a new InnerShift360 Business Systems client from onboarding intake into production. Use it for kickoff calls, implementation planning, weekly project tracking, client communication, QA, launch approval, and post-launch support.

Use this after: the client has purchased, completed the onboarding form, and scheduled the kickoff call. This SOP prevents the project from becoming random consulting. Every client moves through the same production rhythm.

Kickoff Goal

Clarify scope, confirm priorities, identify access needs, define success, and turn the purchased package into an implementation plan.

Implementation Goal

Build the agreed system, test it, train the client, launch it, and document the process so it can be maintained.

Client Experience Goal

The client should feel organized, informed, protected, and confident that the system is being built with both automation and human trust in mind.

Kickoff Call SOP

Use this for every client kickoff, regardless of package. Adjust the depth based on package level.

1. Pre-Kickoff Prep Checklist
Manual AI-Assisted Required Before Call
  • Confirm payment or deposit has been received.
  • Confirm package purchased.
  • Confirm client onboarding form has been submitted.
  • Confirm kickoff call date/time.
  • Review original Lead Leak Assessment result, if applicable.
  • Review Lead Leak Audit Summary, if applicable.
  • Review proposal and deliverables.
  • Review onboarding intake answers.
  • Visit client website.
  • Review social media presence, if relevant.
  • Check whether required access has been provided.
  • Create client folder in Google Drive or preferred storage.
  • Create project record in tracker.
  • Prepare kickoff briefing using AI prompt.

AI Prompt: Kickoff Briefing

Prepare a kickoff briefing for a new InnerShift360 Business Systems client. Client: [CLIENT NAME] Business: [BUSINESS NAME] Package Purchased: [PACKAGE] Proposal / Scope: [PASTE SCOPE] Onboarding Intake Answers: [PASTE ANSWERS] Audit Notes, if available: [PASTE NOTES] Website / Social Observations: [PASTE NOTES] Create: 1. Business overview 2. Package summary 3. Primary business goal 4. Current system summary 5. Follow-up weaknesses 6. What should be automated first 7. What should stay human 8. Required access/assets still missing 9. Suggested implementation timeline 10. First 7 kickoff questions 11. Red flags or missing information Tone: Organized, practical, strategic, and easy for James or a VA to use.
2. Kickoff Call Agenda
Human-Led Strategic
TimeAgenda ItemPurpose
0–5 minWelcome + frame the workRemind client this is about protecting opportunity, not automating away humanity.
5–10 minConfirm package and scopeMake sure expectations match what was purchased.
10–20 minReview current lead flowUnderstand what happens when a lead comes in.
20–30 minReview follow-up gapsIdentify leaks in response, nurture, booking, no-shows, and reactivation.
30–40 minReview automation prioritiesDecide what gets built first.
40–50 minReview access/assetsConfirm what is missing and who is responsible.
50–60 minConfirm next stepsSet timeline, deliverables, approval points, and first production tasks.

Opening Script

Thanks again for trusting InnerShift360 Business Systems. The goal of this kickoff is to make sure we understand your business, your current process, and the exact system we are building. We are not here to automate everything. We are here to automate the repetition, protect your opportunities, and preserve the human conversations that matter most. By the end of this call, we should be clear on scope, access, priorities, timeline, and next steps.

Core Questions

  • What would make this project a success for you?
  • What is the most important offer or service this system should support?
  • Where do most leads come from right now?
  • What happens within the first 5 minutes after someone reaches out?
  • Where do prospects tend to disappear?
  • What part of follow-up currently depends too much on memory?
  • What should be automated first?
  • What should absolutely stay human?
  • Who approves copy, workflows, and launch?
  • What access or assets are still missing?
3. Post-Kickoff Summary + Client Confirmation
AI-Assisted Human Review Send via GHL
  • Paste kickoff notes into the AI prompt below.
  • Generate a post-kickoff summary.
  • Review for accuracy and scope.
  • Confirm missing assets/access.
  • Send to client within 1 business day.
  • Create internal project tasks.
  • Update implementation tracker.

AI Prompt: Post-Kickoff Summary

Create a post-kickoff summary for an InnerShift360 Business Systems client. Client: [CLIENT NAME] Business: [BUSINESS NAME] Package: [PACKAGE] Kickoff Notes: [PASTE NOTES] Create: 1. Brief thank-you opening 2. Confirmed business goal 3. Confirmed package/scope 4. What we are building 5. What should be automated first 6. What should stay human 7. Assets/access still needed 8. Implementation timeline 9. Client responsibilities 10. InnerShift360 next steps Tone: Clear, professional, warm, and organized.

Client Email Template

Subject: Your Kickoff Summary + Next Steps Hi {{contact.first_name}}, Thank you for today’s kickoff call. Below is a summary of what we confirmed and what happens next. Primary goal: [INSERT] What we are building: [INSERT] Automation priorities: [INSERT] What should stay human: [INSERT] Assets/access still needed: [INSERT] Timeline: [INSERT] Next steps: [INSERT] The goal remains simple: Automate the repetition. Humanize the relationship. Protect the opportunity. — InnerShift360 Business Systems

Implementation Project Tracker

Use this as the master production tracker for each client. This can be recreated as a Google Sheet, ClickUp board, Trello board, Notion database, or GHL task pipeline.

4. Project Tracker Columns
Required Tracker
ColumnPurpose
Client NameBusiness/client name.
Package PurchasedDIY, Automation Setup, Growth Systems, Full Business System, Monthly Support.
Project StatusNot Started, Waiting on Client, In Build, In QA, Client Review, Launched, Complete.
Start DateDate production begins.
Target Launch DateExpected launch date.
Primary GoalMain outcome client wants.
Primary OfferOffer/service being promoted.
Lead Source(s)Where leads come from.
Required AssetsLogo, brand colors, images, copy, credentials, access.
Missing ItemsAnything blocking production.
GHL Build StatusNot Started, In Progress, QA, Complete.
Website/Page StatusNot Started, In Progress, QA, Complete.
Workflow StatusNot Started, In Progress, QA, Complete.
Email/SMS StatusDrafting, Review, Approved, Loaded.
QA StatusNot Tested, Testing, Issues Found, Passed.
Client Review StatusNot Sent, Sent, Changes Requested, Approved.
Launch ApprovalPending or Approved.
Next ActionSpecific next step.
OwnerJames, VA, developer, designer, client.
NotesImportant context.
5. Implementation Milestones by Package
Manual Use as Production Checklist
PackageMilestones
DIY Toolkit Payment received → toolkit delivered → VA verifies access → optional custom recommendation sent.
Automation Setup Intake complete → kickoff → pipeline/tags/fields → form/calendar → workflows → QA → client review → launch/training.
Growth Systems Buildout Intake complete → strategy map → landing page → CRM build → nurture/reactivation/review/referral workflows → reporting → QA → training → launch.
Full Business System Discovery → offer ladder → customer journey → CRM architecture → funnels → workflows → SOPs → dashboard → training → 90-day roadmap.
Monthly Support Monthly data collected → dashboard reviewed → report generated → strategy call → updates assigned → improvements implemented.
6. Weekly Project Review SOP
Weekly AI-Assisted Summary
  • Review all active client projects.
  • Check status of each project.
  • Identify blockers.
  • Identify missing client assets/access.
  • Review upcoming deadlines.
  • Review QA issues.
  • Review client feedback.
  • Assign next actions.
  • Send client update if needed.

AI Prompt: Weekly Client Project Update

Create a weekly project update for this InnerShift360 Business Systems client. Client: [CLIENT NAME] Package: [PACKAGE] Current Status: [STATUS] Completed This Week: [PASTE] Still Needed: [PASTE] Blockers: [PASTE] Next Steps: [PASTE] Create: 1. Short progress summary 2. What was completed 3. What is still needed from client 4. What InnerShift360 is doing next 5. Updated timeline 6. Clear client action items Tone: Professional, concise, reassuring, and clear.

Client Weekly Update Email

Subject: Weekly Project Update Hi {{contact.first_name}}, Here is your weekly project update. Completed this week: [INSERT] Currently in progress: [INSERT] Still needed from you: [INSERT] Next steps: [INSERT] Current timeline: [INSERT] We’ll keep moving the system forward and let you know if anything requires your approval. — InnerShift360 Business Systems

Production SOP by Build Area

Use these sections to assign specific work to a VA, developer, or automation builder.

7. GHL Build SOP
Manual Build AI-Assisted Architecture QA Required
  • Create or access client GHL sub-account.
  • Create pipeline.
  • Create tags.
  • Create custom fields.
  • Create form(s).
  • Create calendar.
  • Create workflows.
  • Load approved email/SMS copy.
  • Create internal notifications.
  • Create test contact.
  • Run full workflow test.
  • Document what was built.

AI Prompt: GHL Build Architecture

Create a GHL build architecture for this client. Client: [CLIENT NAME] Business: [BUSINESS NAME] Industry: [INDUSTRY] Package: [PACKAGE] Primary Offer: [OFFER] Lead Sources: [LEAD SOURCES] Desired Client Journey: [PASTE] Create: 1. Recommended pipeline stages 2. Tags 3. Custom fields 4. Forms needed 5. Calendar setup 6. Workflows needed 7. Email/SMS sequence map 8. Human touchpoints 9. QA checklist Output in a format a VA can follow step-by-step.
8. Website / Landing Page Build SOP
Manual Build AI Copy + Structure Client Approval
  • Confirm client website platform.
  • Confirm page goal.
  • Confirm primary CTA.
  • Confirm offer/service being promoted.
  • Draft page copy.
  • Create page or HTML widget.
  • Embed GHL form/calendar if needed.
  • Test desktop and mobile.
  • Test all links.
  • Send to client for review.
  • Make revisions.
  • Approve for launch.

AI Prompt: Landing Page Build

Create a landing page structure and copy for this client. Client: [CLIENT] Industry: [INDUSTRY] Offer: [OFFER] Audience: [AUDIENCE] Primary Pain Point: [PAIN POINT] CTA: [CTA] Create: 1. Hero headline 2. Subheadline 3. Problem section 4. Solution section 5. How it works 6. What they receive 7. Trust/proof section 8. FAQ 9. CTA sections 10. Suggested SEO title and meta description Tone: Clear, modern, conversion-focused, trustworthy, and not hypey.
9. Email/SMS Copy SOP
AI Draft Human Review Load into GHL
  • Identify workflow purpose.
  • Identify audience.
  • Identify offer or next step.
  • Draft email/SMS with AI.
  • Review for accuracy and tone.
  • Remove overpromises.
  • Confirm compliance-sensitive language.
  • Load into GHL workflow.
  • Send test email/SMS.
  • Approve for launch.

AI Prompt: Email/SMS Sequence

Create an email and SMS sequence for this client workflow. Client: [CLIENT] Business: [BUSINESS] Workflow Purpose: [PURPOSE] Audience: [AUDIENCE] Offer / CTA: [CTA] Tone: [TONE] Create: 1. Email subject lines 2. Email body copy 3. SMS copy under 300 characters 4. Timing/cadence recommendation 5. Human follow-up point Rules: Do not overpromise. Keep SMS concise. Make emails clear and action-oriented.
10. QA + Launch Approval SOP
Required Before Launch
  • Submit every form as a test lead.
  • Confirm contact is created in GHL.
  • Confirm tags apply correctly.
  • Confirm pipeline stage moves correctly.
  • Confirm internal notifications send.
  • Confirm emails send.
  • Confirm SMS messages send.
  • Confirm calendar booking works.
  • Confirm appointment reminders work.
  • Confirm missed-call workflow works, if included.
  • Confirm payment link works, if included.
  • Confirm mobile responsiveness.
  • Confirm all page links.
  • Confirm client-facing copy is approved.
  • Confirm client gives written launch approval.

VA QA Prompt

Test this full client system from beginning to end. Client: [CLIENT] Package: [PACKAGE] Test: - landing page - form - CRM contact creation - tags - pipeline movement - email workflow - SMS workflow - calendar - appointment reminders - payment links - internal notifications - mobile layout - all CTAs Report: 1. What passed 2. What failed 3. Screenshots of issues 4. Exact workflow/page where issue happened 5. Recommended fix 6. Whether the system is ready for client review

Launch Approval Email

Subject: System Ready for Launch Approval Hi {{contact.first_name}}, Your system has been built and tested. Please review the links and test flow below: [INSERT TEST LINKS] Before launch, please confirm: 1. The page/form looks correct. 2. The copy is approved. 3. The emails/SMS are approved. 4. The booking/payment flow is approved, if applicable. 5. You approve moving this system live. Once we receive approval, we’ll complete the launch step. — InnerShift360 Business Systems

GHL Workflow for Kickoff + Implementation

Create this workflow to keep every new client moving after onboarding.

11. GHL Workflow: Client Kickoff + Implementation Started
Automated Human Follow-Up

Workflow Name

ISB — Client Kickoff + Implementation Started

Trigger Options

  • Tag added: ISB-Onboarding-Submitted
  • OR Form submitted: InnerShift Business Systems — Client Onboarding Intake
  • OR Pipeline stage moved to Closed Won

Workflow Actions

  • Add tag: ISB-Kickoff-Needed.
  • Create task: Review onboarding intake.
  • Create task: Prepare kickoff briefing.
  • Send client confirmation email.
  • Send SMS confirmation.
  • Wait 1 day.
  • If kickoff not booked, send reminder.
  • After kickoff, manually add tag: ISB-Kickoff-Completed.
  • Trigger production task creation based on package.

Client Confirmation Email

Subject: Your Onboarding Is Received — Next Step Is Kickoff Hi {{contact.first_name}}, We received your onboarding intake. Next, we’ll review your answers and prepare for the kickoff call. During kickoff, we’ll confirm: - your primary business goal - the package scope - what we are building first - what access/assets are still needed - what should be automated - what should stay human - your implementation timeline Please make sure your kickoff call is scheduled or confirmed. — InnerShift360 Business Systems
12. Production Task Templates by Package
Create as GHL Tasks Assign to VA / Builder

Automation Setup Task List

  • Create client GHL pipeline.
  • Create tags and custom fields.
  • Create lead capture form.
  • Create calendar.
  • Create immediate response workflow.
  • Create missed-call workflow.
  • Create appointment reminder workflow.
  • Create 7-day nurture workflow.
  • Run QA.
  • Send for client review.

Growth Systems Task List

  • Create growth system map.
  • Create landing page copy.
  • Create landing page or funnel.
  • Create GHL pipeline/tags/fields.
  • Create lead nurture workflow.
  • Create client reactivation workflow.
  • Create review request workflow.
  • Create referral request workflow.
  • Create reporting dashboard.
  • Create SOP and training notes.
  • Run QA.
  • Send for client approval.

Full Business System Task List

  • Complete discovery session.
  • Create offer ladder.
  • Create customer journey map.
  • Create CRM architecture.
  • Create funnel architecture.
  • Create workflows.
  • Create content-to-conversion strategy.
  • Create team SOPs.
  • Create reporting dashboard.
  • Create 90-day implementation roadmap.
  • Train client/team.

Production Principle

A client should never wonder what happens next. Every kickoff should lead to a clear plan, every plan should become trackable tasks, every task should have an owner, and every launch should be tested before the client sees it.

en_USEnglish
Scroll to Top