KaiRep — Jeremy Phelps · T-Mobile

Joe — Command

Jeremy — Field

Strategy, pitch prep & partnership math — private to Joe

60-day POC progress

Day 1 of 60 · started Jun 11

Tasks Complete

of 0 total

Jun 11

Discovery Call Done

3+ hrs · scope locked

~Aug 10

60-Day POC Window

Started Jun 11

$205K

Yr1 Regional Upside

85 reps × $197/mo

Engagement Progress (Joe checklist)

Critical Unknown Resolved

T-Mobile does NOT prohibit reps from maintaining personal customer tracking (spreadsheet, notebook, rolodex) — they just can't pull full account data without scanning an ID. Path A is fully green-lit. Full automation stack confirmed.

Architecture decision (locked)

KaiRep's CRM lives as a dedicated tagged pipeline inside Joe's existing GHL sub-account (no Agency tier needed yet — migrate to Jeremy's own sub-account once Agency tier unlocks via the Palmier TMS trade). This artifact is the front-end Jeremy and Joe both use day-to-day — "Jeremy — Field" mode is the shared/gamified layer; "Joe — Command" mode is private strategy. Data persists via shared storage so updates sync live between sessions.

Why This Is a Bigger Deal Than It Looked Last Week

▾

Jeremy Is Now a True Believer

He went from "I'm not the biggest fan" of AI to fully bought-in within one session — and he's already mapped the political path: bypass his direct manager (Aaron, a naysayer), go straight to Ryan Baum (RM), then to Tanya (MO/KS/IL regional lead). That's a warm, internally-sponsored path to ~85 reps in one region.

The Real Numbers

85 reps/region × $197/mo = $16,745 MRR (~$205K/yr) for one region. Jeremy's cut at 15% referral = ~$2,511/mo. Both called this "life-changing." This isn't a hypothetical — it's the actual model both of you priced live on the call.

The Strategic Asset This Creates

If KaiRep lands at T-Mobile (even one store/region), it becomes KiNETiQai's flagship case study for the entire "Kinetic Assistant" line — externally positioned as "Kinetic Assistant" (never "AI") to T-Mobile staff. Jeremy is bought in as co-pilot/ambassador, with NDA/contract protection for both of you before any leadership-level conversations. This is the proof-of-concept that everything else (Profile Tech, EYCC KaiGrant, future verticals) gets measured against for "does this actually work in the field."

Immediate Action Checklist

▾

P1 Lock MVP scope to the 3-5 undeniable wins (see MVP Plan tab) — start build this week
P1 Get Jeremy's customer list (notebook digitization) — use the Customers tab import box in Jeremy Mode
P1 Confirm Jeremy's exact base + KPI commission structure (working estimate: ~$18-20/hr base + ~$5-10+/hr commission, ~$22-26/hr total / $45-54K/yr)
P1 Set up Calendly for Jeremy — booking links, availability blocks, no-show policy
P2 Draft NDA / partnership contract — Jeremy stays involved in any future T-Mobile/buyout deal (KaiRep rep-version license only, not core Kai IP)
P2 Set up recurring Google Meet sessions w/ Jeremy (Gemini transcription) — weekly 30-min cadence for first 60 days, also doubles for STyMuLaTioN collab sessions
Notion Update Master Tracker — Jeremy row: Discovery → POC Active, KaiRep scope summary logged
Jeremy Jeremy: check internal data-access constraints (what can he share once Ryan's interested)
Joe Research ethical lead-gen methods (Path B fallback) — deprioritized but keep in back pocket

Context Snapshot (Updated)

▾

Who He Is

In-store T-Mobile rep, High Ridge location. Est. ~$22-26/hr total comp ($45-54K/yr) — base ~$18-20/hr + commission ~$5-10+/hr tied to activations, accessories attach rate, upgrade conversions, and CSAT (Jeremy's own verbal estimate was ~$28/hr; confirm exact split). ~10 reps in his store; 8-10 stores in region under RM Ryan Baum, ~5-12 reps/managers each (~85 reps/region working number).

The Core Opportunity

T-Mobile's #1 corporate KPI is brand-new line/account activations — not upgrades. Jeremy's biggest bottleneck is finding new customers without scraping. KaiRep bridges the "how to / when to / what to do" gap reps are told to handle themselves with zero tooling.

Org Chart / Pitch Path

Jeremy (rep, High Ridge) → bypass Aaron (direct mgr, naysayer) → Ryan Baum (RM, ~8-10 stores / ~85 reps, "cares about results & innovation") → Tanya (or successor — runs MO/KS/IL regional) for multi-region expansion.

The Goal

Build an MVP tailored to 3-5 "undeniable wins" over the next ~30 days — not just sales, but total-impact metrics (reach, time saved, sentiment, conversion vs. baseline). Jeremy's baseline: ~10 outreach/month → ~2 conversions. Target: ~30-50 outreach/month with AI prep.

Build Priority Order (Recommended)

▾

Why This Order

Items 1-3 are the foundation — nothing else works without the CRM + cheat sheets. Items 4-5 are the "wow" automation layer that gets shown to Ryan. Items 6-11 are real but can roll in during weeks 3-4 or post-POC without weakening the pitch.

MVP #1 Customer CRM (GHL pipeline, this artifact's Customers tab) — digitized from Jeremy's notebook. Tracks: what's already sold, active promos qualified for, upgrade timing, family members without devices.
MVP #2 Customer Grading / Opportunity Scorecard — 0-10 ranking by win/effort/ROI/KPI alignment. This is what powers the "morning cheat sheet" (Today tab).
MVP #3 Morning Cheat Sheet + Objection/Advantage Playbook — daily call list (who, why, what to say), sorted by opportunity score, with competitor comparisons baked in.
MVP #4 Automated Follow-Up Engine (GHL) — 30-day post-activation sentiment-branching sequence (positive → review/referral ask; negative/no-reply → internal flag + different nurture).
MVP #5 Calendly Integration — booking links, availability blocks tied to Jeremy's schedule, no-show forfeiture policy.
Phase 1.5 Performance Dashboard — activations, referrals, upgrade conversions month-over-month, + NIA/progress bar tied to his regional KPIs (Wins tab).
Phase 1.5 Family Device Tracking — flags family members on an account without phones/data/watches yet (future sales ops / next-gen buyer angle).
Phase 2 In-Store Consultation QA / Self-Correction Layer — with customer consent, transcribes and flags promo/policy misstatements in real time (SYA + training tool).

The "Undeniable Wins" — What Gets Tracked for Ryan

▾

Reach

Outreach volume: baseline ~10/mo → target 30-50/mo. "I reached out to 50 qualified contacts this month vs. my normal 10."

Conversion

New activations + service conversions + upsells directly traceable to a KaiRep-prompted touchpoint. Baseline ~2/mo conversions from ~10 outreach.

Total Impact

Time saved, customer sentiment/reviews generated, brand representation (even non-responders saw the touch). This is the "totality" framing — not just $ but the whole picture.

The Snowball Sequence

Jeremy's numbers visibly improve → Aaron (manager) notices and asks what's going on → Jeremy frames it casually ("messing with a thing a friend built, seems to work well") → Ryan Baum eventually notices too and asks "what is that?" → that question is the trigger for the Joe + Jeremy + Ryan meeting. Free strategic consultation offered now, before the price triples post-proof.

Delivery architecture (locked)

CRM backbone lives as a tagged pipeline inside Joe's existing GHL sub-account (Option B) — no Agency tier dependency. This artifact (KaiRep) is the front-end Jeremy actually uses, reading/writing to that pipeline's data via shared persistent storage. When Agency tier unlocks (Palmier TMS trade), migrate Jeremy's pipeline to his own sub-account — data structure stays the same, no rebuild.

Phase 1 (POC) · Build Checklist

▾

P1 Personal CRM in GHL — customer list, upgrade timing tracker, contact history, referral status, promo qualification view
P1 Customer Grading / Opportunity Scorecard — 0-10 ranking by win/effort/ROI/KPI
P1 Objection & Advantage Cheat Sheet — playbook per customer (competitor comparisons, pains, ROI)
P1 Morning Cheat Sheet — daily call list, sorted by opportunity score (Jeremy Mode → Today)
P1 AI Follow-Up Engine (GHL) — 30-day post-activation, sentiment-branching, one-tap approve & send
P1 Referral Ask Machine (GHL) — auto-sends post-activation referral asks, tracked in pipeline
P1 Calendly integration — booking links, availability blocks, no-show forfeiture policy
P2 Family Device Tracking — flag family members without phones/data/watches for future sales ops
P2 Performance Dashboard — activations, referrals, upgrade conversions month vs. last + NIA/progress bar tied to regional KPIs
P2 KaiLee Lite — pre-conversation AI script generator based on customer account context
Phase 2 In-Store Consultation QA Layer — with consent, transcribe + flag misstatements in real time (self-correction / SYA / training)

Phase 2 · After 60-Day POC Proves Results

▾

Phase 2 Upgrade Jeremy to KaiPro — full performance dashboard, AI coaching on his own sales data
Phase 2 Build the case study — Jeremy's results documented with real numbers (activations, bonus delta, referrals)
Phase 2 Jeremy intro to Ryan Baum (RM) — Joe pitches KaiRep as a per-rep system with live proof; free strategic consult offer
Phase 2 Tier mapping rollout: KaiLite/every tablet → KaiPal/initiative reps → KaiPro/asst managers → KaiBoss/Ryan Baum
Phase 2 Workshop format — Joe (technical) + Jeremy (digested/applied) + interactive demo → "Kinetic certified" for that tier
Phase 2 Tanya / MO-KS-IL regional expansion — replicate proof in additional regions, 50/50 cost split on first expansion
Phase 2 NDA / contract formalized before any regional VP / corporate conversations — protects KaiRep rep-version license vs. core Kai IP

Recurring Cadence with Jeremy

▾

This week — short kickoff session (30-45 min)

Start customer list import (notebook → Customers tab), confirm exact pay structure, set up Calendly.

Weekly for first 60 days — 30-min check-in (Sun night / Mon)

Sets up Jeremy's week. Review Today tab cheat sheet performance, log Wins, bug/quirk notes go in Thread.

After 60-day POC — drop to bi-weekly

Once cadence is proven and the tool is stable. Cadence resumes weekly around any Ryan Baum pitch milestone.

What This Tab Is

Quick-reference specs for each of the 11 features that came out of the 3-hour call, with the rationale Jeremy gave so the build stays true to what he actually needs.

1. Customer CRM — "What I've Sold + What's Available"

▾

Tracks per-customer: what's already been sold (devices, plans, accessories), active promos they currently qualify for (existing only — never future/unreleased promos), and projected upgrade timing. Jeremy's framing: "a running tracker of what you've already sold them, the new promotions that have just come out." Live in this artifact's Customers tab.

Mockup — Customer Record View

Tony R.iPhone 13 (2yr ago) · eligible for upgrade · Magenta Max

Active promo:Trade-in + $800 off iPhone 16 (ends in 9 days)

Family:2 lines on plan, 1 line (age 11) — no device/data yet

2. Objection & Advantage Cheat Sheet

▾

A per-customer playbook: competitor comparisons, customer pain points, ROI vs. other carriers, price comparisons with other stores. Pre-loads Jeremy with "the best promo guaranteed," who they used to carry, what they might be considering switching to, and how to counter it — before the conversation starts. Live in Jeremy Mode → Playbook.

3. Customer Grading / Opportunity Scorecard

▾

0-10 ranking by overall win-vs-effort ratio, ROI, and KPI alignment. Lets Jeremy instantly know how to approach each customer — "easy ones, zero resistance" vs. "pays in full, hates payment plans" vs. higher-effort/higher-reward conversations.

Mockup — Scorecard

Tony R.9.2 · HOT

Marcus D.6.5 · WARM

Sarah K.3.1 · NURTURE

4. Automated Follow-Up Engine (30-Day, Sentiment-Branching)

▾

30 days post-activation, sends a personal-feeling check-in. If positive reply → ask for Google review / send referral link. If negative or no reply → different nurture sequence + internal flag (not public-facing) so Jeremy can self-correct without it ever becoming a public complaint. Always leads with appreciation before any ask. Built in GHL, surfaced as activity in this artifact's Customers tab.

5. Family Device Tracking — "Next Generation of Tech Buyers"

▾

Flags family members on an account who do NOT yet have a phone/watch/tablet/data plan. Surfaces the right time to approach parents with an "unbeatable heads-up deal" as kids age into their first device. Explicitly framed by Jeremy as market research on "the ideal time/age/approach for recruiting the next generation of tech buyers." Tracked per-customer via the Family field in the Customers tab.

6. In-Store Consultation QA / Self-Correction Layer (Phase 2)

▾

With customer consent (checkbox/verbal), the assistant transcribes the in-store consultation, flags any misstated policy/promo in real time so Jeremy can self-correct on the spot. Jeremy's framing: "a checks and balance that knows all the rules and corrects me later so I can correct myself." Doubles as a liability/SYA tool — proof the rep corrected the mistake protects them from blame, and gives T-Mobile a record of continuous improvement rather than repeat errors.

7. Morning Cheat Sheet

▾

Daily call list: who to contact, why, what to say — sorted by opportunity score. Even on slow days, Jeremy gets the "I cast 30 lines today" feeling — every outreach counts as an effort/win even if the response is "not today." This is the core productivity-momentum feature — live in Jeremy Mode → Today.

8. Calendly / Scheduling Integration

▾

Booking links tied to Jeremy's calendar/availability blocks. 10-15 min grace period, then no-show forfeits the slot to the next person in line — no fee, just structure. Jeremy can plan his day around "who's confirmed to walk in" vs. "who I'm reaching out to."

9. NIA / Progress Bar Tied to Regional KPIs

▾

Shows Jeremy's progress against the specific KPIs/metrics his management team grades on — standard KPIs, quarterly specials, annual awards. Surfaces "what to do next" in a way that's directly impactful and noticeable to superiors — management-visible without Jeremy having to translate it himself. The global progress bar at the top of this artifact (both modes) and the Wins tab cover this.

10. Performance Dashboard

▾

Activations, referrals generated, upgrade conversions — month vs. last. This is what gets screenshotted for the Ryan Baum conversation. Live in Jeremy Mode → Wins.

11. Path B Fallback — Lead-Gen Model (Deprioritized)

▾

Not needed now since Path A is confirmed, but kept on file: Joe generates qualified warm leads via SEO landing pages/calculators, sells to Jeremy/reps at $5-10/qualified lead or flat $100/mo for 100 leads (50%+ buy probability). Jeremy explicitly wants to keep this in a small circle and prove it privately before mentioning to management.

Deal Structure

▾

Phase	Jeremy Pays	Jeremy Provides	Joe's Goal
POC · Days 1–60 (started Jun 11)	$0 (or $50–100 token). Pilot partner status.	Active use, honest feedback, customer list digitization, tracks his own numbers	Prove ROI on 3-5 undeniable wins. Get testimonial. Get Ryan Baum intro.
Live · Post-POC	~$150–300/mo KaiPal tier	Intro to Ryan Baum (RM) with results in hand	Regional license pitch. Per-rep bundle: ~$200/employee (already ~50% below R&D-recommended rate).
Regional Expansion (Jeremy's region)	Earns 10–15% MRR referral fee on each rep who converts	Ongoing advocacy, intro to Tanya for MO/KS/IL multi-region	85 reps × $197/mo = $16,745 MRR / $205,668 Yr1 (one region)

Revenue Upside Calculator

▾

Reps per region

Monthly per rep

Regions targeted

Jeremy referral %

Monthly recurring revenue

$16,745

Jeremy's monthly cut

$2,512

Year 1 total (region)

$200,940

Both Called This "Life-Changing"

At 85 reps × $197/mo, one region generates ~$16,745 MRR / ~$205K Yr1. Jeremy's referral cut alone (10-15%) is ~$1,675-$2,511/mo — described on the call as enough to live on and reinvest. Most of Joe's share reinvests into infrastructure/travel to keep scaling to additional regions.

The T-Mobile Expansion Path

▾

Jeremy's 30-60 Day POC (in progress)

3-5 undeniable wins: reach, conversion, total impact vs. baseline (10 outreach/2 conversions → 30-50 outreach target).

Ryan Baum Introduction (bypassing Aaron)

Jeremy: "I've been messing with a thing my friend built, getting me customers every week." Ryan asks "what is that?" → Joe + Jeremy + Ryan meeting, free strategic consult offered now (price triples once POC is proven/replicable).

Regional Rollout (Jeremy's Region)

Tier mapping: KaiLite on every tablet, KaiPal for initiative-showing reps, KaiPro for asst managers, KaiBoss for Ryan Baum (oversight/visibility across stores). Bundle ~$200/employee. Jeremy earns 10-15% referral fee per converted rep.

Tanya / MO-KS-IL Multi-Region Expansion

50/50 cost-split incubated stress test for 2nd region, then scale to 5, then 10 regions on proven model.

Corporate / Exclusive Partnership Play

Multi-region traction → T-Mobile corporate conversation → exclusive early-adopter positioning, leveraged for Formula 1 / sports / enterprise partnerships using T-Mobile as the flagship case study. NDA/contract locks KaiRep rep-version license (not core Kai IP) before any of these conversations.

10-80-10 Operating Model (Jeremy's Frame)

▾

10% — Jeremy's front-end ideation: goals, voice, what's mundane/manual, how he's measured. 80% — KaiRep executes (CRM updates, follow-ups drafted, cheat sheets built, scheduling) while Jeremy is on the floor or off the clock. 10% — Jeremy's final sign-off before anything goes out to a customer. Nothing auto-sends until he turns on full autopilot later — and even then, only once he's fully comfortable.

Naming Discipline — Read This First

Internally this is "KaiRep." To Jeremy's circle and T-Mobile, it's the "Kinetic Assistant." Never say "AI" — say "assistant," "manager," "coordinator." Mission line if asked: "Knowledge in Motion, Intelligence in Action — most AI replaces, overwhelms, or complicates; KiNETiQai educates, empowers, activates."

The Snowball — Step by Step

▾

Jeremy's numbers visibly improve over 30-60 days

More outreach, more confirmed walk-ins, better-prepped conversations, happier customers (reviews/referrals up).

Aaron (direct manager) notices first — keep it casual

Jeremy's line: "I'm messing with this thing — trying to figure out if it works. Seems to be going pretty well." No pitch, no AI mention. Just visible results.

Ryan Baum eventually notices and asks "what is that?"

This question is the trigger. Jeremy: "Before I blow the load, let's set up a meeting — my buddy normally charges for this, but he's offering it free right now."

Joe + Jeremy + Ryan meeting

Joe leads with outcomes/business-casual language (never "AI" unprompted). Jeremy translates into rep-language. Live demo of the dashboard + cheat sheet.

Free consult urgency framing

"Normally this consultation has a cost. It's free right now because you're early. Once this is proven and replicable, the price triples — and we move on to Verizon/AT&T regardless."

Workshop, not seminar

"Workshop" = interactive, mandatory-feeling, career-advancement training. "Seminar" = optional and boring. Joe explains technical layer → Jeremy translates to rep-language → live interactive demo → attendees leave "Kinetic certified" for their tier.

Key Lines / Quotes Ready to Use

▾

"This isn't a side tool. It's a system that measurably increased Jeremy's outreach, conversions, and referral rate. I want to make it available to your whole team."

"Normally this consultation carries a cost, but I'm offering it free right now to help your team be the front-runner instead of buying into another add-on everyone else already has six months from now."

"I don't get people fired, and I don't replace people. I educate, empower, and activate people and workflows — your reps get more bandwidth, your store gets better numbers, and nobody feels like they're getting left behind."

Objection Handling

▾

If Ryan asks "what does this cost us?"

"Right now, nothing — the consultation and proof-of-concept review are free. If we move forward, pricing reflects database storage, security, and maintenance — not just margin. And I've already priced this about 50% below what I was advised to charge, specifically to prove value first."

If Ryan asks "is this going to replace my reps?"

"The opposite. It gives them back the hour a day they're losing to admin and guesswork, so they can spend more energy actually being present with customers. Jeremy's numbers are the proof."

If Ryan is hesitant about AI specifically

"Think of it as Jeremy's personal assistant — it just helps him track and manage the connections he already has. T-Mobile's current AI is a chatbot that tells people their bill. This is an operating system that makes Jeremy look like he remembers everything about every customer."

Intake Complete — Captured Live on Call (June 11)

All answers below were confirmed live during the 3-hour discovery call. Both critical unknowns are now resolved.

Question

Jeremy's Answer

Activations per month on average?

Tracks past customer upgrade timing? (Yes / Kind of / No)

Current follow-up method with past customers?

Referrals per month on average?

One thing to automate for biggest income impact?

Current tools for managing customer relationships?

Biggest bottleneck right now?

AI openness score 1–10?

T-Mobile policy: can reps use personal outreach tools for past customers?

How are his customer contacts currently stored?

Direct manager name (the "naysayer" — bypass for pitching upward)

Regional Manager (RM) — first pitch target post-POC

Next contact after RM for multi-region expansion (MO/KS/IL)

Store / reps-per-store / stores-per-region (for revenue calc)

Exact base pay + commission structure (working est: ~$18-20/hr base + ~$5-10+/hr commission)

Note

Your June 11 live call notes, build notes, and intake answers are preserved below. This data now persists via shared storage — Save Now / autosave both write to it, no more browser-only localStorage. For shared back-and-forth with Jeremy, use Jeremy Mode → Notes & Chat.

Generate session summary

▾

Pulls from the shared CRM, wins, and Notes & Chat thread — same generator as Jeremy Mode. Use this for your weekly check-in prep or Notion session handoff.

Live Call Notes — June 11 (3hr Discovery Call)

Post-Call Debrief

Build Notes

Partnership Notes

Session Log

All changes saved