Harshit Singh's LinkedIn GTM Strategy for Samora
Author: Harshit Singh
Role: Fractional GTM Engineer
This document outlines my LinkedIn GTM strategy for Samora. My objective is to position Samora as the category leader in enterprise voice AI, generate qualified pipeline, and create a repeatable founder-led demand generation engine that converts LinkedIn attention into enterprise demos and revenue opportunities.
How I Will Execute:
1. Build ICP-specific content for Operations, CX, Support, Revenue, and Growth leaders.
2. Turn customer proof points (UNICEF, Signify, Government of India) into demand-generation assets.
3. Run founder-led distribution and engagement loops.
4. Deploy lead magnets and comment-to-DM workflows.
5. Track content-to-DM, DM-to-demo, and demo-to-opportunity conversion.
6. Create a repeatable LinkedIn revenue engine focused on enterprise pipeline generation.
HARSHIT SINGH'S LINKEDIN GTM STRATEGY
Business context
- What they sell: I voice agents for high-volume inbound and outbound calls. You describe call flows and goals in plain language; Samora handles agent design, testing, integrations, deployment, monitoring, and human escalation. Natural, low-latency conversations across 20+ languages with interruption handling and code-switching, plus CRM writeback and omnichannel coordination (voice, WhatsApp, SMS, email). Go live in ~1 week. Enterprise-grade: 99.99% uptime, encrypted data, no model training on customer data. Pricing is custom/sales-led (book a demo) — not self-serve. YC-backed.
- Who they sell to: Heads of Operations, CX, and Support — plus growth and revenue leaders — at organizations running high call volume who can't staff a call center for it: fintech/financial services, healthcare, large enterprises, and mission-driven orgs (Samora's track record includes Signify/Philips, UNICEF, and Government of India). Sweet spot: teams hitting a wall with manual dialing or expensive call-center ops, especially across multilingual, low-connectivity, or low-literacy audiences.
- The #1 pain they solve: Teams can't talk to enough people. Manual dialing and limited call-center capacity cap how many stakeholders, customers, or beneficiaries they can reach — and language barriers make it worse. Building reliable voice AI in-house means heavy engineering, endless prompt tuning, and the fear that an agent will go off-script with no safe handoff.
- Their proof: Over 1M calls handled, trusted by Signify (Philips), UNICEF, and Government of India. Signify used Samora to reach thousands of stakeholders instantly and reactivate dormant users; UNICEF reached low-connectivity, low-literacy beneficiaries in their own languages to surface career and upskilling opportunities. 99.99% uptime, live in one week.
- Current LinkedIn status: Company page at linkedin.com/company/samora-ai. Draft to edit: ~X followers, posting ~1–2x/week. Likely pattern for this category: customer-impact stories (UNICEF/Signify) and live agent demos outperform; generic "AI is the future" posts flop. Founder posts > company page.
- Weekly time budget for LinkedIn: Placeholder: ~3–5 hours/week including first-hour engagement.
- #1 goal in 90 days: Placeholder to set: e.g. "12 qualified enterprise demos booked from LinkedIn" or "5 pilot conversations with target-account ops/CX leaders." Pick the metric tied to your sales-led motion.
========================================
SECTION 1 — ICP & AUDIENCE BREAKDOWN
### Primary ICP: The Ops/CX Leader at a Call-Volume-Constrained Organization
Titles: Head of Operations, VP of Customer Experience, Director of Support, Head of CX, Country Operations Lead, Head of Field Operations
Industries: Fintech and financial services (lending, insurance, payments), healthcare and healthtech, large enterprise (manufacturing, utilities, FMCG), development-sector organizations (NGOs, multilateral agencies, government programs)
Company profile: 200–5,000 employees; running or needing to run 10,000+ calls/month; operating across 2+ languages or geographies; likely has a CRM (Salesforce, HubSpot, Zoho) and a patchwork of manual dialing, BPO contracts, or an overwhelmed in-house team
What their week looks like:
- Escalating to a BPO vendor about missed SLAs or ballooning per-call costs
- Sitting in a sprint review watching engineering reprioritize the "voice bot project" for the fourth quarter in a row
- Fielding complaints that agents aren't reaching beneficiaries or customers in their preferred language
- Pulling a manual dialing report and doing the math on how many people simply never got called
What keeps them up at night:
- "We have a list of 50,000 people we need to reach and a team that can handle 400 calls a day"
- An AI agent going off-script on a loan repayment call or a patient follow-up with no safe way to hand off
- Compliance and data exposure risk from using a third-party AI they don't control
- Launching in a new market where three languages are spoken and the literacy rate is low
- Building something in-house that takes 18 months and still sounds robotic
What they've already tried:
- IVR systems that customers hang up on in the first 10 seconds
- BPO contracts that don't scale and spike in cost during peak periods
- Internal ML/engineering builds that stall in QA, never handle interruptions correctly, and have no escalation logic
- Off-the-shelf chatbots that can't handle voice, accents, or mid-sentence language switches
The exact language they use (mirror these phrases in content):
- "We can't reach enough people"
- "Our agents are drowning"
- "The BPO is too expensive and too slow to stand up"
- "We need to be in [language] and we don't have agents who speak it"
- "I don't want to build this in-house again"
- "What happens when the bot gets confused?" (escalation anxiety)
- "We went live and it was a disaster" (prior AI failure)
Where they hang out on LinkedIn:
- Commenting on CX thought leaders (Shep Hyken, Jeanne Bliss tier)
- Following UNICEF, WHO, and multilateral org accounts if development-sector
- Engaging with fintech operator communities and revenue/growth leader content
- Posting about team wins, operational challenges, and market expansion moments — not technology for its own sake
### Secondary Audience 1: Growth and Revenue Leaders
VP Sales, Head of Revenue, Chief Growth Officer at the same companies — they care about outbound call capacity as a pipeline lever and dormant-user reactivation, not support cost. Attract them with ROI framing: reactivated revenue, conversion rates on outbound campaigns, cost-per-contacted lead.
### Secondary Audience 2: Implementation and Transformation Partners
SIs, BPO operators, and digital transformation consultancies who already have a relationship with the buyer. They refer and co-sell. Attract them with proof-of-deployment content — integration depth, go-live timelines, and case studies they can hand to their own clients.
SECTION 2 — POSITIONING ANGLES
### Angle 1: The "Live in a Week" Operator
Core claim: Enterprise-grade voice AI that your ops team can deploy in days — not the 6-month engineering project your last vendor promised.
Broken status quo it positions against: The default path for any organization serious about voice AI is a multi-month build: procurement, integration sprints, prompt engineering cycles, and still no guarantee the agent won't go off-script on a customer. Most teams quietly abandon it or settle for a basic IVR.
Why the proof backs it up: Samora has absorbed that entire build burden — agent design, testing, integrations, monitoring, human escalation — for organizations operating at the scale of Signify/Philips and UNICEF. One million calls handled without the customer owning the engineering complexity. "Live in one week" isn't a marketing claim; it's the delivery model.
One-line LinkedIn bio: We deploy enterprise voice AI in a week — your ops team describes the call flow, Samora handles everything else.
### Angle 2: The Reach Multiplier for Teams Hitting a Capacity Wall
Core claim: Your call center can't grow fast enough to reach everyone who needs a conversation. Samora handles the volume your team physically can't.
Broken status quo it positions against: High-volume outreach gets capped by headcount, shift schedules, and the cost of multilingual agents. Most orgs either under-reach their audience or burn budget on outsourced call centers that can't handle code-switching, low-connectivity lines, or low-literacy callers.
Why the proof backs it up: UNICEF used Samora to reach beneficiaries in their own languages across low-connectivity environments — audiences a traditional call center would deprioritize or miss entirely. Signify reactivated dormant users at scale. These aren't pilots; they're production deployments on humanitarian and enterprise infrastructure.
One-line LinkedIn bio: Samora handles the calls your team can't — 20+ languages, 1M+ calls delivered, trusted by UNICEF and Signify.
### Angle 3: The Anti-Hallucination Voice Stack for Regulated Industries
Core claim: Voice AI for fintech, healthcare, and large enterprises has to stay on-script, hand off cleanly, and never train on your customers' data. Most platforms can't promise all three.
Broken status quo it positions against: General-purpose LLM wrappers pitched as "voice agents" are unacceptable in regulated contexts — unpredictable outputs, unclear data handling, no reliable escalation path. Compliance and CX leaders in fintech and healthcare either block AI adoption entirely or run small experiments that never reach production.
Why the proof backs it up: 99.99% uptime, encrypted data, zero model training on customer data, and a human escalation layer built into the architecture — not bolted on. Samora's track record includes government-scale deployments (Government of India), where failure is not an option.
One-line LinkedIn bio: Enterprise voice AI for regulated industries — on-script, encrypted, no data training, with human escalation built in.
### Lead with Angle 2.
Angle 2 speaks the language of the buyer's immediate, felt pain — ops and CX leaders aren't lying awake thinking about compliance architecture; they're thinking about the calls that aren't getting made and the pipeline or service gap that creates. "You can't reach enough people" is a budget conversation already happening in their org. Angles 1 and 3 become the proof layer once that door is open.
SECTION 3 — CONTENT PILLARS (SLAY FRAMEWORK)
### Pillar 1: Authority — Deep Expertise in Voice AI at Scale
Goal: Position Samora as the team that has already solved the hard problems (latency, multilingual handling, safe escalation, CRM integration) so ops/CX leaders trust the engineering before they trust the pitch.
Frequency: 1x/week
- "The 3 reasons voice AI fails in multilingual markets — and why low-latency + code-switching matter more than accent accuracy"
- "What most teams get wrong when building inbound call flows: writing scripts instead of designing conversation states"
- "How we handle interruptions in a voice agent without the call falling apart — a technical breakdown in plain English"
- "Human escalation isn't a failure mode. Here's how we design it as the safest moment in every call flow"
- "Why 99.99% uptime for voice AI is harder than for SaaS — and what enterprise ops leaders should actually ask vendors about it"
### Pillar 2: Proof — Client Results and Behind-the-Scenes Wins
Goal: Make the ROI tangible. Show that real organizations with real scale — UNICEF, Signify, Government of India — trusted Samora with their most sensitive stakeholder conversations.
Frequency: 1x/week
- "UNICEF needed to reach low-literacy beneficiaries across languages with no reliable internet. Here's how a voice agent did it at scale"
- "Signify had thousands of dormant users they couldn't afford to call manually. We reactivated them in days — not quarters"
- "1 million calls handled. The thing that surprised us most wasn't the volume. It was what people said when they felt heard in their own language"
- "From brief to live in 7 days: what our deployment week actually looks like inside a fintech ops team"
- "The Government of India needed call reliability in low-connectivity regions. What we built, and what we learned"
### Pillar 3: Problem-Awareness — Make the ICP Feel the Ceiling
Goal: Surface the exact frustration ops and CX leaders feel before they know Samora exists — the gap between call volume needed and call volume possible.
Frequency: 1x/week
- "If your team is manually dialing to reach customers at scale, you're not doing outreach. You're doing triage."
- "The hidden cost of a call center that only speaks two languages serving a customer base that speaks eight"
- "Your NPS is fine. Your reachability isn't. The customers you never connect with don't leave reviews — they just leave."
- "Every ops leader building voice AI in-house eventually hits the same wall: prompt drift, no safe handoff, and a six-month timeline that becomes twelve"
- "The math on manual outbound calls breaks at 10,000 contacts. What are organizations supposed to do above that threshold?"
### Pillar 4: Personal/Story — Trust Through Founder Perspective (SLAY Format)
Goal: Build the human credibility behind the product. Buyers at the enterprise level invest in teams as much as tools.
Frequency: 1x/week
- Story: "We almost lost a client because our agent went silent for 400ms mid-sentence. Here's what that taught us about what 'natural conversation' actually means." — Lesson: latency is emotional. Action: what to benchmark before deploying. You: What threshold do you hold your vendors to?
- Story: "A UNICEF program officer told us the agent worked because it didn't sound like a robot trying to be human." — Lesson: trust in voice AI is built through restraint, not mimicry. Action: design for the listener, not the demo. You: What would it mean if your most underserved customers felt genuinely heard?
- "The week we went live with a government deployment and the thing that nearly broke wasn't the tech"
- "Why I stopped describing what Samora does as 'AI voice agents' in sales calls — and what changed when I did"
- "What building for UNICEF taught us about designing voice AI for humans who've never trusted a phone call from an unknown number"
SECTION 4 — LEAD MAGNET IDEAS
### 1. "The Voice AI Vendor Scorecard"
Format: Checklist / evaluation template
Why they comment: Ops and CX leaders evaluating voice AI are drowning in vendor claims. A structured scorecard that covers uptime SLAs, latency benchmarks, multilingual handling, human escalation logic, and CRM integration requirements gives them a defensible framework to bring to procurement — and makes Samora's strengths the evaluation criteria.
Comment-to-DM mechanic: Post a stat about vendor evaluation failures ("Most teams evaluate voice AI on demo quality, not production readiness. Here's the 12-point scorecard we built from 1M+ calls across enterprise deployments. Comment SCORECARD and I'll send it over.")
### 2. "Call Flow Design Prompt Pack for Inbound & Outbound"
Format: Prompt template / swipe file
Why they comment: The #1 fear holding ops leaders back from voice AI is going off-script with no safe handoff. A ready-to-use set of call flow prompts — for appointment reminders, collections nudges, beneficiary outreach, dormant user reactivation — removes the blank-page problem and signals: you don't need engineering to start this.
Comment-to-DM mechanic: "We've designed call flows for UNICEF beneficiary outreach, Signify dealer reactivation, and government health programs. Here are 8 copy-paste flow prompts your team can hand off today. Comment FLOWS."
### 3. "The Hidden Cost Calculator: Manual Dialing vs. Voice AI"
Format: Calculator (Google Sheet)
Why they comment: Growth and revenue leaders respond to numbers. A pre-built model showing cost-per-contact at scale — factoring in agent hours, language coverage, call abandonment rates, and missed-reach costs — creates urgency without a sales pitch. It also pre-qualifies: anyone who fills it in knows their call volume.
Comment-to-DM mechanic: "If your team is making more than 5,000 calls a month manually, this calculator will show you the exact cost of not automating. Comment CALCULATE and I'll send the sheet."
### 4. "Multilingual Voice AI Readiness Checklist"
Format: Checklist / mini-guide
Why they comment: Leaders operating across language markets — fintech in Southeast Asia, healthcare in India, NGO programs in Sub-Saharan Africa — have been burned by AI that fails on accents, code-switching, or low-connectivity lines. This checklist (covering language coverage, interruption handling, fallback behavior, and data sovereignty) speaks directly to the operational anxiety they can't articulate to a vendor.
Comment-to-DM mechanic: "Before you deploy any voice agent in a multilingual market, run through this 10-point checklist. We built it from deployments in 20+ languages across low-connectivity environments. Comment MULTILINGUAL."
### 5. "The One-Week Voice AI Launch Plan"
Format: Mini-guide / project template
Why they comment: "Going live in one week" is a credibility claim that sounds too good. This resource makes it tangible — a day-by-day breakdown of what Samora handles (agent design, integrations, testing, escalation setup) versus what the client team owns (use case brief, CRM access, approval sign-off). It deflates implementation fear and makes the first demo conversation dramatically easier.
Comment-to-DM mechanic: "Most teams assume voice AI takes 3–6 months to deploy. Here's the exact week-one plan we run with enterprise clients from kickoff to live calls. Comment LAUNCH and I'll send it over."
SECTION 5 — FUNNEL & CTA STRATEGY
### Stage 1: Content (Awareness → Credibility)
Conversion goal: Get the right ICP scrolling past to stop, read, and follow.
Post ratio: 5 value posts for every 1 promotional post.
Value post types that work for Samora's buyers:
- "We handled 1M calls so your ops team doesn't have to" — proof-led, number-forward
- Specific failure modes buyers recognize: "Your agents can't cover 3am calls in Swahili. Ours can."
- Before/after call center cost vs. Samora deployment (Signify or UNICEF as the anchor)
- Myth-busting: "Voice AI goes off-script and there's no handoff" — here's how we prevent that
- Short-form case vignettes: what UNICEF was trying to do, what was blocking them, what changed in week one
CTA style: Soft. End posts with an observation or a question — "Most ops leaders we talk to don't realize this is the bottleneck until Q4 hits" — not a demo link. Save links for DMs and comments by request.
### Stage 2: Engagement (Credibility → Conversation Signal)
Conversion goal: Surface warm buyers through comments, saves, and DM triggers.
Tactics:
- Use comment-gated CTAs on high-signal posts: "Comment 'CALLS' and I'll send you the exact call flow we used for the Government of India rollout" — this filters for active interest, not passive scrollers
- Reply to every comment within the first hour; the founder's replies are where deals start
- Post a poll quarterly: "What's your biggest blocker for scaling outbound? (a) Staffing (b) Language coverage (c) Compliance (d) Cost" — each option is a Samora pain point and each voter is a lead signal
CTA style: Comment-gated and curiosity-driven. No hard pitches in the feed.
### Stage 3: DM (Conversation → Qualification)
Conversion goal: Move a warm signal into a 10-minute discovery exchange.
The DM playbook:
- Trigger: someone comments, saves, or polls → send within 2 hours
- Opening line references their specific signal: "Saw you voted staffing as your top blocker — that's exactly where most of our fintech and healthcare customers were before we went live with them"
- One qualifying question: "Are you running high-volume inbound, outbound, or both right now?"
- If they engage: deliver the promised asset, then ask "Would a 20-minute call to walk through what this looked like for [Signify/UNICEF] be worth your time?"
Pitch frequency: One soft ask per DM thread. No follow-up pitch if they don't respond to the first.
### Stage 4: Call (Qualification → Demo)
Conversion goal: Book a scoped demo with the right title (Head of Ops, CX, or Support; occasionally a growth lead).
CTA style: Hard. A direct Calendly link with a one-line frame: "20 minutes — we'll show you exactly how the agent handles a live call in your language, your use case."
### Stage 5: Close (Demo → Pilot Conversation)
Conversion goal: Convert demo to a scoped pilot proposal within two weeks.
Content role here: Post one win per month — anonymized if needed — so prospects in late-stage conversations see momentum and don't stall on "we need to see more proof."
SECTION 6 — DM CONVERSION WORKFLOW
### Opening Message (Post Comment → DM)
Hey [Name] — saw your comment on the [post topic]. Sending over that [lead magnet name] now. Lmk if it sparks any questions.
### Delivery Message
Here you go: [link]
Quick context: this was built from what we've seen across 1M+ calls — fintech, healthcare, orgs like UNICEF and Signify. The multilingual / low-connectivity stuff on page [X] tends to hit closest to home for ops and CX teams.
No action needed — just wanted it to be useful.
### 3-Touch Follow-Up Sequence (Days 2, 4, 7)
Day 2
Curious if anything in there reflected what you're dealing with — specifically around call volume or the language coverage piece. We've seen those two show up together a lot for teams in [their vertical].
Day 4
One thing I didn't include in that doc: how Signify used this to reactivate dormant users at scale — literally thousands of outbound calls in days, no added headcount. Happy to share the short version if that's relevant to what you're working on.
Day 7
Last nudge on this — didn't want to let it go cold without asking. If the timing's off or it's not the right fit, totally fine to say so. No hard feelings either way.
### Qualifying Questions (Before Pitching a Call)
Drop these one at a time, conversationally — never as a list:
- "What does your current outbound or inbound call setup look like — are you running an internal team, outsourced, or some mix?"
- "Roughly how many calls are you trying to handle — or trying to avoid not handling?"
- "Is the multilingual side a real constraint for you, or is this mostly single-language?"
- "Is building something in-house on the table, or are you looking for something you can hand off?"
### Transition Line to Book the Call
Once they've confirmed volume, pain, and that in-house isn't the answer:
"Sounds like it might be worth 20 minutes — I can show you exactly how the agent handles [their specific use case] live, and you'd leave knowing whether this is even in the right ballpark for you. No deck, no pitch. Want me to send a link?"
### Handling 'Not Right Now'
If they say timing is off:
"Totally fair — this stuff usually lands when a specific problem forces the conversation. When it does, feel free to come back to this thread. I'll remember the context."
If they say they're evaluating options:
"Makes sense. One thing worth knowing: most teams we talk to have already tried building something internally or with another vendor and hit a wall on the handoff logic or language coverage. If that comes up in your eval, happy to be a second opinion."
If they go quiet after day 7:
"Archiving this for now — but if call volume or language coverage becomes a bigger problem in Q[next quarter], happy to pick it back up."
SECTION 7 — 90-DAY CONTENT ROADMAP
### Month 1 — Authority + Audience (Weeks 1–4)
Milestone: Establish Samora as the go-to voice for "can't-staff-a-call-center" ops and CX leaders. Target 10+ meaningful comments per post from ICP profiles.
Weeks 1–2 — Foundation Posts
- Mon: Pain post — "We ran the numbers: a 500-agent call center still can't dial 1M people in a week. Here's what actually does." (ops/CX audience hook)
- Wed: Proof post — Signify/Philips story: dormant user reactivation at scale, quantified. No fluff, just the outcome.
- Fri: Perspective post — Why building voice AI in-house breaks teams (engineering drag, prompt chaos, no safe handoff). End with what to look for instead.
- Engagement hour: DM everyone who comments with a thoughtful question, not a pitch.
Weeks 3–4 — Credibility Depth
- Mon: Proof post — UNICEF: reaching low-literacy, low-connectivity beneficiaries in their own languages. Frame for healthcare/NGO/government buyers.
- Wed: First lead magnet drop — "The 7 questions ops leaders ask before deploying a voice agent" (PDF or native carousel). Gate via DM reply: "Comment VOICE and I'll send it." Captures warm ICP contacts.
- Fri: Founder post — Why Samora goes live in one week when in-house builds take quarters. Specifics on what "full deployment" actually includes.
### Month 2 — Lead Magnets + DM Volume (Weeks 5–8)
Milestone: 50+ DM conversations started with ICP titles (Head of Ops, Head of CX, Head of Support, Growth/Revenue leads at fintech, healthcare, large enterprise).
Weeks 5–6 — Use-Case Expansion
- Mon: Pain post — Multilingual call centers are expensive and still miss languages. Frame the code-switching and 20+ language capability as a cost and coverage story.
- Wed: Second lead magnet — "Voice agent call flow template for high-volume inbound triage" (fintech or healthcare version). DM-gated.
- Fri: Proof post — Government of India case. Frame for public sector and large-enterprise buyers evaluating uptime and compliance.
Weeks 7–8 — Objection Busting
- Mon: Myth post — "Voice AI goes off-script and you can't stop it." Walk through Samora's human escalation layer and monitoring in plain language.
- Wed: Third lead magnet — "Build vs. buy checklist: what it actually costs to build a voice agent in-house." Targets the ICP already mid-evaluation.
- Fri: Social proof compilation — Pull 3–5 real outcomes (calls handled, languages deployed, time to go live) into a single credibility post.
### Month 3 — Pipeline Conversion + Scale (Weeks 9–12)
Milestone: 8–12 qualified demo calls booked directly from LinkedIn activity.
Weeks 9–10 — Demo Conversion Push
- Mon: Outcome post — "What happens in the first week after a team deploys Samora." Walks the deployment timeline. Ends with a soft CTA: "Curious what your call flow would look like? Let's map it."
- Wed: Live demo clip or agent audio snippet — Real call, real language, real interruption handled. This format outperforms everything else in this category.
- Fri: ICP-specific post — Rotate by vertical (fintech week, healthcare week). Speak the buyer's exact language: "claims intake," "loan collections," "patient reminders."
Weeks 11–12 — Double Down
- Audit which posts generated DM volume and demo requests. Repost the top performer with a new angle.
- Run a direct CTA post: "We have capacity for 3 new deployments this quarter. Here's what the onboarding looks like."
- Fourth lead magnet (optional): ROI calculator framed around replacing or augmenting call-center headcount.
SECTION 8 — KPI TARGETS & GROWTH MILESTONES
### Baseline Assumptions
Estimated starting point: ~200–500 followers, 1–2 posts/week, no structured outreach. Sales motion is demo-led; one booked call with a Head of Ops, CX, or Support at a fintech, health system, or large enterprise is worth more than 1,000 impressions.
90-day goal: 12 qualified enterprise demos booked directly from LinkedIn activity.
### Month 1 — Establish Signal (Weeks 1–4)
Focus: prove what content stops the right buyers and build a warm outbound list.
- Impressions per post: 1,500–4,000 (organic; founder posts should outperform company page 3–5x)
- Profile views (founder): 80–150/week by week 4
- Follower growth: +75–150 net new, skewed toward ICP titles (ops, CX, support, revenue leaders)
- Comments on a case study post (UNICEF or Signify angle): 15–30 meaningful comments, not emoji reactions
- DMs started (outbound + inbound combined): 20–35
- Discovery calls booked: 2–3
- Close rate assumption: Not meaningful yet — focus is pipeline entry, not conversion
### Month 2 — Deepen Reach, Qualify Intent (Weeks 5–8)
Focus: convert content engagement into booked demos through a repeatable DM sequence.
- Impressions per post: 4,000–9,000 (one post should break out if the "1M calls / 1 week to live" proof point is framed correctly)
- Profile views (founder): 150–250/week
- Follower growth: +150–250 net new
- Comments on a lead magnet post (e.g., "how we built a multilingual voice agent for UNICEF"): 25–50
- DMs started: 40–60 (inbound interest plus warm outbound to post engagers)
- Discovery calls booked: 4–5
- Pipeline from LinkedIn: 5–7 active opportunities in CRM
### Month 3 — Convert Pipeline (Weeks 9–12)
Focus: hit the 12-demo target, tighten ICP, and prove repeatable CAC from LinkedIn.
- Impressions per post: 7,000–15,000 (one viral moment is possible if a live agent demo clip lands)
- Profile views (founder): 200–350/week
- Follower growth: +200–300 net new
- Comments per high-intent post: 40–70
- DMs started: 55–80
- Discovery calls booked: 5–6 (cumulative: 12–14 across 90 days)
- Demo-to-proposal rate assumption: 30–40% — these should be pre-qualified ops/CX leaders at 500+ person orgs with a live call-volume problem
### 3 Weekly Leading Indicators to Track
- Founder profile views from ICP titles — if ops/CX/support leaders are landing on the profile, content is reaching the right feed; below 80/week in month 2 means distribution is broken
- DM reply rate on outbound sequences — target 20–30%; below 15% means the hook isn't connecting pain (manual dialing ceiling, multilingual gap) to their world
- Post saves + shares on proof-point content — saves signal intent-to-revisit more reliably than likes for a considered B2B purchase
### Double Down vs. Change Course
Double down when a UNICEF, Signify, or Government of India story generates 20+ comments from ICP titles within 48 hours — repackage that exact proof point in three more formats immediately.
Change course if by the end of week 6 you have fewer than 4 DM conversations in flight and zero demos booked — the problem is almost certainly outbound volume or ICP targeting, not content quality.