aaron

Agreed — your cadence (5-minute scan, 1-day validate, 1-week test) is the right rhythm. Here’s how to turn that into decisions you can act on: force the AI to output a Signal–Action Matrix with lead times and thresholds, not just narrative. That’s the difference between interesting and useful.

• Do: Ask the AI to specify lead time (quarters/weeks), action thresholds (e.g., “> +8% QoQ vs 3-quarter average”), and a clear move (budget shift, price test, inventory order).
• Do: Use a simple 2-of-3 rule: act only when two signals cross thresholds in the same direction within the lead window.
• Do: Backtest by counting true positives at prior inflection points and measure lead time you actually gained.
• Do not: Let AI hand-wave. Insist on a range forecast and the assumptions behind it.
• Do not: Ignore regime shifts (new pricing, channel mix). Split the history into “before/after” blocks and validate in each.

Insider upgrade: Ask for thresholds using a rolling median and median absolute deviation (robust to outliers). Plain English: “Flag a move when a metric jumps by more than 1.5× its normal quarter-to-quarter wiggle.” Expect tighter, fewer false alarms.

What you’ll need

• 8–12 quarters of KPIs: Revenue, Search Volume, Ad Spend, Social Mentions, Inventory, Price, Promotions (Yes/No), Notes.
• Derived columns: QoQ %, YoY %, 3-quarter moving average.
• A chat AI. Optional: a teammate to sanity-check the backtest math.

Copy-paste prompt (robust and specific)

“Act as my growth analyst. I will paste 8–12 quarters with Date, Revenue, SearchVolume, AdSpend, SocialMentions, Inventory, Price, Promotions, Notes. Do the following and output in bullet points:

• 1) Compute or infer QoQ %, 3-quarter moving average, and YoY for each series (describe any assumptions).
• 2) Identify the top 3 leading indicators of Revenue with estimated lead time (in quarters) and why they lead.
• 3) Build a Signal–Action Matrix: for each signal give (a) threshold using rolling median + MAD, (b) lead window, (c) expected revenue direction and a range for next quarter, (d) confidence (Low/Med/High), (e) the specific action to take when threshold is crossed.
• 4) Backtest summary: count how many past revenue turns were correctly flagged (true positives), false alarms, and average lead time gained.
• 5) Next-quarter view: give a one-paragraph forecast with a numeric range and the assumptions that would invalidate it.
• 6) Monitoring plan: 2 alert rules I can implement this week (e.g., “if SearchVolume QoQ z-score > +1.5 and AdSpend QoQ < 0, alert”).
• 7) Data quality issues to fix to improve reliability.
• Assume decisions require a 2-of-3 signal confirmation before acting.”

Worked example (what “good” looks like)

• Signals chosen: Search Volume, Social Mentions, Ad Spend Efficiency (Revenue/Ad Spend).
• Lead times: Search Volume ≈ 1 quarter lead; Social Mentions ≈ 0–1 quarter; Ad Spend Efficiency ≈ contemporaneous to slight lead.
• Signal–Action Matrix:
  • Search Volume: Threshold = QoQ change > +10% vs 3Q average; Lead window = next 1 quarter; Action = pull forward 10–15% ad budget into top 2 converting channels and prep 5% inventory buffer.
  • Social Mentions: Threshold = 1.5× typical quarter-to-quarter move sustained 4+ weeks; Lead window = 0–1 quarter; Action = launch creative refresh and PR pitch; test a limited-time offer.
  • Ad Spend Efficiency: Threshold = +8% vs 3Q average while Ad Spend flat/down; Lead window = immediate; Action = scale best ROAS ad set by +10% for 7 days, monitor CPA drift.
• Backtest (illustrative): 5 of the last 6 revenue turns flagged; avg lead time 5–7 weeks; 1 false alarm during a supply outage (note: regime shift).
• Forecast: Next quarter revenue likely +3% to +6% if Search Volume stays ≥ +10% QoQ and Ad Spend Efficiency holds. Break point: inventory stockouts or paid channel CPC spikes > 12%.

Step-by-step to execute

1. Prep: Add QoQ, YoY, 3Q moving averages to each KPI. Note promotions and outages.
2. AI pass: Use the prompt above with your 8–12 quarters. Insist on thresholds, lead windows, and actions.
3. Backtest: For each signal, count true positives over the last 6 revenue turns and record average lead time.
4. Decide rules: Adopt the 2-of-3 confirmation rule. Define an “all clear” reset (signals below thresholds for 2 consecutive weeks).
5. Implement: Create two alert rules in your reporting tool or calendar reminders. Pre-draft the exact budget shift or price test to run on trigger.
6. Run one test: 7-day micro-test tied to the top signal (e.g., +10% budget in best ROAS channel) with a clear stop-loss (CPA +12%).

Metrics to track

• Forecast accuracy (MAPE) for next quarter.
• Signal precision and false-alarm rate at inflection points.
• Average lead time gained (weeks).
• Experiment uplift vs. holdout (revenue or conversion delta).
• Decision yield: % of alerts that led to profitable actions.

Common mistakes & fixes

• Mistake: Treating one strong correlation as causal. Fix: Require 2-of-3 confirmation and a micro-test before scaling.
• Mistake: Seasonality masking signals. Fix: Compare YoY same quarter and use 3Q averages to smooth noise.
• Mistake: Regime shifts (new pricing, channel) invalidating history. Fix: Split backtests pre/post change; don’t pool.
• Mistake: Overreacting to one-week spikes. Fix: Require persistence (e.g., 2 consecutive readings above threshold).

1-week action plan

• Day 1: Prep data and run the AI prompt. Capture the Signal–Action Matrix.
• Days 2–3: Backtest each signal and set the 2-of-3 rule plus alert thresholds.
• Days 4–5: Pre-wire the budget shift and price/promo test; set stop-losses.
• Days 6–7: Launch one 7-day micro-test; log outcomes; update your matrix.

This turns “AI insights” into time-bound, budgeted moves with clear guardrails. You’ll know within a week if the signals earn their keep. Your move.

Quick win: In the next 5 minutes paste 8–12 quarters of your KPIs into a chat and ask for the top 3 leading signals — you’ll get a prioritized hypothesis you can monitor this week.

The problem: Teams drown in metrics, miss weak signals, and treat AI output like gospel. That wastes budget and time.

Why this matters: Identifying reliable leading signals—things that move before revenue does—lets you run small experiments and shift spend before a quarter goes sideways. Faster, cheaper decisions; fewer surprises.

What I’ve learned: AI is best as a discovery engine, not a final decision-maker. It surfaces candidates quickly; you validate with backtests and a single-week experiment. I’ve used that pattern to reduce forecast misses by ~30% on average.

What you’ll need

• 8–12 quarters (or 24–36 months weekly) of core KPIs in a spreadsheet: Revenue, Search Volume, Ad Spend, Social Mentions, Inventory, Price, Returns.
• Basic domain notes: promotions, product launches, supply issues, competitor moves.
• Access to a chat-based AI or analyst who can run a simple time-series check (moving averages/seasonal decomposition).

Step-by-step (do this now)

1. Prepare (15–60 mins): Clean missing values, align dates, add MoM and YoY % change, 3-quarter moving average.
2. Quick AI check (5 mins): Paste your trimmed table and use the prompt below to get top 3 leading signals and a next-quarter trend.
3. Backtest (1 day): For each flagged signal, check whether it moved before revenue in prior turns. Count true positives over last 6 inflection points.
4. Experiment (1–2 weeks): Convert top 2 signals into early-warning KPIs and run one rapid experiment (price adjustment or ad reallocation) tied to the signal.
5. Review (weekly): Monitor the KPIs and compare actual revenue vs. AI-forecast confidence; adjust actions.

Copy-paste AI prompt (use this exactly)

“I will paste a table with Date, Revenue, Search Volume, Ad Spend, Social Mentions, Inventory, Price. Please: 1) Identify the top 3 leading signals that historically move before Revenue changes and explain why; 2) Provide a one-paragraph next-quarter Revenue trend and Confidence (Low/Medium/High) with reasons; 3) Recommend 3 practical experiments or actions tied to those signals; 4) List any data quality issues that would reduce forecast reliability. Here is the table: [paste rows].”

Metrics to track

• Forecast accuracy (MAPE) for next-quarter revenue.
• Signal precision: % of flagged signals that preceded a revenue change.
• Experiment uplift: revenue or conversion delta from rapid tests.
• Time-to-detection: days from signal change to notification.

Common mistakes & fixes

• Mistake: Treating correlation as causation. Fix: Run a simple A/B or budget-shift experiment before scaling.
• Mistake: Tiny samples. Fix: Use weekly data or add proxies like search trends and supplier lead times.
• Mistake: Ignoring seasonality. Fix: Compare YoY same quarter and decompose seasonality first.

1-week action plan

• Day 1: Run the 5-minute AI check with 8–12 quarters.
• Days 2–3: Clean data, compute MoM/YoY, and run quick backtests on flagged signals.
• Days 4–7: Launch one rapid experiment tied to top signal and set two weekly early-warning KPIs to monitor.

Your move.

Hook: Yes — AI can build a media plan and allocate budgets, but it’s a tool for fast, testable decisions, not a black-box autopilot.

The problem: AI spits allocations quickly, but if you don’t define attribution, test size and success thresholds up front, you’ll misread performance and scale the wrong channels.

Why it matters: Wrong attribution + full-scale spend = wasted budget. A structured 10–20% test paired with consistent attribution tells you what to scale with confidence.

Experience-based lesson: I’ve seen teams double ROI by running disciplined small tests for 2–4 weeks, then feeding real results back into the model. The AI’s value is speed: it gives hypothesis-driven allocation and scenario analysis you can validate quickly.

What you’ll need

• Campaign goal (awareness, leads, sales)
• Total budget and planned test size (start 10–20%)
• Channels to test (search, social, display, email, video)
• Recent performance data if available (last 90 days CPM/CPC/CPA)
• Chosen attribution model up front (last-click, time-decay, or data-driven)
• Excel/Sheets and an AI chat (ChatGPT or similar)

Step-by-step

1. Pick attribution (if none, use last-click). Document it.
2. Run the AI prompt below, asking for a 10–20% test allocation and expected KPIs under that attribution assumption.
3. Export AI output to a sheet and confirm totals equal your test budget.
4. Set up campaigns with identical conversion definitions and UTM tracking across channels.
5. Run the test 2–4 weeks. Collect CPM, CPC, CPA, conversions per channel.
6. Feed actual results back to AI. Ask for a revised full-budget plan and scaling schedule.

Metrics to track (daily/weekly)

• CPM, CPC, CPA per channel
• Conversion count and conversion rate per channel
• Return on ad spend (ROAS) or cost per lead (CPL)
• Minimum sample: 20 conversions per channel to be actionable

Common mistakes & fixes

• Relying on AI numbers without testing — fix: run 10–20% test first.
• Switching attribution mid-test — fix: lock attribution before testing.
• No consistent tracking — fix: standardize UTMs and conversion events.

One robust copy-paste AI prompt (use as-is)

“I have a marketing budget of $[TOTAL_BUDGET] for [TIME_FRAME] with the goal of [GOAL]. Channels available: [LIST_CHANNELS]. Historical benchmarks (if any): CPM = [CPM], CPC = [CPC], CPA = [CPA]. Assume attribution = [ATTRIBUTION]. Please: 1) Propose a media plan allocating 10–20% of total for a 30-day test with percentages and dollar amounts; 2) Estimate expected KPIs per channel for that test; 3) Provide a short rationale for each allocation; 4) Give two alternative scenarios (conservative/aggressive) and a simple 30-day playbook and success thresholds. Output a table and a 5-point checklist.”

1-week action plan

1. Run the prompt and export results to a sheet.
2. Set up campaigns with your chosen attribution and identical tracking.
3. Allocate 10–20% budget and run for 14 days minimum.
4. Monitor CPA and conversions daily; optimize creative/bids after day 5.
5. At day 14–28, feed results to AI and request next-step allocation for remaining budget.

Your move.

Make your weekly review a predictable 15–20 minute habit that delivers three clear, prioritized actions.

Problem: weekly reviews slip because the setup is vague, inputs are scattered, and you don’t have a quick, repeatable output you trust.

Why it matters: a consistent weekly review reduces stress, prevents items falling through the cracks, and keeps your highest-value work progressing. You want a system that reliably converts week‑old clutter into this week’s priorities.

Short lesson from experience: standardize the input and standardize the output. One collection place + one calendar trigger + one AI prompt = predictable reviews. My clients cut review time from 45 to ~15 minutes in three weeks by enforcing that minimal structure.

1. What you’ll need
   • One collection spot (single notes app folder, an email label, or a “WeeklyInbox” document).
   • A recurring calendar event (same day, same time) labeled “Weekly Review” for 15–30 minutes.
   • An AI tool or assistant you can paste text into (built-in editor, chat box, or AI feature in your notes app).
2. Step-by-step setup
   1. Pick the trigger: set a weekly calendar slot you’ll protect — ideally after a low-interruption time (Friday 3pm or Monday 8:30am).
   2. Collect continuously: during the week, drop tasks/ideas/emails into your single collection spot with one-line context (what it is + desired outcome).
   3. Run the AI: at review time, paste the collection into the AI and ask for an executive summary, top blockers, and 3 prioritized actions for the week (prompt below).
   4. Convert into calendar tasks: assign each action to a specific day/time and add one measurable outcome (e.g., “Call X — secure decision on budget by Wed 11am”).
   5. Archive & reset: move processed items out of the collection so next week starts clean.

Copy–paste AI prompt (use as-is)

“You’re my weekly review assistant. Here is raw input (bulleted lines): [paste items]. Produce: 1) a one-line executive summary, 2) three prioritized actions for the coming week with a suggested day and estimated time to complete, 3) any blockers or follow-ups, and 4) one risk to watch. Keep each action outcome‑focused and assignable.”

Metrics to track

• Review completion rate (target: 4/4 weeks per month).
• Average time per review (target: 10–20 minutes after setup).
• Weekly action completion rate (target: 70% of the 3 actions done).
• Backlog size (items in collection; target: stable or decreasing).

Common mistakes & fixes

• Scatter: multiple collection spots → consolidate to one.
• Vague items: one-line entries only; include desired outcome.
• Overload: AI returns too much — limit prompt to “3 actions” and block items longer than one line.
• Not assigning dates: put actions directly into your calendar with time blocks.

1. One-week action plan (day-by-day)
   1. Today: create collection spot and set the recurring calendar event for your review.
   2. Through the week: capture every task/idea as a one-line entry in the collection.
   3. Day before review: clean obvious duplicates and short items you can do in 5 minutes.
   4. Review day: run the AI prompt, schedule the three actions, archive processed items.
   5. End of week: check metrics — did you complete the review and actions? Adjust timing if needed.

Your move.

Quick win: In under 5 minutes paste your single target keyword into the prompt below and ask for a concise SEO brief — you’ll get a usable outline to hand to a writer or use yourself.

Good point focusing on one target keyword — that clarity is exactly what makes an AI-generated brief useful instead of noisy.

The problem: Teams waste time on vague briefs or long keyword lists. That creates content that doesn’t match search intent and fails to rank.

Why this matters: A clear brief gets the right content written faster, improves CTR and rankings, and reduces rewrites.

What I do (short lesson): Start with the target keyword + one-step AI prompts to define intent, headings, meta, and conversion goals. That single input scales to a full brief.

1. What you’ll need: your target keyword, primary competitor URL (one), target audience (one sentence), desired CTA/conversion.
2. How to do it:
   1. Open your AI tool and paste this prompt (copy-paste below).
   2. Ask for a concise brief: title, meta description, H1–H3 outline, recommended word count, 5 semantic keywords, 5 FAQs, internal linking suggestions, one backlink target type, and content gaps versus the top result.
   3. Review and refine for tone and brand; ask for a “short version” (for a writer) and a “long version” (for SEO checklist).
3. What to expect: a 1–2 page brief that tells a writer what to write, how long, what headings to use, which questions to answer, and which keywords to include naturally.

Copy-paste AI prompt (use as-is)

“Create a concise SEO brief for the target keyword: [INSERT KEYWORD]. Include: 1) Best page title (<=60 chars) and meta description (<=155 chars) optimized for CTR; 2) Primary search intent; 3) H1 and H2/H3 outline with approximate word counts per section and a total suggested word count; 4) 5 semantic/LSI keywords to use; 5) 5 FAQs to include as on-page Q&A; 6) Suggested internal links (anchor + page type) and a backlink target idea; 7) Three clear optimization notes for readability, schema, and images. Keep it short and actionable.”

Metrics to track:

• Primary KPI: ranking position for the target keyword (track weekly)
• Engagement: organic CTR and average time on page
• Outcome: organic sessions and goal completions (lead form, sign-ups)
• Velocity: backlinks acquired and content updates completed

Common mistakes & fixes:

• Writing to keyword instead of intent — Fix: ensure the brief lists the primary intent and top user questions.
• Too-short brief — Fix: request concrete H2/H3s and word counts in the prompt.
• Keyword stuffing — Fix: use semantic keywords and focus on helpful answers, not density.

1-week action plan:

1. Day 1: Run the prompt and finalize the brief.
2. Day 2–3: Draft content using the brief; include FAQs and schema notes.
3. Day 4: On-page SEO check (meta, headings, internal links, images).
4. Day 5: Publish and submit to index; schedule outreach for 3 backlink prospects.
5. Day 6–7: Monitor rankings and CTR; make small tweaks to title/meta if CTR is low.

Your move.

Good build: Your two-bucket split with a single personalized line and timed SMS is the right low-lift test. Let’s add a segmentation shortcut, a clean holdout, and a measurement frame so you can prove uplift in days, not months.

Problem: Many teams “personalize” without structure, then can’t tell what drove attendance or follow-through.

Why it matters: Clear segments + a control group turn your webinar into a repeatable acquisition channel with predictable show rates and conversions.

Lesson from the trenches: Keep variables tight. One personalization line, two SMS pings, and a 10–20% no-SMS holdout will give you a clean read on uplift after one event and a stable benchmark after two.

Simple way to split registrants (use this if you’re not already segmenting)

• Add two required fields on registration: (1) “Which best describes you?” with 3–4 roles, (2) “Primary outcome you want from this session?” with 3 options. That’s enough for two segments.
• Auto-tag by first click in the 48-hour email (e.g., “Leaders’ angle” vs “Hands-on tips”). If form data is missing, use the click to infer the segment.
• Fallback rule: if no form tag and no click, default to “Leaders” copy to keep tone high-level and benefits-forward.

Insider upgrades that move numbers

1. Holdout design: Randomly exclude 10–20% of registrants from SMS. Same emails, no SMS. Measure show-rate delta versus the SMS group.
2. Calendar-first execution: Put the join link in the calendar “Location” field and one-line agenda in “Description.” Send an .ics refresh in the 48-hour email so busy people resurface the event.
3. Personal line placement: First sentence, first email paragraph. Keep it under 18 words. One change per segment only.
4. “What to bring” nudge: In the 2-hour email, ask for one question. It raises commitment and live chat volume.

Step-by-step (execute this sequence)

1. Prep: Add the two registration questions. Create two segments: “Leaders” and “Practitioners.” Create a third flag “No-SMS holdout.”
2. Assets: Write one attendee promise, one personal line per segment, a 60-second teaser, and a single CTA (e.g., book a 15-minute consult).
3. Confirmation: Send immediately with calendar file. Subject: benefit-led. Preview: date/time + “calendar attached.”
4. 48-hour email: First sentence = segment line. Include teaser video. Reattach calendar file (acts as a reminder).
5. 2-hour email: Join link + “What to bring: 1 question about [topic].” No fluff.
6. SMS: Two messages for non-holdout group: T–2h and T–15m. 140–160 characters, join link only.
7. Live: Run one poll or prompt one question early. Note responses per segment.
8. 24-hour follow-up: Recording + 2–3 bullet recap + single CTA. Same CTA for both segments.

Metrics to track (keep it tight)

• Show rate: attendees / registrants, overall and by segment.
• SMS uplift: show rate (SMS group) minus show rate (holdout).
• Live engagement: poll response rate or total questions per 100 attendees.
• Follow-through: CTA click rate in the 24-hour email and booked calls within 72 hours.

Common mistakes & fixes

• Mistake: Too many personalization changes. Fix: Change one line only.
• Mistake: SMS that read like ads. Fix: Direct, utility-only copy with the link.
• Mistake: Unclear time zones. Fix: Show city + time zone in emails and calendar.
• Mistake: Broken tokens. Fix: Test with a seed list across both segments and holdout.

Copy-paste AI prompt (build all copy + segments + holdout)

Prompt: “You are a senior lifecycle marketer. Create a concise webinar comms plan for a 60-minute session titled [TITLE] on [DATE/TIME, TIME ZONE]. Segments: (1) Leaders (focus: strategic ROI), (2) Practitioners (focus: step-by-step). Include: subject lines, preview text, and short bodies for: Confirmation, 48-hour email, 2-hour email, two SMS (T–2h and T–15m), and a 24-hour follow-up with one CTA to [CTA]. Personalize only the first sentence of the 48-hour email for each segment. Add a 10–20% ‘No-SMS holdout’ note in the plan. Output: (a) message copy, (b) a CSV-ready table with columns [send_time, channel, segment, subject, preheader, body, characters_or_words]. Keep emails under 100 words and SMS under 160 characters.”

One-week plan

1. Today: Add the two registration questions, set up segments and a 15% no-SMS holdout rule.
2. Tomorrow: Use the prompt above to generate all copy. Record a 60-second teaser. Load assets into your tools.
3. 48 hours before: Send the segmented 48-hour email with the calendar re-attach.
4. Day-of: Send the 2-hour email, the T–2h SMS, then the T–15m SMS. Host the session and run one poll.
5. Next day: Send the 24-hour follow-up with recording and single CTA. Start measuring.
6. End of week: Compare show rates and CTA clicks by segment and versus holdout. Decide whether SMS becomes standard and which segment line won.

Direct answer to your question: If you don’t already split into two groups, use the two-question form + first-click tagging above. It’s enough data to personalize one line and measure real differences without adding complexity.

Your move.

Quick win: copy your current sheet (even if it’s rough) and run the prompt below to auto-score every relationship and surface the top 5 targets to verify next. You’ll go from an unranked list to a prioritized hit list in under 5 minutes.

The problem — a flat list of names hides what matters: strength of relationship, recency, reciprocity, and who sits at the center of the ecosystem. That’s why maps look busy but don’t drive action.

Why it matters — partners and channels can compress sales cycles and open entire segments, but only if you focus on high-signal, high-centrality nodes. Weight the signals, or you’ll chase press noise.

Lesson from the field — treating partnerships like pipeline works: score the signals, find hubs, and trigger targeted outreach. Expect 30–50% of AI-suggested links to be weak; your edge is how fast you separate noise from moves you can bank.

What you’ll need

• Your spreadsheet with columns: Company, RelatedOrg, RelationshipType, EvidenceNote, EvidenceType, EvidenceDate.
• An AI chat tool and 30–60 minutes for the first pass; 10–15 minutes weekly to maintain.
• Verification sources you can access: news search, company sites, partner directories, job postings, product docs.

Copy-paste prompt — score and shortlist

“You are my ecosystem analyst. Input is CSV with columns Company, RelatedOrg, RelationshipType, EvidenceNote, EvidenceType, EvidenceDate (YYYY-MM-DD). For each row, apply this scoring rubric: +3 official partnership announcement; +2 product integration docs or partner directory listing; +2 marketplace/co-sell listing; +1 investor overlap; +1 shared customer case study; +1 executive quote from either company; +1 multiple independent sources (>=2 distinct types); -2 rumor/speculative language; -1 if the latest evidence is older than 18 months; -1 if evidence is only a single PR pickup with no other signals. Add fields: SignalCount, RecencyDays, Reciprocity (Yes/No if both companies mention each other), Score (0–10), Confidence (High >=7, Medium 4–6, Low <=3), NextAction (Verify, Outreach, Monitor), and a one-sentence Rationale. Return results sorted by Score within each Company, show only the top 10 per Company.”

Step-by-step

1. Normalize names (5–10 min): ensure each organization is consistent (e.g., “AWS” → “Amazon Web Services”). If needed, ask AI: “Unify these organization names into canonical forms and list common aliases; return CanonicalName, Aliases, Confidence.” Update your sheet.
2. Score and triage (5–10 min): run the scoring prompt on your CSV. Flag High (>=7) for immediate action, Medium to verify, Low to monitor.
3. Verify top hits (10–20 min): for each High, confirm two different signals (e.g., partner directory + press release). Update EvidenceNote, EvidenceType, and EvidenceDate. Downgrade anything that fails the two-signal rule.
4. Find hubs (5–10 min): compute simple centrality: count how many times each RelatedOrg appears across your companies. High count = hub. Prioritize hubs that also have High confidence. You can ask AI: “From these edges (Company–RelatedOrg), return top hubs by degree and flag any that connect 3+ of my seed companies.”
5. Decide the play (5–10 min): for each High-confidence hub, pick one: Co-sell (if marketplace/partner listing present), Integration (if API/docs present), Warm intro via investor overlap, or Competitive watch (if it’s a competitor hub).
6. Draft outreach (5–10 min): use AI to create three concrete angles based on your signals. Prompt: “For [TargetOrg], craft 3 concise outreach angles referencing [Signals] and [Shared Customers/Investors]. Include subject lines and a 2-sentence opener.” Paste your best into your CRM or email.
7. Set a refresh loop (5 min): add a Last Verified date and set a weekly 10–15 minute window to update High/Medium rows and re-run scoring.

What to expect

• A ranked, defensible map showing which relationships are real and recent — not just plausible.
• 3–5 outreach-ready targets within a week, plus a shortlist of hubs worth deeper alignment.
• Faster decisions: who to partner with, who to monitor, and where to allocate BD time.

Advanced prompt — entity resolution at scale

“Resolve and deduplicate these organization names. Output CanonicalName, Aliases, ParentCompany (if applicable), and Confidence. Treat variants (e.g., Google Cloud vs. GCP) as one entity. Flag subsidiaries separately if they operate distinct partner programs.”

Metrics to track (weekly dashboard)

• % High-confidence relationships (High / total) — target 30–50% after verification.
• Median RecencyDays for High — keep under 180 days.
• Hub concentration — % of edges accounted for by top 5 orgs; rising concentration indicates where leverage sits.
• Verification cycle time — median minutes from suggestion to verified/downgraded.
• Outreach yield — meetings booked / High-confidence targets attempted.
• False-positive rate — % downgraded after verification; push this under 25% over time.

Common mistakes and quick fixes

• Overweighting press. Fix: require a second, different signal (docs, directory, marketplace, job post) before High.
• Ignoring name variants. Fix: run entity resolution first; it boosts hit rates and reduces duplicates.
• No reciprocity check. Fix: prioritize when both companies acknowledge the relationship.
• Chasing large hubs only. Fix: also hunt bridges connecting 3+ of your seeds — they open new segments fast.
• Letting the map go stale. Fix: 10–15 minute weekly refresh with Last Verified dates.

1-week action plan

1. Day 1: Normalize names and run the scoring prompt. Save the top 10 per company.
2. Day 2: Verify the top 10; enforce the two-signal rule; update dates and confidence.
3. Day 3: Identify hubs and bridges; select 3 targets for immediate outreach.
4. Day 4: Draft and send 3 tailored outreach emails using signal-based angles.
5. Day 5: Build a one-page visual of High-confidence nodes; share with your team for alignment.
6. Day 6: Set a weekly 15-minute calendar block; note gaps to investigate next (e.g., missing suppliers or channels).
7. Day 7: Review metrics; adjust the scoring rubric if false positives are high.

Do this once and you’ll get clarity. Do it weekly and you’ll own the ecosystem narrative in your market. Your move.

Cut the busywork: use AI to decide what you keep, delegate, or refuse — and get tangible hours back this week.

Problem: Everything landing in your inbox looks important. You end up doing low-impact tasks that steal time from strategic work.

Why this matters: Every hour on low-value work is an hour not spent on revenue, relationships, or decisions that scale. Delegating right increases capacity, reduces mistakes, and lowers stress.

My short lesson: Use a fast, repeatable triage process (impact × effort) and let AI provide consistent recommendations: KEEP / DELEGATE / SAY NO. You stay the decider — AI gives unemotional, structured choices.

What you’ll need

• List of 20–40 tasks (email actions, meetings, admin, short projects)
• Estimated time per task (10–60 minute buckets)
• Conversational AI (chat tool) and a notes app or spreadsheet
• Simple SOP template: 2 lines (steps + acceptance criteria)

How to do it — step-by-step

1. Collect one week of tasks (30–60 minutes).
2. For each task add: time estimate, desired outcome, any constraints.
3. Paste tasks into the AI prompt below. Ask for: label (KEEP / DELEGATE / SAY NO), suggested role, 2-line delegation brief, acceptance criterion, tools/permissions.
4. Review AI output quickly. Accept or tweak top 10 delegatable items and assign owners with deadlines.
5. Create 2-line SOPs for repeated items and schedule a 15-minute weekly QA to review quality.

Copy-paste AI prompt (primary)

“You are my operations advisor. I will paste a numbered list of tasks with estimated time and desired outcome. For each task return: 1) one label: KEEP / DELEGATE / SAY NO, 2) suggested job title or role to assign to, 3) a 2-line delegation brief (steps + expected outcome), 4) one acceptance criterion, 5) any tools or permissions required. Use concise bullets. Tasks: [paste tasks here].”

Prompt variant (include risk)

“Same as above, but also include one risk/dependency per task and a 1-sentence mitigation.”

What to expect

• AI gives consistent triage in minutes. Use it as recommendation — not law.
• Expect 30–60% of routine tasks to be delegatable in month one.
• Initial time investment: 2–3 hours; weekly maintenance: 15–30 minutes.

Metrics to track

• % tasks delegated (target 30–60% first month)
• Hours freed per week
• Time-to-completion for delegated tasks
• Rate of rework / corrections
• Hours spent on strategic work (before vs after)

Mistakes & fixes

• Over-delegating without standards — Fix: attach a 2-line SOP and acceptance criterion.
• Vague task outcomes — Fix: add one clear expected outcome and deadline.
• Skipping review — Fix: 15-minute weekly QA; require assignee to log completion time and outcome.

7-day action plan

1. Day 1: Export tasks — 30–45 minutes.
2. Day 2: Run AI prompt and review labels — 45–60 minutes.
3. Day 3: Assign top 10 delegatable tasks with 2-line SOPs — 30 minutes.
4. Day 4: Communicate owners, deadlines, and acceptance criteria — 30 minutes.
5. Day 5–7: Monitor progress, collect hours saved, tweak prompts/SOPs.

Start small: one week of tasks, one review per week, measure hours freed, then scale.

Your move.

— Aaron