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.
Clarify scope, confirm priorities, identify access needs, define success, and turn the purchased package into an implementation plan.
Build the agreed system, test it, train the client, launch it, and document the process so it can be maintained.
The client should feel organized, informed, protected, and confident that the system is being built with both automation and human trust in mind.
Use this for every client kickoff, regardless of package. Adjust the depth based on package level.
| Time | Agenda Item | Purpose |
|---|---|---|
| 0–5 min | Welcome + frame the work | Remind client this is about protecting opportunity, not automating away humanity. |
| 5–10 min | Confirm package and scope | Make sure expectations match what was purchased. |
| 10–20 min | Review current lead flow | Understand what happens when a lead comes in. |
| 20–30 min | Review follow-up gaps | Identify leaks in response, nurture, booking, no-shows, and reactivation. |
| 30–40 min | Review automation priorities | Decide what gets built first. |
| 40–50 min | Review access/assets | Confirm what is missing and who is responsible. |
| 50–60 min | Confirm next steps | Set timeline, deliverables, approval points, and first production tasks. |
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.
| Column | Purpose |
|---|---|
| Client Name | Business/client name. |
| Package Purchased | DIY, Automation Setup, Growth Systems, Full Business System, Monthly Support. |
| Project Status | Not Started, Waiting on Client, In Build, In QA, Client Review, Launched, Complete. |
| Start Date | Date production begins. |
| Target Launch Date | Expected launch date. |
| Primary Goal | Main outcome client wants. |
| Primary Offer | Offer/service being promoted. |
| Lead Source(s) | Where leads come from. |
| Required Assets | Logo, brand colors, images, copy, credentials, access. |
| Missing Items | Anything blocking production. |
| GHL Build Status | Not Started, In Progress, QA, Complete. |
| Website/Page Status | Not Started, In Progress, QA, Complete. |
| Workflow Status | Not Started, In Progress, QA, Complete. |
| Email/SMS Status | Drafting, Review, Approved, Loaded. |
| QA Status | Not Tested, Testing, Issues Found, Passed. |
| Client Review Status | Not Sent, Sent, Changes Requested, Approved. |
| Launch Approval | Pending or Approved. |
| Next Action | Specific next step. |
| Owner | James, VA, developer, designer, client. |
| Notes | Important context. |
| Package | Milestones |
|---|---|
| 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. |
Use these sections to assign specific work to a VA, developer, or automation builder.
Create this workflow to keep every new client moving after onboarding.
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.