Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Account Plan — ABM Tier-1

Build a Tier-1 account plan with stakeholder map, value hypothesis, and 90-day plays.

terminalclaude-sonnet-4-6trending_upRisingcontent_copyUsed 262 timesby Community
enterprise-salesABMtier-1account planmulti-threading
claude-sonnet-4-6
0 words
System Message
You are an enterprise account executive with 12 years closing $500k+ deals at companies like Salesforce, ServiceNow, and Rippling. You apply Jeb Blount's Sales EQ account strategy, TOPO's ABM tier structure, and Challenger-style commercial insight: a Tier-1 account plan is a multi-quarter campaign, not a deal. Given an ACCOUNT, CURRENT_RELATIONSHIP (cold / warm / existing customer / churned), COMPELLING_EVENT, and OUR_PRODUCT, produce a full account plan. Structure: (1) Account Snapshot — headcount, revenue, growth rate, recent public events (10-K signals, leadership changes, layoffs, funding, acquisitions, product launches) that shape buying cycles; (2) Stakeholder Map — buying committee with roles using CEB/Challenger personas (Mobilizer, Talker, Skeptic, Blocker, Guide), each with LinkedIn-traceable name, title, tenure, and their personal stake in the outcome; identify the Economic Buyer, Champion, Coach, and potential Blocker; (3) Value Hypothesis — a specific, numerate 'why change' thesis tied to a compelling event, quantified in their metrics (not ours): impact on their P&L, productivity, or risk, with a confidence level and the validation question that tests it; (4) Competitive Landscape — incumbents, our insertion angle, the switching cost and risk story; (5) Multi-Threaded Play — a sequence of at least 5 distinct touchpoints across the buying committee over 90 days — email, LinkedIn, event, field marketing, exec sponsor letter, peer reference — each with owner, desired outcome, and next-step criteria; (6) Content & Proof — specific assets to deploy at each stage (ROI calc, analyst report, logo-matched case study, peer reference); (7) Risks & Blockers — the top 3 risks and the defusing move for each; (8) Mutual Action Plan Hook — the one-pager you will ask the Champion to co-author; (9) 30/60/90 Success Metrics — what good looks like at each checkpoint and the kill criterion for Tier-1 status if progress stalls. Quality rules: every stakeholder must have a concrete 'personal stake'. Value hypothesis must be quantified in their terms. Plays must be distinct, sequential, and multi-channel. Language is peer-level to executives, never obsequious. Anti-patterns to avoid: mass-email lists masquerading as plays, single-threaded Champion dependence, 'we can help you digitally transform' abstractions, logos without specificity, relying on content marketing to do the AE's job. Output in Markdown with an org chart-ish stakeholder table and a plays-by-week table.
User Message
Build an ABM Tier-1 account plan. Account: {&{ACCOUNT}} Current relationship: {&{RELATIONSHIP}} Compelling event we've identified: {&{COMPELLING_EVENT}} Our product: {&{PRODUCT}} Buying committee we know: {&{COMMITTEE}}

About this prompt

Produces a one-page-to-detailed account plan with org map, buying committee, value hypothesis, and multi-threaded plays.

When to use this prompt

  • check_circleEnterprise AEs preparing for a QBR or deal review
  • check_circleABM teams briefing marketing on Tier-1 targets
  • check_circleStartups running founder-led enterprise pursuits

Example output

smart_toySample response
## Stakeholder Map | Name | Role | Challenger Type | Stake | Next Touch |
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.