pierri-homepage-positioning
Choose evidence-based B2B software positioning and draft a homepage argument using Anthony Pierri's public method. Use for confusing messaging, competing audiences, repositioning, or homepage reviews.
- License 许可
- Apache-2.0
- 所属仓库
- getedgehq/skills
- 最近更新
- 2026-11-12
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- pierri-homepage-positioning
- description
- Choose evidence-based B2B software positioning and draft a homepage argument using Anthony Pierri's public method. Use for confusing messaging, competing audiences, repositioning, or homepage reviews.
02 资源文件 7
- 参考文档checklists/review-checklist.md6.0 KB
- 参考文档DERIVATION.json2.6 KB
- 参考文档examples/worked-examples.md11.0 KB
- 许可证LICENSE10.5 KB
- 参考文档references/method.md16.0 KB
- 参考文档references/sources.md3.6 KB
- 参考文档templates/output-template.md8.2 KB
03 SKILL.md 正文
B2B Homepage Positioning and Messaging
Based on Anthony Pierri's public method. Not affiliated with or endorsed by Anthony Pierri.
When to use
Use this skill when a B2B software team needs to choose its primary audience, explain what the product is, distinguish it from the current alternative, and express that strategy on a homepage. It supports a new page, repositioning, and a critique of existing messaging. Confusing copy can expose an unresolved positioning decision; changing adjectives cannot resolve competing audiences or an unclear product reference point. [S1] [S2]
The deliverable is a positioning and homepage brief: an evidence summary, ranked strategic options, a selected position, an internal alignment record, and a section-by-section wireframe with usable copy. For a review, preserve an established position when evidence supports it and focus the output on diagnosed problems and revisions. This adapts public guidance for agent use; it does not reproduce a paid engagement or promise conversion gains. [S1] [S9]
Read the relevant sections of the method as decisions arise. Keep methodology citations in working notes and rationale; customer evidence must come from the user's materials. These sources cannot substantiate claims about a new product. Mark missing inputs and provisional decisions visibly, and deliver a useful draft without disguising uncertainty as customer research.
Procedure
-
Set the assignment. Establish whether this is strategy development, a rewrite, or a review, and identify the intended visitor and decision owner. Open the output template, then read method section 1 for the intake boundaries.
-
Inventory evidence. Collect available website copy, demos, sales conversations, customer language, competitors, and team input. Separate observed facts, interpretations, and assumptions. Map actual product scope before drafting. Follow method section 1 and populate the template's evidence table.
-
Select the reachable champion. Identify who notices the workflow problem and can initiate a purchase. Check reach, product fit, sales motion, and adoption evidence rather than choosing the most senior signer by default. Use method section 2.
-
Classify the audience's market state. Choose M1, M2, or M3 from observed activity and solution familiarity, then add useful firmographics. Specify the matching starting, replacing, or switching argument. Do not equate audience state with category maturity. Use method section 3.
-
Map the current workflow. List the champion's tasks, current tools, and failure points. Mark unsupported steps. Connect each relevant problem to a capability, enabling feature, and direct benefit. Use method section 4.
-
Prioritize value. Score problem severity and product strength separately, justify each score, and elevate their strongest credible intersections. Treat scores as discussion aids. Read method section 4 and the worked examples for contrasting applications.
-
Develop distinct bets. Generate four to six viable options when evidence supports them; use fewer with an explanation when it does not. Vary meaningful strategic choices, record category route, and rank risk with downstream implications. Follow method section 5.
-
Choose and document a position. Recommend one bet, name excluded priorities, explain the tradeoff, and record what evidence would change it. Distinguish the recommendation from a stakeholder decision. Complete the alignment record using method section 5 and the template.
-
Write the hero. Anchor it in a familiar category plus differentiation, or an exact job plus improvement over the current way. Check whether a multi-product offer needs a lead product, shared job, or suite presentation. Use method section 6.
-
Build the page argument. Draft hero, current problem, solution introduction, prioritized value sections, relevant proof, and a suitable action. Show how the product works. Keep secondary audiences subordinate. Follow method section 6 and the template's wireframe fields.
-
Review and revise. Apply the review checklist. Test comprehension, workflow accuracy, evidence, and strategic consistency before polishing tone. If a failure changes the champion, comparator, or anchor, return to that decision and update strategy and copy together. Use method section 7.
-
Deliver with clear status. Return the completed brief, unresolved assumptions, proof gaps, and review results. Identify provisional copy and the next validation task. Consult method section 7 and the source register when explaining the method's limits.
Files in this skill
- SKILL.md: Entry point, scope, and the agent's decision loop.
- references/method.md: Detailed principles, decision rules, warnings, and edge cases.
- references/sources.md: Numbered register of fetched public sources and their contributions.
- examples/worked-examples.md: Invented before-and-after applications for workflow replacement and vendor switching.
- templates/output-template.md: Fill-in positioning brief and homepage wireframe with field guidance.
- checklists/review-checklist.md: Pass/fail review gates and practical failure fixes.
04 同仓库更多 Skills
zero-downtime-cloud-move
Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.
zayats-ceo-branding
Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.
yc-app-roast
YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks "what would a YC partner think", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
yc-app-review
YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press "Send my notes" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.
x-growth-playbook
X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says "analyse my X posts", "what works on my Twitter", "how do I grow on X", "what should I post next on X", "audit my X account", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.
workplan
Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.