Grok BotSalesRevenue growthAI score · 83/100AI-assisted edit · no obvious prompt-injection riskGitHub

Growth Ideas Logger: Capture and Score Growth Ideas by Voice

Voice dictation → structured entry → impact/effort scoring → stack-ranked output

Some experienceStepsWorkflowPrompt
Who
Product managers, growth leads, or founders who need to quickly capture and rank growth ideas
You get
Turn spoken growth ideas into scored, structured entries and maintain a stack-ranked playbook document
You need

Constraints

Prerequisites: access to a voice-capable grok-bot and an available GROWTH PLAYBOOK document (e.g., Notion, Google Docs, or Markdown file). This template does not own implementation, does not decide what ships, and requires no human approval. No specific integrations are listed in the source; actual connectivity depends on your platform.

What they did

The source describes a bot named 'Vincent' (named after the day-3 growth guest) that captured growth ideas via voice dictation during a stream. Specific ideas logged included: share-your-win with an OG image, share-a-card-for-a-rarer-card, player-vs-player challenges, welcome DM with 10 free gold, and sponsored cards instead of pay-to-win. The bot converted these into structured entries, maintained a growth playbook document, and stack-ranked them by impact and effort.

How it went

No quantitative results are provided in the source (author_report). The template describes the intended function: generating scored entries after each dictation and returning the top three with rationale when asked 'what's next'. Actual performance depends on the bot platform's document access and the model's instruction-following stability.

Worth knowing

Known limitations: - The template explicitly states 'Does not own: Building any of it' and 'Deciding what ships'—the bot does not implement ideas or make final prioritization decisions; - The specific grok-bot model version is not stated in the source; behavior may vary by version; - No integration configuration (e.g., Notion API, Google Docs connection) is listed; users must ensure the bot can access the playbook document; - The README.md caveats note: all descriptions are reconstructions from stream content, 'none of them were published verbatim, so treat each block as a reconstruction to edit, not a template that was tested as-is'; - This site has not tested the template (reproduction=not_tested); verify document writing and ranking logic after setup.

Steps

  1. Configure the bot role description

    Create a new bot in your bot platform and paste the role description below into the system prompt or character field. Replace {NAME} with the bot name (e.g., 'Vincent') and {GROWTH PLAYBOOK} with the actual document name or link.

    Execution prompt · Source text。Bot system prompt / character field; replace placeholders before saving

    You are {NAME}. When I dictate a growth idea, log it in {GROWTH
PLAYBOOK}: one-line title, the mechanic, who it targets, impact
(1–5), effort (1–5), and why. Keep the doc stack-ranked. Don't
build anything; when I ask "what's next", give me the top three
with the reasoning.

  2. Dictate a growth idea to trigger logging

    Send a growth idea to the bot via voice or text. Trigger by speaking the idea directly or sending "Log this idea: [idea description]". The bot will convert it to a structured entry and write it to the GROWTH PLAYBOOK.

  3. Review ranking and get priority recommendations

    Ask the bot "what's next" or similar. The bot returns the top three ideas from the playbook with scoring rationale. The stack-rank is automatically recalculated after each new entry.

Prompt you can copy

Setup guidance · Editorial suggestion。Hand to setup assistant to confirm placeholders and document access permissions

This block is the prompt. Ads are never placed here.

You are a growth ideas logging assistant. My goal is to turn spoken growth ideas into structured, sortable entries. Please help me:
1. Confirm I have correctly filled the {NAME} and {GROWTH PLAYBOOK} placeholders;
2. Verify the playbook document is accessible and writable by the bot;
3. Run a test dictation to validate the output format (one-line title, mechanic, target, impact 1–5, effort 1–5, rationale).
If document access fails, report the specific error—do not assume connectivity is configured.

Replace {NAME} and {GROWTH PLAYBOOK} first, then test with one sample idea to verify format.

Source

growth-ideas-logger · unicodef1wn · GitHub · 2026-09-18

Comments & feedback

Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.

Loading…

    Related