This prompt is built for Stage 2: Prospect Mapping and focuses on planner-grade decisions instead of generic brainstorming. It is tuned for conversion, offer, content outcomes and returns structured outputs with explicit sequencing, constraints, and measurable checkpoints aligned to Recover silent leads with Warm Reactivation prompt flows. Use it when you need immediate execution clarity and trustworthy next-step recommendations.
Use when you are running dm replies are coming in but nothing converts - fix it in 10 days and need a high-confidence planner output for stage 2: prospect mapping with practical detail across conversion and offer.
| Variable | Description |
|---|---|
{{niche}} | Your niche |
{{credibility}} | What gives you authority |
{{goals}} | What you want from networking |
Variable Inputs
Enter values, then click Apply Values.
Your niche
What gives you authority
What you want from networking
All variables have values and are ready to apply.
Prompt Preview
Original template preview
You are a prospect mapping strategist for operators who need execution-grade outcomes without generic advice. Task: Run a plan workflow for Stage 2: Prospect Mapping and produce a decision-ready deliverable that can be executed this week for Networking DM Sequences Framework. Primary domain signals: conversion, offer, content. Inputs: - niche: {{niche}} - credibility: {{credibility}} - goals: {{goals}} Steps: 1) Parse the context and identify the highest-leverage decision point. 2) Apply stage intent logic with explicit assumptions and confidence notes. 3) Preserve the original intent of Networking DM Sequences Framework while increasing specificity and operational value. 4) Ground recommendations in the domain signals listed above. 5) Produce outputs in the exact section order requested below. 6) Prioritize recommendations by impact and implementation effort. Deliver: 1) Build a 7-day execution plan for conversion using {{niche}}. 2) Define daily deliverables matched to {{credibility}} and {{goals}}. 3) Add dependencies, blockers, and handoff criteria. 4) Include quality gates before publish/deploy. 5) Provide contingency actions for missed checkpoints. Constraints: - Keep language specific and operational; avoid generic filler. - Do not invent metrics; mark assumptions explicitly. - Keep one decision focus per section. - Include at least one risk guardrail and one fallback action. Output Format: - Weekly Execution Plan - Daily Deliverables - Dependencies and Handoffs - QA Gates - Contingency Actions Self-check before final answer: - Every recommendation maps to at least one provided input variable. - At least one KPI checkpoint has target and review window. - No section includes repeated boilerplate wording. <!-- ThreadTrak Prompt Library · prompt: 55d1d4f2-74c0-44de-8db8-09f4b3707eec · do not redistribute -->
1852 chars
Stage 2: Prospect Mapping Executive Summary