[ { "id": "account-market-map", "title": "Build a sourced target-account map", "description": "Turn an ideal customer profile into a researchable company list with visible fit evidence.", "category": "Account research", "tool": "Approved AI assistant", "toolUrl": null, "level": "Beginner", "evidence": "Practitioner report", "output": "A deduplicated account table with domain, fit reasons, supporting URLs, and open questions.", "inputs": [ "Written ideal customer profile and exclusion rules", "Approved company sources or a seed account export" ], "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.", "prompt": "Research [small batch size] companies against [ICP and exclusions]. For each, return canonical domain, stated business, geography, relevant public signals, dated source URLs, and fit reasons tied to the ICP. Use unknown for unsupported fields. Separate verified facts from hypotheses. Merge duplicate domains and explain exclusions. Do not guess personal emails or contact anyone.", "steps": [ "Translate the ICP into concrete inclusion and exclusion criteria.", "Build a small seed list and approve the source types to use.", "Research each account with dated evidence and deduplicate by domain.", "Review borderline companies before extending the list or adding it to the CRM." ], "review": "A revenue owner checks the fit rationale and source freshness for every pilot account.", "limits": [ "Public data can lag company changes.", "A large list is not proof of an addressable or reachable market." ], "measure": "Verified account coverage, duplicate rate, and accepted versus rejected fit reasons.", "sources": [ { "title": "TAM as a living company database", "url": "https://x.com/codyschneider/status/2099558800428544344", "author": "Cody Schneider", "note": "September 14, 2026. Visible post describes company domains, marketing ownership, funding, and hiring signals. Our scoring rules and prompt are original.", "kind": "Practitioner report" } ] }, { "id": "buying-signal-review", "title": "Review buying signals before drafting outreach", "description": "Explain why a recent event might matter without pretending it proves intent.", "category": "Account research", "tool": "Approved AI assistant", "toolUrl": null, "level": "Beginner", "evidence": "Practitioner report", "output": "A signal queue with event date, evidence, relevance hypothesis, and a draft conversation opener.", "inputs": [ "A reviewed account list", "Approved public hiring, funding, or product-change sources" ], "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.", "prompt": "Review [accounts] for [defined buying-signal theory]. Return only signals supported by dated public sources. For each, explain the event, why it might relate to [offer], alternative explanations, and confidence. Draft one restrained conversation opener referencing the actual event. Mark it unsent. Do not infer private plans, fabricate familiarity, or send outreach.", "steps": [ "Define one hypothesis connecting an event to the problem you solve.", "Collect recent first-party evidence for a small reviewed account set.", "Compare signal interpretations and record false positives.", "Let the account owner approve any draft and its recipient before use." ], "review": "Check that the event is real, recent, relevant, and not being presented as proof of purchase intent.", "limits": [ "Hiring or fundraising does not automatically indicate demand.", "Contact data and outreach permissions require separate verification." ], "measure": "Signal precision in manual review and relevant conversations from approved outreach.", "sources": [ { "title": "Account research and campaign preparation", "url": "https://x.com/MichLieben/status/2102103085409849554", "author": "Michel Lieben", "note": "September 21, 2026. Describes account research, buying signals, contact checks, and outreach prepared for human review. Outcome metrics are not shown.", "kind": "Practitioner report" } ] }, { "id": "sales-meeting-brief", "title": "Prepare a sales meeting from approved business context", "description": "Combine account facts and previous notes into questions a salesperson can use.", "category": "Sales preparation", "tool": "Approved AI assistant", "toolUrl": null, "level": "Beginner", "evidence": "Editorial adaptation", "output": "A concise pre-meeting brief with known facts, open questions, and source references.", "inputs": [ "Approved CRM notes and meeting context", "Current company pages and the meeting objective" ], "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.", "prompt": "Prepare a brief for [meeting] using [approved CRM notes] and [company sources]. Separate known facts, past commitments, and unanswered questions. Cite a source beside each important claim. Suggest five discovery questions tied to [meeting objective], plus any contradictions to clarify. Do not invent a relationship history, purchasing authority, or budget. Do not edit the CRM or email attendees.", "steps": [ "Define what the meeting should resolve and which notes may be used.", "Combine read-only source material with dates and owner names.", "Draft the brief and check all past commitments against original notes.", "Let the salesperson select questions and add the actual outcome afterward." ], "review": "The account owner verifies relationship history and removes speculative statements before the meeting.", "limits": [ "Stale notes can misrepresent priorities or contacts.", "Live CRM access requires configured permissions; an export is enough for the pilot." ], "measure": "Preparation time, factual corrections, and useful questions carried into the meeting.", "sources": [ { "title": "Building a marketing agent", "url": "https://x.com/codyschneider/status/2042724315888496753", "author": "Cody Schneider", "note": "April 10, 2026. Visible post describes delegation and live business data. Public X oEmbed verified author and excerpt; the full implementation is not reproduced here.", "kind": "Practitioner report" } ] }, { "id": "search-demand-pipeline", "title": "Turn search demand into a GTM experiment backlog", "description": "Prioritize search opportunities by audience fit and business relevance.", "category": "Demand generation", "tool": "Approved AI assistant", "toolUrl": null, "level": "Intermediate", "evidence": "Practitioner report", "output": "A ranked backlog linking a query group to audience intent, relevant offer, and a bounded experiment.", "inputs": [ "Search Console and GA4 exports with matching periods", "Product positioning and conversion definitions" ], "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.", "prompt": "Using [dated GSC and GA4 exports], identify search themes relevant to [ICP and offer]. Separate informational interest from buying intent. For each candidate, show observed metrics, data limitations, proposed landing-page change, owner, and success measure. Avoid claiming causal impact from correlation. Do not publish pages or rewrite content automatically. Return the smallest useful experiment backlog.", "steps": [ "Align dates, property scope, and conversion definitions.", "Group queries by audience problem and connect them to existing pages.", "Check whether each opportunity genuinely matches the offer.", "Approve one change with a baseline and review date before expanding." ], "review": "Marketing and sales jointly check audience fit, conversion quality, and whether the proposed page answers the query.", "limits": [ "Search Console rows may be incomplete.", "Search traffic is not qualified pipeline and seasonality can distort comparisons." ], "measure": "Qualified inquiries by page and the outcome of each approved experiment.", "sources": [ { "title": "Search opportunities from first-party data", "url": "https://x.com/codyschneider/status/2105764696691192319", "author": "Cody Schneider", "note": "October 1, 2026. Proposes using Search Console and GA4 data to find opportunities and draft changes. Ranking gains are not verified.", "kind": "Practitioner report" }, { "title": "Search Console query API", "url": "https://developers.google.com/webmaster-tools/v1/searchanalytics/query", "author": "Google", "note": "Official query interface for search-performance data; returned rows may not cover all data.", "kind": "Official documentation" } ] }, { "id": "campaign-change-review", "title": "Create an approval queue for campaign changes", "description": "Separate ad-platform operations from the decision to spend or pause.", "category": "Campaign operations", "tool": "Approved AI assistant", "toolUrl": null, "level": "Advanced", "evidence": "Practitioner report", "output": "A proposed change log with campaign IDs, exact before-and-after settings, justification, and approval status.", "inputs": [ "Read-only campaign settings and performance exports", "Budget boundaries and an owner-approved operating policy" ], "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.", "prompt": "Review [campaign export] against [operating policy]. Propose only changes supported by the provided data. For each, state campaign ID, current setting, proposed setting, evidence, downside, spend impact, and rollback step. Mark every item pending approval. Do not upload creative, create campaigns, change budgets, or pause ads. Flag missing data instead of guessing.", "steps": [ "Export the current campaign configuration and preserve a baseline.", "Define the spend boundaries, minimum evidence, and authorized approver.", "Generate proposed changes with explicit reasons and rollback instructions.", "Apply only reviewed changes through your normal process and log their results." ], "review": "The campaign owner checks exact account IDs, budget math, sample size, and rollback feasibility.", "limits": [ "API access does not guarantee safe campaign decisions.", "Delayed attribution and small samples can make apparent performance misleading." ], "measure": "Incorrect proposals prevented, approved changes logged, and post-change results.", "sources": [ { "title": "Advertising API operations", "url": "https://x.com/codyschneider/status/2106021448405958689", "author": "Cody Schneider", "note": "October 2, 2026. Describes creative uploads and campaign operations through an API. We add approval controls; the visible excerpt does not establish performance.", "kind": "Practitioner report" } ] }, { "id": "weekly-revenue-brief", "title": "Build a weekly revenue-team action brief", "description": "Turn approved channel and pipeline data into a short owner-assigned review agenda.", "category": "Revenue operations", "tool": "Approved AI assistant", "toolUrl": null, "level": "Beginner", "evidence": "Editorial adaptation", "output": "A weekly memo separating observed changes, hypotheses, decisions needed, and owners.", "inputs": [ "Approved CRM stage data and channel summaries", "Agreed metric definitions and previous action log" ], "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.", "prompt": "Create a weekly revenue brief from [approved dated exports]. Reconcile metric definitions before comparing periods. Summarize material changes with source references, separate observed facts from explanations, and identify decisions requiring an owner. Carry forward unfinished actions. Do not attribute revenue to a channel without evidence or alter forecasts. Keep the final brief to one page plus a discrepancy appendix.", "steps": [ "Agree metric definitions and the source of truth for pipeline stages.", "Prepare matching-period exports and last week’s decisions.", "Generate the brief and reconcile important totals.", "Use the meeting to assign actions and record actual decisions." ], "review": "Revenue operations checks totals, stage changes, attribution, and ownership before circulation.", "limits": [ "Different systems may define a lead or conversion differently.", "The agent cannot know offline activity absent from the inputs." ], "measure": "Reconciliation errors, action completion, and time to resolve data discrepancies.", "sources": [ { "title": "Building a marketing agent", "url": "https://x.com/codyschneider/status/2042724315888496753", "author": "Cody Schneider", "note": "April 10, 2026. Visible post describes delegation and live business data. Public X oEmbed verified author and excerpt; the full implementation is not reproduced here.", "kind": "Practitioner report" } ] }, { "id": "x-lead-discovery", "title": "Find people on X asking for what your product does", "description": "Review a short list of recent buying signals every four hours, with direct post links, fit reasons, and helpful reply drafts.", "category": "Demand generation", "tool": "Grok Bot", "toolUrl": "https://grok.com/", "level": "Intermediate", "evidence": "User-supplied report", "reviewed": "2026-10-13", "output": "A ranked shortlist of posts from the last 24 hours, with author handles, intent labels, relevance scores, and reply drafts. Each report ends with “What needs my attention?” and up to three strongest opportunities.", "inputs": [ "Product description, target customer profile, and clear exclusions", "Competitor names, customer problem phrases, and examples of relevant and irrelevant posts", "A persistent log of previously reported post IDs and handles, a report destination, and a timezone for the four-hour schedule" ], "connections": "Requires a configured Grok Bot environment with authorized X search access, a persistent deduplication log, and a report destination. Set up the recurring four-hour schedule separately after reviewing a manual sample. This directory does not schedule runs or connect your X account.", "prompt": "Act as a lead discovery agent for [PRODUCT].\nProduct description: [WHAT YOUR PRODUCT DOES]\nTarget customers: [WHO YOUR PRODUCT HELPS]\nCompetitors and exclusions: [COMPETITORS, GEOGRAPHY, AND EXCLUSIONS]\n\nFor each run of a separately configured four-hour schedule, search X for posts published within the last 24 hours. Record the run time and timezone. Focus on five types of posts:\n1. Requests for recommendations for products like mine.\n2. Complaints about problems my product solves.\n3. Frustration with competitors or requests for alternatives.\n4. Descriptions of workflows my product could improve.\n5. Explicit requests for help with something my product does.\n\nFor every relevant post, provide the original post text available to you and its direct link, the author's X handle, publication time, a specific fit reason tied to the product description, intent (actively looking, exploring alternatives, or expressing frustration), a relevance score from 1–10 with a one-line reason, and a suggested natural reply that helps the person. If no intent label fits, say unclear rather than forcing one. Reply drafts must make only supported product claims and must not imply that I am an unaffiliated customer.\n\nPrioritize explicit requests for a solution over general conversation. Use 8–10 for an explicit need and strong customer fit, 5–7 for a relevant problem with uncertain purchase intent, and 1–4 for weak fit; scores are judgment calls, not purchase probabilities. Exclude promotions, apparent bots, irrelevant mentions, and posts older than 24 hours. Bot detection is uncertain; flag ambiguous cases rather than claiming certainty. Never invent posts, links, user details, or quoted text. If the original cannot be verified, leave it out of the lead shortlist and note the access limitation.\n\nCheck [PERSISTENT REPORTED-LEAD LOG] before reporting. Do not repeat previously reported posts or leads. Group multiple posts from the same author into one opportunity. Record post IDs, handles, source times, and report times for leads included in a successfully delivered report. If the log cannot be read or written, disclose that and do not claim deduplication worked.\n\nKeep the report short, with a maximum of [10] new opportunities, highest intent first. A small or empty report is acceptable; do not pad it. End with “What needs my attention?” and highlight up to three most promising opportunities, or state that no qualifying new opportunities were found. Report incomplete searches or failed runs separately from zero matches.\n\nDo not reply, follow, DM, or otherwise contact anyone. I will review each opportunity and decide whether to respond.", "steps": [ "Define your product, customer profile, exclusions, and search phrases for all five signal types; choose a small report limit.", "Run one manual search and check each post, timestamp, fit reason, and reply draft against the original context.", "Set up a persistent reported-lead log and confirm that a repeated sample run does not resend the same posts or people.", "Configure the four-hour schedule and report destination in your own environment. Review the report before any response and inspect failures or empty runs." ], "review": "Open each original post before acting. Check that the request is current, the product actually fits, and the draft offers useful help without unsupported claims or disguised affiliation. A relevance score does not prove buying intent. All replies, follows, and DMs remain manual decisions.", "limits": [ "The excerpt’s author, original URL, and publication date are unverified. It describes an experiment and a suggested prompt, not measured lead or revenue results.", "X search coverage and account access can be incomplete. Freshness depends on checking post timestamps, not when a search engine indexed the page.", "A prompt alone does not create a scheduler or durable memory. Reliable deduplication requires a persistent log across runs.", "Intent scoring and bot detection are fallible. A complaint or workflow description is not necessarily a purchase request." ], "measure": "New opportunities accepted after review, duplicate and stale-post rates, unsupported fit claims, and conversations that progress after a human chooses to respond.", "sources": [ { "title": "X lead-discovery prompt — user-supplied excerpt", "url": null, "author": null, "kind": "User-supplied report", "note": "The supplied excerpt proposes four-hour X searches across five buying-signal types, a 24-hour freshness window, relevance scoring, deduplication, helpful reply drafts, and human review before any contact. The original author, URL, and date are not verified. This guide adapts the prompt and adds implementation checks; no conversion or revenue outcome has been established." } ] } ]