Linq's best proof is hidden. Since May it has published eight customer stories on the blog (VentNow, Caddy, Town, Slash, Lindy, Ollie, Zo Computer and an AI talent agent), including VentNow's A/B test with 40% lower churn and a 16% higher lifetime value. But the customer stories page still shows only Poke and Tomo from March 2025, its canonical tag points to /blog so search engines are told to ignore it, the homepage "Read Stories" button opens the 2025 Tomo post, and llms.txt tells AI assistants the case studies are "Poke and Tomo". The Growth Strategist is hired to write case studies and build landing pages; this is the first page to fix.
First action
Change the canonical tag on /s/customer-stories to itself and add the eight newer stories as cards.
How to measure it
Demo requests that viewed a customer story
- Now
- –
- Target
- +25%
- By
- 60 days
Steps
Fix the canonical
Self-referencing canonical on /s/customer-stories; resubmit in Search Console.
Software Engineer 1 hour
List every story
All ten stories as cards, newest first, with a headline number each.
Growth Strategist 1 day
Add filters
Use case and company stage, so a fintech or companion buyer finds its peer.
Software Engineer 2 days
Repoint links
Homepage "Read Stories", llms.txt and the AI context page to the hub.
Growth Strategist 2 hours
Place proof near decisions
One relevant story on pricing, talk-to-an-expert and the iMessage API page.
Growth Strategist 2 days
Tag the blog
Mark Caddy and every future story as "Customer Story" so it flows to the hub.
Growth Strategist 1 hour
Measure
Story views before a demo request, by story.
Head of Product & Growth monthly
Why it works
Rebuild /s/customer-stories as the hub for all ten stories, with a self-referencing canonical, a headline result on each card (VentNow: 40% lower churn; Slash: $1 billion a month in volume; Caddy: iMessage beat email and Slack on the same backend), and filters by use case (assistant, companion, fintech, recruiting, family). Point the homepage "Read Stories" button and llms.txt at it, link the relevant story from pricing and talk-to-an-expert, and add a short results strip ("40% lower churn", "16% higher LTV") above the form.
Buyers of messaging infrastructure want evidence that the channel moves their own numbers. The results already exist; putting them where buyers, search engines and AI assistants look turns them into pipeline.
Ready to use
ChecklistCustomer stories hub launch list
[ ] Canonical on /s/customer-stories points to itself [ ] All ten stories listed with one headline number [ ] Filters: assistant, companion, fintech, recruiting, family [ ] Homepage "Read Stories" points to the hub [ ] llms.txt and AI context page updated [ ] One story on pricing and talk-to-an-expert [ ] Caddy re-tagged as Customer Story [ ] Each customer approved its card
Risks and how to handle them
Customers object to more prominent placement
Send each customer the card before publishing.
A single A/B test is overstated
Keep VentNow's "What these numbers do not show" caveat on the card.
Evidence
- Your websiteThe customer stories page (/s/customer-stories) shows two stories, "How Poke Scaled Messaging" and "How Tomo Scaled to Hundreds of Thousands of Messages" (both published in March 2025), and its canonical tag points to /blog rather than to itself. The homepage "Read Stories" button links to the March 2025 Tomo post.Source
- Your websiteBlog sitemap (34 posts, checked November 4, 2026): eight customer stories published since May 2026 that the stories page does not list: Zo Computer (May 20), Lindy (July 14), Ollie (August 11), an AI talent agent (August 21), Slash (August 24, "Slash processes over $1 billion in transaction volume per month"), VentNow (September 1), Caddy (September 4) and Town (October 8).Source
- Your websiteVentNow story: users on iMessage "sent 20% more messages per session, were about 40% more active on a daily basis, and churned 40% less on paid plans. Early results estimate a 16% higher lifetime value." The post includes a section "What these numbers do not show". Caddy: "We took the same backend. We threw it into email, we threw it into Slack, we threw it into iMessage. iMessage immediately took off."Source
- Your websitellms.txt, the file written for AI assistants, describes the stories page as "Case studies including Poke and Tomo" and lists four comparison pages (Linq vs Sendblue, Blooio, Photon and Chert) and the iMessage vs SMS guide.Source
- HiringGrowth Strategist (San Francisco, posted July 20, 2026, $85K-$110K plus equity): the growth team "is responsible for finding, converting, and retaining the businesses and developers who power their products on Linq". The role covers "events, gifting campaigns, writing blog posts, building landing pages, and spinning up new channels you think we are missing"; it will "Help write content: blog posts, case studies, landing pages", "Own our gifting campaigns to target customers & prospects", "Coordinate campaigns with our influencers" and help run "customer dinners, our annual conference, hackathons", working directly with the Head of Product & Growth.Source