Edge Copy setup link
Edge / Skills / B2B Homepage Positioning and Messaging
Positioning · expert method

B2B Homepage Positioning and Messaging

Choose evidence-based B2B software positioning and draft a homepage argument using Anthony Pierri's public method.

Based on Anthony Pierri's public method.

Not affiliated with or endorsed by Anthony Pierri. Each step cites the public work it comes from: 9 sources.
What changes with this skill

From broad platform to a familiar job

Anchors the homepage in the reachable champion's workflow and the method the product replaces.

Default AI draft
Maintenance inspection startupHomepage hero for facilities teams

Operations platform that boosts productivity

Transform your operations with our platform.

Learn more
Vague categoryOutcome onlyWorkflow hidden
With B2B Homepage Positioning and Messaging
Maintenance inspection startupHomepage hero for facilities teams

Inspection software for facilities teams that replaces paper checklists

Scheduled mobile checklists and a manager dashboard replace paper forms and spreadsheets for multi site inspections.

See inspection software
Familiar categoryChampion cueOld method named
1Gather the raw material2Pick champion and market state3Map old way against product4Generate positioning bets5Build the homepage argument

Illustration from the skill's worked example, not a recorded run.

What it does

When your agent should reach for this skill.

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. 12

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. 19

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.

The method

12 steps, restated from Anthony Pierri's public work. Numbers link to the sources.

1

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.

2

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.

3

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.

4

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.

5

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.

6

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.

7

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.

8

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.

9

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.

10

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.

11

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.

12

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.

Worked example

How the method plays out on one case.

Invented illustration from the skill package. Not a recorded run.

1: Replace paper inspections with a visible workflow

Brief and weak first draft

Imagine FieldLedger, software for facilities teams managing inspections across several buildings. In the scenario, the supplied demo shows scheduled mobile checklists, a dashboard of incomplete inspections, and assignment of flagged issues. The product does not manage spare parts, purchasing, or all maintenance work.

The first draft reads:

H1: Unlock the future of operational excellence.

Supporting line: An intelligent platform that empowers every team to maximize productivity and transform performance.

Value sections: Work smarter. Improve collaboration. Accelerate growth.

CTA: Discover more.

This draft offers no recognizable product or owned task. Its platform claim overstates scope, and its benefits contain no mechanism. 468

Evidence and audience decision

The invented input set contains:

  • E1: A demo showing recurring checklist scheduling, mobile submissions, and issue assignment.
  • E2: Notes from facilities managers describing paper forms, spreadsheet logs, and calls to chase missing inspections.
  • E3: Deal notes showing managers initiate evaluation while an operations director approves purchasing.

Choose the facilities manager as champion. Technicians are users; the director is the approver. The priority buyers already conduct inspections through paper and spreadsheets, so the segment is M2. Their need is a better way to complete existing work, not an explanation of why inspections matter. 58

Workflow map and prioritization

Scores below are illustrative discussion judgments using the package's 1 to 5 anchors.

| Activity and old limitation | Feature and capability | Direct benefit | Severity | Strength | Total | | --- | --- | --- | --- | --- | --- | | Prepare and distribute recurring paper forms | Recurring schedules assign the next mobile checklist | Avoid preparing each recurring form manually | 3 | 4 | 7 | | Reconcile paper forms with the spreadsheet | Submission dashboard shows completed and missing inspections by site | Identify missing submissions without reconciling paper stacks | 5 | 4 | 9 | | Call around to assign a flagged issue | Issue assignment sends the item to its responsible supervisor | Avoid manual reassignment calls | 4 | 4 | 8 | | Order replacement components | Unsupported | No claim | Not scored | Not scored | Not scored |

The higher priorities address specific failures with visible capabilities. The unsupported procurement step stays outside the promise. 89

Strategic options

| Bet | Sample anchor | Risk and decision | | --- | --- | --- | | Full facilities platform | Manage every aspect of your buildings | High scope risk: the product lacks broad maintenance and purchasing coverage | | Mobile checklist app for any team | Digital checklists for any recurring task | Moderate focus risk: broad users require different proof and acquisition motions | | Inspection software for facilities managers | Replace paper inspections across your facilities | Best-supported recommendation: aligns with the scenario's workflow, product, and reachable champion |

Three options suffice for this small illustrative brief; a full assignment should seek four to six genuinely viable alternatives when inputs support them. This recommendation favors fit rather than declaring one category route inherently safe. 13

Use an existing inspection-software category, but explain it through the paper workflow because these buyers have not adopted that type of solution. M2 describes the buyers, not a claim that the category was newly invented. 35

Improved result

H1: Inspection software that replaces paper checklists across your facilities.

Supporting line: Schedule mobile inspections, see which sites have submitted their forms, and assign flagged issues to the responsible supervisor.

Primary CTA: See the inspection workflow.

Problem section: Paper forms make missing inspections hard to spot. When checklists come back from several buildings, you have to compare them with a spreadsheet before you know which teams need follow-up.

Solution introduction: FieldLedger keeps scheduled checklists and submitted inspections in one manager view while technicians complete forms on mobile.

Value section 1: Find missing inspections without sorting paper forms. The submission dashboard shows completed and outstanding checklists by site.

Value section 2: Give flagged issues a clear owner. Assign an issue from its inspection record so the supervisor receives the item without a round of reassignment calls.

Value section 3: Keep recurring checklists ready for the next inspection. Schedule repeated assignments instead of preparing a new paper form each time.

Proof placement: Show the actual completion dashboard beside section 1 and an assignment walkthrough beside section 2. Customer outcome proof remains a gap in this illustration; no percentage or testimonial is invented.

Secondary path: Link technicians to a mobile walkthrough below the manager's primary argument.

Rules that made the difference

The familiar category establishes what is sold; the paper comparator matches M2. A reachable champion replaces the vague all-team audience. Capability mapping converts broad productivity language into explainable tasks. Product limits prevent the platform claim. Prioritization gives the most consequential workflow failure the first value section. 45689

The recommendation is provisional until managers confirm the terminology and importance of missing submissions. The desk review can assess clarity and internal consistency; it cannot claim customer validation.

1 more worked example in examples/worked-examples.md.

What's in the package

7 files, pinned at d5668a9. Open any file on GitHub.

Sources

The public work this skill is built from. Read Anthony Pierri's originals.

  1. FletchPMM, Homepage Positioning Sprintfletchpmm.com
  2. FletchPMM, About: The FletchPMM Origin Storyfletchpmm.com
  3. FletchPMM, There are only three positioning strategiesfletchpmm.com
  4. FletchPMM, How to write an H1fletchpmm.com
  5. FletchPMM, You're building your ICP wrongfletchpmm.com
  6. FletchPMM, The Pitfalls of Becoming a Platformfletchpmm.com
  7. FletchPMM, What everyone gets wrong about category creationfletchpmm.com
  8. EarlyNode, The 7-Step Framework For Writing Killer Homepage Messaging with Anthony Pierriearlynode.com
  9. Churn.fm, Crafting Your Homepage to Increase Conversions and Boost Customer Retentionchurn.fm
Pinned commitd5668a9
LicenseApache-2.0

The skill file also covers: Files in this skill. Read the full SKILL.md.

Edge wrote this skill from Anthony Pierri's public writing and talks listed above. It is not affiliated with or endorsed by Anthony Pierri. If something misrepresents the method, write to [email protected] and we will correct or remove it.

Use B2B Homepage Positioning and Messaging with Edge

One paste sets up Edge, then your agent can use this skill.

Paste into Claude Code, Codex or Cursor

Use the pierri-homepage-positioning skill on https://getedge.cc/skills/pierri-homepage-positioning/ with Edge for my unfinished task in this conversation. First check whether Edge MCP tools are usable here. If not, fetch https://getedge.cc/SKILL.md with curl, read it, explain the setup change and data flow, and ask before making it. Preserve this skill choice, my task, and existing permissions through any required restart. Ask only for missing inputs. If this skill is unavailable or unsuitable, tell me; do not install it separately without asking.

Or add the MCP yourself

claude mcp add edge -- npx -y @getedge/mcp

Then ask your agent: "use the pierri-homepage-positioning skill via Edge for <what I'm doing>"

Not on Claude Code? Codex, Cursor, Claude app

Install this skill only

Review the publisher package and ask before installing without Edge.

Install only the pierri-homepage-positioning skill from https://github.com/getedgehq/skills/tree/d5668a96f82cfdfa299daf98273895d5d5429da8/pierri-homepage-positioning, without connecting Edge. Review package files, source, and permissions first; ask before installation. Preserve my unfinished task and existing permissions.