LinkedIn Market Persona Journeys

Summary: This document maps how the nine personas (a–i, per linkedin-market-index.md §Personas) actually traverse the LinkedIn tool market, using the kimi-k3-reviewed JTBD analysis (jtbd-analysis.md) as the primary input and the five cluster research files (A–E) as the raw material. It defines a 5-stage journey framework (Find → Send → Engage → Publish → Compound), maps the 17 canonical jobs (J1–J17, per jtbd-analysis.md §3) onto those stages, then walks each persona through the stages it actually traverses — with the jobs hired for, the tools that serve them (entry price + compliance method), the persona’s switching criteria, and the failure point where the market fails them. Cross-persona synthesis shows Send and Find are overcrowded red oceans while Compound is the market’s structurally abandoned stage (J10 has 0 dedicated tools; J11 has 1). The GrowReach opportunity map closes the document: GrowReach’s comment-gen + Unipile posting (J8 + J6) already sits inside the Engage and Publish stages; the least-friction extension is completing the Engage loop (first-hour engagement + lead detection, per jtbd §6 #1), and the recommended target journey is persona (f) SMB marketing team traversing Publish → Engage → Compound at the (f)×(i) intersection — the J10 slot the cluster-E research calls “GrowReach’s clearest slot” (per cluster-E takeaway #4).

---

1. The Journey Framework

The LinkedIn tool market is not a single pipeline. Five distinct stages emerge from the JTBD layer (jtbd-analysis.md §2) and the job-density map (jtbd-analysis.md §3). Each stage is defined by the job being hired for, the pain that motivates the hire, and the success metric that closes the hire. Not every persona traverses all five stages — most live in 2–4 (see §3 for the convergence map).

Stage definitions

Stage	What it means for a LinkedIn user	Job (from jtbd §2 verbatim JTBD language)	Pain	Success metric
1. Find	Build clean, verified, fresh prospect/candidate lists and capture buying signals before any outreach	”Turn hours of prospecting into minutes” (cluster-A #1 Apollo); “only pay for valid emails” (cluster-A #5 Wiza); “capture niche signals, monitor real-time activity” (cluster-A #12 PhantomBuster)	Stale databases, CSV hell, bounce waste, no fresh intent	List quality: verified emails/phones, bounce rate near zero, fresh signals per week
2. Send	Execute outreach: connection requests, messages, follow-up sequences, multichannel (LinkedIn + email), AI-personalized copy — and, for agencies, run this across many client accounts	”Reach and exceed quotas” (cluster-C #2 Expandi); “Auto-follow up until prospects reply” (cluster-B #8 Waalaxy); “10x your LinkedIn outbound. Unlimited senders, one fixed cost” (cluster-C #1 HeyReach)	Manual sequences burn nights/weekends; follow-ups get lost; accounts get restricted	Replies/meetings booked; reply detection; account survival
3. Engage	Get the critical first-hour engagement that triggers the algorithm, manage the comment inbox, convert comments into pipeline, and communicate with personality intelligence	”put your content in front of the algorithm in the first hour” (cluster-E #3 Linkboost); “turn engagement into opportunities” (cluster-D #3 SayWhat); “Understand the person behind the résumé” (cluster-A #8 Crystal)	Posting into silence; comments going unanswered; engagement not converting	First-hour engagement velocity; replies-to-leads conversion; 2–3× reach
4. Publish	Create voice-true content, schedule and post it consistently, on a connection that won’t get the account banned	”sound like yourself” (cluster-D #1 Kleo); “Go from idea to published post in minutes” (cluster-D #1 Kleo); “Queue a week in one sitting” (cluster-D #4 FeedBoss)	Inconsistent posting; robotic voice; ToS risk from cookie-automation	Posts/week at consistent cadence; voice authenticity; compliant connection
5. Compound	Turn individual activity into organizational leverage: employees amplify the brand (advocacy), or an autonomous agent runs the whole personal-brand loop	”Your employees’ combined networks are 10 times larger than your page following” (cluster-E #6 GaggleAMP); “He handles the whole loop: Voice note in. Draft, schedule, post, and the numbers back.” (cluster-D #11 Stanley)	Company-page organic reach dying; no agent to run the loop; advocacy only buyable at enterprise price	Reach multiplier (10× networks); ROI/attribution (EMV, CPC); loop run autonomously

The 17 jobs mapped onto the 5 stages

Job numbering and density verdicts are taken verbatim from the jtbd-analysis.md §3 density table; stage assignment is this document’s synthesis (jobs with dual homes are marked with their secondary stage).

Stage	Jobs	Count / verdict (per jtbd §3)
Find	J1 Find & verify B2B contact data / build clean lists (~20 — red ocean); J14 Intent signals / warm-lead capture (~10–12 — crowding, turning red); J15 CRM hygiene / zero manual data entry (~11 — moderate/red-ish); J16 Recruiter candidate sourcing (0 dedicated, ~15 adjacent — served only via adjacent tools)	4 jobs, 2 red oceans, 1 structurally unserved
Send	J2 Automate LinkedIn connect/message/follow-up sequences (~22 — most over-served job in the market); J3 Multi-channel outreach (~13 — red ocean); J4 AI-personalized messaging (~15 — red ocean); J17 Agency multi-client ops (~17 — red ocean at agency level)	4 jobs, all red oceans — the market’s core
Engage	J7 First-hour engagement amplification (3 dedicated + ~4 adjacent — moderate, small dedicated field); J8 Turn engagement/comments into pipeline (~9, 0 flagship — under-served as a primary job); J12 Personality / communication intelligence (1 live — under-served niche)	3 jobs, all under-served as primary positions
Publish	J5 Personal-brand content creation (12 — red ocean within category); J6 Post scheduling / publishing / content calendar (~15 — red ocean); J13 Official-API-verified compliance for posting (2 verified — white space)	3 jobs, 2 red oceans, 1 white space
Compound	J9 Employee advocacy at enterprise scale (7 core + 5 adjacent — well-served at enterprise); J10 Employee advocacy at SMB/mid-market price (0 dedicated — white space); J11 Autonomous AI-agent posting + engagement (1 dedicated — white space (content variant))	3 jobs — the only stage with two white-space jobs

Two jobs span stages and are assigned to their primary home above: J16’s employer-brand half lives in Compound (recruiters hire advocacy platforms to amplify job posts, per jtbd §2 (e)3 and cluster-E 11/9), and J11’s loop technically traverses Publish → Engage → Compound but is counted in Compound because its autonomous-orchestration essence belongs there (per jtbd §3 J11 row).

Reading: Send and Find are where the market is saturated; Engage is where every adjacent job is under-served as a primary position (J8’s ~9 tools all touch it, none lead with it — per jtbd §3 reading); Compound is where the market is structurally absent at every price point except enterprise.

---

2. The Nine Persona Journeys

For each persona: the stage sequence they actually traverse, per-stage jobs (from jtbd §2/§3), tools with entry price + compliance method (from cluster files), switching criteria, and failure point. A compact journey-map table closes each section.

2.1 (a) Solo founder / consultant

Journey: Find → Send → Engage → Publish (4 stages; Compound only via single-seat tools like Stanley). The founder is simultaneously the sales team and the brand (per jtbd §1 (a): “founder IS the sales team and often the brand”), so the Find→Send loop and the Publish loop are both load-bearing — and both must run on $0–$99/mo with free tiers as the entry point (per jtbd §1 (a) budget context).

Find. Jobs: J1 (a1: “prospect and reach out myself with automation… without hiring”, per jtbd §2 (a)1); J3-adjacent cash constraint (a3: “free or cheap tool that covers the core loop… validate outbound before committing money”, per jtbd §2 (a)3). Tools: Apollo Free 0 (database + Chrome extension for one-click LinkedIn enrichment — cluster-A #1 field 10), Evaboot 9 (extension inside Sales Navigator, live extraction, “imposes a daily limit so you never cross LinkedIn’s limitations” — cluster-A #4), Wiza Free 0 (extension, real-time verification — cluster-A #5), AeroLeads 49 (extension “for individual prospecting”, 10 free credits — cluster-A #7), Scalelist 99 flat (database + extension, "Pay for Results, Not Fluff" — cluster-A #6). Switching criteria: free tiers first, then 9–$99;"0bans"/safetyframing(a5:"scalewithoutgettingbanned",perjtbd\S 2(a)5);ease("turnhoursofprospectingintominutes",perjtbd\S 2(a)1).Failurepoint:thedatalayeriscommoditizingunderthem—Apoll{o}^{\prime }sfreetier,Wiz{a}^{\prime }sreal-timeverification,andScalelis{t}^{\prime }s$99 flat “squeeze the middle” (per cluster-A takeaway #1), so the founder’s data cost advantage is eroding, and the raw-scraping infra they might use is dead (NetNut FBI-seized, per cluster-A #9).

Send. Jobs: J2 (a4: “follow-ups and busywork automated… actually sell”, per jtbd §2 (a)4); J4 (personalization, adjacent to the founder’s a4/a5 jobs). Tools: Octopus CRM 9.99 (extension, "we'll never ask for your LinkedIn credentials" — cluster-B #2), Dux-Soup 14.99 (extension; “0 reports… banned” safety FAQ — cluster-B #1), LeadConnect 0 free-forever (extension, "not endorsed or certified by LinkedIn… use at your own risk" disclaimer — cluster-B #3), LinkedHelper 15 (desktop app, “no code injected into the LinkedIn page — safer by design” — cluster-B #4), Botdog 35 (cloud, "runs 24/7", no extension — cluster-B #6), Waalaxy €19 (extension, "75% of our users had never done LinkedIn outreach before" — cluster-B #8), Meet Alfred 59 (cloud — cluster-C #5), HeyReach 79/sender (cloud + dedicated residential proxy per sender — cluster-C #1). Switching criteria: 0–$99 band, free trials, “saving 10+ hours per week” (Botdog) / “Start saving 3hrs of work every day” (Meet Alfred), safety language everywhere (“every tool claims safety” — cluster-B takeaway #5). Failure point: the entire cluster-B toolset is ToS-risky — none of the 11 claims official API (cluster-B compliance table), and 5/11 are browser extensions with detection risk (cluster-B takeaway #1); the founder’s a5 job (“safe… under the radar”, per jtbd §2 (a)5) is only answered with claims, not architecture.

Engage. Jobs: J7/J8 (d-adjacent: comments on their posts are their lead source). Tools: Linkboost $0/$31/47 (server-side, no extension, "rate-limited and spaced out to match natural LinkedIn activity" — cluster-E #3), Podawaa €29–€159 (Private Mode = "no extension, no password, your account never used" — cluster-E #2), Lempod 9.99+ (extension — removed from the Chrome Web Store, needs manual Developer-Mode install, per cluster-E #1). Switching criteria: price (pods run $0–$200/mo, per cluster-E summary A), account safety (Podawaa’s compliance testimonial: “approved it in 24h”, per cluster-E #2). Failure point: the cheap engagement options are exactly the detectable ones — HeyReach’s own article warns pods are algorithmically detectable (per cluster-E #1 field 10/12), and Lempod’s extension was pulled (per cluster-E #1); the compliant first-hour-boost job (jtbd §4.2 #6 “safe amplification”) is “transitional — no tool owns the compliant-boost position outright” (per jtbd §4.2 #6).

Publish. Jobs: J5 (a2: “my personal brand is my only lead source… turn my LinkedIn into my best sales channel”, per jtbd §2 (a)2); J6. Tools: ContentIn 15 (extension for some features, not official API — cluster-D #10), Supergrow 19 (web app, no extension, no cookie scraping — cluster-D #5), FeedBoss 29 ("Official OAuth, never a password" + extension — cluster-D #4), MagicPost 21 (“LinkedIn-verified partner”, official API — cluster-D #8), Typefully 99/yr (official LinkedIn API — cluster-D #7), AuthoredUp 19.95 (extension, “100% secure. No automation. No cookies.” — cluster-D #12), Taplio 39 (extension + cookie-based auth — cluster-D #2), Kleo 99 (web app, “does not automate posting” — cluster-D #1), Stanley 149 (AI agent that drafts/schedules/auto-posts, single-seat, no trial — cluster-D #11). Switching criteria: 15–99 band (per jtbd §1 (a) budget context), voice authenticity ("AI that writes like you, not for you", per cluster-D #5), no-automation safety posture (SayWhat: "no automated behavior which LinkedIn doesn't like", per cluster-D #3). Failure point: the creation job (J5, 12 tools) is a red ocean with commoditized pricing anchored at 15–$99/mo (per jtbd §3 J5 row and §5 Candidate B AGAINST #4) — and no single tool closes the loop: Kleo explicitly does not automate posting (cluster-D #1), SayWhat converts comments but doesn’t auto-post (cluster-D #3), Stanley posts but has no engagement/conversion capability (per jtbd §5 Candidate B FOR #3 and §6 #5). The founder must stitch 3–5 tools to run one personal-brand motion.

Journey map (a):

Stage	Job(s)	Tools (price / compliance)	Failure point
Find	J1, a3	Apollo Free $0(extensionenrichment);Evaboot$9 (extension, live); Wiza Free (extension, real-time); AeroLeads $49(extension);Scalelist$99 (DB+ext)	Data layer commoditizing; NetNut seized = infra dead (cluster-A 1/9)
Send	J2, J4	Octopus $9.99(ext);Dux-Soup$14.99 (ext); LeadConnect $0(ext);LinkedHelper$15 (desktop); Botdog $35(cloud);Waalaxy€19(ext);MeetAlfred$59 (cloud); HeyReach $79/sender (cloud+proxy)	0/11 cluster-B tools have official API; safety is claim-only (cluster-B compliance table, takeaway #5)
Engage	J7, J8	Linkboost $0/$31/$47(server-side);Podawaa€29+(cloudPrivateMode);Lempod$9.99 (ext, store-removed)	Compliant boost job unowned; pods detectable (cluster-E 1/2/3; jtbd §4.2 #6)
Publish	J5, J6	ContentIn $15(ext);Supergrow$19 (web); FeedBoss $29(OAuth+ext);MagicPost$21 (official API); Typefully $99/yr(officialAPI);AuthoredUp$19.95 (ext, no cookies); Taplio $39(ext/cookies);Stanley$149 (agent)	J5 red ocean; loop decoupled — nobody owns create→post→engage→convert (jtbd §5 Candidate B)

2.2 (b) SDR / BDR

Journey: Find → Send → Engage (3 stages; employer-funded seat at $49–$129/seat/mo, per jtbd §1 (b) budget context — the most-targeted persona in the premium cluster). The SDR’s journey is quota-shaped: everything is justified by meetings booked (per jtbd §1 (b): “Justification = meetings booked/quota hit”).

Find. Jobs: J1 (b2: “verified emails and phone numbers… only pay for valid emails”, per jtbd §2 (b)2); J14 (b2-adjacent freshness). Tools: Wiza $49–$199 (extension, “No cached data. No surprise bounces.” — cluster-A #5), UpLead $99–$199 (“We’ll refund you for bounces and poor data” — cluster-A #3), Scalelist 99 (DB+ext, "keep bounce rates low" — cluster-A #6), Evaboot 9–99 (extension, Sales Nav export — cluster-A #4), Apollo 49/seat (extension + 240M+ DB — cluster-A #1), AeroLeads $49–$149 (extension, sales tier — cluster-A #7). Switching criteria: per-credit honesty (TexAu “Failed lookups cost zero”, cluster-A #11), pay-for-valid-emails, employer seat so $49–$199 acceptable. Failure point: J1 is a ~20-tool red ocean (per jtbd §3) — the SDR has no differentiation problem with tools, only a data-quality problem; LeadFuze (a legacy SDR/recruiter tool) abandoned end-user software entirely for a $1,500–$2,000/mo wholesale license (per cluster-A #2), showing the low end of the data layer is consolidating away from individual reps.

Send. Jobs: J2 (b1: “reach and exceed quotas”, b3: “auto-follow up until prospects reply”, per jtbd §2 (b)1/(b)3); J3 (multichannel); J4 (b4: “personalized LinkedIn messages with AI… that don’t feel like spam”, per jtbd §2 (b)4); J4.2-shift job (b5: copilot control over AI SDRs, per jtbd §2 (b)5). Tools: Expandi 99 (cloud + dedicated country-based IP + auto warm-up — cluster-C #2), Salesflow 99 → 24.99/seat at 100+ (cloud, "safest" positioning — cluster-C #4), Meet Alfred 59–99 (cloud — cluster-C #5), Skylead 100/seat (cloud — cluster-C #3), Dripify $59–$99 (cloud, “Cloud-based performance” — cluster-B #7), Waalaxy €19–€69 (extension + email — cluster-B #8), Botdog $35–$49 (cloud — cluster-B #6), lemlist $69–$109 (cloud + extension for capture — cluster-C #8), Reply $49–$89 (cloud; LinkedIn is a paid add-on 69/acct — cluster-C #7), PhantomBuster 56€–352€ (cloud, cookie/session automation via own accounts — cluster-A #12), Salestools 79/seat (cloud AI SDR, CoPilot “approve every send” vs Autopilot — cluster-C #11). Switching criteria: $49–$129/seat band (per jtbd §1 (b)), reply detection (“smart reply detection — halts sends on reply”, cluster-C #3), quota evidence (Skylead “Book 3x more meetings”, cluster-C #3), and now AI-SDR copilot control (b5, per jtbd §2 (b)5). Failure point: the AI-SDR wave is eating the job itself — Salestools’ Nico/Olivia/Sally agents “prospect and book on autopilot” (cluster-C #11), Reply’s Jason AI SDR from $500/mo (cluster-C #7), Salesflow’s Ariel (cluster-C #4). The “direct the agents” copilot-governance job exists (jtbd §4.2 #2: approval queues, caps, “My Day” drafts/replies/approvals queue) but “nobody yet sells this as a standalone product” (per jtbd §4.2 #2) — the SDR’s safest career position (human-in-the-loop governance) is unmarketable today.

Engage. Jobs: J8 (comments as pipeline; b4-adjacent); J7 (when they post content as part of quota). Tools: Linkboost $0/$31/47 (server-side pods; B2B sales consultant testimonial: "booking two discovery calls a week straight from LinkedIn comments" — cluster-E #3), Taplio 39–199 Pro (auto-DM, lead database, smart replies — cluster-D #2), Lempod 9.99+ (extension — cluster-E #1). Switching criteria: reply rates, meeting bookings from comments. Failure point: J8 is “under-served as a primary job… ~9 tools, 0 flagship” (per jtbd §3 J8 row) — the SDR’s single most valuable inbound channel (comments on their posted content) has no dedicated pipeline tool; and the AI-SDR shift means the content variant of the agent job (J11) — the thing a quota-carrying rep could own — is “the interesting leftover” (per jtbd §4.2 #1).

Journey map (b):

Stage	Job(s)	Tools (price / compliance)	Failure point
Find	J1, J14, b2	Wiza $49–199(ext,real-time);UpLead$99–199 (ext); Scalelist $99(DB+ext);Evaboot$9–99 (ext); Apollo $49/seat(ext);AeroLeads$49–149 (ext)	J1 red ocean ~20 tools; LeadFuze pivoted away from reps (cluster-A #2)
Send	J2, J3, J4, J4.2#2	Expandi $99(cloud+IP);Salesflow$99→$24.99(cloud);MeetAlfred$59–99 (cloud); Skylead $100(cloud);Dripify$59–99 (cloud); Waalaxy €19–69 (ext); lemlist $69–109(cloud);Reply$49–89 (cloud); PhantomBuster 56€ (cloud/cookies); Salestools $79 (cloud AI SDR)	AI SDRs commoditize the job; copilot governance unowned (jtbd §4.2 #2; cluster-C #11)
Engage	J8, J7	Linkboost $0/$31/$47(server-side);Taplio$39+ (ext/cookies); Lempod $9.99 (ext)	J8: 0 flagships; comment-to-pipeline unowned (jtbd §3 J8)

2.3 (c) Agency owner

Journey: Find → Send → Engage → Publish (all four, multi-client; cost passes through to clients, $100–$2,999/mo, white-label is a purchase trigger — per jtbd §1 (c) budget context). The agency is the market’s most demanding buyer: everything must isolate per client, report per client, and survive per client.

Send. Jobs: J17 (c1: “manage a big volume of clients” with workspaces/per-client isolation; c2: white-label and transparent reporting “generate leads for your clients’ pipelines”; c3: “unlimited senders and actions at a fixed cost, so my margin scales”, per jtbd §2 (c)1/(c)2/(c)3); J2 (outreach engine). Tools: HeyReach $79/sender\to Agency$999 (25 senders) → Unlimited 2,999 (workspaces, Master View, whitelabel, dedicated residential proxy per sender — cluster-C #1), Skylead 100/seat → Agency $999/50seats/$1,999/unlimited (agency dashboard, white-label option — cluster-C #3), Salesflow Agency 29.98/seat at 50+ (whitelabel URL/UI on Pro+, "Generate leads for your clients' pipelines" — cluster-C #4), Meet Alfred 59–99 (white label 5+, dedicated /agencies — cluster-C #5), Reply Agency Core from 210/mo (multi-workspace, white-label option — cluster-C #7), We-Connect Agency custom (10+ accounts, /agency + white-label — cluster-B #11), Expandi Agency custom 10+ seats white-label (cluster-C #2). Switching criteria: white-label, per-client isolation, unlimited senders at fixed cost (c3), client-account survival. Failure point: J17 is a red ocean at agency level (~17 tools, per jtbd §3) — and the safety infra arms race (c4: proxies, warm-up, hard limits, per jtbd §2 (c)4) is the only differentiator left, yet every option is ToS-risky: none of cluster C claims official LinkedIn API-partner status for automation (per cluster-C table B), and HeyReach’s own Agency tier makes the agency “bring your own proxies” (per cluster-C #1 FAQ). The agency’s client-accounts-survive job (c4) is answered by proxy infrastructure, not by compliant architecture.

Find. Jobs: J1 (client list building at volume); J17-adjacent. Tools: TexAu Teams 549 (table workspace, 200+ actions, client deliverables from one workspace — cluster-A #11), Scalelist 99 (“Run high-volume campaigns”, “More Replies for Your Clients” — cluster-A #6), PhantomBuster 56€–352€ (Belkins logo, agency automation — cluster-A #12). Switching: pay-on-match credits, per-client workspaces. Failure point: the same data-layer commoditization as (a) — agencies buy the same squeezed middle (cluster-A takeaway #1).

Engage. Jobs: J8 (client comment-to-pipeline); J7 (client amplification). Tools: Lempod Agency $149.99/AgencyXL$179.99 (extension — store-removed risk — cluster-E #1), Linkboost Plus $47 “for power users and ghostwriters” / Enterprise custom “for teams and agencies” (server-side — cluster-E #3), Podawaa €159 Private Dominate (cloud — cluster-E #2). Switching: margin (agency tiers), ghostwriter support, safe mechanics for client accounts. Failure point: running pods for client accounts multiplies the ToS risk — Lempod’s extension removal (cluster-E #1) and HeyReach’s own pod-detection warning (cluster-E #1 field 10/12) make the “safe amplification for clients” job (jtbd §4.2 #6) commercially radioactive for an agency.

Publish. Jobs: J5/J6 (c5: “manage multiple client voices from one workspace, so I can cross-sell content services”, per jtbd §2 (c)5). Tools: MagicPost agency/ghostwriter track (custom; “Manage every client’s LinkedIn without the chaos. And actually scale.” — official API verified partner — cluster-D #8), Supergrow 139 Teams ("Manage multiple client voices from one workspace" — cluster-D #5), FeedBoss Studio 149 (workspaces/approvals — cluster-D #4), ContentIn Ghostwriter/Agency custom (multi-profile — cluster-D #10), Taplio Pro 199 (/agencies — cluster-D #2), AuthoredUp Business 14.95/profile min 3 (ghostwriters free for managers — cluster-D #12). Switching: per-profile pricing, approval flows, white-label reports. Failure point: J5/J6 are red oceans (12 and ~15 tools, per jtbd §3) — content services are commoditized, so the agency’s cross-sell margin (c5) is under price pressure from the same $15–$99 creator tools their clients can buy directly.

Journey map (c):

Stage	Job(s)	Tools (price / compliance)	Failure point
Send	J17, J2, J3	HeyReach $79\to$999→$2,999(cloud+proxy,whitelabel);Skylead$100→$999/50seats(cloud);Salesflow$29.98/seat 50+ (cloud, whitelabel); Meet Alfred $59+(cloud,WL5+);ReplyAgency$210+ (cloud); We-Connect Agency custom (cloud+IP); Expandi Agency custom (cloud+IP)	J17 red ocean ~17 tools; safety = proxy arms race, no official API (cluster-C table B)
Find	J1	TexAu Teams $549(API/table);Scalelist$99 (DB+ext); PhantomBuster 56€ (cloud/cookies)	Data layer commoditizing (cluster-A takeaway #1)
Engage	J8, J7	Lempod Agency $149.99(ext,store-removed);Linkboost$47+/Enterprise (server-side); Podawaa €159 (cloud)	Client-account pod risk; compliant boost unowned (cluster-E 1/2/3; jtbd §4.2 #6)
Publish	J5, J6	MagicPost agency (official API); Supergrow $139Teams(web);FeedBoss$149 Studio (OAuth+ext); ContentIn agency custom (ext); Taplio $199Pro(ext/cookies);AuthoredUp$14.95/profile (ext, no cookies)	J5/J6 red oceans; content commoditized (jtbd §3 J5/J6)

2.4 (d) Personal brand creator

Journey: Publish → Engage → Compound (3 stages; the core persona of all 12 cluster-D tools, per cluster-D persona matrix C — self-funded at $15–$99/mo with free trials and no procurement, per jtbd §1 (d)). The creator’s journey is the inverse of the SDR’s: content first, pipeline second.

Publish. Jobs: J5 (d1: “never run out of content ideas… idea to published post in minutes”; d3: “sound like yourself”, per jtbd §2 (d)1/(d)3); J6 (d5: “publish everywhere at once”, per jtbd §2 (d)5). Tools: ContentIn 15 (extension — cluster-D #10), Supergrow 19 (web app, “AI that writes like you, not for you” — cluster-D #5), FeedBoss 29 ("drafts like you on your sharpest day" — cluster-D #4), Taplio 39–199 (extension + cookie-based auth, "grow on LinkedIn in 10 min/day" — cluster-D #2), MagicPost 21–39 (**official API, "LinkedIn-verified partner"** — cluster-D #8), SayWhat 47.99 (browser-side, “no automated behavior which LinkedIn doesn’t like” — cluster-D #3), Kleo 99 (web app, **"does not automate posting"** — cluster-D #1), Typefully 99/yr (official API, cross-platform — cluster-D #7), EasyGen 59.99 ⚠️ (extension, single plan — cluster-D #9), AuthoredUp 19.95 (extension, no cookies — cluster-D #12), Stanley 149 (AI agent, auto-posts across 6 platforms, no trial — cluster-D #11). Switching criteria: voice authenticity (d3), price band 15–$99(perjtbd\S 1(d)),no-extensionsafety(Supergrow/SayWhat/AuthoredUpsellit),freetrials(perjtbd\S 1(d):"self-serveat$19–99/mo with free trials”). Failure point: J5 is a red ocean within the category (12 tools) with commoditized pricing (per jtbd §3 J5 row) — and the two official-API tools (MagicPost $21,Typefully$99/yr) bracket the whole cluster on compliance (per cluster-D table B: only 2 of 12 claim official API/verified-partner status).

Engage. Jobs: J7 (d2: “engagement in the critical first hour… 10x my LinkedIn reach”, per jtbd §2 (d)2); J8 (d4: “turn engagement into opportunities… land clients from comments”, per jtbd §2 (d)4). Tools: Linkboost $0/$31/47 (server-side, first-hour boost — cluster-E #3), Lempod 9.99+ (extension, store-removed — cluster-E #1), Podawaa €29–€159 (cloud Private Mode / ext Community Mode — cluster-E #2), SayWhat (comment inbox + AI quick responses + “convert engagement to opportunities” — cluster-D #3), Taplio (auto-reply, smart replies — cluster-D #2), MagicPost (lead detection, “Turn engagement into leads” — cluster-D #8). Switching criteria: first-hour velocity, comment-to-lead conversion, account safety (Podawaa: “your account never used” — cluster-E #2). Failure point: J8 has 0 flagships (per jtbd §3) — even the creator-focused tools touch conversion as an add-on, never as the lead product; and the pods that serve J7 are the ToS-riskiest tools in the dataset (Lempod store removal, HeyReach’s pod-detection warning — cluster-E #1).

Compound. Jobs: J11 (the full create→post→engage→convert loop; d-adjacent autonomy). Tools: Stanley $149 (the only autonomous content agent — drafts, schedules, auto-posts; no engagement or comment-conversion capability, per jtbd §5 Candidate B FOR #3 and §6 #5; single-seat, no trial — cluster-D #11), Podawaa (claims the full loop “From writing the post to landing the lead” but is “an engagement-pod root with a weak AI composer, not a credible full-loop system at team scale”, per jtbd §5 Candidate B FOR #3). Switching criteria: autonomy (“He handles the whole loop”, cluster-D #11), voice fidelity. Failure point: J11 is white space with one weak incumbent — “the integrated loop… is claimed by nobody credibly” (per jtbd §5 Candidate B FOR #3); the loop’s components exist but are decoupled: writers don’t boost, pods don’t author, SayWhat converts but doesn’t post, Stanley posts but doesn’t engage (per jtbd §5 Candidate B FOR #3).

Journey map (d):

Stage	Job(s)	Tools (price / compliance)	Failure point
Publish	J5, J6, d1/d3/d5	ContentIn $15(ext);Supergrow$19 (web); FeedBoss $29(OAuth+ext);Taplio$39–199 (ext/cookies); MagicPost $21(officialAPI);SayWhat$47.99 (browser); Kleo $99(web,noautomation);Typefully$99/yr (official API); AuthoredUp $19.95(ext,nocookies);Stanley$149 (agent)	J5 red ocean (12 tools); only 2/12 have official API (cluster-D table B)
Engage	J7, J8, d2/d4	Linkboost $0/$31/$47(server-side);Lempod$9.99 (ext, store-removed); Podawaa €29+ (cloud); SayWhat (browser); Taplio (ext); MagicPost (official API)	J8: 0 flagships; pods detectable (jtbd §3 J8; cluster-E #1)
Compound	J11	Stanley $149 (single-seat agent, no engage/convert); Podawaa (weak full-loop claim)	J11 white space; loop decoupled (jtbd §5 Candidate B)

2.5 (e) Recruiter

Journey: Find → Send → Compound (3 stages; employer seat at $49–$150/mo — “no dedicated LinkedIn-recruiting platform exists in the dataset; recruiters buy adjacent sales tools”, per jtbd §1 (e)). The recruiter is the dataset’s most structurally underserved persona.

Find. Jobs: J16 (e1: “search and contact data on hard-to-find profiles… reach them directly instead of waiting for applicants”, per jtbd §2 (e)1); J1 (contact data); J12 (e4: personality insights for interviews, per jtbd §2 (e)4). Tools: AeroLeads Climb 149 ("For sales and recruiting teams" — cluster-A #7), Crystal Hiring 49–199 (personality analysis; "Understand the person behind the résumé", candidate fit scores, interview questions — cluster-A #8), Wiza 49–199 (Digital Sourcing Specialist testimonial — cluster-A #5, partial), Octopus CRM 9.99 (Recruiter Lite compatibility — cluster-B #2). Switching criteria: passive-candidate access, per-seat employer price, no dedicated tool so any adjacent tool wins. Failure point: J16 is “served only via adjacent tools” — ~15 adjacent, 0 dedicated (per jtbd §3 J16 row) — and Wiza explicitly notes Evaboot “doesn’t work on LinkedIn Recruiter” (cluster-A #4 FAQ), meaning the recruiter’s own platform is excluded from half the scraping layer.

Send. Jobs: J2 (e2: “automated invites and follow-up cadences… fill roles faster”, per jtbd §2 (e)2). Tools: Octopus CRM 9.99 (extension — cluster-B #2), Botdog 35–49 (cloud, "recruitment teams" — cluster-B #6), We-Connect 49–59 (cloud + dedicated country IP, dedicated /recruiters page — cluster-B #11), Expandi 99 (cloud + IP, “Recruiters — Increase your talent acquisition velocity” — cluster-C #2), Meet Alfred 59 (cloud, "Recruiters" tab — cluster-C #5), Salesflow 99 (cloud, “Recruitment — Head hunting & business development” — cluster-C #4), LinkedHelper 15 (desktop, Recruiter project import — cluster-B #4), LinkedFusion 46.95 (cloud + dedicated IP, recruitment case study — cluster-B #10). Switching criteria: invite/message cadence, Recruiter-account compatibility, account safety (recruiters run on their employer’s named accounts). Failure point: same as (b) — the entire Send layer is extension/cookie/session automation with 0 official-API tools (cluster-B compliance table), and a banned recruiter account is a compliance event, not an inconvenience.

Compound. Jobs: J9 (e3: “employees amplify job posts… attract top talent at a fraction of job-ad cost”, per jtbd §2 (e)3); J16 employer-brand half. Tools: DSMN8 custom quote (Talent Acquisition/HR track; “reduce the time and cost to hire”; consent-based Delegate Access for exec LinkedIn posting — cluster-E #11; ⚠️ third-party floor $850–$3,500/mo), Parliament custom (inside Hootsuite Enterprise; “People teams use… for hiring”, ⚠️ third-party 240/user/mo — cluster-E #9), EveryoneSocial custom (hiring testimonials, ⚠️ third-party 24/user/mo or $20k–$80k+/yr — cluster-E #10), Lempod 9.99+ ("lempod for Recruiting", Spendesk: "we were able to attract top talent" — cluster-E #1). Switching criteria: employer-brand ROI vs job-ad cost (DSMN8: "-91% Cost Per Click… 0.49 vs $5.26 LinkedIn Ads average” — cluster-E #11). Failure point: the employer-brand half of the recruiter’s job is only buyable at enterprise price — every advocacy platform is custom-quote, demo-gated, annual-contract (per cluster-E pricing table), so a mid-market recruiter’s J16 employer-brand job falls into the J10 white space (0 dedicated tools, per jtbd §3 J10 row) with no compliant, self-serve option.

Journey map (e):

Stage	Job(s)	Tools (price / compliance)	Failure point
Find	J16, J1, J12	AeroLeads $149(ext,"salesandrecruiting");CrystalHiring$49–199 (analysis layer); Wiza $49–199(ext,partial);Octopus$9.99 (ext, Recruiter Lite)	J16: 0 dedicated tools; Evaboot excludes Recruiter accounts (jtbd §3 J16; cluster-A #4)
Send	J2	Octopus $9.99(ext);Botdog$35–49 (cloud); We-Connect $49–59(cloud+IP);Expandi$99 (cloud+IP); Meet Alfred $59(cloud);Salesflow$99 (cloud); LinkedHelper $15(desktop);LinkedFusion$46.95 (cloud+IP)	ToS risk on employer accounts; 0 official API in cluster B (cluster-B compliance table)
Compound	J9, J16 (brand half)	DSMN8 custom (consent OAuth); Parliament custom (add-on); EveryoneSocial custom (OAuth); Lempod $9.99 (ext)	Employer-brand job enterprise-priced only; J10 gap (cluster-E pricing table; jtbd §3 J10)

2.6 (f) SMB marketing team

Journey: Find → Send → Publish → Compound (4 stages; $49–$199/mo, self-serve, no procurement chain, annual discounts matter — per jtbd §1 (f) budget context). The SMB team is the “all-in-one” buyer (f1: “don’t buy five tools when one does it better”, per jtbd §2 (f)1) — and its journey ends at Compound, where the market abandons it.

Find. Jobs: J1/J14 (f4-adjacent: analytics and what-works visibility). Tools: UpLead $99–$199 (ext, “4,000+ businesses” — cluster-A #3), AeroLeads $49–$299 (ext, “B2B contact data for every team size” — cluster-A #7), Scalelist 99 (DB+ext, "Sales & Marketing Teams" use-case — cluster-A #6), Apollo 49–119/seat (Marketing persona page — cluster-A #1), Octoparse 0–$69 (general scraper, user-acquisition research testimonial — cluster-A #10). Switching: budget band, all-in-one consolidation (f1). Failure point: J1’s ~20-tool red ocean (per jtbd §3) offers no consolidation — the SMB team that wants one tool (f1) still needs a data tool, an outreach tool, and a content tool.

Send. Jobs: J2/J3 (f2: “multi-channel campaigns (LinkedIn + email)… where they actually respond”, per jtbd §2 (f)2); J4. Tools: Dripify $59–$99 (cloud, “Automate sales on LinkedIn & email” — cluster-B #7), We-Connect $49–$79 (cloud + country IP, “Small business. Nonprofits.” — cluster-B #11), Waalaxy €19–€69 (ext + email, Business tier “LinkedIn + email at full scale” — cluster-B #8), lemlist $69–$109 (cloud, “run outbound across multiple channels”, unlimited users — cluster-C #8), Reply $49–$89 (cloud, Email Volume tiers — cluster-C #7), Skylead 100/seat (cloud, "all-in-one" — cluster-C #3), Salestools 79/seat (cloud AI SDR, per-seat self-serve — cluster-C #11). Switching: annual discounts (Dripify $39annual,We-Connect$49 annual — per cluster-B pricing tables), f5 compliance review (“procurement doesn’t block the rollout”, per jtbd §2 (f)5 — Podawaa’s “compliance team approved it in 24h”, cluster-E #2). Failure point: f5 is the SMB team’s quiet killer — the cheapest Send options are extensions with “use at your own risk” disclaimers (LeadConnect/LinkedFusion/We-Connect all print them, per cluster-B 3/10/11), and no cluster-B/C tool can answer an official-API compliance question (per cluster-B compliance table, cluster-C table B).

Publish. Jobs: J5/J6 (f3: “approval workflows and team scheduling… post on-brand”, per jtbd §2 (f)3); J13 (f5-adjacent). Tools: Supergrow Teams 139 (web app, feedback & approval workflow, "post on-brand", leaderboard gamification — cluster-D #5), MagicPost Teams custom (official API, "send for approval", free advocacy simulator — cluster-D #8), FeedBoss 29+ (Team Approvals, OAuth “never a password” — cluster-D #4), Typefully Business 18/mo per social set (official API, "modern marketing teams" — cluster-D #7), ContentIn 15+ (company pages — cluster-D #10), AuthoredUp Business $14.95/profile (team analytics — cluster-D #12). Switching: approval flows, on-brand consistency, team seats, compliance. Failure point: J5/J6 red oceans (12/~15 tools, per jtbd §3) — the SMB team’s content stack is served, but with no single owner of the team workflow; the tools that have approval flows cap at 4 accounts (Supergrow Teams, per jtbd §5 Candidate A AGAINST #1) or are custom-quote (MagicPost Teams).

Compound. Jobs: J10 (the (f)×(i) intersection: a 20–200 person company wanting execs/employees to amplify LinkedIn content); J9-adjacent. Tools: nothing dedicated — closest: Supergrow Teams 139/4 accounts (per jtbd §5 Candidate A AGAINST #1), MagicPost Teams custom (per cluster-D #8), Lempod Company Pod 9.99–149.99 (extension, ToS-risky; Spendesk testimonial — cluster-E #1), Linkboost Enterprise custom (per cluster-E #3). Switching: 100–500/mo self-serve, compliant connection, team scale. Failure point: **J10 is the dataset's clearest white space — 0 dedicated tools** (per jtbd §3 J10 row and §5 Candidate A verdict); the (f)×(i) intersection "is served by nobody in this cluster. That is GrowReach's clearest slot." (per cluster-E takeaway #4); the price gulf is 10–100× between 0–$200/mopodsand$850+/mo enterprise advocacy (per cluster-E summary A); and the only cheap options are exactly the ToS-risky ones (Lempod store removal — cluster-E #1).

Journey map (f):

Stage	Job(s)	Tools (price / compliance)	Failure point
Find	J1, J14	UpLead $99–199(ext);AeroLeads$49–299 (ext); Scalelist $99(DB+ext);Apollo$49+ (ext); Octoparse $0–69 (scraper)	J1 red ocean ~20 tools; no consolidation for the all-in-one buyer (jtbd §3 J1)
Send	J2, J3, J4	Dripify $59–99(cloud);We-Connect$49–79 (cloud+IP); Waalaxy €19–69 (ext); lemlist $69–109(cloud);Reply$49–89 (cloud); Skylead $100(cloud);Salestools$79 (cloud)	f5 compliance: no official-API option in cluster B/C (cluster-B compliance table)
Publish	J5, J6, J13	Supergrow Teams $139(web);MagicPostTeamscustom(officialAPI);FeedBoss$29+ (OAuth+ext); Typefully Business $18(officialAPI);ContentIn$15+ (ext); AuthoredUp $14.95/profile (ext)	Team approval workflows half-built; 4-account caps (jtbd §5 Candidate A AGAINST #1)
Compound	J10	Nothing dedicated; Supergrow Teams $139 (4 accts); Lempod Company Pod (ext); Linkboost Enterprise custom	J10 = 0 dedicated tools; (f)×(i) unclaimed (cluster-E takeaway #4; jtbd §3 J10)

2.7 (g) Enterprise RevOps

Journey: Find → Send → Compound (3 stages; custom-quote, $3,000+/mo, annual contracts, SSO/SOC 2/ISO table stakes — per jtbd §1 (g) budget context). The RevOps buyer purchases orchestration and proof, not features.

Find. Jobs: J1 (g3: “licensed identity graphs and enrichment APIs… the freshest data on the market”, per jtbd §2 (g)3); J14 (attribution signals). Tools: LeadFuze $1,500–$2,000/mo (wholesale data license, post-pivot — cluster-A #2), NetNut (infra — site seized by FBI, per cluster-A #9), Apollo Organization 119/seat (240M+ DB — cluster-A #1), Scalelist 99 + custom (RevOps use-case page, MCP server — cluster-A #6), Wiza Team custom (enterprise ABM testimonials — cluster-A #5). Switching: data licensing, API access, compliance certs. Failure point: the infrastructure layer is consolidating violently — LeadFuze abandoned SaaS (cluster-A #2) and NetNut was FBI-seized (cluster-A #9), which jtbd flags as “a live compliance warning for the whole cookie/proxy-scraping category” (per jtbd §4.1 Shift 4 and cluster-A takeaway #5).

Send. Jobs: J2/J3 (g1: “one orchestration layer across cadence, dialer, and data… confidently call your sales number”, per jtbd §2 (g)1); J11-outbound (g2: “AI SDRs that prospect and book on autopilot… grow pipeline without hiring”, per jtbd §2 (g)2); g5 (SOC 2/ISO/SSO). Tools: Salesloft custom (revenue orchestration platform; Advanced/Elite, “Request a Demo” only; LinkedIn Sales Navigator partner via ecosystem; 3M/Stripe/IBM logos — cluster-C #10), Salestools $79–$199/seat → Enterprise 3,000+ (AI SDR agents, SOC 2 Type II, SSO/SAML/SCIM — cluster-C #11), Reply AI SDR 500–1,500+ (Jason; enterprise tier — cluster-C #7), LGM €60–€180/identity (explicit "For GTM, Growth, RevOps, or SalesOps"; MCP + Skills library; dedicated 5G mobile proxies — cluster-C #6), lemlist 109+ (SOC 2 certified, “For RevOps” nav — cluster-C #8), Salesflow Enterprise 24.99/seat at 100+ (cluster-C #4). Switching: SOC 2/ISO/SSO (g5), pipeline forecasting, AI-SDR ROI ("10x more opportunities" — cluster-C #7). Failure point: the AI-SDR wave (jtbd §4.1 Shift 1) is being served for outbound — Salestools' reprice to 79/seat “turned this from an enterprise line-item into an SMB purchase” (per jtbd §4.2 #1) — which means the enterprise’s content variant (J11: execs’ personal brands as pipeline) has “no equivalent” (per jtbd §5 Candidate B FOR #2): the board-level attribution job (g4) is served for employee shares (GaggleAMP/DSMN8 EMV/UTM, per cluster-E 6/11) but not for executive content.

Compound. Jobs: J9 (g4: “attribution from social activity to pipeline, so I can prove channel ROI”, per jtbd §2 (g)4); J13-adjacent (compliance-proof stack, per jtbd §4.2 #5). Tools: GaggleAMP custom (pipeline/EMV/UTM attribution, intent signals, SOC 2, “Proven to drive ROI in 90 days” — cluster-E #6), DSMN8 custom (CPC benchmarks, Salesforce/Marketo integrations, ISO-27001 — cluster-E #11), Haiilo custom (ISO/IEC 27001:2022 + SOC 2 Type II; Salesforce 25,000 employees — cluster-E #7), EveryoneSocial custom (SAML SSO, SCIM, SOC 2 Type 2, OAuth linking — cluster-E #10), Firstup custom (398% ROI TEI — cluster-E #8). Switching: security certs, board-level ROI proof, SSO. Failure point: J13’s verified-API posting is a 2-tool white space (MagicPost, Typefully — per jtbd §3 J13 row) — for an org whose procurement runs security review, the “compliance-proof my stack” job (jtbd §4.2 #5) can only be fully answered for posting by two small content tools, not by any enterprise platform (per cluster-D compliance table; cluster-E table B: none of the 11 advocacy/engagement tools claims a verified-partner badge).

Journey map (g):

Stage	Job(s)	Tools (price / compliance)	Failure point
Find	J1, J14	LeadFuze $1.5–2k/mo(datalicense);NetNut(seized);ApolloOrg$119/seat (ext); Scalelist $99+ (DB+ext, MCP); Wiza Team custom (ext)	Infra consolidating: LeadFuze pivot + NetNut FBI seizure (cluster-A 2/9)
Send	J2, J3, J11-outbound, g5	Salesloft custom (Sales Nav partner); Salestools $79–199\to$3,000+ (cloud AI SDR, SOC 2); Reply $500+(cloud);LGM€60–180(cloud+5Gproxies,MCP);lemlist$109+ (cloud, SOC 2); Salesflow $24.99/seat 100+ (cloud)	Content variant (J11) of AI agents unbuilt; outbound variant now SMB-priced (jtbd §4.2 #1; §5 Candidate B FOR #2)
Compound	J9, J13-adjacent	GaggleAMP custom (SOC 2, EMV/UTM); DSMN8 custom (ISO-27001); Haiilo custom (ISO+SOC 2); EveryoneSocial custom (SSO/SCIM); Firstup custom	J13 verified posting = only 2 tools; compliance-proof stack unserved at platform level (jtbd §3 J13; cluster-D compliance table)

2.8 (h) Growth hacker / power user

Journey: Find → Send → Engage → Publish (4 stages, agent-first; $0–$150/mo tooling + usage-based infra; values API/MCP access over UI — per jtbd §1 (h) budget context). The growth hacker buys the market as components and composes them — which is why the 2026 MCP wave (jtbd §4.1 Shift 2) is the single most relevant shift to this persona.

Find. Jobs: J14 (h2: “fresh signals… capture niche signals that no stale database has”, per jtbd §2 (h)2); J1 (via API). Tools: PhantomBuster 56€–352€ (cloud automations, “surface leads in context, not from stale databases”, MCP server — cluster-A #12), TexAu $79–$549 (table + REST API + MCP at mcp.texau.com, “Failed lookups cost zero” — cluster-A #11), Scalelist 99 (MCP server "Connect AI agents to Scalelist" — cluster-A #6), Octoparse 69–$249(no-codescraper,API,residentialproxies$3/GB — cluster-A #10), Wiza $49+ (no cached data — cluster-A #5), Crystal Data API custom (Personality AI MCP — cluster-A #8), NetNut (dead — cluster-A #9). Switching: pay-on-match credits, API/MCP over UI (per jtbd §1 (h)), 24/7 server-side execution (h3, per jtbd §2 (h)3). Failure point: the MCP layer is “enabled but not yet owned by any single vendor” (per jtbd §4.2 #3) — 14+ tools ship MCP servers (per jtbd §6 #4) and the growth hacker must still assemble the stack themselves.

Send. Jobs: J2/J4 (via automations); h4 (granular control — limits, timing, credit models, per jtbd §2 (h)4). Tools: LGM €60–€180 (MCP + Skills library, dedicated 5G mobile proxies, “stay under the radar” — cluster-C #6), lemlist 109 (MCP/API/CLI/agents — cluster-C #8), Salestools 79–199 (Nico, "MCP-native AI GTM Engineer" — cluster-C #11), HeyReach 79+ (MCP/CLI/API — cluster-C #1), TexAu (API+MCP — cluster-A #11), Dux-Soup 14.99 ("growth hackers" explicitly named — cluster-B #1), LinkedHelper 15 (30+ actions, “Operate completely under the radar” — cluster-B #4). Switching: API surface, granular limits, pay-on-match pricing. Failure point: none — Send is the growth hacker’s best-served stage (J2/J4 red oceans are advantageous to a power user who composes them); the failure is elsewhere: the content agent job (J11) is unbuilt, so the agentic loop they can run is outbound-only.

Engage. Jobs: J7/J8 (automation of engagement); h4 (credit/ghost-mode control). Tools: Lempod $9.99+(Gold/Silvercreditmodel,GhostMode$49.99 add-on — cluster-E #1), Linkboost $31–$47 (Smart Feed, Discover & Engage, analytics, buy-likes — cluster-E #3), Podawaa €29–€159 (auto-boost, lead-magnet seeding — cluster-E #2). Switching: credit economics, ghost mode, feed control. Failure point: engagement automation is the ToS wall — “LinkedIn’s official API restricts engagement automation… which is exactly why pods use extensions and why Lempod got pulled from the Chrome Web Store” (per jtbd §5 Candidate B AGAINST #3); the growth hacker’s J7/J8 automation runs entirely in ToS-grey territory.

Publish. Jobs: J6 (via MCP); J11-adjacent (autonomous content agents). Tools: MagicPost 21+ (**29-tool LinkedIn MCP server — write, schedule, analyze, engage, detect leads from Claude/ChatGPT**; official API — cluster-D #8), Taplio 39+ (Taplio LinkedIn MCP — cluster-D #2), Supergrow 19+ (MCP — cluster-D #5), Typefully 99/yr (MCP/API/agents, official API — cluster-D #7), FeedBoss $29+ (API — cluster-D #4), ContentIn (LinkedIn MCP — waitlist — cluster-D #10). Switching: MCP tool count, agent compatibility, API. Failure point: J11 (autonomous content agent) is 1-tool white space (Stanley, per jtbd §3 J11 row) — the growth hacker can orchestrate the loop via MagicPost’s MCP (per jtbd §5 Candidate B AGAINST #2: “an agentic wrapper… can already deliver most of the loop”) but nobody sells it as a product; per jtbd §6 #4, tools without an MCP story are invisible to exactly this buyer.

Journey map (h):

Stage	Job(s)	Tools (price / compliance)	Failure point
Find	J14, J1	PhantomBuster 56€ (cloud, MCP); TexAu $79–549(API+MCP);Scalelist$99 (MCP); Octoparse $69–249 (API); Crystal API custom (MCP)	Agentic-access job enabled, not owned (jtbd §4.2 #3)
Send	J2, J4, h4	LGM €60–180 (cloud+5G proxies, MCP); lemlist $109(MCP/API/CLI);Salestools$79–199 (MCP-native); HeyReach $79+(MCP/CLI);Dux-Soup$14.99 (ext); LinkedHelper $15 (desktop)	Best-served stage; no failure — J2/J4 red oceans favor composers
Engage	J7, J8	Lempod $9.99+(ext,creditmodel);Linkboost$31–47 (server-side); Podawaa €29+ (cloud)	Engagement automation hits the ToS wall (jtbd §5 Candidate B AGAINST #3)
Publish	J6, J11-adjacent	MagicPost $21+(officialAPI+29-toolMCP);Taplio$39+ (ext, MCP); Supergrow $19+(web,MCP);Typefully$99/yr (official API, MCP); FeedBoss $29+ (OAuth, API)	J11 unbuilt as a product; only orchestratable (jtbd §3 J11; §5 Candidate B AGAINST #2)

2.9 (i) Corporate marketing / employee advocacy

Journey: Publish → Compound (2 stages; custom-quote, annual contracts, demo-gated — NO public pricing anywhere in the segment, per jtbd §1 (i) budget context; 500+ employee floor, per cluster-E #7 Haiilo). This is the shortest journey in the market and the most enterprise-gated.

Publish. Jobs: J5/J6 (i2-adjacent: content creation for the advocacy feed); J13 (compliance). Tools: the advocacy platforms’ own content tools — Parliament AI content writer (“instantly craft captions and content” — cluster-E #9), DSMN8 AI Content Assistant (“tailored to your company voice” — cluster-E #11), GaggleAMP “Create activities with AI — AI paraphrasing, unique post variations per advocate” (cluster-E #6), Haiilo Advocacy (AI content creation — cluster-E #7), Sociabble (“AI-suggested captions” — cluster-E #5). Switching: brand governance (i2: “pre-approved, on-brand content feeds”, per jtbd §2 (i)2), content feed quality. Failure point: the creation capability inside advocacy platforms is a module, not the product (Smarp→Haiilo is now “intranet + comms + advocacy”, per cluster-E 4/7); there is no advocacy-native, voice-true creator — the J5 red ocean (12 tools) serves individuals, not employee feeds.

Compound. Jobs: J9 (i1: “employees share brand content… networks 10 times larger than our page following”; i2: content governance; i3: “attribution and earned-media value, so I can prove ROI”; i4: “Teams/Slack distribution, SSO, and compliance certs… at scale”; i5: “delegated posting on behalf of executives”, per jtbd §2 (i)1–(i)5). Tools: GaggleAMP custom (Slack/Teams one-click, SOC 2, EEMV/ROI calculator, “Amplify the executive voice” — cluster-E #6), Haiilo custom (MS Teams feed, ISO 27001 + SOC 2 Type II, 561% reach stat — cluster-E #7), DSMN8 custom (Delegate Access exec posting “without password sharing”, ISO-27001 — cluster-E #11), EveryoneSocial custom (execs/staff/company pages, OAuth, SOC 2 Type 2, SAML SSO, SCIM, “Built for regulated industries” — cluster-E #10), Parliament custom (92% new-to-brand stat, Teams/Slack, inside Hootsuite Enterprise — cluster-E #9), Firstup custom (Dynamic Signal heritage — cluster-E #8), Sociabble custom (Poppulo merger pending — cluster-E #5). Switching: security review (i4), annual contract, demo-gated purchase, 500+ employee floor (per cluster-E #7). Failure point: J10 — the SMB variant of this exact journey — is 0 dedicated tools (per jtbd §3 J10 row): “between Lempod/Linkboost ($0–$200/mo, self-serve, ToS-risky pods) and the enterprise advocacy platforms ($850+/mo,annualcontracts,demo-gated,500+employeebuyers)thereisessentiallynocredibleofferingat$100–$500/mo” (per cluster-E takeaway #1); and the buying-behavior mismatch is structural — a 20–200 person company “cannot buy them self-serve even if it could afford them” (per jtbd §5 Candidate A FOR #3).

Journey map (i):

Stage	Job(s)	Tools (price / compliance)	Failure point
Publish	J5/J6 (feed), J13	Parliament AI writer (custom, platform); DSMN8 AI assistant (custom); GaggleAMP AI paraphrase (custom); Haiilo Advocacy AI (custom); Sociabble AI captions (custom)	Creation is a module inside comms suites, not voice-true product (cluster-E 4/7)
Compound	J9, i1–i5	GaggleAMP custom (Slack/Teams, SOC 2); Haiilo custom (ISO+SOC 2); DSMN8 custom (Delegate Access); EveryoneSocial custom (OAuth, SSO/SCIM); Parliament custom (add-on); Firstup custom; Sociabble custom	J10 = 0 dedicated tools; 10–100× price gulf; demo-gated (jtbd §3 J10; cluster-E summary A, takeaway #1)

---

3. Cross-Persona Synthesis

3.1 Stage traffic: overcrowded vs abandoned

Count = personas whose journey (per §2) includes the stage.

Stage	Personas traversing	Count	Jobs at that stage (verdict per jtbd §3)	Market verdict
Send	a, b, c, e, f, g, h	7	J2 (~22, most over-served), J3 (~13), J4 (~15), J17 (~17)	Most overcrowded stage — every commercial persona converges here; 4 red-ocean jobs
Find	a, b, c, e, f, g, h	7	J1 (~20), J14 (~10–12), J15 (~11), J16 (0 dedicated)	Overcrowded — same 7 personas; 2 red oceans + 1 structurally unserved
Publish	a, c, d, f, h, i	6	J5 (12), J6 (~15), J13 (2 — white space)	Overcrowded at the tool level — but the only stage carrying a white-space job (J13)
Engage	a, b, c, d, f, h	6	J7 (3 dedicated), J8 (~9, 0 flagship), J12 (1 live)	Under-served as primary positions — every job here is touched-but-not-owned
Compound	d, f, g, i (e partially)	3–4	J9 (7 core, enterprise-priced), J10 (0), J11 (1)	Abandoned in the middle — the stage where the market structurally disappears

Reading: Send and Find are where 7 of 9 personas converge and where the market’s 6 red-ocean jobs live (J2/J1/J17/J4/J6/J3; J14 “turning red” excluded from the count — 7 with it) (per jtbd §3 reading). Engage is traversed by 6 personas but every one of its jobs is under-served as a primary position — J8 especially: “~9 tools, 0 flagship” (per jtbd §3 J8 row). Compound is traversed by the fewest personas (d weakly, f aspirationally, g/i at enterprise price only) and is the only stage with two white-space jobs (J10: 0 tools; J11: 1 tool) (per jtbd §3).

3.2 Shared journeys (cluster analysis)

Journey cluster	Personas	Shared stages	Why they converge	Evidence
The outbound cluster	(a) founder, (b) SDR, (c) agency, (e) recruiter	Find → Send	All four hire the same Find→Send loop but at different price bands and with different accountability (self-funded vs quota vs client pass-through vs employer seat)	jtbd §2 (a)1/(b)1/(c)1/(e)2; the persona×price-band table (jtbd §1) shows (a) $0–99,(b)$49–129, (c) $100–2,999,(e)$49–150
The brand cluster	(d) creator, (i) corporate advocacy	Publish → Compound	Same “people amplify content” mechanics, opposite buying journeys: (d) self-serve $19–99/mowithfreetrialsandnoprocurement;(i)custom-quote$733+/mo effective with annual contracts and security review	jtbd §1 (d) contrast with (i) — explicitly called out
The all-in-one straddler	(f) SMB marketing team	Find → Send → Publish → Compound	The only persona that traverses all four commercial stages — buys “all-in-one” (f1) and dies at Compound (J10)	jtbd §2 (f)1; cluster-E takeaway #4
The infra buyers	(g) RevOps, (h) growth hacker	Find → Send (+ Engage/Publish for h)	Both compose the market rather than buy one tool — g at $3,000+/mocustomwithcerts,hat$0–150/mo + MCP/API; both are why MCP became the 2026 integration standard	jtbd §1 (g)/(h); jtbd §4.1 Shift 2
The single-stage specialists	(i) only	Publish → Compound only	The most concentrated journey — everything happens inside the advocacy platform	§2 (i); cluster-E 6/7/9

3.3 The compound stage is the market’s weakest link

• Structurally empty in the middle: J10 (SMB employee advocacy) has 0 dedicated tools and J11 (autonomous content agent) has 1 (Stanley) — the only two white-space verdicts among the 17 jobs besides J12 (personality intelligence, 1 live: Crystal) and J13 (verified-API posting, 2) (per jtbd §3 J10/J11/J12/J13 rows). J9 is “well-served at enterprise” but only at enterprise price: all seven advocacy vendors are custom-quote, demo-gated, annual-contract (per cluster-E pricing table), with third-party floors of $850–$3,500/mo (DSMN8), ~$733/mo(GaggleAMP$8,800/yr ⚠️), $240/user/mo(Parliament⚠️),$24/user/mo or $20k–$80k+/yr (EveryoneSocial ⚠️) — a ~10–100× price gap vs the $0–$200/mo pods (per cluster-E summary A).
• The personas that need Compound can’t buy it, the ones that can buy it don’t traverse it: (f) SMB teams hit the J10 wall (cluster-E takeaway #4: the (f)×(i) intersection “is served by nobody in this cluster”); (d) creators get a half-product (Stanley posts but doesn’t engage/convert — per jtbd §5 Candidate B FOR #3); (g) RevOps can buy J9 but its content-agent variant (J11) is unbuilt (per jtbd §5 Candidate B FOR #2).
• The compliance wedge makes it worse: the cheap Compound options are exactly the ToS-risky ones — Lempod’s extension was removed from the Chrome Web Store (cluster-E #1), HeyReach warns pods are algorithmically detectable (cluster-E #1 field 10/12) — while the compliant OAuth/consent mechanism (EveryoneSocial, DSMN8) exists only at enterprise price (per cluster-E takeaway #2).

---

4. The Opportunity Map for GrowReach

GrowReach = LinkedIn comment-generation + posting automation via Unipile (per task context). In JTBD terms that is: J8 (comment-to-pipeline) + J6 (posting) — per jtbd §6 #1, GrowReach “already owns the comment half of J8 (comment-gen) and the posting half of J6 (Unipile)“.

4a. Which persona journeys GrowReach currently serves

GrowReach feature	Job served	Stage	Personas served on that stage (from §2)
Comment generation (J8)	J8 turn engagement/comments into pipeline	Engage	(a) founder — d4-equivalent “turn engagement into opportunities”; (d) creator — d4; (b) SDR — comment-to-pipeline; (c) agency — client comment conversion; (f) SMB team — f4 analytics
Posting automation via Unipile (J6)	J6 post scheduling/publishing	Publish	(a) founder — a2 “turn my LinkedIn into my best sales channel”; (d) creator — d1/d5; (c) agency — c5 multi-client voices; (f) SMB team — f3 team publishing; (i) advocacy-adjacent — i2 feed
Unipile OAuth/API connection (J13-adjacent)	J13 official-API-verified compliance	Publish (compliance layer)	All of the above — but critically (f) f5 “tool that passes review” and (g) the compliance-proof-stack job (jtbd §4.2 #5)

Per jtbd §6 #2, Unipile’s OAuth/API connection “puts GrowReach structurally in the company of MagicPost and Typefully — the only two official-API posting tools in the dataset” — so GrowReach’s compliance posture is already a differentiator no cluster-B/C tool and no pod can claim (per cluster-B compliance table: 0/11 official API; cluster-E table B: none of 11 claims a verified-partner badge).

Gap in current coverage: GrowReach today covers Engage (comment half) and Publish (posting half) but not the boost half of Engage (J7 first-hour engagement), not the lead-detection half of J8 (MagicPost already ships lead detection, per cluster-D #8), and nothing in Compound (J9/J10/J11) — no team accounts, no approval workflows, no advocacy layer (per jtbd §6 #3: “comment-gen + posting alone is a content tool”).

4b. Least-friction adjacent extension

Extend into the rest of the Engage stage: first-hour engagement (J7) + lead detection (J8). Per jtbd §6 #1: “Adding first-hour engagement or lead-detection would make GrowReach the only tool credibly spanning author→boost→convert at team scale — a position no tool in the 58 holds (per cluster-D #1 Kleo doesn’t automate, per cluster-E 1/2/3 pods don’t author credibly, per cluster-D #3 SayWhat doesn’t post automatically, per cluster-D #11 Stanley doesn’t engage).”

Why least friction:

1. The jobs are adjacent to what GrowReach already runs — comment-gen is the comment half of J8; lead detection is the other half of the same job; J7 (first-hour engagement) is the missing middle between Publish (already owned via Unipile) and Convert (already owned via comment-gen). The loop create→post→boost→convert is two features from complete (per jtbd §6 #1).
2. The white space is documented — J8 has ~9 tools but 0 flagships (per jtbd §3 J8 row); J7 has 3 dedicated tools, all with the pod-compliance problem (per jtbd §3 J7 row; cluster-E takeaway #2).
3. The compliance wedge makes the boost extension defensible — jtbd §6 #2: the compliant-first-hour-boost job (jtbd §4.2 #6, “safe amplification”) is “transitional — no tool owns the compliant-boost position outright”; GrowReach’s Unipile connection is the only mechanism in the cheap band that can answer it without a store-removable extension (per jtbd §6 #2; cluster-E #1).
4. The agent story compounds it — jtbd §6 #4: “GrowReach’s comment-gen + posting is a natural 5–10 tool MCP surface (write comment → schedule post → detect leads). Without it, GrowReach is invisible to exactly the buyers the 2026 market is consolidating around” — i.e., publishing an MCP server simultaneously serves persona (h) and completes the Engage loop for everyone else.

4c. Recommended target journey for GrowReach’s positioning

Primary target: persona (f) SMB marketing team on the Publish → Engage → Compound journey — the (f)×(i) intersection, i.e., J10 (SMB employee advocacy at $100–$500/mo).

Why:

1. It is the dataset’s clearest unowned job. jtbd §5 bottom line: “Candidate A (compliant SMB employee advocacy at $100–$500/mo) is the clearest unowned job in the dataset — a documented price gap, an unclaimed persona intersection, and a compliance wedge with no incumbent.” Cluster-E takeaway #4 names the (f)×(i) intersection “GrowReach’s clearest slot”; the price gap is 10–100× ($0–$200/mo pods vs $850+/mo enterprise advocacy, per cluster-E summary A).
2. The density map supports it. J10 = 0 dedicated tools; J9 = 7 core but enterprise-priced; the only partials (Supergrow Teams $139/4 accounts, MagicPost Teams custom, Lempod Company Pod) each “lack at least one of: compliant connection, self-serve price, team scale” (per jtbd §5 Candidate A verdict) — GrowReach’s Unipile connection + public pricing + comment-gen covers exactly the missing combination.
3. It converts GrowReach’s current features into a Compound entry — per jtbd §6 #3: to claim J10 “GrowReach needs the advocacy layer: team accounts, approval workflows, a leaderboard, and per-employee sharing — then price publicly in the $100–$500/mo band, exactly between Linkboost Plus (47, per cluster-E #3) and GaggleAMP (~733/mo ⚠️ third-party, per cluster-E #6)”.
4. The flank against Stanley stays open. The secondary beneficiary of the same positioning is persona (d) on Publish → Engage: jtbd §6 #5 — Stanley’s loop lacks comment generation and team scale, “the two things GrowReach has”; “the flanking move is not ‘another AI poster’ — it’s the loop + engagement + team.”

Secondary target: persona (d) personal brand creator + persona (h) growth hacker on the Publish → Engage loop — the J8/J11-adjacent position (full create→post→engage→convert loop at self-serve price, per jtbd §5 Candidate B verdict: “real but partially occupied by Stanley and threatened by MCP-orchestration commoditization” — hence secondary, not primary).

Positioning statement the data supports (synthesis of jtbd §6 #1–#6): GrowReach should position as the compliant engagement loop for teams — comment-gen + posting (owned today) extended with first-hour engagement and lead detection (least-friction J7/J8 extension), sold at public self-serve prices ($29–$99/mo content+engagement, or $100–$500/mo advocacy — per jtbd §6 #6) with the Unipile official-connection story (“official connection, no cookies, no extension” — per jtbd §6 #2), and an MCP server to stay visible to the agent-first buyer (per jtbd §6 #4).

---

Report generated 2026-08-14 from jtbd-analysis.md (kimi-k3-reviewed, primary input), the five cluster research files (A–E), and linkedin-market-index.md. All pricing figures marked ⚠️ third-party in the source files (GaggleAMP $8,800/yr,DSMN8$850–$3,500/mo,Parliament$240/user/mo, EveryoneSocial $24/user/moand$20k–$80k/yr,EasyGen$59.99, Brandled $47) are NOT confirmed on vendor sites and are treated as secondary evidence. Dead/off-market tools (NetNut, SaleeAI, LiProspect, Brandled, Smarp-as-brand) are cited only as market-structure evidence. This document feeds the final market analysis (Stage 3).