ProgrammableMarketing/redis.io (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 6
  • This quarter · 11
  • Big bets · 3
  • Wildcards · 2
Generated Oct 23, 2026
  1. Programmable
  2. Playbooks
  3. Redis
Redis logo

growth playbook · Oct 23, 2026

redis.io (opens in a new tab)

Redis growth playbook

Diagnosis

Redis has unmatched developer reach (about 64.5 million Docker pulls and over 40 million weekly npm downloads) and is now leading with Redis Iris for AI agents.

Its new Lead, Growth Marketing is asked to build agent-led growth, where an agent finds the right product, reads the docs and creates an account in one session, while communications, FinServ and regional sales roles scale demand.

The quickest gap is in that agent path: llms.txt does not mention Iris or the sign-up, product and pricing pages have no markdown versions, and 20 navigation pages, Iris and Pricing included, use a fallback description about "Redis Enterprise". This playbook fixes those first, then adds measurement, comparison pages for the agent memory category, creator and benchmark programs, a capital markets story, localized pages and faster activation.

Growth Score

8/10

Biggest Opportunity

Be the store AI agents choose by default, by giving agents a clean path from need to product to account.

Biggest Risk

Agent memory is a crowded, fast-moving category (Mem0, Pinecone, open source forks such as Valkey), and if agents and assistants describe Redis only as a cache, Iris will be overlooked.

01

Start here

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

  1. 1

    Add Redis Iris and the free sign-up to the llms.txt agents read

    Add the Iris, MCP and sign-up links to llms.txt today.

    High impact First result in 2 weeks
  2. 2

    Replace the "Redis Enterprise" fallback description on 20 key pages, Iris and Pricing included

    Rewrite the homepage, Iris and Pricing descriptions.

    High impact First result in 1 month
  3. 3

    Serve the product and pricing pages in markdown, like the docs already do

    Publish /iris/ and /pricing/ in markdown.

    High impact First result in 1 month

02

Your idea portfolio

22 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.

  • 6 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 · 2Big bets · 11Fill-ins · 4Reconsider · 5
Effort →

Showing 22 of 22 ideas

This week 6

Quick wins with a clear first action.

  • 01

    The Lead, Growth Marketing post describes the goal exactly: an AI agent should "identify the right Redis solution, review the relevant documentation, and create an account in a single session". Redis Iris now leads the homepage navigation, and the docs already have about 60 Iris and context-engine pages in markdown. But redis.io/llms.txt, the map Redis serves to agents (also at /agents/), never mentions Iris, Context Retriever or the Redis MCP server, links only one of those 60 pages, and has no link to /try-free/. An agent following the map today can learn every Redis command but cannot find Redis's newest product or the step that creates an account.

    High impactLow effort First result in 2 weeks Lead

    First action

    Add the Iris, MCP and sign-up links to llms.txt today.

    How to measure it

    Iris sign-ups from agent and assistant sessions

    Now
    –
    Target
    2x
    By
    60 days

    Steps

    1. 1

      List the path

      For each product: overview, quickstart, create-service doc, pricing, sign-up.

      Lead, Growth Marketing 1 day

    2. 2

      Write the section

      "Agents and context" in llms.txt with markdown links.

      Developer Relations 1 day

    3. 3

      Add a chooser

      Need to product, in plain lines.

      Product Marketing 1 day

    4. 4

      Link the account step

      /try-free/?rcplan=iris with a note on the free plan.

      Lead, Growth Marketing 1 hour

    5. 5

      Publish

      Same file at /llms.txt and /agents/.

      Web Engineering 1 hour

    6. 6

      Test with agents

      Ask three coding agents to build an agent with memory on Redis.

      Developer Relations 2 days

    7. 7

      Tag sessions

      Mark sign-ups whose referrer is an assistant or agent.

      Lead, Growth Marketing 1 week

    8. 8

      Review monthly

      Add every new product page and quickstart.

      Lead, Growth Marketing monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Lead, Growth Marketing

    Smallest test

    Add the five most important Iris links and measure agent referrals for two weeks.

    Why it works

    Add an "Agents and context" section to llms.txt: Redis Iris, Context Retriever, Agent Memory and LangCache, each with its overview, quickstart and create-service doc in markdown (the .md versions already exist), the Redis MCP server install page, the pricing page, and /try-free/?rcplan=iris as the account step. Add a short "Choosing a Redis product" entry that maps needs (cache, vector search, agent memory, context retrieval) to products. Then ask the main coding agents to build a small agent with memory on Redis and see whether they reach the Iris docs and the sign-up.

    Agents follow what the map gives them; adding the newest product and the sign-up turns the existing docs into the single-session path the role is hired to build. It is a text-file change that takes a day, and it can be measured by watching agent sessions reach /try-free/.

    Ready to use

    Checklistllms.txt "Agents and context" section

    [ ] Redis Iris overview
    [ ] Context Retriever: concepts, create service
    [ ] Agent Memory: overview, Python/TypeScript/REST quickstarts
    [ ] LangCache: concepts, create service
    [ ] Redis MCP server install
    [ ] Pricing
    [ ] /try-free/?rcplan=iris as the account step
    [ ] "Choosing a Redis product" lines
    [ ] Same file at /llms.txt and /agents/

    Risks and how to handle them

    • File grows too long

      Keep a short top section and link a full version.

    • Agents create accounts without a person

      Keep the human confirmation step in sign-up.

    Evidence

    • HiringLead, Growth Marketing (United States, posted September 30, 2026): "the audience discovering and evaluating Redis is no longer exclusively human. AI agents can identify a need, decide which solution fits, review technical documentation, and create a new account within one continuous session." The role owns "the website, SEO, answer engine optimization, generative engine optimization, conversion-rate optimization, and the measurement system", must "Build a low-friction journey in which an agent can identify the right Redis solution, review the relevant documentation, and create an account in a single session", and directs "contractors and an agency partner".Source
    • Your websitellms.txt check (October 22, 2026): redis.io/llms.txt (also served at /agents/) lists 81 links under headings from Core Docs to Tutorials. It never mentions Redis Iris, Context Retriever or the Redis MCP server, and does not link the free sign-up page (/try-free/); of the roughly 60 docs pages under /operate/iris/ and /develop/ai/context-engine/, it links one (LangCache concepts). Those docs already exist in markdown, e.g. /docs/latest/operate/iris/agent-memory/index.html.md.Source
    • Your websiteHomepage: title "Redis - Real-time data for agents & apps"; the navigation leads with "Redis Iris - Real-time context for agents", then LangCache, Context Retriever, Agent Memory, Data Integration and Flex; a banner reads "86.5% accuracy. ~$0.07 per session. See how Redis stacks up in the Agent Memory Benchmark"; a sign-up link is /try-free/?rcplan=iris; links ask ChatGPT, Claude and Perplexity "How can I use Redis Iris as a real-time context engine for AI apps?".Source
    • Your websiteRedis Iris page headings: "Your agents should be getting smarter", "Introducing Redis Iris", "Address any data with Context Retriever", "Agentic AI gets smarter with Agent Memory", "The State of Context Engineering 2026" and "Take the context maturity self assessment". Docs include Agent Memory quickstarts for Python, TypeScript and REST, and Google ADK integration guides.Source
    • Your websitePricing page: Free "From $0 /hour"; Essentials "From $0.007 /hour", shared deployment 250 MB-100 GB; Pro "First $200 free", "From $0.014 /hour", "Minimum $200 /month", dedicated, active-active, up to 99.999% uptime; sold direct and through partner marketplaces.Source
  • 02

    Of the 53 pages in the homepage navigation, 20 share one fallback description that still talks about "Redis Enterprise", including the homepage, Redis Iris, Context Retriever, Agent Memory, Pricing and Financial services. Search results and assistants read these descriptions to decide what a page is for.

    High impactLow effort First result in 1 month Lead

    First action

    Rewrite the homepage, Iris and Pricing descriptions.

    How to measure it

    Search CTR on rewritten pages

    Now
    –
    Target
    +15%
    By
    60 days

    Steps

    1. 1

      List pages

      All using the fallback.

      Lead, Growth Marketing 1 hour

    2. 2

      Write

      One description each.

      Product Marketing 2 days

    3. 3

      Publish

      In the CMS.

      Web Engineering 1 day

    4. 4

      Require the field

      No publish without it.

      Web Engineering 1 day

    5. 5

      Update fallback

      Current product names.

      Web Engineering 1 hour

    6. 6

      Measure

      CTR in Search Console.

      Lead, Growth Marketing 60 days

    First result
    1 month
    Cost
    $0
    Owner
    Lead, Growth Marketing

    Smallest test

    Rewrite three descriptions today.

    Why it works

    Write a specific description for each of the 20 pages (Iris: real-time context for agents; Pricing: Free, Essentials, Pro), make the CMS require one before publish, and stop the fallback from using an old product name.

    Specific descriptions lift click-through and help assistants match the right page to a question.

    Risks and how to handle them

    • More pages appear later

      The required field stops new ones.

    Evidence

    • Your websiteDescription check of the 53 pages linked in the homepage navigation (October 22, 2026): 20 use the same fallback meta description, "Developers love Redis. Unlock the full potential of the Redis database with Redis Enterprise and start building blazing fast apps.", including the homepage, Redis Iris, Context Retriever, Agent Memory, Flex, Pricing, AI cost optimization, Real-time decisioning, Financial services, Retail, Telco, Dev Hub and Support.Source
    • Your websiteHomepage: title "Redis - Real-time data for agents & apps"; the navigation leads with "Redis Iris - Real-time context for agents", then LangCache, Context Retriever, Agent Memory, Data Integration and Flex; a banner reads "86.5% accuracy. ~$0.07 per session. See how Redis stacks up in the Agent Memory Benchmark"; a sign-up link is /try-free/?rcplan=iris; links ask ChatGPT, Claude and Perplexity "How can I use Redis Iris as a real-time context engine for AI apps?".Source
    • HiringLead, Growth Marketing (United States, posted September 30, 2026): "the audience discovering and evaluating Redis is no longer exclusively human. AI agents can identify a need, decide which solution fits, review technical documentation, and create a new account within one continuous session." The role owns "the website, SEO, answer engine optimization, generative engine optimization, conversion-rate optimization, and the measurement system", must "Build a low-friction journey in which an agent can identify the right Redis solution, review the relevant documentation, and create an account in a single session", and directs "contractors and an agency partner".Source
    • Your websitePricing page: Free "From $0 /hour"; Essentials "From $0.007 /hour", shared deployment 250 MB-100 GB; Pro "First $200 free", "From $0.014 /hour", "Minimum $200 /month", dedicated, active-active, up to 99.999% uptime; sold direct and through partner marketplaces.Source
  • 03

    Docs pages have markdown versions that agents read cleanly, but /iris/index.html.md and /pricing/index.html.md return 404. The pages where agents decide which product fits and what it costs are the heavy ones, at well over a megabyte of HTML each.

    High impactMedium effort First result in 1 month Web Engineering

    First action

    Publish /iris/ and /pricing/ in markdown.

    How to measure it

    Key pages with .md versions

    Now
    –
    Target
    50
    By
    1 month

    Steps

    1. 1

      Pick pages

      Product, pricing, compare, solutions.

      Lead, Growth Marketing 1 day

    2. 2

      Build export

      CMS to markdown.

      Web Engineering 1 week

    3. 3

      Add alternates

      rel=alternate link tags.

      Web Engineering 1 day

    4. 4

      Link in llms.txt

      Markdown links.

      Lead, Growth Marketing 1 hour

    5. 5

      Test agents

      Compare answers before and after.

      Developer Relations 1 week

    6. 6

      Monitor

      Requests to .md pages.

      Lead, Growth Marketing monthly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Web Engineering

    Smallest test

    Hand-write the Iris markdown page.

    Why it works

    Generate markdown versions of product, pricing, comparison and solution pages from the CMS at the same .md pattern, link them from llms.txt, and add a rel="alternate" link on each HTML page.

    Agents get the facts quickly and consistently, which lowers the chance they misdescribe products or prices.

    Risks and how to handle them

    • Markdown drifts from HTML

      Generate both from one source.

    Evidence

    • Your websiteMarkdown versions exist for docs pages (e.g. /docs/latest/integrate/redis-mcp/index.html.md returns text/markdown) but not for product pages: /iris/index.html.md and /pricing/index.html.md return 404.Source
    • Your websitellms.txt check (October 22, 2026): redis.io/llms.txt (also served at /agents/) lists 81 links under headings from Core Docs to Tutorials. It never mentions Redis Iris, Context Retriever or the Redis MCP server, and does not link the free sign-up page (/try-free/); of the roughly 60 docs pages under /operate/iris/ and /develop/ai/context-engine/, it links one (LangCache concepts). Those docs already exist in markdown, e.g. /docs/latest/operate/iris/agent-memory/index.html.md.Source
    • HiringLead, Growth Marketing (United States, posted September 30, 2026): "the audience discovering and evaluating Redis is no longer exclusively human. AI agents can identify a need, decide which solution fits, review technical documentation, and create a new account within one continuous session." The role owns "the website, SEO, answer engine optimization, generative engine optimization, conversion-rate optimization, and the measurement system", must "Build a low-friction journey in which an agent can identify the right Redis solution, review the relevant documentation, and create an account in a single session", and directs "contractors and an agency partner".Source
    • Your websitePricing page: Free "From $0 /hour"; Essentials "From $0.007 /hour", shared deployment 250 MB-100 GB; Pro "First $200 free", "From $0.014 /hour", "Minimum $200 /month", dedicated, active-active, up to 99.999% uptime; sold direct and through partner marketplaces.Source
  • 04

    Real visitors see fast loading (LCP 1.6s, INP 79ms) but CLS of 0.25, so pages jump while loading, often from banners, fonts or late-loading navigation.

    Medium impactMedium effort First result in 2 months Web Engineering

    First action

    Record the shifts on the homepage in a performance trace.

    How to measure it

    CLS p75

    Now
    –
    Target
    <= 0.1
    By
    2 months

    Steps

    1. 1

      Trace

      Find shifting elements.

      Web Engineering 1 day

    2. 2

      Reserve space

      Banner and images.

      Web Engineering 2 days

    3. 3

      Fonts

      Preload and size-adjust.

      Web Engineering 1 day

    4. 4

      Cookie bar

      Fixed position.

      Web Engineering 1 day

    5. 5

      Test

      Key templates.

      Web Engineering 2 days

    6. 6

      Monitor

      CrUX monthly.

      Lead, Growth Marketing monthly

    First result
    2 months
    Cost
    Engineering time
    Owner
    Web Engineering

    Smallest test

    Fix the banner height first.

    Why it works

    Reserve space for the benchmark banner and images, preload fonts, and set fixed heights for the navigation and cookie bar; test on the homepage, pricing and try-free first.

    Stable pages are easier to read and click, and Core Web Vitals feed search ranking.

    Risks and how to handle them

    • Design changes

      Keep visuals, fix sizing only.

    Evidence

    • Google PageSpeedChrome UX Report for redis.io (real visitors, p75): LCP 1.6s and INP 79ms are "good" and LCP is 29% faster than before, but CLS is 0.25, above the 0.1 "good" threshold, so pages visibly shift as they load.Source
    • Your websiteHomepage: title "Redis - Real-time data for agents & apps"; the navigation leads with "Redis Iris - Real-time context for agents", then LangCache, Context Retriever, Agent Memory, Data Integration and Flex; a banner reads "86.5% accuracy. ~$0.07 per session. See how Redis stacks up in the Agent Memory Benchmark"; a sign-up link is /try-free/?rcplan=iris; links ask ChatGPT, Claude and Perplexity "How can I use Redis Iris as a real-time context engine for AI apps?".Source
  • 05

    The pages sitemap lists template and test pages that robots.txt blocks, and the named AI crawler groups contain only "Allow: /", so the rules that keep other crawlers out of non-public sections do not apply to them.

    Medium impactLow effort First result in 1 week Lead

    First action

    Copy the Disallow lines into the named groups.

    How to measure it

    Template or test URLs in sitemaps

    Now
    –
    Target
    0
    By
    1 week

    Steps

    1. 1

      Audit sitemaps

      Every sitemap file.

      Lead, Growth Marketing 1 day

    2. 2

      Remove pages

      Templates and tests.

      Web Engineering 1 day

    3. 3

      Fix robots.txt

      Same rules for all.

      Web Engineering 1 hour

    4. 4

      Test

      robots testing tools.

      Lead, Growth Marketing 1 hour

    5. 5

      Search Console

      Remove indexed test URLs.

      Lead, Growth Marketing 1 day

    6. 6

      Add a check

      Build fails on template URLs in sitemap.

      Web Engineering 1 day

    First result
    1 week
    Cost
    $0
    Owner
    Lead, Growth Marketing

    Smallest test

    Remove the test pages from the sitemap today.

    Why it works

    Remove template and test pages from the sitemap, copy the general Disallow lines into each named crawler group (or drop the named groups since "*" already allows them), and review robots.txt with each new product launch.

    Agents then see only current, public pages, so they are less likely to cite test or outdated pages.

    Risks and how to handle them

    • Blocking useful pages

      Test each rule before publishing.

    Evidence

    • Your websiteSitemap and robots.txt: the pages sitemap lists template and test pages that robots.txt blocks for general crawlers; robots.txt gives named AI crawlers their own groups containing only "Allow: /", so the general Disallow rules do not apply to them. robots.txt also sets "Content-Signal: search=yes, ai-input=yes, ai-train=yes".Source
    • HiringLead, Growth Marketing (United States, posted September 30, 2026): "the audience discovering and evaluating Redis is no longer exclusively human. AI agents can identify a need, decide which solution fits, review technical documentation, and create a new account within one continuous session." The role owns "the website, SEO, answer engine optimization, generative engine optimization, conversion-rate optimization, and the measurement system", must "Build a low-friction journey in which an agent can identify the right Redis solution, review the relevant documentation, and create an account in a single session", and directs "contractors and an agency partner".Source
    • Your websitellms.txt check (October 22, 2026): redis.io/llms.txt (also served at /agents/) lists 81 links under headings from Core Docs to Tutorials. It never mentions Redis Iris, Context Retriever or the Redis MCP server, and does not link the free sign-up page (/try-free/); of the roughly 60 docs pages under /operate/iris/ and /develop/ai/context-engine/, it links one (LangCache concepts). Those docs already exist in markdown, e.g. /docs/latest/operate/iris/agent-memory/index.html.md.Source
  • 06

    The role must "Connect human and agent discovery to meaningful outcomes". The homepage already links visitors to ask assistants about Iris, and sign-ups carry a plan parameter (rcplan=iris).

    High impactMedium effort First result in 1 month Lead

    First action

    List current referrers from assistants in analytics.

    How to measure it

    Agent and assistant share of sign-ups

    Now
    –
    Target
    reported weekly
    By
    30 days

    Steps

    1. 1

      Define sources

      Referrers and agents.

      Lead, Growth Marketing 2 days

    2. 2

      Tag sessions

      Analytics rules.

      Web Engineering 1 week

    3. 3

      Sign-up question

      Add an AI assistant option.

      Lead, Growth Marketing 2 days

    4. 4

      Path reports

      Docs to sign-up.

      Lead, Growth Marketing 1 week

    5. 5

      Dashboard

      Weekly.

      Lead, Growth Marketing 1 week

    6. 6

      Review

      With leadership.

      Lead, Growth Marketing monthly

    First result
    1 month
    Cost
    Analytics time
    Owner
    Lead, Growth Marketing

    Smallest test

    Add the sign-up question.

    Why it works

    Tag sessions from assistant and agent referrers and user agents, track docs-to-sign-up paths and the rcplan parameter, add "how did you find Redis?" with an "AI assistant" option at sign-up, and build one weekly dashboard.

    What is measured gets budget; this makes agent-led growth visible next to search and paid.

    Risks and how to handle them

    • Agents hide their identity

      Combine referrers, user agents and the sign-up answer.

    Builds on

    Evidence

    • HiringLead, Growth Marketing (United States, posted September 30, 2026): "the audience discovering and evaluating Redis is no longer exclusively human. AI agents can identify a need, decide which solution fits, review technical documentation, and create a new account within one continuous session." The role owns "the website, SEO, answer engine optimization, generative engine optimization, conversion-rate optimization, and the measurement system", must "Build a low-friction journey in which an agent can identify the right Redis solution, review the relevant documentation, and create an account in a single session", and directs "contractors and an agency partner".Source
    • Your websiteHomepage: title "Redis - Real-time data for agents & apps"; the navigation leads with "Redis Iris - Real-time context for agents", then LangCache, Context Retriever, Agent Memory, Data Integration and Flex; a banner reads "86.5% accuracy. ~$0.07 per session. See how Redis stacks up in the Agent Memory Benchmark"; a sign-up link is /try-free/?rcplan=iris; links ask ChatGPT, Claude and Perplexity "How can I use Redis Iris as a real-time context engine for AI apps?".Source
    • Your websitePricing page: Free "From $0 /hour"; Essentials "From $0.007 /hour", shared deployment 250 MB-100 GB; Pro "First $200 free", "From $0.014 /hour", "Minimum $200 /month", dedicated, active-active, up to 99.999% uptime; sold direct and through partner marketplaces.Source

This quarter 11

The core plays for the next three months.

  • 07

    Redis has 15 English comparison pages, all for caches and databases (ElastiCache, Valkey, Memorystore and others), but none for agent memory or context tools such as Mem0, and the only Pinecone comparison is an older "Redis Enterprise" resource. Iris competes in that new category.

    High impactMedium effort First result in 1 quarter Product Marketing

    First action

    Draft the agent memory comparison.

    How to measure it

    Iris sign-ups from compare pages

    Now
    –
    Target
    +25%
    By
    2 quarters

    Steps

    1. 1

      Pick rivals

      Agent memory and vector.

      Product Marketing 1 week

    2. 2

      Research

      Public docs and pricing.

      Product Marketing 2 weeks

    3. 3

      Write

      One page each.

      Product Marketing 2 weeks

    4. 4

      Review

      Legal and engineering.

      Product Marketing 1 week

    5. 5

      Publish

      HTML and markdown.

      Web Engineering 1 week

    6. 6

      Refresh

      Quarterly.

      Product Marketing quarterly

    First result
    1 quarter
    Cost
    Content time
    Owner
    Product Marketing

    Smallest test

    Publish one page.

    Why it works

    Publish fair comparison pages for Iris and Agent Memory against the main agent-memory and vector options, with the benchmark method, pricing basis and when each fits; give each a markdown version.

    Developers and agents compare options before choosing; Redis should supply the facts.

    Risks and how to handle them

    • Rivals dispute numbers

      Publish the method and dates.

    Evidence

    • Your websiteComparison pages (sitemap, October 22, 2026): /compare/ covers ElastiCache, Memorystore, Memcached, Valkey, Aiven, Hazelcast, GemFire, Oracle Coherence, OpenSearch, Kafka, MongoDB, MySQL and Oracle; none covers agent memory or context tools; the only Pinecone comparison is an older resource titled "comparing-redis-enterprise-with-pineconevector-database". Localized pages still use old paths such as /de/redis-enterprise/technologie/ and /fr/redis-enterprise/avantages/.Source
    • Competitor researchRivals' own homepages: Valkey, "open source (BSD) high-performance key/value datastore... backed by the Linux Foundation"; Dragonfly, "the most performant in-memory data store"; Mem0, "the memory layer for AI agents and applications"; Pinecone, "the trusted AI knowledge company" for "10,000+ customers and 1M developers".Source
    • Your websiteHomepage: title "Redis - Real-time data for agents & apps"; the navigation leads with "Redis Iris - Real-time context for agents", then LangCache, Context Retriever, Agent Memory, Data Integration and Flex; a banner reads "86.5% accuracy. ~$0.07 per session. See how Redis stacks up in the Agent Memory Benchmark"; a sign-up link is /try-free/?rcplan=iris; links ask ChatGPT, Claude and Perplexity "How can I use Redis Iris as a real-time context engine for AI apps?".Source
    • Your websiteRedis Iris page headings: "Your agents should be getting smarter", "Introducing Redis Iris", "Address any data with Context Retriever", "Agentic AI gets smarter with Agent Memory", "The State of Context Engineering 2026" and "Take the context maturity self assessment". Docs include Agent Memory quickstarts for Python, TypeScript and REST, and Google ADK integration guides.Source
  • 08

    The homepage sends people to ask assistants how to use Redis Iris, and the role is to make sure Redis is "accurately represented, cited, recommended, and selected".

    High impactMedium effort First result in 1 quarter Lead

    First action

    Write the 30 questions.

    How to measure it

    Questions where Redis is recommended correctly

    Now
    –
    Target
    20 of 30
    By
    2 quarters

    Steps

    1. 1

      Write questions

      30 across needs.

      Lead, Growth Marketing 1 week

    2. 2

      Baseline

      All assistants.

      Lead, Growth Marketing 1 week

    3. 3

      Score

      Accuracy and recommendation.

      Lead, Growth Marketing 1 week

    4. 4

      Fix sources

      Pages behind wrong answers.

      Product Marketing monthly

    5. 5

      Repeat

      Monthly.

      Lead, Growth Marketing monthly

    6. 6

      Report

      To leadership.

      Lead, Growth Marketing quarterly

    First result
    1 quarter
    Cost
    Agency time
    Owner
    Lead, Growth Marketing

    Smallest test

    Run ten questions this week.

    Why it works

    Ask the main assistants and coding agents 30 fixed questions each month (best memory store for agents, how to add memory to an agent, Redis vs others), score accuracy and whether Redis is recommended, and fix the pages behind wrong answers.

    A fixed audit turns AEO from guesswork into a scorecard the team can improve.

    Risks and how to handle them

    • Answers vary run to run

      Run each question several times.

    Builds on

    Evidence

    • HiringLead, Growth Marketing (United States, posted September 30, 2026): "the audience discovering and evaluating Redis is no longer exclusively human. AI agents can identify a need, decide which solution fits, review technical documentation, and create a new account within one continuous session." The role owns "the website, SEO, answer engine optimization, generative engine optimization, conversion-rate optimization, and the measurement system", must "Build a low-friction journey in which an agent can identify the right Redis solution, review the relevant documentation, and create an account in a single session", and directs "contractors and an agency partner".Source
    • Your websiteHomepage: title "Redis - Real-time data for agents & apps"; the navigation leads with "Redis Iris - Real-time context for agents", then LangCache, Context Retriever, Agent Memory, Data Integration and Flex; a banner reads "86.5% accuracy. ~$0.07 per session. See how Redis stacks up in the Agent Memory Benchmark"; a sign-up link is /try-free/?rcplan=iris; links ask ChatGPT, Claude and Perplexity "How can I use Redis Iris as a real-time context engine for AI apps?".Source
    • Your websitellms.txt check (October 22, 2026): redis.io/llms.txt (also served at /agents/) lists 81 links under headings from Core Docs to Tutorials. It never mentions Redis Iris, Context Retriever or the Redis MCP server, and does not link the free sign-up page (/try-free/); of the roughly 60 docs pages under /operate/iris/ and /develop/ai/context-engine/, it links one (LangCache concepts). Those docs already exist in markdown, e.g. /docs/latest/operate/iris/agent-memory/index.html.md.Source
  • 09

    The new communications role owns an influencer program for "independent engineers, OSS maintainers, technical YouTubers/newsletter writers". Iris has quickstarts for Python, TypeScript and REST.

    High impactMedium effort First result in 2 quarters Principal Manager

    First action

    Shortlist 20 creators.

    How to measure it

    Published creator builds

    Now
    –
    Target
    20
    By
    2 quarters

    Steps

    1. 1

      Shortlist

      By audience fit.

      Principal Manager, Communications & Developer Influence 2 weeks

    2. 2

      Offer

      Credits and early access.

      Principal Manager, Communications & Developer Influence 2 weeks

    3. 3

      Support

      DevRel office hours.

      Developer Relations ongoing

    4. 4

      Publish

      Creator channels.

      Principal Manager, Communications & Developer Influence ongoing

    5. 5

      Amplify

      Redis social.

      Principal Manager, Communications & Developer Influence ongoing

    6. 6

      Measure

      Sign-ups by creator link.

      Lead, Growth Marketing monthly

    First result
    2 quarters
    Cost
    Credits and fees
    Owner
    Principal Manager, Communications & Developer Influence

    Smallest test

    Sign five creators.

    Why it works

    Recruit 20 creators to build and publish a real agent with Iris memory in a framework they already cover, with early access, credits and a shared repo; amplify on Redis channels.

    Developers trust builders they follow, and each build becomes a tutorial agents can find.

    Risks and how to handle them

    • Paid posts lose trust

      Disclose sponsorship clearly.

    Evidence

    • HiringPrincipal Manager, Communications & Developer Influence (HQ San Francisco, posted September 1, 2026): owns PR, executive visibility, social and "an influencer program that identifies and develops relationships with independent engineers, OSS maintainers, technical YouTubers/newsletter writers"; positions Redis "as a real-time agentic platform"; measured on "media quality, share of voice, executive visibility, and business impact".Source
    • Your websiteRedis Iris page headings: "Your agents should be getting smarter", "Introducing Redis Iris", "Address any data with Context Retriever", "Agentic AI gets smarter with Agent Memory", "The State of Context Engineering 2026" and "Take the context maturity self assessment". Docs include Agent Memory quickstarts for Python, TypeScript and REST, and Google ADK integration guides.Source
    • Public profilesDeveloper reach: Docker Hub images with about 64.5 million pulls (top image redis/redis-stack-server); npm packages with about 40.6 million weekly downloads (redis and @redis/client alone about 8.6 and 9.0 million); "Redis 8.8: New array data structure, rate limiter, performance improvements" reached 229 points on Hacker News (2026).Source
  • 10

    Every page carries "86.5% accuracy. ~$0.07 per session" from the Agent Memory Benchmark. A public, reproducible benchmark is a story for press, creators and assistants.

    High impactMedium effort First result in 1 quarter Principal Manager

    First action

    Publish the method page.

    How to measure it

    Articles and posts citing it

    Now
    –
    Target
    50
    By
    2 quarters

    Steps

    1. 1

      Package

      Code and data.

      Developer Relations 2 weeks

    2. 2

      Method page

      Plain explanation.

      Product Marketing 1 week

    3. 3

      Leaderboard

      Open submissions.

      Web Engineering 2 weeks

    4. 4

      Pitch

      Press and creators.

      Principal Manager, Communications & Developer Influence 1 month

    5. 5

      Update

      Quarterly runs.

      Developer Relations quarterly

    6. 6

      Measure

      Citations and sign-ups.

      Lead, Growth Marketing monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Principal Manager, Communications & Developer Influence

    Smallest test

    Publish the repo.

    Why it works

    Publish the method, data and code on GitHub, invite rivals and the community to submit runs, keep a leaderboard, and pitch the results to developer and AI press.

    Reproducible numbers earn citations and trust; opaque ones invite doubt.

    Risks and how to handle them

    • Others beat the score

      Report honestly and improve.

    Evidence

    • Your websiteHomepage: title "Redis - Real-time data for agents & apps"; the navigation leads with "Redis Iris - Real-time context for agents", then LangCache, Context Retriever, Agent Memory, Data Integration and Flex; a banner reads "86.5% accuracy. ~$0.07 per session. See how Redis stacks up in the Agent Memory Benchmark"; a sign-up link is /try-free/?rcplan=iris; links ask ChatGPT, Claude and Perplexity "How can I use Redis Iris as a real-time context engine for AI apps?".Source
    • HiringPrincipal Manager, Communications & Developer Influence (HQ San Francisco, posted September 1, 2026): owns PR, executive visibility, social and "an influencer program that identifies and develops relationships with independent engineers, OSS maintainers, technical YouTubers/newsletter writers"; positions Redis "as a real-time agentic platform"; measured on "media quality, share of voice, executive visibility, and business impact".Source
    • Competitor researchRivals' own homepages: Valkey, "open source (BSD) high-performance key/value datastore... backed by the Linux Foundation"; Dragonfly, "the most performant in-memory data store"; Mem0, "the memory layer for AI agents and applications"; Pinecone, "the trusted AI knowledge company" for "10,000+ customers and 1M developers".Source
  • 11

    Redis is hiring a FinServ strategic AE and a Principal Solution Architect to sell Iris to hedge funds and asset managers, and the Financial services page uses the generic fallback description.

    High impactMedium effort First result in 1 quarter Strategic Account Executive

    First action

    Draft the three architectures.

    How to measure it

    Capital markets meetings

    Now
    –
    Target
    20
    By
    2 quarters

    Steps

    1. 1

      Interview SAs

      Real use cases.

      Principal Solution Architect, FinServ 2 weeks

    2. 2

      Architectures

      Three diagrams.

      Principal Solution Architect, FinServ 2 weeks

    3. 3

      Page

      With due diligence pack.

      Product Marketing 2 weeks

    4. 4

      Review

      Security and legal.

      Product Marketing 1 week

    5. 5

      Outbound

      Named accounts.

      Strategic Account Executive, FinServ ongoing

    6. 6

      Measure

      Meetings and pipeline.

      Strategic Account Executive, FinServ monthly

    First result
    1 quarter
    Cost
    Content time
    Owner
    Strategic Account Executive, FinServ

    Smallest test

    Use one architecture in outbound this month.

    Why it works

    Build a capital markets page with three reference architectures (agentic trading assistant, real-time risk monitoring, client servicing), compliance and security notes for due diligence, and a briefing request for Heads of Trading and CTOs.

    Regulated buyers need a specific story and due diligence material before the first meeting.

    Risks and how to handle them

    • Long procurement

      Lead with due diligence material.

    Evidence

    • HiringStrategic Account Executive, FinServ (NYC, posted October 20, 2026): sells to hedge funds and asset managers "the core Redis platform - the real-time data layer already trusted by trading, risk, and fraud-detection systems" alongside "our newest offering, Redis Iris, a context and memory engine purpose-built for AI agents operating on live enterprise data"; use cases "agentic trading assistants, real-time risk and compliance monitoring, AI-driven client servicing". A Principal Solution Architect, FinServ was posted October 22, 2026.Source
    • Your websiteDescription check of the 53 pages linked in the homepage navigation (October 22, 2026): 20 use the same fallback meta description, "Developers love Redis. Unlock the full potential of the Redis database with Redis Enterprise and start building blazing fast apps.", including the homepage, Redis Iris, Context Retriever, Agent Memory, Flex, Pricing, AI cost optimization, Real-time decisioning, Financial services, Retail, Telco, Dev Hub and Support.Source
    • Your websiteRedis Iris page headings: "Your agents should be getting smarter", "Introducing Redis Iris", "Address any data with Context Retriever", "Agentic AI gets smarter with Agent Memory", "The State of Context Engineering 2026" and "Take the context maturity self assessment". Docs include Agent Memory quickstarts for Python, TypeScript and REST, and Google ADK integration guides.Source
  • 12

    Redis is hiring French- and German-speaking SDRs, a DACH AE and a Mexico AE, but localized pages still sit under old "redis-enterprise" paths and none cover Iris.

    Medium impactMedium effort First result in 1 quarter Lead

    First action

    List localized pages by traffic.

    How to measure it

    Sign-ups from localized pages

    Now
    –
    Target
    +30%
    By
    2 quarters

    Steps

    1. 1

      Audit

      Localized pages.

      Lead, Growth Marketing 1 week

    2. 2

      Translate

      Top pages.

      Localization agency 1 month

    3. 3

      Redirect

      Old paths.

      Web Engineering 1 week

    4. 4

      hreflang

      All versions.

      Web Engineering 1 week

    5. 5

      SDR pages

      Per region.

      SDR Manager 2 weeks

    6. 6

      Measure

      Replies and sign-ups.

      SDR Manager monthly

    First result
    1 quarter
    Cost
    Translation
    Owner
    Lead, Growth Marketing

    Smallest test

    Refresh the German Iris page.

    Why it works

    Refresh the top localized pages (product overview, Iris, pricing, try-free) in German, French and Spanish, redirect old paths, add hreflang, and give SDRs local landing pages for outreach.

    Local-language pages raise reply and sign-up rates for the regional teams being hired.

    Risks and how to handle them

    • Translation errors

      Native reviewers in sales.

    Evidence

    • HiringSales hiring across regions: French-speaking and German-speaking SDRs in London (posted September 23-24, 2026), an Enterprise AE for DACH, an AE for Mexico (September 25), SDRs in Austin (October 1), Regional Sales Directors for the West, TOLA and Austin (October 17-20), and a Field Partner Leader for India, the Middle East and Africa covering "distributors, resellers/VARs, system integrators, MSPs, and hyperscalers" (September 23). Every post cites "our 10,000+ worldwide customers".Source
    • Your websiteComparison pages (sitemap, October 22, 2026): /compare/ covers ElastiCache, Memorystore, Memcached, Valkey, Aiven, Hazelcast, GemFire, Oracle Coherence, OpenSearch, Kafka, MongoDB, MySQL and Oracle; none covers agent memory or context tools; the only Pinecone comparison is an older resource titled "comparing-redis-enterprise-with-pineconevector-database". Localized pages still use old paths such as /de/redis-enterprise/technologie/ and /fr/redis-enterprise/avantages/.Source
    • Your websitePartner and program pages: Redis on AWS ("Buy with cloud commits"), Azure Managed Redis, Redis on Google Cloud marketplace; a /startups/ page and localized /try-free/ pages in German, French, Spanish, Italian, Korean and Portuguese; a LangCache cost calculator at /calculator/langcache/.Source
  • 13

    The new Field Partner Leader must recruit distributors, VARs, integrators and MSPs across three regions, and Redis sells through cloud marketplaces.

    Medium impactMedium effort First result in 2 quarters Field Partner Leader

    First action

    Draft the kit.

    How to measure it

    Partner pipeline in MEA

    Now
    –
    Target
    2x
    By
    2 quarters

    Steps

    1. 1

      Kit

      Pitch, pricing, demo.

      Field Partner Leader, MEA 1 month

    2. 2

      Recruit

      Top partners.

      Field Partner Leader, MEA 1 quarter

    3. 3

      Joint plans

      Per partner.

      Field Partner Leader, MEA 1 month

    4. 4

      Campaigns

      One per region.

      Field Partner Leader, MEA quarterly

    5. 5

      Partner finder

      Public listing.

      Web Engineering 1 month

    6. 6

      Measure

      Pipeline by partner.

      Field Partner Leader, MEA monthly

    First result
    2 quarters
    Cost
    Partner funds
    Owner
    Field Partner Leader, MEA

    Smallest test

    Sign one distributor.

    Why it works

    Build a partner kit (pitch, pricing guide, Iris demo, deal registration), run one joint campaign per region with a top partner, and add partners to a public partner finder.

    Partners carry Redis into accounts the direct team cannot reach.

    Risks and how to handle them

    • Partners sell rivals

      Joint plans with targets.

    Evidence

    • HiringSales hiring across regions: French-speaking and German-speaking SDRs in London (posted September 23-24, 2026), an Enterprise AE for DACH, an AE for Mexico (September 25), SDRs in Austin (October 1), Regional Sales Directors for the West, TOLA and Austin (October 17-20), and a Field Partner Leader for India, the Middle East and Africa covering "distributors, resellers/VARs, system integrators, MSPs, and hyperscalers" (September 23). Every post cites "our 10,000+ worldwide customers".Source
    • Your websitePartner and program pages: Redis on AWS ("Buy with cloud commits"), Azure Managed Redis, Redis on Google Cloud marketplace; a /startups/ page and localized /try-free/ pages in German, French, Spanish, Italian, Korean and Portuguese; a LangCache cost calculator at /calculator/langcache/.Source
    • Your websitePricing page: Free "From $0 /hour"; Essentials "From $0.007 /hour", shared deployment 250 MB-100 GB; Pro "First $200 free", "From $0.014 /hour", "Minimum $200 /month", dedicated, active-active, up to 99.999% uptime; sold direct and through partner marketplaces.Source
  • 14

    Redis has about 64.5 million Docker pulls and over 40 million weekly npm downloads. Many companies run Redis open source without talking to sales.

    High impactMedium effort First result in 1 quarter SDR Manager

    First action

    Build the first list from cloud sign-up domains.

    How to measure it

    PQL-sourced opportunities

    Now
    –
    Target
    25% of SDR pipeline
    By
    2 quarters

    Steps

    1. 1

      Data sources

      Sign-ups, downloads, community.

      Lead, Growth Marketing 2 weeks

    2. 2

      Scoring

      Fit and activity.

      Lead, Growth Marketing 2 weeks

    3. 3

      Plays

      Iris and Cloud.

      SDR Manager 2 weeks

    4. 4

      Route

      To SDRs by region.

      SDR Manager 1 week

    5. 5

      Run

      Weekly.

      SDR Manager weekly

    6. 6

      Measure

      Meetings and pipeline.

      SDR Manager monthly

    First result
    1 quarter
    Cost
    Data time
    Owner
    SDR Manager

    Smallest test

    Run the play on 50 accounts.

    Why it works

    Combine sign-ups, Redis Insight downloads, community activity and company domains into a product-qualified lead list; give SDRs plays for teams building AI agents (Iris) and for teams scaling (Cloud Pro).

    Teams that already use Redis convert faster than cold accounts.

    Risks and how to handle them

    • Privacy

      Use only consented and business data.

    Evidence

    • Public profilesDeveloper reach: Docker Hub images with about 64.5 million pulls (top image redis/redis-stack-server); npm packages with about 40.6 million weekly downloads (redis and @redis/client alone about 8.6 and 9.0 million); "Redis 8.8: New array data structure, rate limiter, performance improvements" reached 229 points on Hacker News (2026).Source
    • HiringSales hiring across regions: French-speaking and German-speaking SDRs in London (posted September 23-24, 2026), an Enterprise AE for DACH, an AE for Mexico (September 25), SDRs in Austin (October 1), Regional Sales Directors for the West, TOLA and Austin (October 17-20), and a Field Partner Leader for India, the Middle East and Africa covering "distributors, resellers/VARs, system integrators, MSPs, and hyperscalers" (September 23). Every post cites "our 10,000+ worldwide customers".Source
    • Your websitePricing page: Free "From $0 /hour"; Essentials "From $0.007 /hour", shared deployment 250 MB-100 GB; Pro "First $200 free", "From $0.014 /hour", "Minimum $200 /month", dedicated, active-active, up to 99.999% uptime; sold direct and through partner marketplaces.Source
  • 15

    Redis 8.8 reached 229 points on Hacker News. Each release is news, but the follow-through often stays on the blog.

    Medium impactLow effort First result in 1 quarter Principal Manager

    First action

    Plan the kit for the next release.

    How to measure it

    Posts and videos per release

    Now
    –
    Target
    30
    By
    2 quarters

    Steps

    1. 1

      Template

      Kit contents.

      Principal Manager, Communications & Developer Influence 1 week

    2. 2

      Briefings

      Creators a week ahead.

      Principal Manager, Communications & Developer Influence per release

    3. 3

      Samples

      Code and video.

      Developer Relations per release

    4. 4

      llms.txt

      Same-day update.

      Lead, Growth Marketing per release

    5. 5

      Social

      Executives and engineers.

      Principal Manager, Communications & Developer Influence per release

    6. 6

      Measure

      Coverage and downloads.

      Principal Manager, Communications & Developer Influence per release

    First result
    1 quarter
    Cost
    Team time
    Owner
    Principal Manager, Communications & Developer Influence

    Smallest test

    Use it for the next release.

    Why it works

    For each release, ship a kit: a markdown changelog, code samples, a short video, creator briefings a week ahead and an llms.txt update on the day.

    Coordinated releases get more coverage, and assistants learn new features quickly.

    Risks and how to handle them

    • Embargo leaks

      Brief trusted creators only.

    Evidence

    • Public profilesDeveloper reach: Docker Hub images with about 64.5 million pulls (top image redis/redis-stack-server); npm packages with about 40.6 million weekly downloads (redis and @redis/client alone about 8.6 and 9.0 million); "Redis 8.8: New array data structure, rate limiter, performance improvements" reached 229 points on Hacker News (2026).Source
    • HiringPrincipal Manager, Communications & Developer Influence (HQ San Francisco, posted September 1, 2026): owns PR, executive visibility, social and "an influencer program that identifies and develops relationships with independent engineers, OSS maintainers, technical YouTubers/newsletter writers"; positions Redis "as a real-time agentic platform"; measured on "media quality, share of voice, executive visibility, and business impact".Source
    • Your websitellms.txt check (October 22, 2026): redis.io/llms.txt (also served at /agents/) lists 81 links under headings from Core Docs to Tutorials. It never mentions Redis Iris, Context Retriever or the Redis MCP server, and does not link the free sign-up page (/try-free/); of the roughly 60 docs pages under /operate/iris/ and /develop/ai/context-engine/, it links one (LangCache concepts). Those docs already exist in markdown, e.g. /docs/latest/operate/iris/agent-memory/index.html.md.Source
  • 16

    Redis has a LangCache calculator and quotes "~$0.07 per session" for agent memory, but buyers must work out Iris costs for their own traffic.

    Medium impactMedium effort First result in 1 quarter Product Marketing

    First action

    Write the cost formula.

    How to measure it

    Sign-ups from the calculator

    Now
    –
    Target
    15%
    By
    1 quarter

    Steps

    1. 1

      Formula

      From pricing.

      Product Marketing 1 week

    2. 2

      Build

      Calculator page.

      Web Engineering 2 weeks

    3. 3

      Markdown

      Formula for agents.

      Lead, Growth Marketing 1 day

    4. 4

      Link

      From Iris and pricing.

      Web Engineering 1 day

    5. 5

      Test

      With customers.

      Principal Solution Architect, FinServ 2 weeks

    6. 6

      Measure

      Use and sign-ups.

      Lead, Growth Marketing monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Product Marketing

    Smallest test

    Publish a static table first.

    Why it works

    Build a calculator: sessions per day, memory size and retrieval calls in, monthly cost and the plan (Free, Essentials or Pro) out, with the method shown and a sign-up button pre-set to Iris.

    Clear costs remove an evaluation step for humans and agents alike.

    Risks and how to handle them

    • Estimates differ from bills

      Show assumptions clearly.

    Evidence

    • Your websitePartner and program pages: Redis on AWS ("Buy with cloud commits"), Azure Managed Redis, Redis on Google Cloud marketplace; a /startups/ page and localized /try-free/ pages in German, French, Spanish, Italian, Korean and Portuguese; a LangCache cost calculator at /calculator/langcache/.Source
    • Your websiteHomepage: title "Redis - Real-time data for agents & apps"; the navigation leads with "Redis Iris - Real-time context for agents", then LangCache, Context Retriever, Agent Memory, Data Integration and Flex; a banner reads "86.5% accuracy. ~$0.07 per session. See how Redis stacks up in the Agent Memory Benchmark"; a sign-up link is /try-free/?rcplan=iris; links ask ChatGPT, Claude and Perplexity "How can I use Redis Iris as a real-time context engine for AI apps?".Source
    • Your websitePricing page: Free "From $0 /hour"; Essentials "From $0.007 /hour", shared deployment 250 MB-100 GB; Pro "First $200 free", "From $0.014 /hour", "Minimum $200 /month", dedicated, active-active, up to 99.999% uptime; sold direct and through partner marketplaces.Source
  • 17

    The homepage sends visitors to /try-free/?rcplan=iris, and the role leads CRO on "sign-up flows". Activation, not sign-up, is the outcome that matters.

    High impactMedium effort First result in 1 quarter Lead

    First action

    Measure the current time to first call.

    How to measure it

    Median time to first memory call

    Now
    –
    Target
    <10 minutes
    By
    1 quarter

    Steps

    1. 1

      Instrument

      Sign-up to first call.

      Web Engineering 1 week

    2. 2

      First screen

      Key and quickstart.

      Web Engineering 2 weeks

    3. 3

      Sample repo

      One command.

      Developer Relations 2 weeks

    4. 4

      Email

      Help if no call in a day.

      Lead, Growth Marketing 1 week

    5. 5

      Test

      A/B the flow.

      Lead, Growth Marketing 1 month

    6. 6

      Measure

      Activation.

      Lead, Growth Marketing monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Lead, Growth Marketing

    Smallest test

    Add the quickstart to the first screen.

    Why it works

    Measure time from sign-up to first Agent Memory API call, add a copy-paste quickstart and API key on the first screen, and test a sample agent repo that runs in one command.

    Developers who succeed in minutes stay; those who stall rarely return.

    Risks and how to handle them

    • Shortcuts weaken security

      Keep key handling safe.

    Evidence

    • Your websiteHomepage: title "Redis - Real-time data for agents & apps"; the navigation leads with "Redis Iris - Real-time context for agents", then LangCache, Context Retriever, Agent Memory, Data Integration and Flex; a banner reads "86.5% accuracy. ~$0.07 per session. See how Redis stacks up in the Agent Memory Benchmark"; a sign-up link is /try-free/?rcplan=iris; links ask ChatGPT, Claude and Perplexity "How can I use Redis Iris as a real-time context engine for AI apps?".Source
    • HiringLead, Growth Marketing (United States, posted September 30, 2026): "the audience discovering and evaluating Redis is no longer exclusively human. AI agents can identify a need, decide which solution fits, review technical documentation, and create a new account within one continuous session." The role owns "the website, SEO, answer engine optimization, generative engine optimization, conversion-rate optimization, and the measurement system", must "Build a low-friction journey in which an agent can identify the right Redis solution, review the relevant documentation, and create an account in a single session", and directs "contractors and an agency partner".Source
    • Your websiteRedis Iris page headings: "Your agents should be getting smarter", "Introducing Redis Iris", "Address any data with Context Retriever", "Agentic AI gets smarter with Agent Memory", "The State of Context Engineering 2026" and "Take the context maturity self assessment". Docs include Agent Memory quickstarts for Python, TypeScript and REST, and Google ADK integration guides.Source

Big bets 3

Larger plays that can change the trajectory.

  • 18

    The stated goal is an account created "in a single session". Today an agent can read docs but sign-up needs a browser form.

    High impactHigh effort First result in 3 quarters Lead

    First action

    Design the flow with security.

    How to measure it

    Accounts created through the agent flow

    Now
    –
    Target
    10% of free sign-ups
    By
    3 quarters

    Steps

    1. 1

      Design

      Flow and limits.

      Lead, Growth Marketing 1 month

    2. 2

      Security review

      Abuse controls.

      Security 1 month

    3. 3

      Build

      MCP and CLI.

      Cloud Engineering 1 quarter

    4. 4

      Docs

      In llms.txt.

      Developer Relations 2 weeks

    5. 5

      Launch

      With creators.

      Principal Manager, Communications & Developer Influence 1 month

    6. 6

      Measure

      Accounts and activation.

      Lead, Growth Marketing monthly

    First result
    3 quarters
    Cost
    Engineering time
    Owner
    Lead, Growth Marketing

    Smallest test

    Prototype with internal users.

    Why it works

    Offer a device-code style flow through the Redis MCP server and CLI: the agent requests a free account and database, the developer approves in one click, and the agent gets connection details.

    It removes the last step between an agent choosing Redis and Redis being used.

    Risks and how to handle them

    • Abuse

      Rate limits and human approval.

    Builds on

    Evidence

    • HiringLead, Growth Marketing (United States, posted September 30, 2026): "the audience discovering and evaluating Redis is no longer exclusively human. AI agents can identify a need, decide which solution fits, review technical documentation, and create a new account within one continuous session." The role owns "the website, SEO, answer engine optimization, generative engine optimization, conversion-rate optimization, and the measurement system", must "Build a low-friction journey in which an agent can identify the right Redis solution, review the relevant documentation, and create an account in a single session", and directs "contractors and an agency partner".Source
    • Your websitellms.txt check (October 22, 2026): redis.io/llms.txt (also served at /agents/) lists 81 links under headings from Core Docs to Tutorials. It never mentions Redis Iris, Context Retriever or the Redis MCP server, and does not link the free sign-up page (/try-free/); of the roughly 60 docs pages under /operate/iris/ and /develop/ai/context-engine/, it links one (LangCache concepts). Those docs already exist in markdown, e.g. /docs/latest/operate/iris/agent-memory/index.html.md.Source
    • Your websiteMarkdown versions exist for docs pages (e.g. /docs/latest/integrate/redis-mcp/index.html.md returns text/markdown) but not for product pages: /iris/index.html.md and /pricing/index.html.md return 404.Source
  • 19

    The Iris page offers a "context maturity self assessment" and a "State of Context Engineering 2026" report. These answers show how far along a team is.

    Medium impactHigh effort First result in 3 quarters SDR Manager

    First action

    Map answers to stages.

    How to measure it

    SDR meetings from assessments

    Now
    –
    Target
    100
    By
    3 quarters

    Steps

    1. 1

      Stages

      Map answers.

      Product Marketing 2 weeks

    2. 2

      Scoring

      In marketing automation.

      Lead, Growth Marketing 2 weeks

    3. 3

      Routing

      To SDRs or nurture.

      SDR Manager 1 week

    4. 4

      Briefs

      Per stage.

      SDR Manager 2 weeks

    5. 5

      Report

      Anonymized results.

      Principal Manager, Communications & Developer Influence yearly

    6. 6

      Measure

      Meetings and pipeline.

      SDR Manager monthly

    First result
    3 quarters
    Cost
    Ops time
    Owner
    SDR Manager

    Smallest test

    Route the next 50 assessments.

    Why it works

    Score assessment answers, send early-stage teams to self-serve content and advanced ones to SDRs with a tailored brief, and publish anonymized results in next year's report.

    SDRs spend time on teams ready to buy, and the report gets fresh data.

    Risks and how to handle them

    • Few completions

      Promote in docs and webinars.

    Evidence

    • Your websiteRedis Iris page headings: "Your agents should be getting smarter", "Introducing Redis Iris", "Address any data with Context Retriever", "Agentic AI gets smarter with Agent Memory", "The State of Context Engineering 2026" and "Take the context maturity self assessment". Docs include Agent Memory quickstarts for Python, TypeScript and REST, and Google ADK integration guides.Source
    • HiringSales hiring across regions: French-speaking and German-speaking SDRs in London (posted September 23-24, 2026), an Enterprise AE for DACH, an AE for Mexico (September 25), SDRs in Austin (October 1), Regional Sales Directors for the West, TOLA and Austin (October 17-20), and a Field Partner Leader for India, the Middle East and Africa covering "distributors, resellers/VARs, system integrators, MSPs, and hyperscalers" (September 23). Every post cites "our 10,000+ worldwide customers".Source
  • 20

    Redis sells on AWS, Azure and Google Cloud marketplaces ("Buy with cloud commits"). Enterprises prefer to spend committed cloud budgets on AI tools.

    High impactHigh effort First result in 4 quarters VP

    First action

    Check marketplace listing requirements.

    How to measure it

    Iris deals through marketplaces

    Now
    –
    Target
    30%
    By
    4 quarters

    Steps

    1. 1

      Listings

      Three marketplaces.

      VP, Partner Sales 1 quarter

    2. 2

      Private offers

      Templates.

      VP, Partner Sales 1 month

    3. 3

      Co-sell

      Cloud AI teams.

      VP, Partner Sales ongoing

    4. 4

      Workshops

      Joint events.

      Principal Manager, Communications & Developer Influence quarterly

    5. 5

      Train sales

      Marketplace motion.

      Regional Sales Director 1 month

    6. 6

      Measure

      Deals by channel.

      VP, Partner Sales quarterly

    First result
    4 quarters
    Cost
    Marketplace fees
    Owner
    VP, Partner Sales

    Smallest test

    List on one marketplace.

    Why it works

    List Iris as its own marketplace offer with private offers, co-sell with each cloud's AI teams, and run joint workshops.

    Buying through existing commits removes procurement friction for large AI projects.

    Risks and how to handle them

    • Margin

      Price for marketplace fees.

    Evidence

    • Your websitePartner and program pages: Redis on AWS ("Buy with cloud commits"), Azure Managed Redis, Redis on Google Cloud marketplace; a /startups/ page and localized /try-free/ pages in German, French, Spanish, Italian, Korean and Portuguese; a LangCache cost calculator at /calculator/langcache/.Source
    • HiringStrategic Account Executive, FinServ (NYC, posted October 20, 2026): sells to hedge funds and asset managers "the core Redis platform - the real-time data layer already trusted by trading, risk, and fraud-detection systems" alongside "our newest offering, Redis Iris, a context and memory engine purpose-built for AI agents operating on live enterprise data"; use cases "agentic trading assistants, real-time risk and compliance monitoring, AI-driven client servicing". A Principal Solution Architect, FinServ was posted October 22, 2026.Source
    • Your websitePricing page: Free "From $0 /hour"; Essentials "From $0.007 /hour", shared deployment 250 MB-100 GB; Pro "First $200 free", "From $0.014 /hour", "Minimum $200 /month", dedicated, active-active, up to 99.999% uptime; sold direct and through partner marketplaces.Source

Wildcards 2

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

  • 21

    Iris has guides for one agent framework (Google ADK), and the communications role wants OSS maintainers as voices. Framework defaults decide which store agents use.

    Medium impactLow effort First result in 2 quarters Developer Relations

    First action

    List the top ten frameworks.

    How to measure it

    New framework integrations

    Now
    –
    Target
    5
    By
    2 quarters

    Steps

    1. 1

      List frameworks

      By adoption.

      Developer Relations 1 week

    2. 2

      Approach maintainers

      Grant offer.

      Principal Manager, Communications & Developer Influence 2 weeks

    3. 3

      Support

      Engineering help.

      Developer Relations ongoing

    4. 4

      Docs

      In both repos.

      Developer Relations per integration

    5. 5

      Announce

      Joint posts.

      Principal Manager, Communications & Developer Influence per integration

    6. 6

      Measure

      Sign-ups by integration.

      Lead, Growth Marketing monthly

    First result
    2 quarters
    Cost
    Grants
    Owner
    Developer Relations

    Smallest test

    Fund one integration.

    Why it works

    Offer small grants and engineering help to maintainers of popular agent frameworks to add first-class Redis Agent Memory support, with docs in their repos.

    A default integration in a framework sends developers to Redis without a single ad.

    Risks and how to handle them

    • Seen as buying influence

      Transparent grants, no exclusivity.

    Evidence

    • Your websiteRedis Iris page headings: "Your agents should be getting smarter", "Introducing Redis Iris", "Address any data with Context Retriever", "Agentic AI gets smarter with Agent Memory", "The State of Context Engineering 2026" and "Take the context maturity self assessment". Docs include Agent Memory quickstarts for Python, TypeScript and REST, and Google ADK integration guides.Source
    • HiringPrincipal Manager, Communications & Developer Influence (HQ San Francisco, posted September 1, 2026): owns PR, executive visibility, social and "an influencer program that identifies and develops relationships with independent engineers, OSS maintainers, technical YouTubers/newsletter writers"; positions Redis "as a real-time agentic platform"; measured on "media quality, share of voice, executive visibility, and business impact".Source
    • Public profilesDeveloper reach: Docker Hub images with about 64.5 million pulls (top image redis/redis-stack-server); npm packages with about 40.6 million weekly downloads (redis and @redis/client alone about 8.6 and 9.0 million); "Redis 8.8: New array data structure, rate limiter, performance improvements" reached 229 points on Hacker News (2026).Source
  • 22

    Redis is building an agent-led growth system and the communications role measures share of voice. Nobody publishes how coding agents choose infrastructure.

    Medium impactLow effort First result in 1 quarter Principal Manager

    First action

    Run the first five builds.

    How to measure it

    Monthly report shares

    Now
    –
    Target
    1,000
    By
    1 quarter

    Steps

    1. 1

      Design apps

      Five standard builds.

      Developer Relations 1 week

    2. 2

      Run

      Monthly.

      Developer Relations monthly

    3. 3

      Analyze

      Choices and reasons.

      Lead, Growth Marketing monthly

    4. 4

      Publish

      Method and results.

      Principal Manager, Communications & Developer Influence monthly

    5. 5

      Act

      Fix docs behind losses.

      Lead, Growth Marketing monthly

    6. 6

      Share

      Creators and press.

      Principal Manager, Communications & Developer Influence monthly

    First result
    1 quarter
    Cost
    Team time
    Owner
    Principal Manager, Communications & Developer Influence

    Smallest test

    Run one build set.

    Why it works

    Each month, ask leading coding agents to build the same five apps and record which data stores they pick and why; publish the results and method openly, including when Redis is not chosen.

    It is newsworthy, keeps the team honest and shows which docs drive agent choices.

    Risks and how to handle them

    • Results look self-serving

      Publish method and losses.

    Evidence

    • HiringLead, Growth Marketing (United States, posted September 30, 2026): "the audience discovering and evaluating Redis is no longer exclusively human. AI agents can identify a need, decide which solution fits, review technical documentation, and create a new account within one continuous session." The role owns "the website, SEO, answer engine optimization, generative engine optimization, conversion-rate optimization, and the measurement system", must "Build a low-friction journey in which an agent can identify the right Redis solution, review the relevant documentation, and create an account in a single session", and directs "contractors and an agency partner".Source
    • HiringPrincipal Manager, Communications & Developer Influence (HQ San Francisco, posted September 1, 2026): owns PR, executive visibility, social and "an influencer program that identifies and develops relationships with independent engineers, OSS maintainers, technical YouTubers/newsletter writers"; positions Redis "as a real-time agentic platform"; measured on "media quality, share of voice, executive visibility, and business impact".Source
    • Competitor researchRivals' own homepages: Valkey, "open source (BSD) high-performance key/value datastore... backed by the Linux Foundation"; Dragonfly, "the most performant in-memory data store"; Mem0, "the memory layer for AI agents and applications"; Pinecone, "the trusted AI knowledge company" for "10,000+ customers and 1M developers".Source
Website review of redis.io More example playbooks and reviews

More growth playbooks

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

  • Mammotion growth strategyMakes wire-free robotic lawn mowers (LUBA, LUBA mini, YUKA and the commercial Maston line) that navigate with RTK, LiDAR and vision, plus…23 growth ideas
  • OpenSesame growth strategyAn AI-powered marketplace of 60,000+ curated training courses with LMS and HR platform integrations, human and AI curation, translation…21 growth ideas
  • Element451 growth strategyAn AI platform for higher education: Bolt AI agents that work on an institution's existing systems (Slate, Salesforce, Ellucian) and…22 growth ideas
  • Magentic growth strategyAI agents ("Mages") that take on procurement and supply chain work for global manufacturers: sourcing, contract checks, ordering and…21 growth ideas
  • Warehouse-Lighting.com growth strategyAn online LED lighting distributor and manufacturer based in New Berlin, Wisconsin: industrial, commercial, outdoor, architectural and…22 growth ideas
  • PreSonus growth strategyA Baton Rouge audio brand, owned by Fender since 2021, that makes Eris studio monitors, StudioLive Series III SE digital mixers, Air XD PA…22 growth ideas
  • AutoSitu growth strategyAn AI system for real estate development that connects site feasibility, design review and QA/QC, code compliance, submittal completeness…24 growth ideas
  • GlossGenius growth strategyAll-in-one software for appointment businesses: booking websites, scheduling, payments and POS, marketing, payroll, EMR for medspas, and…22 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on October 23, 2026, and cites them throughout. Redis did not commission, review or endorse it, and Programmable is not affiliated with Redis. 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 Redis runs its business.

Something wrong, or do you represent Redis? 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 306 ideas

    llms.txt for Iris and sign-up, descriptions, markdown product pages, layout shift, sitemap and robots cleanup, agent-growth measurement.

  2. Days 31 to 6013 ideas

    Agent memory comparisons, answer audit, creators, benchmark, capital markets page, localized pages, MEA partners, open source PQLs, release kits, cost calculator and activation; the framework grants and agent-choice report.

  3. Days 61 to 903 ideas

    Commit to the big bets: agent sign-up, assessment routing and marketplaces.

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 speed and simplicity. The most cited problem: choosing between open source, Cloud and Software.

  • Huge client and community ecosystem
  • Costs at scale
  • In their words: “sub-millisecond”

Market

Competitive landscape

5 competitors compared: Valkey, Dragonfly, Mem0, Pinecone and 1 more.

  • Gap to exploit: A clear agent path from need to account
  • Valkey: No agent context products
  • Dragonfly: Smaller ecosystem

Hiring signals

Redis is hiring to turn Iris and agent-led growth into pipeline.

  • Lead, Growth Marketing: Agent-led growth: agent finds product, reads docs, creates account. Ideas 1, 2, 3, 6, 18.
  • Principal Manager, Communications & Developer Influence: Creators, OSS maintainers and share of voice. Ideas 9, 10, 15.
  • Strategic Account Executive - FinServ (NYC): Redis Iris for hedge funds and asset managers. Idea 11.

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