ProgrammableMarketing/ably.com (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 5
  • This quarter · 9
  • Big bets · 3
  • Wildcards · 3
  • How we can help
Generated Oct 18, 2026
  1. Programmable
  2. Playbooks
  3. Ably
Ably logo

growth playbook · Oct 18, 2026

ably.com (opens in a new tab)

Ably growth playbook

Diagnosis

Ably runs realtime infrastructure at enormous scale (30B+ connections and 2T+ API operations a month, 7+ years of 100% uptime) and has made an early, well-documented bet on AI Transport, a durable session layer for AI agents.

Its hiring says the next stage is winning the AI-agent developer: it is standing up a dedicated DevRel function "from the ground up" aimed at showing up in AI assistant answers and the Temporal and Vercel communities, a product marketer to own AI Transport positioning and competitive intelligence, and a GTM Engineer to build the commercial systems that nobody owns end to end today.

The gaps are in turning deep assets into pulled-in developers: the best writing on resumable AI streaming is scattered across a dozen blog posts with no canonical page, the AI Transport landing page hides the price behind sales, and about 630 bulk comparison pages were built for the old realtime-messaging buyer.

Growth Score

7/10

Biggest Opportunity

Own the "durable session layer for AI agents" decision before a rival names it: one canonical comparison page, a forkable demo and accurate AI-readable docs, so that when a developer or an AI assistant asks how to keep an AI session alive across a dropped connection, Ably is the answer, routed into the free tier.

Biggest Risk

Ably is read as realtime messaging infrastructure while the AI-agent buyer looks elsewhere, and the Vercel AI SDK, Cloudflare or a new entrant defines the AI session-continuity category first; without a dedicated developer presence and a clear, cited story, Ably competes on price against bundled and build-it-yourself options.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    A "resumable streaming for AI agents" comparison page: Ably AI Transport vs the Vercel AI SDK, Temporal and roll-your-own

    Outline the decision table (connection drop, tab switch, device switch, multi-agent, human handoff) with an honest yes/no/partial for each option.

    High impact First result in 2-4 weeks
  2. 2

    Put the AI support chatbot cost ($109.50/month) on the AI Transport page

    Lift the AI support chatbot example onto the AI Transport page above the sales CTA.

    High impact First result in 2 weeks
  3. 3

    Alert sales the moment a free AI Transport project crosses a usage threshold

    Write the threshold query over usage and list this week's free projects that already cross it.

    High impact First result in 3 weeks

02

Your idea portfolio

20 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 8 ideas are marked Unexpected: plays you are unlikely to have tried.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 3Big bets · 8Fill-ins · 3Reconsider · 6
Effort →

Showing 20 of 20 ideas

This week 5

Quick wins with a clear first action.

  • 01

    Developers now pick infrastructure on what AI assistants tell them, and the first thing someone building an AI agent hits is a dropped stream. Ably already has the deepest writing on this, but it is spread across a dozen blog posts with no single page that answers "what should I use?".

    High impactLow effort First result in 2-4 weeks Developer Relations Manager

    First action

    Outline the decision table (connection drop, tab switch, device switch, multi-agent, human handoff) with an honest yes/no/partial for each option.

    How to measure it

    Signups from the resumable-streaming comparison

    Now
    –
    Target
    250 in the first quarter
    By
    12 weeks

    Steps

    1. 1

      Map the four options

      Vercel AI SDK resumable-stream, Workflow DevKit, roll-your-own SSE, Ably AI Transport, each with its real limits.

      Developer Relations Manager 1 day

    2. 2

      Build the decision table

      Rows for the failure modes developers actually hit; be fair about where Ably is overkill.

      Developer Relations Manager 3 hours

    3. 3

      Write runnable snippets

      A before/after in the Vercel AI SDK that a developer can paste and run.

      Developer Relations Manager 1 day

    4. 4

      Fix the duplicate explainers

      Collapse the /vercel/ and /topic/ai-stack/ versions to one URL so the canonical page is unambiguous.

      Senior Developer Experience Writer 1 hour

    5. 5

      Make it AI-readable

      A clean markdown version in llms.txt so assistants quote the current page.

      Senior Developer Experience Writer 2 hours

    6. 6

      Seed it honestly

      The DR shares it in the Vercel and Temporal communities as a resource, not an ad.

      Developer Relations Manager ongoing

    First result
    2 to 4 weeks
    Cost
    $0, about three days of work
    Owner
    Developer Relations Manager

    Smallest test

    Publish the decision table alone and watch which rows get quoted and linked.

    Why it works

    Publish one authoritative, regularly dated page that lays out the four ways to keep an AI session alive across a dropped connection (the Vercel AI SDK resumable-stream, Vercel Workflow DevKit, build-your-own on SSE, and Ably AI Transport), what each covers and does not, with a decision table and runnable snippets. Written to be quoted by AI assistants, not just ranked.

    The DevRel role is hired to make AI Transport known to developers who "ask AI assistants which realtime infrastructure to use" and already names LangGraph reconnection failures and Temporal objections. A single honest comparison is the page an assistant cites and a developer forwards.

    Risks and how to handle them

    • Reads as marketing in a developer community

      Lead with the cases where Ably is the wrong choice; credibility is the point.

    Evidence

    • HiringDeveloper Relations Manager: "Ably hasn't had a dedicated DevRel function in some time", so the role builds one; be "the feedback loop between developers and Ably", build a genuine presence in the Temporal and Vercel communities, and get "Ably showing up accurately when developers ask AI assistants to support technical evaluations and builds". Developers now choose infrastructure on "what AI assistants tell them, not search rankings alone".Source
    • Your websiteThe blog has a deep AI Transport series (why AI agents need a durable session layer, Vercel AI SDK production session layer, Temporal workflow streams, OpenAI Responses API, mid-run steering, database hydration) and a long-form "Vercel AI SDK resumable stream: what it covers and what it doesn't" explainer.Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
    • Your websiteTwo near-identical AI-stack explainers exist at ably.com/vercel/... and ably.com/topic/ai-stack/..., both with the canonical set to the /vercel/ URL. The /compare pages are generated in bulk, including many rival-vs-rival pairings that do not mention Ably (for example amazon-eventbridge-vs-pubnub).Source
  • 02

    The DevRel post names two live pains: LangGraph reconnection failures and recurring Temporal objections. Those conversations are happening now in Discords, GitHub issues and forums, from people mid-build who have not heard of AI Transport.

    Medium impactLow effort First result in 2 weeks Developer Relations Manager

    First action

    Set up saved searches for reconnection and resume questions across the five communities.

    How to measure it

    Helpful community answers a week that cite a working fix

    Now
    –
    Target
    10 a week
    By
    6 weeks

    Steps

    1. 1

      Set the listening posts

      Saved searches and alerts across Temporal, Vercel, LangGraph, GitHub and Reddit.

      Developer Relations Manager 2 hours

    2. 2

      Write three canned fixes

      Reusable, specific answers for the three most common reconnection failures.

      Developer Relations Manager 3 hours

    3. 3

      Answer as a peer

      Working code first; the product link only when it is the honest answer.

      Developer Relations Manager ongoing

    4. 4

      Carry feedback back

      Log recurring objections for product and the PMM each week.

      Developer Relations Manager 30 minutes a week

    5. 5

      Turn clusters into docs

      When one question recurs, the DX writer turns it into a docs page.

      Senior Developer Experience Writer as needed

    6. 6

      Report

      Answers given, upvotes, and signups that follow.

      Developer Relations Manager 15 minutes a week

    First result
    2 weeks
    Cost
    $0
    Owner
    Developer Relations Manager

    Smallest test

    Spend one week answering only Temporal reconnection questions and count the replies.

    Why it works

    Run a weekly sweep of the Temporal, Vercel, LangGraph and r/LocalLLaMA communities for "stream dropped", "resume after reload" and reconnection questions, and answer them as an engineer with a working fix, linking the comparison page only when it genuinely helps.

    Building a "genuine presence in the Temporal and Vercel communities" is the role's stated success measure. Helpful answers at the moment of need are how a brand-new DevRel function earns trust, and each one is a durable, searchable, AI-indexed answer.

    Risks and how to handle them

    • Comes across as drive-by promotion

      Measure on helpful answers, not links dropped; let moderators see a real contributor.

    Evidence

    • Search resultsThe DevRel post names concrete developer pain it has already heard: LangGraph reconnection failures and recurring Temporal objections. The role is framed as complementary to a Developer Growth Manager who owns the rest of the funnel.Source
    • HiringDeveloper Relations Manager: "Ably hasn't had a dedicated DevRel function in some time", so the role builds one; be "the feedback loop between developers and Ably", build a genuine presence in the Temporal and Vercel communities, and get "Ably showing up accurately when developers ask AI assistants to support technical evaluations and builds". Developers now choose infrastructure on "what AI assistants tell them, not search rankings alone".Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
  • 03

    The pricing page already has a worked example showing an AI support chatbot costs about $109.50 a month for 35,000 chats, but the AI Transport landing page sends buyers to "Speak to sales" without a number. Developers bounce when there is no price.

    High impactLow effort First result in 2 weeks Product Marketing Manager

    First action

    Lift the AI support chatbot example onto the AI Transport page above the sales CTA.

    How to measure it

    AI Transport page to free-project starts

    Now
    –
    Target
    +20% relative
    By
    4 weeks

    Steps

    1. 1

      Surface the examples

      Move the chatbot and agent cost examples onto the AI Transport page.

      Product Marketing Manager 2 hours

    2. 2

      Lead with the free tier

      500 MAUs, no card, stated before "Speak to sales".

      Product Marketing Manager 1 hour

    3. 3

      Link the calculator

      A "what will my use case cost" link into the pricing examples.

      GTM Engineer 2 hours

    4. 4

      A/B test the order

      Free-tier-first against sales-first for two weeks.

      GTM Engineer 2 hours

    5. 5

      Track starts

      Free project starts from the AI Transport page by variant.

      GTM Engineer 1 hour

    6. 6

      Roll out the winner

      Keep whichever lifts self-serve starts.

      Product Marketing Manager 15 minutes

    First result
    2 weeks
    Cost
    $0
    Owner
    Product Marketing Manager

    Smallest test

    Add only the free-tier line and the one cost example and watch project starts.

    Why it works

    Add the worked cost examples and the free 500-MAU tier directly to the AI Transport page, with a "see what your use case costs" calculator link, so a developer sees a concrete number before deciding to build.

    The PMM owns AI Transport positioning and launches, and the self-serve funnel is the DevRel role's top of funnel. A concrete monthly cost next to the free tier removes the biggest reason a developer defers the decision.

    Risks and how to handle them

    • A published price scares off large deals

      Keep "Speak to sales" for enterprise; the price serves the self-serve developer.

    Evidence

    • Your websiteThe AI support chatbot pricing example on the pricing page costs about $109.50/month for 35,000 chats, and AI Transport docs include a dedicated pricing page and a "going to production" guide; the free tier is 200 concurrent connections and 6M messages a month.Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
    • HiringProduct Marketing Manager: targets technical and developer personas in B2B SaaS, owns launches and positioning, and a responsibility is "creating an AI-powered competitive intelligence system".Source
  • 04

    Ably has about 630 comparison pages and 31 alternatives pages, but they were built for the old "realtime messaging" buyer and many (such as amazon-eventbridge-vs-pubnub) do not involve Ably at all. None leads with what now decides the choice: does it keep an AI session alive.

    Medium impactLow effort First result in 4-8 weeks Product Marketing Manager

    First action

    List every /compare page that does not contain the word "Ably" and decide retire or noindex.

    How to measure it

    Signups from the updated comparison pages

    Now
    –
    Target
    +30% relative
    By
    8 weeks

    Steps

    1. 1

      Audit the set

      Flag rival-vs-rival pages with no Ably mention; flag thin pages.

      Product Marketing Manager 1 day

    2. 2

      Retire or noindex

      Remove crawl budget from pages that send readers to competitors.

      Senior Developer Experience Writer 2 hours

    3. 3

      Add the AI row

      An AI session-continuity section on the Ably-vs-PubNub/Pusher/Supabase/Durable Objects pages.

      Product Marketing Manager 1 day

    4. 4

      Keep claims honest

      Cite each rival's own docs; date every page.

      Product Marketing Manager 3 hours

    5. 5

      Internal links

      Link the comparison page from AI Transport and the resumable-streaming page.

      Senior Developer Experience Writer 1 hour

    6. 6

      Measure

      Rankings, clicks and signups per updated page.

      GTM Engineer 30 minutes a week

    First result
    4 to 8 weeks
    Cost
    $0
    Owner
    Product Marketing Manager

    Smallest test

    Update only the Ably-vs-PubNub and Ably-vs-Cloudflare pages and compare signups.

    Why it works

    Audit the compare and alternatives pages, retire or noindex the rival-vs-rival pages that never mention Ably, and add an "AI session continuity" section to the Ably-vs-X pages (PubNub, Pusher, Supabase, Cloudflare Durable Objects) that most buyers now read.

    The PMM owns competitive intelligence and positioning. Reclaiming crawl budget from pages that help competitors, and updating the ones that matter for the AI buyer, is a direct lift with assets that already rank.

    Risks and how to handle them

    • Removing pages loses some long-tail traffic

      Noindex rather than delete first, and keep anything that converts.

    Evidence

    • programmable.infoSite scan: 793 blog posts, 771 docs pages, about 630 /compare pages and 31 /alternatives pages (PubNub, Pusher, Socket.IO, Cloudflare Durable Objects, Supabase, Firebase and more), 25 case studies, and a published llms.txt index. The homepage is freemium from $29/month; Tranco rank about 49,000; 91 Hacker News mentions; 1,307 GitHub stars across public repos (top repo ably-pubsub-js, 368).Source
    • Your websiteTwo near-identical AI-stack explainers exist at ably.com/vercel/... and ably.com/topic/ai-stack/..., both with the canonical set to the /vercel/ URL. The /compare pages are generated in bulk, including many rival-vs-rival pairings that do not mention Ably (for example amazon-eventbridge-vs-pubnub).Source
    • Competitor researchRealtime infrastructure rivals: PubNub and Pusher (Ably's longest-standing comparisons), Supabase Realtime and Firebase (bundled with a backend), Cloudflare Durable Objects (a build-it-yourself primitive), and Stream and Sendbird (chat-specific). For AI session continuity the alternatives are the Vercel AI SDK's Redis-backed resumable-stream, Vercel Workflow DevKit and rolling your own on SSE.Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
  • 05

    Thousands of developers start free projects, but with no dedicated DevRel or usage-based routing until now, a team quietly scaling AI Transport in production can pass the point of a sales conversation unnoticed.

    High impactLow effort First result in 3 weeks GTM Engineer

    First action

    Write the threshold query over usage and list this week's free projects that already cross it.

    How to measure it

    Meetings booked from usage-triggered PQLs

    Now
    –
    Target
    15 a month
    By
    end of quarter

    Steps

    1. 1

      Define the thresholds

      Connections, messages and MAUs that signal a production workload.

      GTM Engineer 1 day

    2. 2

      Reconcile the data

      Join product usage to HubSpot and Snowflake so the number is trusted.

      GTM Engineer 2 days

    3. 3

      Enrich the account

      Company size and stack on the record automatically.

      GTM Engineer 1 day

    4. 4

      Draft the outreach

      An agent drafts a first note referencing what they are building; a human sends it.

      GTM Engineer 2 days

    5. 5

      Route to sales

      Top-tier PQLs become tasks with the usage context attached.

      GTM Engineer 1 day

    6. 6

      Review weekly

      PQL volume against meetings booked; tune thresholds.

      GTM Engineer 30 minutes a week

    First result
    3 weeks
    Cost
    $0, about a week of engineering
    Owner
    GTM Engineer

    Smallest test

    Hand-pull the top 20 free projects by usage this week and have sales email them.

    Why it works

    Build the exact system the GTM Engineer post describes: when a free or self-serve project crosses a connection, message or MAU threshold, flag it as a product-qualified lead, enrich the company, and draft the first outreach for a human to send.

    The GTM Engineer is hired to "flag an best-fit customer profile account the moment its usage crosses a threshold and draft the first outreach". Usage is the truest buying signal Ably has, and nobody owns it end to end today.

    Risks and how to handle them

    • Outreach feels like surveillance of usage

      Reference only aggregate account usage, lead with help, and make it easy to opt out.

    Evidence

    • HiringGTM Engineer (Operations): "nobody's holding the full picture end to end" across commercial data and workflows; ~70% is building (pipelines, lead scoring and routing, AI enrichment across the CRM, sales and marketing stack), for example "an agent that flags an best-fit customer profile account the moment its usage crosses a threshold and drafts the first outreach"; shares HubSpot upkeep. Reconciles HubSpot and Snowflake "so nobody's arguing about whose number is right".Source
    • Your websiteHomepage: "Realtime platform for chat, AI and live apps at scale"; claims 30B+ connections a month, 2B+ connected devices a month, 2T+ API operations a month, 7+ years of 100% uptime, 700+ points of presence and under 6.5ms delivery; customers named include HubSpot, Webflow, Toyota, EA, Panasonic, Harness and the Australian Open.Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source

This quarter 9

The core plays for the next three months.

  • 06

    Developers building with Cursor, Claude Code and ChatGPT let the assistant pick the library. Ably already publishes an llms.txt, but keeping the AI-readable docs accurate and complete is the difference between being recommended and being skipped.

    High impactMedium effort First result in 4 weeks Senior Developer Experience W…

    First action

    Write 25 realtime and AI-session prompts and record which library each major assistant recommends today.

    How to measure it

    Assistant answers recommending Ably for the tracked tasks

    Now
    –
    Target
    +15 points
    By
    2 quarters

    Steps

    1. 1

      Write the prompt set

      25 realtime and AI-session prompts, naming no vendor.

      Developer Relations Manager 2 days

    2. 2

      Baseline the assistants

      Record Cursor, Claude Code, ChatGPT and Gemini recommendations.

      Developer Relations Manager 1 day

    3. 3

      Fill the gaps

      Task-shaped markdown pages for the prompts where Ably is missed.

      Senior Developer Experience Writer 2 weeks

    4. 4

      Keep llms.txt current

      Automate the index so new docs appear for assistants.

      Senior Developer Experience Writer 3 days

    5. 5

      Recheck weekly

      Re-run the prompts and track the share that names Ably.

      Developer Relations Manager 1 hour a week

    6. 6

      Report

      Tool-choice share next to self-serve signups.

      GTM Engineer 30 minutes a week

    First result
    4 weeks
    Cost
    Under $500 a month in assistant runs
    Owner
    Senior Developer Experience Writer

    Smallest test

    Run 25 prompts by hand in two assistants and see how often Ably is named.

    Why it works

    Treat "what an AI assistant recommends for realtime and AI session continuity" as a growth metric: keep markdown docs and the llms.txt current, add task-shaped pages (how to add resumable streaming to a Vercel AI SDK app), and run a weekly check of what the major assistants actually suggest.

    The DX writer role is explicitly AI-first ("accurate for developers and AI coding assistants"), and the DevRel role wants Ably to "show up accurately when developers ask AI assistants". A tracked tool-choice metric turns that goal into a weekly loop.

    Risks and how to handle them

    • Assistant behaviour shifts with each model release

      Track by model version and treat post-release drops as signals, not noise.

    Builds on

    Evidence

    • HiringSenior Developer Experience Writer and Staff Tech Lead, Web & Developer Products: an AI-first docs role that writes "reusable prompts and skills" so docs stay accurate "for developers and AI coding assistants", and an engineering lead (reporting to the CTO) who owns the dashboard, docs platform, marketing website and billing UI as "a reference point for the industry".Source
    • HiringDeveloper Relations Manager: "Ably hasn't had a dedicated DevRel function in some time", so the role builds one; be "the feedback loop between developers and Ably", build a genuine presence in the Temporal and Vercel communities, and get "Ably showing up accurately when developers ask AI assistants to support technical evaluations and builds". Developers now choose infrastructure on "what AI assistants tell them, not search rankings alone".Source
    • programmable.infoSite scan: 793 blog posts, 771 docs pages, about 630 /compare pages and 31 /alternatives pages (PubNub, Pusher, Socket.IO, Cloudflare Durable Objects, Supabase, Firebase and more), 25 case studies, and a published llms.txt index. The homepage is freemium from $29/month; Tranco rank about 49,000; 91 Hacker News mentions; 1,307 GitHub stars across public repos (top repo ably-pubsub-js, 368).Source
  • 07

    The fastest way to prove AI Transport is a working app a developer can fork, not a pitch. The library integrations exist, but there is no single showcase that takes a developer from zero to a resumable agent in minutes.

    High impactMedium effort First result in 6-8 weeks Developer Relations Manager

    First action

    Scope the smallest agent that shows resume-after-reload convincingly.

    How to measure it

    Signups attributed to the demo app

    Now
    –
    Target
    150
    By
    10 weeks

    Steps

    1. 1

      Build the agent

      A real task, not a toy; resume works across reload, tab and device.

      Developer Relations Manager 2 weeks

    2. 2

      Add a deploy button

      One click to a running instance with a free Ably key.

      Developer Relations Manager 3 days

    3. 3

      Write the walkthrough

      The failure it fixes, then the fix, with runnable code.

      Developer Relations Manager 3 days

    4. 4

      Record a short video

      Drop the connection on camera and watch it resume.

      Developer Relations Manager 1 day

    5. 5

      Launch in community

      Share in the Vercel and Temporal communities and on the blog.

      Developer Relations Manager 1 day

    6. 6

      Maintain it

      Update on every AI Transport release so it never breaks.

      Developer Relations Manager ongoing

    First result
    6 to 8 weeks
    Cost
    $0, about three weeks of work
    Owner
    Developer Relations Manager

    Smallest test

    Ship a minimal reload-only demo and measure forks before building the full version.

    Why it works

    Build and maintain an open-source demo: an AI agent on the Vercel AI SDK that survives reloads, tab switches and device changes via AI Transport, with a deploy button, a written walkthrough and a video. Keep it current with each AI Transport release.

    The DevRel role is measured on content that gets shared and drives self-serve signups. A forkable, genuinely useful app is the most shareable developer asset there is, and it doubles as the reference the docs and comparison page point to.

    Risks and how to handle them

    • An out-of-date demo does more harm than good

      Tie its upkeep to the release checklist so it never rots.

    Builds on

    Evidence

    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
    • HiringDeveloper Relations Manager: "Ably hasn't had a dedicated DevRel function in some time", so the role builds one; be "the feedback loop between developers and Ably", build a genuine presence in the Temporal and Vercel communities, and get "Ably showing up accurately when developers ask AI assistants to support technical evaluations and builds". Developers now choose infrastructure on "what AI assistants tell them, not search rankings alone".Source
    • Your websiteThe blog has a deep AI Transport series (why AI agents need a durable session layer, Vercel AI SDK production session layer, Temporal workflow streams, OpenAI Responses API, mid-run steering, database hydration) and a long-form "Vercel AI SDK resumable stream: what it covers and what it doesn't" explainer.Source
  • 08

    Ably is known as realtime messaging infrastructure, but AI Transport serves a different buyer: a team building an AI agent who has never thought about websockets. The current site makes them read through realtime-messaging positioning to find it.

    High impactMedium effort First result in 6 weeks Product Marketing Manager

    First action

    Interview five AI Transport users about what they were building and what they searched before they found it.

    How to measure it

    Self-serve AI Transport signups a month

    Now
    –
    Target
    2x the current run rate
    By
    end of quarter

    Steps

    1. 1

      Interview users

      Five AI Transport builders: the problem, the search, the alternatives.

      Product Marketing Manager 1 week

    2. 2

      Rewrite the entry

      A landing experience that opens with the agent problem.

      Product Marketing Manager 1 week

    3. 3

      Plan the launches

      A moment per release, cut into blog, social and demo.

      Product Marketing Manager 2 days

    4. 4

      Run a monthly webinar

      Durable AI sessions, with a customer or framework guest.

      Developer Relations Manager 1 day a month

    5. 5

      Enable sales

      A one-page AI Transport narrative and objection handling.

      Product Marketing Manager 2 days

    6. 6

      Measure

      Signups and pipeline from the AI buyer against the messaging buyer.

      GTM Engineer weekly

    First result
    6 weeks
    Cost
    $0
    Owner
    Product Marketing Manager

    Smallest test

    Run one AI-agent-first landing page against the current one for two weeks.

    Why it works

    Run AI Transport as its own go-to-market: a landing experience for the AI-agent builder, launch moments around each release (OpenAI Responses API, mid-run steering), a monthly webinar on durable AI sessions, and messaging that starts from the agent problem, not from pub/sub.

    The PMM owns launches and positioning to developer personas. Separating the AI-agent story from the realtime-messaging story lets each land with the buyer it is for, and AI Transport is the product the market is pulling on now.

    Risks and how to handle them

    • Splitting the story confuses the core realtime brand

      Keep one platform story; AI Transport is a track within it, not a separate company.

    Builds on

    Evidence

    • HiringProduct Marketing Manager: targets technical and developer personas in B2B SaaS, owns launches and positioning, and a responsibility is "creating an AI-powered competitive intelligence system".Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
    • Your websiteThe blog has a deep AI Transport series (why AI agents need a durable session layer, Vercel AI SDK production session layer, Temporal workflow streams, OpenAI Responses API, mid-run steering, database hydration) and a long-form "Vercel AI SDK resumable stream: what it covers and what it doesn't" explainer.Source
    • Search resultsAbly raised a $70M Series B in June 2021 (Insight Partners and Dawn Capital), about $77M to $78M in total. It is UK-based (London) and remote-first, with a growing US presence, and cites 200% year-on-year growth. AI Transport became generally available (the blog dates it to early 2026).Source
  • 09

    The communities the DevRel role must win are Temporal and Vercel, and Ably already positions AI Transport as the session layer that sits next to Temporal's durable execution. That is a partnership, not just a comparison.

    High impactMedium effort First result in 6 weeks Developer Relations Manager

    First action

    Email the Temporal and Vercel DevRel teams proposing a co-written piece built on the existing Temporal workflow streams post.

    How to measure it

    Signups from Temporal and Vercel co-marketing

    Now
    –
    Target
    120
    By
    8 weeks after launch

    Steps

    1. 1

      Ship the integrations

      A supported, documented path for the Vercel AI SDK and Temporal.

      Developer Relations Manager 3 weeks

    2. 2

      Pitch the partners

      Co-written posts and a joint webinar, drafts first.

      Developer Relations Manager 1 week

    3. 3

      Get listed

      Each ecosystem's integrations directory.

      Product Marketing Manager 2 weeks

    4. 4

      Run the webinar

      Live, recorded, cut into clips.

      Developer Relations Manager 1 day

    5. 5

      Measure

      Referral signups and directory clicks.

      GTM Engineer 30 minutes a week

    6. 6

      Repeat with LangGraph

      Same pattern once the first two land.

      Developer Relations Manager 3 weeks

    Who to approach

    • Temporal

      Durable execution; AI Transport is positioned as the session layer beside it, and objections already surface in its community.

    • Vercel AI SDK

      The default AI app framework; its own resumable-stream has gaps AI Transport fills.

    First result
    6 weeks
    Cost
    $0, about three weeks of work
    Owner
    Developer Relations Manager

    Smallest test

    Co-write one post with the partner whose community already raises the objection.

    Why it works

    Turn the comparison into collaboration: a documented, supported integration with the Vercel AI SDK and Temporal, co-written posts (Ably already has a Temporal workflow streams piece), a joint webinar, and a listing in each ecosystem's integrations directory.

    Being in the Temporal and Vercel communities "genuinely" is the role's success measure. An official integration and co-marketing reach those exact developers at the moment they need a session layer, with the partner's credibility behind it.

    Risks and how to handle them

    • Partners see a competitor and decline

      Lead with where Ably complements them; the session layer is additive, not a replacement.

    Builds on

    Evidence

    • HiringDeveloper Relations Manager: "Ably hasn't had a dedicated DevRel function in some time", so the role builds one; be "the feedback loop between developers and Ably", build a genuine presence in the Temporal and Vercel communities, and get "Ably showing up accurately when developers ask AI assistants to support technical evaluations and builds". Developers now choose infrastructure on "what AI assistants tell them, not search rankings alone".Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
    • Your websiteThe blog has a deep AI Transport series (why AI agents need a durable session layer, Vercel AI SDK production session layer, Temporal workflow streams, OpenAI Responses API, mid-run steering, database hydration) and a long-form "Vercel AI SDK resumable stream: what it covers and what it doesn't" explainer.Source
    • Search resultsThe DevRel post names concrete developer pain it has already heard: LangGraph reconnection failures and recurring Temporal objections. The role is framed as complementary to a Developer Growth Manager who owns the rest of the funnel.Source
  • 10

    The GTM Engineer post says "nobody's holding the full picture end to end" and teams argue about "whose number is right". A go-to-market that cannot agree on its funnel cannot tell which channel to scale.

    High impactMedium effort First result in 6 weeks GTM Engineer

    First action

    List every place a "signup" or "pipeline" number is computed today and where they disagree.

    How to measure it

    Funnel metrics with a single agreed source

    Now
    –
    Target
    all core metrics
    By
    end of quarter

    Steps

    1. 1

      Inventory the numbers

      Every definition of signup, activation, MQL and pipeline in use.

      GTM Engineer 3 days

    2. 2

      Reconcile nightly

      A job that aligns HubSpot and Snowflake and flags mismatches.

      GTM Engineer 1 week

    3. 3

      Define each metric once

      Agreed definitions, documented, owned.

      GTM Engineer 2 days

    4. 4

      Build the dashboards

      Spend and content to signup, activation and revenue.

      GTM Engineer 1 week

    5. 5

      Wire in attribution

      UTMs and self-serve events feed the same model.

      GTM Engineer 1 week

    6. 6

      Review weekly

      The team reads one dashboard in the growth review.

      Head of Marketing 30 minutes a week

    First result
    6 weeks
    Cost
    $0, about three weeks of engineering
    Owner
    GTM Engineer

    Smallest test

    Reconcile just the signup number across both systems and publish the agreed definition.

    Why it works

    Build the reconciliation layer: a nightly job that aligns HubSpot and Snowflake, one source of truth for the self-serve and sales funnel, and dashboards that tie spend and content to signups, activation and revenue, so the PMM and DevRel can see what actually works.

    Every other idea here is judged on signups and pipeline, which is only possible once the numbers are trusted. This is the foundation the GTM Engineer is hired to build, and it makes the whole team's experiments measurable.

    Risks and how to handle them

    • Becomes an endless data-cleanup project

      Ship the three metrics that drive decisions first, then expand.

    Evidence

    • HiringGTM Engineer (Operations): "nobody's holding the full picture end to end" across commercial data and workflows; ~70% is building (pipelines, lead scoring and routing, AI enrichment across the CRM, sales and marketing stack), for example "an agent that flags an best-fit customer profile account the moment its usage crosses a threshold and drafts the first outreach"; shares HubSpot upkeep. Reconciles HubSpot and Snowflake "so nobody's arguing about whose number is right".Source
    • Your websiteHomepage: "Realtime platform for chat, AI and live apps at scale"; claims 30B+ connections a month, 2B+ connected devices a month, 2T+ API operations a month, 7+ years of 100% uptime, 700+ points of presence and under 6.5ms delivery; customers named include HubSpot, Webflow, Toyota, EA, Panasonic, Harness and the Australian Open.Source
    • HiringProduct Marketing Manager: targets technical and developer personas in B2B SaaS, owns launches and positioning, and a responsibility is "creating an AI-powered competitive intelligence system".Source
  • 11

    Ably has strong logos (HubSpot, Toyota, EA, the Australian Open) and 25 case studies, but they are mostly about realtime messaging at scale, not about the AI and live-agent use cases the market is buying now.

    Medium impactMedium effort First result in 8 weeks Product Marketing Manager

    First action

    Ask three customers (one on AI Transport) for permission to publish their numbers.

    How to measure it

    New AI-era case studies published and used by sales

    Now
    –
    Target
    3
    By
    end of quarter

    Steps

    1. 1

      Pick three customers

      One AI Transport, one live-experience, one collaboration.

      Product Marketing Manager 1 week

    2. 2

      Get the numbers

      Uptime, latency and scale they will put their name to.

      Product Marketing Manager 2 weeks

    3. 3

      Write and design

      One story each, with a one-page sales summary.

      Product Marketing Manager 2 weeks

    4. 4

      Publish and link

      From AI Transport, pricing and the comparison pages.

      Senior Developer Experience Writer 3 days

    5. 5

      Arm sales

      The one-pagers in the deal room with talk tracks.

      Product Marketing Manager 2 days

    6. 6

      Measure

      Views in closed deals and sales usage.

      GTM Engineer 30 minutes a week

    First result
    8 weeks
    Cost
    $0
    Owner
    Product Marketing Manager

    Smallest test

    Publish one AI Transport case study and track its use in live deals.

    Why it works

    Produce three new case studies focused on the current buyer: a team using AI Transport for a production agent, a live-experience customer at event scale, and a collaboration use case, each with real numbers (uptime, latency, connections) and a reusable one-page summary for sales.

    The PMM owns customer proof and launches. Proof from named peers doing the exact thing a prospect is trying is the strongest asset in a long, technical sale, and the current library does not cover the AI buyer.

    Risks and how to handle them

    • Customers will not share numbers

      Use relative figures or a descriptor ("a Fortune 100 automaker") with the metric.

    Evidence

    • Your websiteHomepage: "Realtime platform for chat, AI and live apps at scale"; claims 30B+ connections a month, 2B+ connected devices a month, 2T+ API operations a month, 7+ years of 100% uptime, 700+ points of presence and under 6.5ms delivery; customers named include HubSpot, Webflow, Toyota, EA, Panasonic, Harness and the Australian Open.Source
    • HiringProduct Marketing Manager: targets technical and developer personas in B2B SaaS, owns launches and positioning, and a responsibility is "creating an AI-powered competitive intelligence system".Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
  • 12

    The PMM post explicitly asks for "an AI-powered competitive intelligence system". In a market where PubNub, Pusher, Supabase, Cloudflare and the Vercel AI SDK all ship weekly, static competitor comparisons and compare pages are wrong within a month.

    Medium impactMedium effort First result in 6 weeks Product Marketing Manager

    First action

    List the 8 rivals and the exact pages (docs, pricing, changelog) worth watching for each.

    How to measure it

    Median days from a rival change to an updated competitor comparison

    Now
    –
    Target
    under 3
    By
    end of quarter

    Steps

    1. 1

      Pick the watch list

      Rivals and the specific pages to monitor.

      Product Marketing Manager 2 days

    2. 2

      Build the watcher

      Detect and summarise changes to those pages.

      GTM Engineer 1 week

    3. 3

      Route the updates

      Flagged changes go to the compare pages, competitor comparisons and docs.

      Product Marketing Manager 3 days

    4. 4

      Keep a human in the loop

      Someone approves each change before it publishes.

      Product Marketing Manager ongoing

    5. 5

      Feed AI answers

      Updated facts flow into the llms.txt docs.

      Senior Developer Experience Writer 2 days

    6. 6

      Review monthly

      What changed, what Ably shipped in response.

      Product Marketing Manager 1 hour a month

    First result
    6 weeks
    Cost
    $0, about a week of engineering
    Owner
    Product Marketing Manager

    Smallest test

    Watch two rivals' pricing pages for a month and route changes to the competitor comparisons by hand.

    Why it works

    Build a system that watches rivals' docs, pricing, changelogs and launches, flags what changed, and feeds the updates into the compare pages, the sales competitor comparisons and the AI-readable docs, with a human approving each change.

    It turns a named responsibility into leverage: the comparison pages, the resumable-streaming page and the assistant answers all stay accurate without a person re-checking every rival by hand, and sales always has the current story.

    Risks and how to handle them

    • Automated updates publish an error

      Require human approval before anything goes live.

    Builds on

    Evidence

    • HiringProduct Marketing Manager: targets technical and developer personas in B2B SaaS, owns launches and positioning, and a responsibility is "creating an AI-powered competitive intelligence system".Source
    • programmable.infoSite scan: 793 blog posts, 771 docs pages, about 630 /compare pages and 31 /alternatives pages (PubNub, Pusher, Socket.IO, Cloudflare Durable Objects, Supabase, Firebase and more), 25 case studies, and a published llms.txt index. The homepage is freemium from $29/month; Tranco rank about 49,000; 91 Hacker News mentions; 1,307 GitHub stars across public repos (top repo ably-pubsub-js, 368).Source
    • Competitor researchRealtime infrastructure rivals: PubNub and Pusher (Ably's longest-standing comparisons), Supabase Realtime and Firebase (bundled with a backend), Cloudflare Durable Objects (a build-it-yourself primitive), and Stream and Sendbird (chat-specific). For AI session continuity the alternatives are the Vercel AI SDK's Redis-backed resumable-stream, Vercel Workflow DevKit and rolling your own on SSE.Source
    • Your websiteTwo near-identical AI-stack explainers exist at ably.com/vercel/... and ably.com/topic/ai-stack/..., both with the canonical set to the /vercel/ URL. The /compare pages are generated in bulk, including many rival-vs-rival pairings that do not mention Ably (for example amazon-eventbridge-vs-pubnub).Source
  • 13

    The gap between a signup and a retained user is a first working integration. AI Transport has docs, but there is no single guided path that takes a developer from an empty project to a resumable stream in one sitting.

    High impactMedium effort First result in 4 weeks Senior Developer Experience W…

    First action

    Time yourself going from empty project to resumable stream and cut every step that is not essential.

    How to measure it

    Signups reaching a first resumable stream

    Now
    –
    Target
    +15 points
    By
    end of quarter

    Steps

    1. 1

      Define success

      The single moment that counts: a stream that resumes after a drop.

      Senior Developer Experience Writer 2 hours

    2. 2

      Cut the path

      Remove every step not needed to reach that moment.

      Senior Developer Experience Writer 3 days

    3. 3

      Add checkpoints

      A "you should see this" at each step.

      Senior Developer Experience Writer 2 days

    4. 4

      Handle the top errors

      Inline fixes for the three most common failures.

      Senior Developer Experience Writer 2 days

    5. 5

      Keep it AI-accurate

      Update the markdown and llms.txt versions.

      Senior Developer Experience Writer 1 day

    6. 6

      Measure

      Signup-to-first-stream rate by cohort.

      GTM Engineer 30 minutes a week

    First result
    4 weeks
    Cost
    $0, about a week of work
    Owner
    Senior Developer Experience Writer

    Smallest test

    Ship the reload-only quickstart and measure how many reach a working resume.

    Why it works

    Build a focused quickstart: copy a key, paste a snippet, run it, drop the connection, watch it resume, all inside ten minutes, with a checkpoint at each step and a fallback for the common errors, kept accurate for AI assistants too.

    The DX writer owns docs quality and activation is what turns a free signup into a paying team. A quickstart that reliably reaches a first success is a direct, measurable lift that every other acquisition idea feeds into.

    Risks and how to handle them

    • Over-simplifying hides real complexity

      Link a deeper guide from each step for those who need it.

    Builds on

    Evidence

    • HiringSenior Developer Experience Writer and Staff Tech Lead, Web & Developer Products: an AI-first docs role that writes "reusable prompts and skills" so docs stay accurate "for developers and AI coding assistants", and an engineering lead (reporting to the CTO) who owns the dashboard, docs platform, marketing website and billing UI as "a reference point for the industry".Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
    • Your websiteThe AI support chatbot pricing example on the pricing page costs about $109.50/month for 35,000 chats, and AI Transport docs include a dedicated pricing page and a "going to production" guide; the free tier is 200 concurrent connections and 6M messages a month.Source
  • 14

    A brand-new DevRel function needs a recurring place where developers meet Ably, and live help is where trust and feedback are built fastest. There is no regular Ably developer event today.

    Medium impactMedium effort First result in 1-2 months Developer Relations Manager

    First action

    Pick the first build and a date, and invite the developers already asking reconnection questions.

    How to measure it

    Developers attending or watching the monthly session

    Now
    –
    Target
    200 a month
    By
    third session

    Steps

    1. 1

      Fix a cadence

      The same day each month, every month.

      Developer Relations Manager 1 hour

    2. 2

      Plan the build

      A real, useful thing shipped live in 30 minutes.

      Developer Relations Manager 1 day

    3. 3

      Run office hours

      Developers bring their own problems; answer live.

      Developer Relations Manager 1 day a month

    4. 4

      Invite the right people

      Those already asking reconnection questions in-community.

      Developer Relations Manager 2 hours

    5. 5

      Cut the clips

      Repurpose the session for YouTube and social.

      Developer Relations Manager 1 day a month

    6. 6

      Carry feedback back

      Log every objection for product and the PMM.

      Developer Relations Manager 30 minutes a month

    First result
    1 to 2 months
    Cost
    $0
    Owner
    Developer Relations Manager

    Smallest test

    Run one session and measure attendance and follow-up signups.

    Why it works

    Run a monthly livestream: build something real on Ably in the first half (often AI Transport), then open office hours where developers bring their own realtime and AI problems, recorded and cut into clips.

    The DevRel role is the developer feedback loop and is measured on genuine community presence. A recurring live event is the most direct way to earn that presence, gather the objections product needs, and produce a month of content from one session.

    Risks and how to handle them

    • Low early attendance

      Seed the first few with developers you already help in-community.

    Builds on

    Evidence

    • HiringDeveloper Relations Manager: "Ably hasn't had a dedicated DevRel function in some time", so the role builds one; be "the feedback loop between developers and Ably", build a genuine presence in the Temporal and Vercel communities, and get "Ably showing up accurately when developers ask AI assistants to support technical evaluations and builds". Developers now choose infrastructure on "what AI assistants tell them, not search rankings alone".Source
    • Search resultsThe DevRel post names concrete developer pain it has already heard: LangGraph reconnection failures and recurring Temporal objections. The role is framed as complementary to a Developer Growth Manager who owns the rest of the funnel.Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source

Big bets 3

Larger plays that can change the trajectory.

  • 15

    Ably carries 30B+ connections, 2B+ devices and 2T+ API operations a month. Aggregated, that is a unique, defensible view of how realtime and AI traffic is actually growing that analysts and reporters would cite.

    High impactHigh effort First result in Launch quarter Head of Marketing

    First action

    Define the five questions the report answers and confirm which metrics can be shared safely.

    How to measure it

    Enterprise opportunities influenced by the report

    Now
    –
    Target
    20
    By
    6 months after launch

    Steps

    1. 1

      Set the questions

      Five questions engineering leaders argue about, answerable from the data.

      Head of Marketing 1 week

    2. 2

      Clear the data

      Aggregates only, with a privacy and disclosure review.

      CEO 2 weeks

    3. 3

      Analyse

      Growth, reconnection, session-length and regional trends.

      GTM Engineer 3 weeks

    4. 4

      Design and write

      A report with one chart per finding and a public method.

      Head of Marketing 3 weeks

    5. 5

      Launch

      Embargoed press, a talk, and a webinar.

      Head of Marketing 1 week

    6. 6

      Cut into content

      Posts, charts and a webinar across the next quarter.

      Head of Marketing ongoing

    First result
    Launch quarter
    Cost
    $5,000 to $10,000 for design and launch
    Owner
    Head of Marketing

    Smallest test

    Publish one chart from the data as a blog post and measure citations before committing.

    Why it works

    Publish an annual report from aggregated, anonymised network data: realtime and AI session growth, reconnection and session-length patterns, regional and device trends, with a public methodology, launched with press and a talk, and cut into a quarter of content.

    Original data is what earns citations, backlinks and brand in a technical market, and it is the one asset a smaller rival cannot copy. It gives DevRel, PMM and sales a flagship to carry all year.

    Risks and how to handle them

    • Aggregated data still leaks something sensitive

      Legal and privacy review before anything is published; customer-level data never appears.

    Builds on

    Evidence

    • Your websiteHomepage: "Realtime platform for chat, AI and live apps at scale"; claims 30B+ connections a month, 2B+ connected devices a month, 2T+ API operations a month, 7+ years of 100% uptime, 700+ points of presence and under 6.5ms delivery; customers named include HubSpot, Webflow, Toyota, EA, Panasonic, Harness and the Australian Open.Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
    • Search resultsAbly raised a $70M Series B in June 2021 (Insight Partners and Dawn Capital), about $77M to $78M in total. It is UK-based (London) and remote-first, with a growing US presence, and cites 200% year-on-year growth. AI Transport became generally available (the blog dates it to early 2026).Source
  • 16

    The problem AI Transport solves (keeping an AI session alive across drops, devices and agents) does not yet have an agreed name, and Ably has already written most of the thinking on it. Whoever names the category shapes how buyers and AI assistants compare options.

    High impactHigh effort First result in 2 quarters Head of Marketing

    First action

    Write the one-sentence definition of the category and the three properties that define it.

    How to measure it

    Third-party and assistant use of the category term

    Now
    –
    Target
    measurable adoption
    By
    2 quarters

    Steps

    1. 1

      Define the category

      A clear definition and the properties that qualify a tool.

      Head of Marketing 1 week

    2. 2

      Publish the canon

      A definition page, reference architecture and the comparison.

      Head of Marketing 3 weeks

    3. 3

      Say it everywhere

      One consistent term across docs, blog, sales and talks.

      Product Marketing Manager ongoing

    4. 4

      Take the stage

      Talks at AI and infra conferences on the category.

      Developer Relations Manager 1 quarter

    5. 5

      Seed the assistants

      The definition in AI-readable docs so assistants use it.

      Senior Developer Experience Writer 2 weeks

    6. 6

      Track adoption

      Who else uses the term, and inbound that cites it.

      GTM Engineer monthly

    First result
    2 quarters
    Cost
    Mostly senior time plus conference costs
    Owner
    Head of Marketing

    Smallest test

    Publish the definition page and see whether others start using the term unprompted.

    Why it works

    Run a deliberate category play: a canonical definition page, a reference architecture, the comparison and demo assets, conference talks, and consistent language ("durable AI session layer") across docs, blog and sales, so that when a developer or an assistant reaches for the term, Ably is the source.

    In developer infrastructure the vocabulary decides the shortlist. Ably has the data series, the deep blog archive and the product to back the claim, and the window is open before Vercel, Cloudflare or a new entrant plants the flag.

    Risks and how to handle them

    • The market adopts a rival's term instead

      Lead with the most useful, honest content; the best resource usually wins the term.

    Builds on

    Evidence

    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
    • Your websiteThe blog has a deep AI Transport series (why AI agents need a durable session layer, Vercel AI SDK production session layer, Temporal workflow streams, OpenAI Responses API, mid-run steering, database hydration) and a long-form "Vercel AI SDK resumable stream: what it covers and what it doesn't" explainer.Source
    • Competitor researchRealtime infrastructure rivals: PubNub and Pusher (Ably's longest-standing comparisons), Supabase Realtime and Firebase (bundled with a backend), Cloudflare Durable Objects (a build-it-yourself primitive), and Stream and Sendbird (chat-specific). For AI session continuity the alternatives are the Vercel AI SDK's Redis-backed resumable-stream, Vercel Workflow DevKit and rolling your own on SSE.Source
    • HiringDeveloper Relations Manager: "Ably hasn't had a dedicated DevRel function in some time", so the role builds one; be "the feedback loop between developers and Ably", build a genuine presence in the Temporal and Vercel communities, and get "Ably showing up accurately when developers ask AI assistants to support technical evaluations and builds". Developers now choose infrastructure on "what AI assistants tell them, not search rankings alone".Source
  • 17

    Ably's largest customers (Toyota, EA, Panasonic-scale) have committed cloud spend and slow vendor onboarding. A marketplace listing turns Ably into a line item they can buy without a new procurement process.

    Medium impactHigh effort First result in 2 quarters CEO

    First action

    Ask the five largest enterprise prospects whether they buy infrastructure through a cloud marketplace.

    How to measure it

    Sales cycle for marketplace deals

    Now
    –
    Target
    30% shorter than direct
    By
    3 quarters

    Steps

    1. 1

      Check demand

      How the largest prospects actually buy.

      CEO 1 week

    2. 2

      Register as a seller

      AWS first, then Azure.

      CEO 2 weeks

    3. 3

      Build the listings

      SaaS contract listings with private offers.

      GTM Engineer 2 weeks

    4. 4

      Attach compliance

      SOC 2, HIPAA, DPA and security docs.

      CEO 2 days

    5. 5

      Train sales

      When and how to offer the marketplace path.

      CEO 2 hours

    6. 6

      Co-sell

      Apply to the cloud ISV programs once the first deals close.

      CEO ongoing

    First result
    2 quarters
    Cost
    Marketplace fees on transacted revenue plus about a month of setup
    Owner
    CEO

    Smallest test

    Offer one enterprise prospect a private offer on AWS Marketplace.

    Why it works

    Publish private-offer-ready AWS and Azure Marketplace listings for Enterprise, with the SOC 2 and HIPAA documentation attached, and give sales a standard marketplace path for deals above a set size.

    Marketplace procurement shortens the security and vendor-onboarding stage that slows enterprise deals, and draws on budgets that are already approved. It is a channel Ably's buyers already use for the rest of their stack.

    Risks and how to handle them

    • Marketplace fees cut margin

      Price the fee into private offers for large deals.

    Evidence

    • Your websiteHomepage: "Realtime platform for chat, AI and live apps at scale"; claims 30B+ connections a month, 2B+ connected devices a month, 2T+ API operations a month, 7+ years of 100% uptime, 700+ points of presence and under 6.5ms delivery; customers named include HubSpot, Webflow, Toyota, EA, Panasonic, Harness and the Australian Open.Source
    • Search resultsAbly raised a $70M Series B in June 2021 (Insight Partners and Dawn Capital), about $77M to $78M in total. It is UK-based (London) and remote-first, with a growing US presence, and cites 200% year-on-year growth. AI Transport became generally available (the blog dates it to early 2026).Source
    • Your websiteThe AI support chatbot pricing example on the pricing page costs about $109.50/month for 35,000 chats, and AI Transport docs include a dedicated pricing page and a "going to production" guide; the free tier is 200 concurrent connections and 6M messages a month.Source

Wildcards 3

Unexpected experiments, each with a cheap way to test it.

  • 18

    The developer in pain is not searching for Ably; they are searching for why their AI response cut off after a reload or a tab switch. That moment is upstream of any product decision.

    Medium impactMedium effort First result in 6-8 weeks Developer Relations Manager

    First action

    Document the five most common causes of a dropped AI stream with a reproduction for each.

    How to measure it

    Signups from the diagnostic and teardowns

    Now
    –
    Target
    200
    By
    2 quarters

    Steps

    1. 1

      Catalogue the causes

      Reload, tab switch, device switch, network change, server stop.

      Developer Relations Manager 3 days

    2. 2

      Build the diagnostic

      A short input that maps a developer to their cause.

      GTM Engineer 1 week

    3. 3

      Write the teardowns

      Reproduce and fix each in a popular stack.

      Developer Relations Manager 3 weeks

    4. 4

      Be honest about fixes

      Show the non-Ably fix where it is the right one.

      Developer Relations Manager ongoing

    5. 5

      Distribute

      Community, newsletter and the blog.

      Developer Relations Manager 1 week

    6. 6

      Track

      Diagnostic completions and signups.

      GTM Engineer 30 minutes a week

    First result
    6 to 8 weeks
    Cost
    $0
    Owner
    Developer Relations Manager

    Smallest test

    Publish one teardown of the reload case and measure reads and signups.

    Why it works

    Publish a diagnostic (paste your setup, learn which of the five common drop causes you have hit) plus a teardown series that reproduces each failure in popular stacks and shows the fix, with AI Transport as one option among honest alternatives.

    It meets developers at the symptom, not the category, builds the DevRel function's credibility through genuine usefulness, and every teardown is a durable, AI-indexed answer that routes the ready ones to a free project.

    Risks and how to handle them

    • Looks like a lead-gen quiz

      Give the full answer for free, with no gate on the diagnosis.

    Builds on

    Evidence

    • Your websiteThe blog has a deep AI Transport series (why AI agents need a durable session layer, Vercel AI SDK production session layer, Temporal workflow streams, OpenAI Responses API, mid-run steering, database hydration) and a long-form "Vercel AI SDK resumable stream: what it covers and what it doesn't" explainer.Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
    • HiringDeveloper Relations Manager: "Ably hasn't had a dedicated DevRel function in some time", so the role builds one; be "the feedback loop between developers and Ably", build a genuine presence in the Temporal and Vercel communities, and get "Ably showing up accurately when developers ask AI assistants to support technical evaluations and builds". Developers now choose infrastructure on "what AI assistants tell them, not search rankings alone".Source
  • 19

    Ably has worked pricing examples buried on the pricing page (an AI chatbot at about $109.50 a month), but developers comparing options want to plug in their own numbers and get a figure they can paste into a planning doc.

    Medium impactLow effort First result in 4 weeks Developer Relations Manager

    First action

    Turn the existing pricing examples into a parameterised formula.

    How to measure it

    Signups from the cost calculator

    Now
    –
    Target
    100
    By
    2 quarters

    Steps

    1. 1

      Build the formula

      From the published examples, parameterised by usage.

      GTM Engineer 3 days

    2. 2

      Add honest comparisons

      Like-for-like estimates for roll-your-own and rivals, method shown.

      Product Marketing Manager 3 days

    3. 3

      Make it embeddable

      A widget other sites and docs can embed.

      GTM Engineer 3 days

    4. 4

      Link it widely

      Pricing, AI Transport, the comparison pages and the diagnostic.

      Senior Developer Experience Writer 1 hour

    5. 5

      Distribute

      Share in communities as a useful tool.

      Developer Relations Manager 2 hours

    6. 6

      Track

      Uses, embeds and signups.

      GTM Engineer 30 minutes a week

    First result
    4 weeks
    Cost
    $0, about a week of work
    Owner
    Developer Relations Manager

    Smallest test

    Ship the Ably-only calculator first and see how often it is used and shared.

    Why it works

    Publish a clean, embeddable calculator: enter connections, messages, MAUs or chats, get a transparent monthly cost for Ably and a like-for-like estimate for the roll-your-own and rival options, with the method shown.

    A transparent cost tool answers the "what will this cost at scale" question that stalls adoption, gets shared in team discussions, and earns backlinks. It also feeds the comparison pages with concrete numbers.

    Risks and how to handle them

    • Rival estimates are disputed

      Show the method and let users adjust the assumptions.

    Builds on

    Evidence

    • Your websiteThe AI support chatbot pricing example on the pricing page costs about $109.50/month for 35,000 chats, and AI Transport docs include a dedicated pricing page and a "going to production" guide; the free tier is 200 concurrent connections and 6M messages a month.Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
    • Competitor researchRealtime infrastructure rivals: PubNub and Pusher (Ably's longest-standing comparisons), Supabase Realtime and Firebase (bundled with a backend), Cloudflare Durable Objects (a build-it-yourself primitive), and Stream and Sendbird (chat-specific). For AI session continuity the alternatives are the Vercel AI SDK's Redis-backed resumable-stream, Vercel Workflow DevKit and rolling your own on SSE.Source
  • 20

    With 771 docs pages and an AI-first docs mandate, the highest-leverage growth work may be fixing the specific pages where developers stall on the way to a first working integration, which nobody currently measures.

    Medium impactMedium effort First result in 6-8 weeks Senior Developer Experience W…

    First action

    Instrument the quickstart pages and find the step with the highest drop-off.

    How to measure it

    Developers reaching a first working integration

    Now
    –
    Target
    +15 points
    By
    2 quarters

    Steps

    1. 1

      Instrument the docs

      Time, copy events, search dead-ends and helpfulness per page.

      GTM Engineer 1 week

    2. 2

      Find the stalls

      The quickstart steps where developers abandon.

      Senior Developer Experience Writer 3 days

    3. 3

      Rewrite the worst

      Fix the top five blocking pages first.

      Senior Developer Experience Writer 2 weeks

    4. 4

      Keep them AI-accurate

      Update the markdown and llms.txt versions too.

      Senior Developer Experience Writer 3 days

    5. 5

      Close search gaps

      Create pages for searches that return nothing.

      Senior Developer Experience Writer 1 week

    6. 6

      Measure

      Activation rate by cohort after each fix.

      GTM Engineer 30 minutes a week

    First result
    6 to 8 weeks
    Cost
    $0, about three weeks of work
    Owner
    Senior Developer Experience Writer

    Smallest test

    Instrument only the quickstart and fix its worst step, then measure activation.

    Why it works

    Add lightweight analytics to the docs (time on page, copy events, search dead-ends, "was this helpful"), find the pages where developers abandon the quickstart, and rewrite those first, keeping them accurate for AI assistants too.

    The DX writer owns docs quality and velocity, and activation (first working integration) is what turns a signup into a retained user. Fixing the pages that block that is a direct, measurable lift that compounds.

    Risks and how to handle them

    • Analytics on docs feels invasive

      Aggregate and privacy-safe; no per-developer tracking.

    Builds on

    Evidence

    • HiringSenior Developer Experience Writer and Staff Tech Lead, Web & Developer Products: an AI-first docs role that writes "reusable prompts and skills" so docs stay accurate "for developers and AI coding assistants", and an engineering lead (reporting to the CTO) who owns the dashboard, docs platform, marketing website and billing UI as "a reference point for the industry".Source
    • programmable.infoSite scan: 793 blog posts, 771 docs pages, about 630 /compare pages and 31 /alternatives pages (PubNub, Pusher, Socket.IO, Cloudflare Durable Objects, Supabase, Firebase and more), 25 case studies, and a published llms.txt index. The homepage is freemium from $29/month; Tranco rank about 49,000; 91 Hacker News mentions; 1,307 GitHub stars across public repos (top repo ably-pubsub-js, 368).Source
    • Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source

03

How Programmable can help

Where an idea in this playbook is something Programmable builds or runs, it's listed here with what we'd do. Everything else is yours to run.

ProgrammableTalk

Fill the events in this plan

These ideas are events. Talk gets registrants for them and tells you who's coming and what their company does before the day.

Plan an event (opens programmable.talk in a new tab)
Website review of ably.com More example playbooks and reviews
ProgrammableDigital

Show Ably’s product working

Turn screenshots or the website into an animated product demo in its own brand, for the homepage, launch posts and outreach in this playbook.

Make a demo (opens programmable.digital in a new tab)

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • Found growth strategyA telehealth weight care program: board-certified clinicians, GLP-1 and other medications (compounded and branded), coaching, an app and…22 growth ideas
  • Rune Technologies growth strategyDefense software for military logistics and sustainment: TyrOS, an AI-enabled, offline-first logistics command and control platform, with…20 growth ideas
  • Icarus growth strategyBuilds APOLLO, a solar-powered autonomous aircraft that flies above 60,000 ft for persistent sensing, communications relay and data…22 growth ideas
  • Unsiloed AI growth strategyA document ingestion API that turns PDFs, slides, spreadsheets and images into JSON and Markdown for LLMs and AI agents, with Parse…23 growth ideas
  • Teads growth strategyAn omnichannel advertising platform, merged with Outbrain in 2025, selling branding and performance campaigns across the open web, mobile…20 growth ideas
  • Elyos AI growth strategyAI agents for trades and field service businesses that answer calls, emails and WhatsApp messages, book and reschedule jobs, confirm…22 growth ideas
  • Stella Carakasi growth strategyA Berkeley, California women's clothing brand (founded 1995 as Two Star Dog) making small-batch, sustainable, size-inclusive tops, tunics…20 growth ideas
  • Watchmaker Genomics growth strategyDevelops and manufactures NGS library preparation kits, library amplification, Cas9-based normalization, engineered enzymes and qPCR…22 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on October 18, 2026, and cites them throughout. Ably did not commission, review or endorse it, and Programmable is not affiliated with Ably. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Ably runs its business.

Something wrong, or do you represent Ably? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 305 ideas

    Ship the quick wins listed under This week.

  2. Days 31 to 609 ideas

    Build the repeatable engines listed under This quarter.

  3. Days 61 to 906 ideas

    Commit to the big bets on the first 60 days of evidence, and run the wildcards.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value realtime that just works at scale, with years of 100% uptime. The most cited problem: AI streams drop on reload, tab switch, device change and network change.

  • Breadth of SDKs and a single platform for messaging, chat, sync and presence
  • Rolling your own session continuity on SSE is fragile and underspecified
  • In their words: “durable session layer”

Market

Competitive landscape

5 competitors compared: PubNub, Pusher, Supabase Realtime and Firebase, Cloudflare Durable Objects and 1 more.

  • Gap to exploit: No agreed name or canonical reference for durable AI session continuity
  • PubNub: Not focused on AI session continuity
  • Pusher: Less suited to large-scale or AI workloads

Hiring signals

Ably is hiring to win the AI-agent developer and to build the commercial engine behind a product-led motion.

  • Developer Relations Manager: A dedicated DevRel function built from scratch: be the developer feedback loop, win the Temporal and Vercel…
  • Product Marketing Manager: Own AI Transport positioning and launches to developer personas, and build an AI-powered competitive intelligence system…
  • GTM Engineer: Build the commercial systems nobody owns end to end: usage-triggered PQLs, lead scoring, and HubSpot/Snowflake reconciliation. Ideas…

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks first (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence