Tell customers when the feature they asked for finally ships

The system remembers who asked for what, then drafts a personal email the moment that feature launches.

How the work actually flows

A straight line. Runs once per each matching customer request.

Pattern: Multiple Instances without Synchronization (12)

flowchart TD trig>"you ship a new feature"]:::trig s0[["search past requests for match"]]:::mi s1["draft personalized launch email"]:::svc s2[("save draft to gmail")]:::store trig --> s0 s0 --> s1 s1 --> s2 out[/"personalized launch emails drafted"/]:::out pay{{"closes the loop with requesting customers"}}:::pay s2 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itAn outside serviceRuns once per itemA record or sheetResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
AI Agents & Autonomous SystemsKnowledge Base & RAGEmail Automation
Connects
TallySupabaseOpenAIGmail

The problem it solves

Customers ask for features and then you never follow up once you actually build them, so the moment of goodwill is lost. Keeping track of who wanted what, especially when they describe it differently than you name it later, is nearly impossible by hand.

Who it fits

Best for a product manager, founder, or customer success team that collects feature requests but rarely closes the loop.

How it works

  1. A customer submits a feature request through your form
  2. The system stores the meaning of the request, not just the exact words
  3. When you ship a new feature, it searches past requests for anyone who asked for something similar
  4. It drafts a personal email connecting their original request to the new feature
  5. The draft is saved to Gmail for you to review and send
What you get

Customers who feel remembered and valued

You get a ready-to-send note that reminds customers you heard their request the moment the feature they wanted actually ships.

What you get

Ready-to-send draft emails to the exact customers who requested a feature you just launched.

What you need

A Supabase account, an OpenAI account, a Tally Forms account, and a Gmail account.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook