E-commerce / DTC

How Kindling Coffee used Linkeddit MCP to wire Reddit conversations into Shopify and Klaviyo

Kindling Coffee Co.DTC specialty coffee brand, $4M ARR

AI Content Writer (niche-voice tuning)Linkeddit MCP + Shopify + KlaviyoSubreddit-level sentiment tracking via get_lead_insights
$84k
Attributed revenue / 90 days
6.3k
New email subscribers
11x
ROAS vs. Meta ads
2.9x
Email LTV lift

After Meta CPAs doubled in 12 months, Kindling rebuilt their top-of-funnel around Reddit. The Linkeddit MCP connection to Shopify and Klaviyo meant a recommendation on r/Coffee could become a tagged Klaviyo segment, a UTM'd discount code, and a tracked order — without copy-paste.

Background

Kindling roasts small-lot single-origin coffee. Their customers are the kind of people who own a V60 and argue about water chemistry on Reddit. Meta worked until it didn't — the iOS update collapsed their lookalikes and the team watched ROAS drop from 4.8 to 1.6 inside six months. They needed a channel where their actual product knowledge was an advantage, not a commodity.

The problem

DTC coffee is margin-thin. A $28 bag at 62% gross leaves $17 per customer — minus $14 CAC on Meta leaves $3 to pay for everything else. Reddit looked like the only channel where authentic brand voice could drive CAC below $10, but managing it manually would burn out their one-person marketing team.

Pipeline configuration

Kindling Coffee Co. runs 2 Linkeddit pipelines. Each one is scoped to a narrow set of subreddits and keyword patterns so the lead queue never turns into noise.

Purchase-intent signals

Subreddits
r/Coffeer/espressor/pourover
Refresh cadence
Refreshed every 2 hours
Keywords
single origin recommendationlight roast subscriptionbest beans for V60switching from blue bottletrade coffee alternative
Filters
  • Contactability score ≥ 60
  • Thread age < 48 hours
  • OP must have coffee-related comment history

Brand-comparison threads

Subreddits
r/Coffeer/roasting
Refresh cadence
Refreshed every 4 hours
Keywords
vs onyx coffeevs sey coffeevs blue bottleindie roaster recommendations
Filters
  • Contactability score ≥ 70
  • Thread has ≥ 10 comments
  • Recent activity in last 12 hours

AI Content Writer workflow

  1. 1.The Content Writer was tuned on Elena's 40-post corpus until drafts passed a 'would Elena post this?' blind test from her team.
  2. 2.Every reply is structurally required to recommend 2–3 roasters (Kindling only named when objectively relevant), cite specific beans with origin + process, and disclose 'full disclosure I roast' where applicable.
  3. 3.Each reply appends a tracked bit.ly redirect that flows into Shopify as a UTM source — no ugly ?utm_campaign= strings in the actual comment.
  4. 4.Drafts failing three Elena-voice quality gates (anti-shill, specificity, humility) are auto-rewritten before surfacing.

Linkeddit MCP + AI integration

Kindling's Claude setup runs a weekly 'subreddit sentiment report' that informs product roadmap, email segmentation, and even roast decisions. This is where MCP moves from marketing to operations.

Linkeddit MCP tools used
  • search_leads— surfaces buyers
  • get_lead_insights— pulls bio, niche tags, engagement score
  • fetch_subreddit— weekly pulls of r/Coffee top threads for sentiment
  • search_reddit— surfaces long-tail coffee queries Kindling could own on SEO
External MCPs connected
  • Shopify MCP — creates single-use discount codes tagged with thread ID
  • Klaviyo MCP — adds opted-in subscribers into 'Reddit: r/Coffee' segments with custom flows
  • Notion MCP — drops weekly sentiment report into the ops doc for the roasting team
  • Google Sheets MCP — logs every reply + outcome for cohort analysis
Example Claude prompt
Every Monday at 9am, pull the 40 highest-scored leads from the last 7 days, cluster them by coffee style preference (natural vs washed, light vs medium, espresso vs filter), and write a one-page brief for the roasting team. Include 5 quote examples from each cluster. Then create 4 Klaviyo segments matching these clusters and draft the first email for each.

Want to run this workflow yourself? Set up the Linkeddit MCP server or connect via the Claude connector.

Daily rhythm

  • Morning — Elena skims overnight leads in Slack, replies to 3–5 herself to keep voice calibrated.
  • Afternoon — Ops manager batches 8–12 replies using Content Writer drafts.
  • Monday 9am — Weekly Claude-generated sentiment brief lands in Notion.
  • Friday 4pm — Cohort analysis: which threads drove orders, which segments had highest LTV.

Thread breakdown

A V60 hobbyist in r/pourover asked about 'a natural Ethiopian under $25 that isn't Onyx.' Kindling surfaced it at 14 minutes. The reply recommended three roasters (Onyx as #3 to de-shill the post), cited Kindling's current Guji lot with TDS numbers, and linked to a tracked URL. OP ordered within 30 minutes. Six months later, OP is on subscription, LTV $340+.

Subreddits monitored

r/Coffeer/espressor/pouroverr/roastingr/baristar/Coffee_Shop

Results

  • $84k in first-touch attributed revenue over 90 days.
  • 6,300 new email subscribers — 41% higher list-growth rate than the Meta-era peak.
  • Reddit-sourced subscribers have 2.9x the LTV of Meta-sourced.
  • Two of Kindling's 2026 lot-purchasing decisions were informed by the weekly sentiment report.

Lessons

  • 1.Voice tuning is the entire game. A blind 'would Elena post this?' test — scored by her team, not Elena — caught every off-brand draft.
  • 2.Don't link the store directly. A content-first post (blog, brew guide, flavor notes) converts 4x better than a product page.
  • 3.Weekly sentiment reports shifted product decisions. Reddit became the cheapest market research in the company.

I didn't want 'more marketing.' I wanted to talk to people who actually care about coffee. Linkeddit plus Claude MCP turned that into an ops system — the reply, the Klaviyo segment, the discount code, and even what we roast next month are all downstream of a Reddit thread.

Elena Rodriguez, Founder, Kindling Coffee Co.

Build a DTC Reddit + MCP stack

Same stack, same playbook. Free to start, under 5 minutes to set up.

Other case studies