Open intake list for AI ideas (L1)

Collect every AI idea in one visible list with the problem, the owner, and the current manual cost. No committee, no scoring model, just visibility so duplicate pilots stop happening in four teams at once.

WORKFLOW1Ask for problems, not too…sAirtable2Make the list public inte…nallyNotion3Triage monthly in thirty …inutesManual4Publish what shippedSlack
4 steps, in order, with the tool that owns each one.
Adoption ladderSix levels from Starter to Rebuilt. This item sits at level 1.L1 StarterOne tool, no workflow changeL2 AssistedAI drafts, humans approveL3 IntegratedWired into CRM and SlackL4 OrchestratedMulti-step, owned, measuredL5 AutonomousAgent runs, human auditsL6 RebuiltThe process itself changes
This playbook belongs at L1 Starter. Running it above your level is how pilots stall.
Measures of successideas submitted per month; triage response time; duplicate pilots avoidedPROVE IT WORKEDideas submitted per monthtriage response timeduplicate pilots avoided

The steps

  1. 01

    Ask for problems, not tools

    Tool: Airtable

    The form captures the problem, who has it, how often, and the current time cost. Tool name is optional and last. Tool first intake produces a shopping list rather than a roadmap. Owner: ops lead. DoD: form live with problem first fields.

  2. 02

    Make the list public internally

    Tool: Notion

    Everyone sees every entry. Visibility alone kills most duplicate pilots and surfaces the people already solving the same thing. Pitfall: a private list owned by one team. DoD: list is readable company wide.

  3. 03

    Triage monthly in thirty minutes

    Tool: Manual

    Three buckets: do now, watch, no. Say no out loud and record the reason. Unanswered ideas are how you get shadow projects. Owner: ops lead. DoD: every entry has a status and a date within 30 days.

  4. 04

    Publish what shipped

    Tool: Slack

    Monthly post of what moved from the list into production and what it returned. This is what keeps submissions coming. Owner: ops lead. DoD: monthly shipped post.

Tools in this playbook

Next playbooks

Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.

Share this playbook

Posting to Instagram or TikTok? Copy the link, it carries the title, summary and share image.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.