Lantern Social Selling Playbook

Enter the access code to view this document.

GTMify × Lantern Studios · 3-Month Pilot

Lantern Social Selling Playbook.

Turning LinkedIn into Lantern's most reliable pipeline channel — a strategic and operational guide for Adam Drutz, Ben McMann, and the US sales team.
About Lantern
Lantern is a Microsoft Solution Partner across all six designations and a Fabric Featured Partner. The studio model combines AI, Agile, and design-led delivery to accelerate every stage of the AI journey — from vision to value — for mid-market and large enterprise organizations on the Microsoft platform.
Client
Lantern Studios
Engagement
GTMify 3-Month Pilot
Version
v1.1 — 2026-04-13
Prepared by
GTMify

0.How to Use This Playbook

This is a layered document. Part 1 is the strategic brief for Adam and Ben — the why, the business case, the operating model, and the pilot scorecard tied to the three contractual KPIs. Part 2 is the operator playbook for the sellers — the daily execution manual with profile templates, DM scripts, weekly schedules. Part 3 is the appendix reference — persona-to-content matrix, practice-area-to-case-study matrix, 33-case-study proof library, objection handlers, launch checklist.

Read Part 1 to align. Operate from Part 2. Reference Part 3 when you need a template, a proof point, or a response.

Part 1 — Strategic Brief

1.Executive Summary

Lantern's pipeline today is disproportionately dependent on referrals, partner-driven introductions, and Microsoft co-sell motion. That works — until it doesn't. It is not a system. It is not predictable. It does not scale when Adam needs to add a new seller, enter a new region, or chase a newly-announced buying signal at an account like Bell Textron or Arcosa.

Social selling on LinkedIn is the most efficient addition Lantern can make to its pipeline mix right now — not because LinkedIn is magic, but because Lantern's five buyer personas (CIO, CDO, CISO, Chief Innovation Officer, COO) are measurably the most active enterprise buyers on LinkedIn, and because the GTMify system transforms LinkedIn from a content hobby into a pipeline engine.

The Precedent
A GTMify customer in the Microsoft partner ecosystem — a direct Lantern peer — generated 60 net-new meetings from 175 target accounts in 8 weeks using this methodology. No paid ads. No inbound waiting. Systematic profile views, reactions, and comments on target personas, followed by warm connection requests, followed by value-first DMs.
60
Net-new meetings from 175 target accounts (peer Microsoft partner, 8 weeks)
2–5×
Email response lift when recipient is pre-warmed on LinkedIn
4–6h
Seller time per week to run the full loop

The target outcome for the 3-month pilot

8–12 qualified meetings per seller per month by week 8, with >40% connection acceptance and >25% DM response rates — directly feeding the three contractual pilot KPIs (Target Account Engagement Rate, High-Fit Pipeline Velocity, Signal-to-Meeting Yield).

2.Why Social Selling, Why Lantern, Why Now

2.1 The Pipeline Reality

Lantern's current pipeline engine has three strong pillars — referrals, Microsoft co-sell, and event-driven relationships. It has one structural gap: there is no repeatable, seller-owned channel that produces qualified meetings on demand. When the referral flow slows, there is no lever to pull.

Traditional outbound email alone will not close that gap for Lantern. Lantern's buyers are senior, they are inundated, and they increasingly ignore cold email from consulting firms they do not recognize. The active DFW Tier 1 outbound campaign proves the motion works, but single-channel email has a ceiling. LinkedIn is not an alternative to outbound email — it is the accelerant that makes outbound email work. Email response rates typically lift 2–5× materially when the recipient has seen the sender's profile or accepted a connection in the prior week.

2.2 Why Lantern Is Structurally Advantaged Here

  1. The audience lives on LinkedIn. CIOs, CDOs, CAOs, VPs of Data & Analytics, and Chief Innovation Officers are the most active senior audience on LinkedIn.
  2. Lantern's brand voice converts on LinkedIn. "Inspiring Clarity" — confident, approachable, jargon-free — is exactly the tonal register that outperforms on the feed.
  3. Lantern's proof is concrete and quantified. 33 case studies with named clients (Banfield, Smoothie King, Apex Utilities, Avocados From Mexico, Unifi, Santander) and real numbers (20% safety-incident reduction, 94% model accuracy, 90% adoption endorsement, 34.5 hours saved per month, 7.5× more fraud cases caught).

2.3 The Business Case

MetricCurrent State (Est.)Pilot Target (8–12 weeks)Steady-State
Seller-sourced meetings/monthReferral-dependent, variable8–12 per seller15–20 per seller
DFW Tier 1 account penetration~25 engaged / 59 target>40 engaged (multi-threaded)100% (quarterly)
Connection acceptance rateNot tracked>40%>50%
DM-to-meeting conversionNot tracked>5%>8%
Time investment / seller / weekAd-hoc, 0–10 hrs inconsistent4–6 hrs consistent4 hrs consistent
Applied to Lantern's DFW list
A peer Microsoft partner hit 34% account-to-meeting conversion in 8 weeks using this methodology. Applied to Lantern's 59-account DFW Tier 1 + Tier 2 list, the directional target is 18–20 net-new meetings in the first 8 weeks of pilot execution — before counting the broader ICP set.

3.The Framework at a Glance — The LinkedIn Pipeline Engine

Social selling at Lantern is not "posting more on LinkedIn." It is a closed-loop engine with six sequential stages that every seller runs every week:

┌──────────────────────────────────────────────────────────────┐
│          LANTERN WEEKLY SOCIAL SELLING LOOP                  │
├──────────────────────────────────────────────────────────────┤
│                                                              │
│   1. SIGNAL ──────▶ Sales Nav + PitchGhost finds + DFW       │
│                     Tier 1/2 + intent (exec moves, funding)  │
│            ↓                                                 │
│   2. WARM-UP ─────▶ 5-day engagement protocol                │
│                     (view, react, comment)                   │
│            ↓                                                 │
│   3. CONNECT ─────▶ Personalized connection request          │
│            ↓                                                 │
│   4. CONVERSE ────▶ 15-day value-first DM sequence           │
│                     (text → voice → video → direct ask)      │
│            ↓                                                 │
│   5. MEETING ─────▶ Calendar booking or AE hand-off          │
│            ↓                                                 │
│   6. LEARN ───────▶ Update CRM, log signals, refine search   │
│                                                              │
│   [Loop back to SIGNAL with refined criteria]                │
│                                                              │
└──────────────────────────────────────────────────────────────┘

Four Structural Principles

4.Integration With What Lantern Already Has

This playbook slots into Lantern's existing stack — it does not replace it.

Existing AssetHow This Playbook Extends It
Active DFW Tier 1 outbound campaign
639 Tier 1 + 1,999 Tier 2 leads across 59 accounts
LinkedIn warm-up runs 5 days ahead of email first touch. Email response lifts materially when the recipient has seen the sender's profile.
PitchGhost DM Radar ghosts
5 live ghosts, Tier 1 + Tier 2 people and companies
Surfaces daily engagement signals. A lead posts about Fabric → seller comments within 24 hrs. The SIGNAL step automated.
HubSpot CRMAll LinkedIn signals logged against the account record. Detailed deal-stage mapping in §15.3.
Octave-Lantern workspacePowers AI-assisted DM drafting via Ben (/octave:linkedin, /octave:voice-agent). Sellers route requests through Ben during pilot.
Enhanced ICP v2.1Personas, firmographic filters, negative filters (§4.1), intent signals — single source of truth for targeting.
33 Lantern case studiesProof-point library organized by industry (Appendix B.1) and by practice area (Appendix B.2).
Microsoft co-sell programLantern's 6× Solution Partner + Fabric Featured Partner status unlocks formal co-sell coordination — see §15.5.

4.1 Negative Filters — Who NOT to Target

Non-negotiable. These filters apply to every Sales Navigator search, every warm-up batch, every DM sequence. A seller who ignores them burns account credibility and violates the engagement.

Never Target
  • Price-driven buyers — not aligned with Lantern's value-first approach
  • Body-shopping / staff-aug engagements — Lantern partners, doesn't staff
  • Transactional one-off project seekers — no strategic partnership fit
  • Non-Microsoft stack companies — outside core competencies
  • Existing Lantern clients — blacklist, signal monitoring only, zero automated outreach
  • Dynamics 365 CRM or ERP seekers — not a Lantern specialty (D365 Power Platform IS in scope)

The existing-client blacklist lives in accounts_for_pilot/ and MUST be applied as an exclusion filter on every Sales Navigator saved search before outreach begins.

5.Operating Model — Who Does What

Social selling is a shared-execution motion with explicit accountabilities. Ambiguity kills consistency.

RoleWeekly TimeCore Responsibilities
Adam Drutz (US Head of Sales)1.5 hrsGovern the scorecard, approve Tier 1 batches, coach underperformers, escalation for Microsoft co-sell overlap
Ben McMann (GTM)2 hrsContent strategy, playbook refresh, Octave workspace, measurement hygiene, HubSpot governance
Each US seller (AE)4–6 hrsProfile optimization (one-time), daily 30-min block, weekly KPI self-report, monthly retro
Lantern Marketing lead (TBD)1 hrContent coordination, Featured-section approvals, Lantern company page amplification
GTMify (pilot period)On-callWeekly optimization review, DM A/B testing, HubSpot-LinkedIn signal integration, escalation
The Non-Negotiable
Each seller commits to 30 minutes, every business day, on LinkedIn. Not batched. Not skipped. Embedded in the calendar as a recurring block. The discipline matters more than the clever tactics.

6.The 90-Day Pilot Scorecard — Mapped to the Three Pilot KPIs

Pilot success is measured against the three contractual KPIs from the engagement SOW: Target Account Engagement Rate, High-Fit Pipeline Velocity, and Signal-to-Meeting Yield. This playbook operationalizes all three.

6.1 KPI Mapping

Pilot KPI (from SOW)How This Playbook Drives ItMeasurement
Target Account Engagement Rate
% of target accounts moving Cold → Active Conversation → Discovery
§9 Warm-Up + §10 DM sequence move accounts from Cold to engaged. Multi-threading across the buying committee (§13) doubles the surface per account.DFW Tier 1 accounts with ≥1 accepted connection + ≥1 two-way DM exchange in last 30 days
High-Fit Pipeline Velocity
Days First Touch → Qualified Opportunity
§10 15-day sequence with voice + video (§11) accelerates first meeting. Co-sell coordination (§15.5) shortcuts trust ramp. Hot-score accelerators (§12.2) compress cycle for 80+ scored leads.HubSpot timestamp from first LinkedIn touch → deal stage "Qualified"
Signal-to-Meeting Yield
% of high-intent alerts → Discovery Meeting (target: 1 in 5)
§12 Signal Scoring surfaces alerts. §10.5 Voice Note + §10.6 Direct Ask on hot-score accounts convert alerts into meetings.HubSpot alert → calendar event within 14 days of alert

6.2 Operational Metrics (Leading Indicators)

KPIWeek 2Week 6Week 12
Connection acceptance rateBaseline captured>35%>40%
DM response rateBaseline captured>20%>25%
Meetings booked / seller / month0–24–68–12
DFW Tier 1 account penetration>10%>40%>60%

Red flag thresholds: any seller below 25% connection acceptance or below 10% DM response at week 6 gets coaching intervention — usually a profile audit or a DM voice recalibration.

6.5Adoption Risk & Change Management

The largest pilot risk is not technical — it is adoption. Most social selling pilots at consulting firms fail at adoption, not methodology.

6.5.1 Predictable Resistance Patterns

Objection (seller says…)Likely Root CauseAdam's Response
"I don't have time to post on LinkedIn"Believes content IS the playbook (it isn't)Re-orient: content supports outreach; daily block is 30 min
"LinkedIn doesn't work in our market"Hasn't run the full loopShow the precedent + require 6-week commitment before judging
"My profile is fine"Low audit score, unaware of impactAudit together; show before/after acceptance rate data
"I'm not comfortable doing video"New muscle; fear of being cringe-worthy§11 standards — 45 sec, screen share, not influencer-polished
"My accounts aren't on LinkedIn"Hasn't searched correctlyLive Sales Nav session; run the persona saved searches together

6.5.2 The Rollout Sequence

Do not launch all sellers at once. Use a 3-cohort rollout:

  1. Cohort 1 (Week 1, 2 sellers): LinkedIn-comfortable sellers. Produce first wins, become internal case studies.
  2. Cohort 2 (Week 3, middle 2–3 sellers): Onboarded with Cohort 1's real data. Peer-coached.
  3. Cohort 3 (Week 5, remaining): Onboarded only after Cohorts 1 & 2 show visible meetings.

This sequencing preserves momentum, surfaces issues early, and converts skeptics through peer evidence, not top-down mandate.

6.5.3 Coaching Checkpoints

Part 2 — Operator Playbook

7.Profile Optimization — The Foundation

Before any outreach begins, the seller's LinkedIn profile must convert visitors to connections. A strong profile lifts acceptance rates 15–25 points on its own.

7.1 The Profile Audit (target score 60+ / 70)

ElementLantern StandardScore
BannerMicrosoft partner credential, client logo set, or "From Vision to Value" lockup — not stock abstract/10
HeadlineWHO + OUTCOME + credibility marker, not job title/10
About / SummaryInsight hook, three value-prop bullets, clear CTA/10
FeaturedCase study + Microsoft credential + calendar link/10
ExperienceResults-focused, quantified impact/10
Creator ModeEnabled with 3–5 relevant topics/10
Custom Button"Book a call" → seller's calendar/10

7.2 Lantern Headline Formula

Formula[WHO YOU HELP] achieve [OUTCOME] on [MICROSOFT PLATFORM] | [CREDIBILITY MARKER]
PatternExample
Persona-anchoredHelping CIOs at mid-market manufacturers turn AI experiments into enterprise value on Azure
Practice-anchoredI help enterprise data leaders build AI-ready Microsoft Fabric platforms — Lantern, a Microsoft Solution Partner
Outcome-anchoredHelping CPG & manufacturing leaders go from AI pilot → production in 12 weeks | Fabric Featured Partner
Credential-stacked[Your credential: Microsoft-certified / prior exec role / specific expertise] | Helping Fortune 1000 teams unlock Copilot value | Lantern — 6× Solution Partner
Use real credentials only
If the seller doesn't have a specific credential (e.g., "Ex-Microsoft"), leave that position blank and anchor on Lantern's own credentials (6× Solution Partner, Fabric Featured Partner) instead of fabricating.

7.3 The About Section (2,600-char framework)

Lantern About TemplateSTEP 1 — PATTERN INTERRUPT Most enterprises think they have an AI problem. They don't. They have a data and adoption problem — and AI without either is just expensive experimentation. STEP 2 — CREDIBILITY I work with CIOs, CDOs, and Heads of AI at $1B–$10B organizations to turn Microsoft AI investments into measurable outcomes — at Lantern, a Microsoft Solution Partner across all six designations and a Fabric Featured Partner. STEP 3 — PAIN POINTS • Your AI pilots are stalling at POC and not moving into production • Your data foundations (Fabric, Azure, Databricks) are fragmented • Your people aren't adopting the Copilot licenses you've paid for STEP 4 — SOLUTION BRIDGE Lantern's studio model combines AI, Agile, and design-led delivery — "done with" your team, not "done to" them. STEP 5 — PROOF (verified numbers) • Unifi: AI-powered safety platform delivering 20% reduction in safety incidents with 94% predictive model accuracy across 2,000 employees • Smoothie King: Microsoft Fabric franchisee analytics platform delivered in just 4 weeks • Avocados From Mexico: Power Platform supply chain automation cutting requisition time from 15 minutes to under 1 minute (34.5 hours saved per month) STEP 6 — CTA If your AI is stuck in pilot or your team isn't using the Copilot you've licensed — DM me "AI" or grab 15 minutes: [calendar link]

7.4 Featured Section — The Three Pins

SlotContentPurpose
1Best-performing Lantern case study post (Smoothie King Fabric, Unifi AI safety, Banfield)Inbound credibility
2Microsoft Solution Partner / Fabric Featured Partner credentialAuthority
315-min discovery call booking linkDirect conversion

8.Content Strategy — Four Pillars, Nine Practice Areas

Content on LinkedIn supports outreach. It is never the goal by itself. Sellers need to become visible, credible, and specific — not influencers.

8.1 The Four Content Pillars

Pillar%StagePurposeExample
Challenge30%TOFUInterrupt their thinking"Most AI pilots fail at adoption, not accuracy. The 94% accurate model nobody uses is still a zero."
Educate40%MOFUTeach a framework"The 5-step path from Fabric POC to production — what breaks at step 3."
Proof20%BOFUConcrete client outcomes"How Smoothie King went from zero to Fabric franchisee analytics in 4 weeks."
Human10%TOFU/BOFUTrust via personal POV"What I learned sitting through 8 hours of AI governance debates."

8.2 Mapping to Lantern's Nine Practice Areas

Each practice area is a topic lane. Sellers stay in their lanes — the LinkedIn algorithm rewards consistency over breadth. Each seller picks one primary + one secondary lane for the pilot, not all nine.

Practice AreaCore Content Angles
AI FoundationsAzure platform design; identity & governance; cost controls; experiment-to-enterprise journey
AI StrategyAI operating models; business case framing; value realization; executive alignment
Agentic DevAI agents in the SDLC; autonomous development; GitHub Copilot Workspace
Azure AI AppsCloud-native AI patterns; responsible AI in production; Azure AI Foundry; embedded AI workflows
Copilot & Business AppsCopilot adoption; Power Platform governance; measuring productivity gains
Data & AIFabric, Databricks, Azure SQL; data product thinking; AI-ready foundations
GitHubDeveloper productivity; agentic GitHub workflows; enterprise Copilot
Modern WorkM365 transformation; Teams/Office/OneDrive adoption; collaboration at scale
OCM / AdoptionWhy 70% of AI programs fail at adoption; change management for AI

8.3 Weekly Posting Schedule

DayPillarTime
MondayChallenge (TOFU)20 min
WednesdayEducate (MOFU)25 min
FridayProof (BOFU, cite a case study)20 min
(Optional) ThursdayHuman10 min

Total ~75 min/week. AI-assisted drafting via Ben → Octave-Lantern accelerates while preserving voice.

8.5 Lantern Company Page Amplification

Individual seller content is the engine. The Lantern company page is the multiplier.

  1. Reshare with commentary, not just repost. Every Lantern company post deserves a personal seller angle: "This case study landed with a CIO I've been talking to because [specific insight]."
  2. @-mention engaged prospects when a company post is directly relevant. Example: "A point @[prospect name] raised last week ties directly to what our Copilot adoption team is seeing across regulated industries."
  3. Engage first on every Lantern company post within 2 hours of publication. The first 20 reactions drive the algorithm; sellers are that first 20.
  4. Cross-link Featured sections — every seller's Featured section should include at least one Lantern-branded asset.

9.The 5-Day Warm-Up Protocol

Runs on every target lead. 10 minutes per seller per day for a batch of 50.

DayActionDurationWhat the Target Sees
Day −5View profile30 sec/lead"This person viewed my profile"
Day −4React to 2–3 recent posts2 min/lead"This person reacted to your post"
Day −3Thoughtful comment on their best recent post5 min/lead"This person commented on your post"
Day −2Follow (if not connected)30 sec/lead"This person started following you"
Day 0Personalized connection request2 min/leadWarm request referencing shared context

9.1 Comment Templates — Lantern Voice

For an AI Strategy postThis resonates — the observation about governance vs. speed is the tension nobody names. We see the same pattern: the teams that scale AI are the ones treating data governance as an enabler, not a gate.
For a Fabric adoption questionFrom what we've seen helping organizations like Smoothie King scale Fabric — the adoption curve usually breaks at the semantic model stage, not the platform stage. The trap is over-engineering data products before the first business unit is using them.
For a promotion or team winCongrats on this. The specific detail about [X] stood out — most organizations struggle to get to that level of data-driven decisioning inside 18 months.

Always: specific, additive, non-promotional. Never: "great post!" or any generic compliment.

9.3 Worked Example — First 5 Accounts to Warm This Week

Drawn from DFW Tier 1 Must-Target (all score 8+ on the EICP, all HQ'd in DFW). The concrete first-week warm-up plan:

1

Bell Textron

Aerospace · AI Foundations + Data & AI
Target: VP Engineering Systems, CDO
"Working with Microsoft-first aerospace programs on the shift from engineering data silos to unified Fabric platforms"
2

Arcosa

Infrastructure · Copilot & Business Apps
Target: CIO, VP IT
"Helping mid-market industrial manufacturers unlock measurable Copilot adoption in operations"
3

Atmos Energy

Utilities · AI Foundations + OCM
Target: CIO, VP Data & Analytics
"Apex Utilities' SharePoint transformation is a near-mirror of what Atmos is navigating — happy to share the playbook"
4

Flowserve

Industrial Manufacturing · Data & AI
Target: CDO, VP Data
"Seeing strong Fabric + Azure patterns across industrial manufacturers with distributed plant data"
5

Lennox International

HVAC Manufacturing · Copilot + Agentic Dev
Target: CTO, VP Digital
"Helping Microsoft-first manufacturers build first production AI agents in 12 weeks — not 12 months"
Week 1 target
5 accepted connections across these 5 accounts by end of week 2. Realistic first-week outcome, visible team win.

10.The 15-Day DM Sequence

Once a connection is accepted, run the following 8-touch sequence. Every message is Challenger-framed in Lantern's Inspiring Clarity voice.

DayStepChannelAction
0Connection RequestLinkedIn300-char personalized note
1Thank You + QuestionLinkedIn DMThanks + one specific question
3Value DMLinkedIn DMShare a Lantern asset
5Voice NoteLinkedIn DM45–60 sec personalized audio
8Content TagLinkedInTag in a relevant post or comment
10Video MessageLinkedIn DM45–75 sec LinkedIn native video
12Direct AskLinkedIn DMClear CTA for a 15-min conversation
15Breakup + Email PivotEmailSoft breakup, switch to email

10.1 Connection Request Templates (300 chars max)

CIO/CTO — DFW Tier 1 (warm, after engagement)[First Name], saw your comment on [topic/post] — sharp take on [specific detail]. Working with a handful of Microsoft-first enterprises on the same shift from pilot to production. Would enjoy connecting.
Chief Data Officer / VP Data & Analytics[First Name], been following your posts on [Fabric / data governance / AI adoption]. Similar challenge shows up at most of the enterprise data teams I work with — comparing notes could be useful. Connect?
Executive move triggerCongrats on the [Role] move at [Company], [First Name]. First-90-days playbooks in Microsoft-heavy shops is exactly what we do at Lantern. Happy to share what's working with similar leaders. Connect?
Fabric / Copilot / Azure AI Foundry content trigger[First Name], [specific post reference]. The pattern you described shows up at most of the Fabric adoptions we see. Happy to share what's working at similar scale. Let's connect.

10.2 Day 1 — Thank You DM

Thanks for connecting, [First Name]. Quick question — what's your biggest focus this quarter around [AI adoption / data modernization / Copilot rollout]? Asking because we're seeing a sharp split in how teams are approaching it, and I'm curious where you land.

10.3 Day 3 — Value DM

[First Name], based on our brief exchange — thought this case study might be useful: [Link to most relevant Lantern case study — Banfield for healthcare, Apex Utilities for energy, Smoothie King for retail, Avocados From Mexico for CPG, Unifi for transportation] The part worth your time is on page 2 where [specific insight]. No strings — just thought it mapped to what you're navigating.

10.4 Day 5 — Voice Note Script (45–60 sec)

[Wave] Hey [First Name], [Your Name] here at Lantern. I noticed [specific observation — recent post, announcement, job posting]. Most [CIO/CDO] leaders I talk to in [their industry] are wrestling with the same thing — [pain point specific to persona]. We helped [named client — e.g., "Unifi drive a 20% reduction in safety incidents with AI" or "Smoothie King ship Fabric franchisee analytics in just 4 weeks"]. If that maps to what you're thinking about, I'd love 15 minutes. Either way, keep doing what you're doing — your recent post on [X] was sharp.

10.5 Day 10 — Video Message (45–75 sec, LinkedIn native)

[SHOW THEIR COMPANY'S LINKEDIN PAGE OR RECENT NEWS] [First Name], quick video for you. I was looking at [specific signal — job posting, news, earnings mention] at [Company] — [observation]. Most [role] teams in [industry] approach this by [common approach], but we've seen [better approach] deliver [specific result] faster. [SHOW RELEVANT CASE STUDY PAGE BRIEFLY] We recently helped [named client] go from [before] to [after — use verified numbers from Appendix B]. 15 minutes — I'll drop my calendar below.

10.6 Day 12 — Direct Ask

[First Name], circling back. The [CIO/CDO/Head of AI] leaders I've been comparing notes with this quarter are focused on [specific outcome — moving Copilot from licensed to adopted, getting first production AI agent shipped, tightening AI governance]. If that's on your radar — 15 minutes could surface some quick wins. [Calendar link] or happy to work around your schedule.

10.7 Day 15 — Breakup + Email Pivot

Subject: closing the loop[First Name], Wanted to close the loop on my LinkedIn outreach — no response usually means wrong timing, not wrong target. Here's a 4-page read on what separates AI adoption leaders from pilot-stuck organizations — might be useful either way: [link to Lantern case study or ebook] If the timing changes, I'm easy to find. Best, [Your Name] Lantern — From Vision to Value

11.Voice & Video Messaging — The Differentiators

Voice notes and video messages convert 3× better than text DMs. Everyone sends text. Almost nobody sends voice or video. The ones who do, stand out.

11.1 When to Use Video

ScenarioFormatWhy
Day 10 of sequenceScreen shareShows the seller did the homework
Lead score ≥ 80 (Hot)Face-to-cameraPriority targets deserve personal touch
Re-engagement (went cold)Screen sharePattern interrupt
Post-meeting follow-upFace-to-cameraRelationship building

11.2 Production Standards

Lantern Voice Standard for Video
Confident but not slick. Not scripted. Not salesy. Conversational, specific, brief. Treat it like a 45-second internal voice memo to a colleague you respect.

12.LinkedIn Signal Scoring

Every LinkedIn action on a target account rolls into the lead score in HubSpot, weighted alongside email and campaign signals.

12.1 Signal Catalog

SignalWeightScoreDecay
Profile view (single)Low+53 days
Profile view (repeat, 2+ in 7 days)High+207 days
Connection accepted by targetHigh+25
Reacted to our postMedium+157 days
Commented on our postCritical+3014 days
Voice note listened >30 secCritical+3014 days
Video viewed >50%Critical+3014 days
DM reply (positive)Critical+40
DM reply (neutral/question)High+25
DM reply (negative)N/A−20
Job change to target titleCritical+4090 days
Promotion to decision-makerCritical+3590 days
Webinar/event registrationHigh+2514 days

12.2 Score Threshold Actions

90–100 Hot
Immediate voice note + calendar link. Adam-approved.
70–89 Hot
Accelerate sequence, insert video message.
50–69 Warm
Standard 15-day sequence, monitor.
30–49 Cold
Light-touch nurture — reactions only.

13.Sales Navigator — The Five Lantern Personas

Prerequisite
Each Lantern seller participating in the pilot must hold an active LinkedIn Sales Navigator (Advanced or higher) license. Confirm licensing during the §17 launch checklist before the seller starts warm-ups.

Each of the five personas gets its own saved search. Sellers pull weekly from these.

1. The Technology Strategist

CIO • CTO • VP of IT — "AI pilots stalling; budget committed, value unclear"
Best proof: Smoothie King Fabric-in-4-weeks; Banfield 90% adoption. Meeting-direct within 15 days.

2. The Data & AI Visionary

CDO • CAO • VP Data & Analytics — "Data foundations fragmented; AI not tied to outcomes"
Best proof: nLight Cosmos; Banfield Power BI; Unifi 94% model accuracy. Framework-first, meeting within 20 days.

3. The Governance & Risk Guardian

CISO • CRO • VP Risk — "AI governance risk; compliance and fraud exposure"
Best proof: Healthcare payer fraud prevention — 7.5× more cases, $2.4M recovered year 1. Educate-heavy, meeting within 30 days.

4. The Innovation & Transformation Agent

Chief Innovation Officer • VP Strategy — "Need visible AI wins fast"
Best proof: Smoothie King 4-week Fabric; Unifi 20% safety reduction; Avocados From Mexico supply chain. Proof-first, meeting within 15 days.

5. The Business & Operations Executive

COO • EVP Ops • GM — "Operational efficiency, cost pressure, adoption reality"
Best proof: Unifi 20% safety reduction; Avocados 34.5 hrs saved/month; invoice automation. Outcome-driven, meeting within 20 days.

13.2 Account Alerts — Non-Negotiable

AlertAction
Job change (target persona title)Within 48 hrs — warm-up protocol initiated
Company news (funding, acquisition, earnings)Same-day — Adam notified, sequence accelerated
Content engagement by target personaWithin 24 hrs — comment or reaction
Profile update (new role, skills)Within 48 hrs — re-engagement trigger

14.Weekly Cadence — The 30-Minute Daily Block

14.1 Daily 30-Minute Block

TimeActivity
0–5 minReview PitchGhost finds from last 24 hrs
5–15 min10 profile views + 8 reactions on warm-up batch
15–25 min3 thoughtful comments on target persona content
25–30 minRespond to positive DM replies, log to HubSpot

14.2 Weekly Rhythm

DayDeep Work
MondayPost Challenge content + pull new warm-up batch
TuesdayWarm-up day 2 + send voice notes from day-5 cohort
WednesdayPost Educate content + warm-up day 3
ThursdayWarm-up day 4 + record video messages for day-10 cohort
FridayPost Proof content + review weekly KPIs + retro

15.Integration Points

15.1 PitchGhost → LinkedIn Action

Every morning at 8 AM ET, PitchGhost's DM Radar ghosts surface new finds. Seller workflow: open dashboard → filter by assignment → comment on relevant finds within 24 hrs → log in HubSpot → escalate high-value signals.

15.2 DFW Tier 1 Outbound → LinkedIn Warm-Up

Every new lead entering the campaign: seller adds to warm-up batch → warm-up runs 5 days ahead of email first touch → email response rates lift 2–5× when warm-up runs correctly.

15.3 HubSpot Integration — Specific Properties and Stages

Every LinkedIn action gets logged to HubSpot. The required configuration:

Custom contact properties

Custom activities

Deal-stage mapping

LinkedIn OutcomeDeal Stage Trigger
Connection acceptedCreate deal at "Engaged" stage (if account has no open deal)
Positive DM replyAdvance deal to "Qualified Conversation"
Meeting bookedAdvance deal to "Discovery Scheduled"
Meeting heldAdvance deal to "Discovery Completed"

Reporting view (Adam): HubSpot custom report "LinkedIn Pipeline" filtered by pilot sellers, grouped by deal stage, with linkedin_signal_score as secondary sort. Ben owns dashboard configuration.

15.4 Octave-Lantern → DM Drafting

During the pilot, sellers route DM drafting through Ben, who uses /octave:linkedin in the Octave-Lantern workspace. All AI-drafted DMs require human review — a Lantern non-negotiable. Post-pilot, Ben documents the prompting patterns for self-serve.

15.5 Microsoft Co-Sell Coordination

Lantern's 6× Solution Partner + Fabric Featured Partner status unlocks formal Microsoft co-sell motion. Social selling coordinates with it:

Microsoft SignalSocial Selling Response
Microsoft AE shares co-sell opportunitySeller runs §9 warm-up within 48 hrs — Microsoft AE becomes the warm intro bridge
MPP deal registration approvedSeller engages buying committee (Personas 1+2+4 multi-thread) citing the Microsoft engagement
Microsoft event attendance (Ignite, Inspire, Fabric Summit)Day-of LinkedIn engagement with their event post; post-event connection request
Microsoft customer story for a competitive accountComment on the story, then connection request to the mentioned contact
Do not double-cover
If a Microsoft AE is actively working an account, coordinate with them before social-selling into the same contacts. Adam owns deconfliction — surface Microsoft-owned accounts in the Friday dashboard.

16.Human-in-the-Loop

ActionAutomationRationale
Profile viewsSeller-executed, systematicLow-risk, high-volume
ReactionsSeller-executedLow-risk
CommentsAlways manual, never templatedQuality and authenticity matter
Connection requestsBatch-reviewed, seller-approvedTemplate-based but personalized
Text DMsBatch-reviewed, human-approvedTemplate-based but personalized
Voice notesAlways manually recordedPersonal delivery is the point
Video messagesAlways manually recordedPersonal delivery is the point
Meeting schedulingHuman-managedRelationship continuity

17.Verification Checklist

Before any Lantern seller launches, Adam (or Ben) signs off on every checkbox:

Licensing & Access

Profile Readiness

Targeting Quality

Sequence Readiness

Tracking Setup

Content Readiness

Microsoft Co-Sell Coordination

Part 3 — Appendices

A.Persona-to-Content Matrix

PersonaPrimary PainBest Proof Point (Verified)CTA Cadence
Technology Strategist (CIO/CTO)AI pilots stalling; budget committed, value unclearSmoothie King Fabric in 4 weeks; Banfield 90% associate endorsementMeeting-direct within 15 days
Data & AI Visionary (CDO/CAO)Data foundations fragmented; AI not tied to outcomesnLight Cosmos; Banfield Power BI; Unifi 94% model accuracyFramework-first, meeting within 20 days
Governance & Risk Guardian (CISO/CRO)AI governance risk-laden; compliance exposureHealthcare payer fraud prevention — 7.5× more cases, $2.4M uncovered year 1Educate-heavy, meeting within 30 days
Innovation & Transformation AgentNeed visible AI wins fastSmoothie King 4-week Fabric; Unifi 20% safety reduction; Avocados From MexicoProof-first, meeting within 15 days
Business & Operations Executive (COO)Operational efficiency, cost pressure, adoptionUnifi 20% safety reduction; Avocados 34.5 hrs saved/monthOutcome-driven, meeting within 20 days

B.Case Study Proof Point Library

Lantern's 33 case studies organized two ways: by industry (B.1) and by practice area (B.2). All quantified numbers sourced from case study content.

B.1 By Industry

Healthcare / Life Sciences

Manufacturing / Industrial

Financial Services

Retail / Consumer

Energy / Utilities

Cross-Industry

B.2 By Practice Area

Match a practice-area lane to its strongest proof points.

Practice AreaTop Proof Points
AI FoundationsUnifi (Azure ML/Databricks/ADLS platform), nLight Cosmos, Modern Data Architecture
AI StrategyBuilding Organizational Alignment for AI; Microsoft 365 Copilot Foundation
Agentic DevGenerative AI Project Management
Azure AI AppsLeading Consumer Brand (Azure modern web app), Digital Empathy
Copilot & Business AppsAvocados From Mexico, Little Potato Company, Comprehensive Copilot Deployment, Grant Compliance
Data & AISmoothie King (Fabric in 4 weeks), Banfield (90% adoption), Unifi (94% model accuracy), Healthcare Payer Fraud
GitHubEmerging practice area — new case studies Q2 2026
Modern WorkApex Utilities (1.5 TB migration), Employee Experience Digital Transformation
OCM / AdoptionBanfield (90% endorsement), Building Organizational Alignment for AI, Comprehensive Copilot Deployment

C.Objection Handler Library

When a prospect replies with an objection, do not improvise. Reach for a proven response.

"We're already working with [other Microsoft partner / Big 4 / large SI / global consultancy]."

Understood — most of our best clients started with someone else. The question worth asking is whether they're embedded in your team the way a studio model requires, or whether they're delivering against a statement of work. The difference shows up at week 12, not week 4. Happy to share a 90-day Fabric outcome from [similar client] if it's useful.

"We don't have budget this quarter."

Fair — and most of the teams we're working with right now are in exactly the same spot. The reason we're having the conversation is because the investments made in Q3/Q4 need visible value in Q1. That's usually where we come in. Not pitching a project — just thinking the same thing through with you.

"We built this in-house / we have our own team."

Good — that's the right starting point. The clients we add the most value to are the ones with strong internal teams who need senior co-delivery on the parts that are either new (agentic dev, Fabric semantic modeling) or politically complex (AI governance, org change). Never a replacement, always an accelerator.

"Not a priority right now."

Got it. What is a priority — for the end of this quarter, specifically? I'll stop pushing on AI and see if there's anywhere else we can be useful, or I'll leave you alone. No wrong answer.

"Send me some information."

Happy to — but the specific case study that's going to land for you depends on what you're actually navigating. 2-question reply: industry + AI maturity stage, and I'll send the one that's genuinely relevant instead of the generic deck.

"Call me in [6 months / next year]."

Done — putting it on my calendar for [specific date]. Between now and then, if something shifts, I'm easy to find. I'll also drop a useful read into your DMs once a month until then — no ask attached.

"Not the right person — talk to [X]."

Thank you — I'll reach out to [X]. Before I do, one quick thing: on a scale of 1–10, how much does [the core pain point] actually show up in your world? Asking because decisions usually involve a committee, and I want to make sure I'm not missing your perspective before I go to [X].

D.90-Day Launch Timeline

Weeks 1–2 — Foundation (Cohort 1: 2 sellers)

Weeks 3–4 — Soft Launch (Cohort 1 live; Cohort 2 onboards)

Weeks 5–8 — Scale (All cohorts live)

Weeks 9–12 — Optimize + Govern

E.Tool Stack Reference

ToolPurposeOwnerPrerequisite
LinkedIn Sales Navigator (Advanced+)Targeting, saved searches, account alertsEach sellerActive license required before warm-up begins
LinkedIn Premium BusinessProfile views without limits, DM reachEach sellerActive license required
PitchGhostAutomated signal monitoring on target profiles and companiesAdam (admin), each seller (assigned leads)Seat active before week 1
DFW Tier 1 Outbound PlatformActive outbound email sequenceBen (admin), sellers (inbox)Inbox assignments confirmed
HubSpotCRM, LinkedIn signal logging, deal stagesBen (admin), each sellerCustom properties configured per §15.3
Octave-LanternAI-assisted DM drafting, persona libraryBen (admin); sellers route through Ben during pilotWorkspace access confirmed
LinkedIn native videoVideo message recording (primary)Each sellerNo setup required
GTMify Optimization LoopWeekly A/B testing, script iterationGTMify pilot; handoff to Ben post-pilotSlack channel set up