Generate a personalized marketing plan as soon as a visitor leaves e-mail and company

What was done

Same page, workflow 3. "When a visitor submits their email and company name on a Brevo landing page, the data is stored in Supabase and triggers a Dust agent. The agent generators has tailored marketing plan... then write the output back to Supabase, which renders it as an unique, personalized page. » « Fully automated end-to-end... no human in the loop. » Distinct from BDR emails. RevOps internal support ("30%+ of requests") is mentioned without production details: not retained as a separate sheet.

Before you start

Tool cited by the source: Dust (MCP Supabase). Fill in the bracketed items: [coller]. Strip confidential data that is not needed and check your tool’s access terms. Features and plans can change.

The method, in three steps.

1. 01

   Gather the context

   Spot the bracketed items in the prompt ([coller]) and prepare what they ask for.

2. 02

   Adapt the prompt

   Copy the prompt below, replace the bracketed items, then paste it into the AI assistant you use. The cited tool (Dust (MCP Supabase)) is not necessarily available to the public..

3. 03

   Reread before using

   Reread the result, correct it if needed and keep the final decision. Caveats are detailed below.

Your starting point.

Replace the bracketed items, then adapt the proposal to your situation. This prompt is written by the iadujour desk It is not a quotation from the source.

Visitor company (name, public sector): [coller]. Brevo offer to glue (without inventing): [coller].

Map of one page: 3 channels, 3 ideas, calendar 30 days. Mark the assumptions. No invented ROI.

What deserves your attention

Useful skills

Official skills on the same task, paired by the desk: they are not part of the described case.

• Good practices Postgres (Supabase)Supabase · Collects the best Postgres practices maintained by Supabase, valid for a Postgres hosted anywhere, not just on Supabase.
• Develop with SupabaseSupabase · This skill applies to any Supabase task: base, Auth, Edge Functions, Realtime, Storage, vectors, cron, file, client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro or Remix, troubleshooting (session, JWT, cookies, getSession, getUser, getClaims, RLS), CLI or MCP server, schemas, migrations, audits, Postgres extensions, and debugging ( HTTP or Postgres errors, RLS, schema cache, timesouts, Logs Explorer / ClickHouse logs).
• Optimize Postgres according to Supabase practices, in Build Web AppsOpenAI · Collect, in the OpenAI Build Web Apps plugin, Postgres optimization practices maintained by Supabase.
• Configuring Supabase auth emailsPostHog · Connect a Supabase project so that its auth emails send via PostHog email templates via the Supabase Send Crochet Email, in an order that never breaks an entry.