Acme Metrics: Positioning Diagnosis and 6-Week Test Plan
I haven't seen your site copy, competitor pages, or funnel data, so the diagnosis below is a hypothesis built from your description. Week 1 is designed to confirm or kill it.
Diagnosis
This is a positioning problem, not a product or awareness problem. You match two triggers in the skill's decision tree: awareness is strong but conversion is weak, and your messaging sounds like three competitors. Buyers know who you are but can't tell why to pick you, so they stall or default to whichever vendor they already shortlisted.
Likely contributing causes:
- Commoditized claims. "Usage analytics for finance teams" probably leads with table-stakes language such as "insights," "visibility," "real-time" and "easy." If all four vendors say these, none of them differentiates.
- Category-level description instead of an outcome. You describe what the product is (analytics) rather than the decision it enables or the pain it removes.
- Possibly the wrong persona. Finance teams include the FP&A lead, the CFO, RevOps and the finance-systems owner. They care about different things, and one message for all of them lands with none.
- No claim you can defend. You need to find out whether you have a structural advantage, such as data model, integrations, billing-system depth, audit-readiness or pricing model. Without one, any claim is a feature that competitors can copy.
Step 1: Find the position (Week 1 work)
- Competitor audit. Collect headlines and subheads from your 3 direct competitors, plus 2–4 adjacent ones. Mark the claims they share. Those claims are off-limits as differentiators.
- Customer interviews. Talk to 8–10 of your best customers and 3–5 recent losses. Ask why they chose you, what they'd say if a peer asked what you do, and what they almost bought instead.
- Structural advantage check. Use the skill's defensibility hierarchy. A structural advantage beats category ownership, which beats a feature. A position that a competitor could copy in one sprint isn't worth testing.
Pick two candidate angles, not more. The skill warns against testing many at once. Draft the Layer 2 positioning statement for each: who, what problem, how you're different, and proof.
| Angle type | Illustrative example (replace with what your interviews support) |
|---|---|
| Outcome/persona | "Usage-to-revenue reconciliation for FP&A, so month-end close doesn't wait on data" |
| Structural | "Audit-ready usage data your auditors will accept" (only if the product truly supports it) |
Also check wording. The skill's key lesson is that one word can change deal progression ("autonomous" became "teammate"). Look for scary or vague words in your copy, such as "AI-powered," "automated," or "replaces manual work." Finance buyers tend to react to loss of control and audit risk, so "you stay in control" framing is worth testing.
6-Week Plan (Crawl → Walk, with Run as a decision gate)
The skill's methodology is Crawl (1–2 weeks), Walk (2–3 weeks), then Run. Run is the rebrand itself, so I've kept it outside these six weeks. Don't run the phases in parallel.
Weeks 1–2: Crawl (validate)
| Week | Actions |
|---|---|
| 1 | Competitor audit. 10–15 customer and loss interviews. Choose 2 angles (A, B) and write a positioning statement and headline/subhead for each. Pull baseline metrics for current messaging: homepage CTA click-through, outbound reply rate, demo-to-trial rate. |
| 2 | Launch homepage A/B/C: current vs. angle A vs. angle B. Launch two outbound sequences (about 100+ prospects per variant, same ICP, same sender profile). Run the "would you still recognize us?" check with 5–8 existing customers. |
Go/No-Go (end of week 2): At least one variant beats the incumbent by 20% or more on outbound reply rate. Existing customers don't say "that's not what you do." If results are tied or the test is too short, extend it a week or try a different angle. Don't force a winner.
Sample size caveat: 100 prospects per variant is small. A 20% relative lift on a low base reply rate (say 3% to 3.6%) is statistical noise. Either use larger sends or treat the result as directional and confirm it with qualitative reply content and booked meetings. Website CTR is also only moderate-strength evidence.
Weeks 3–5: Walk (align, with no public rebrand)
| Week | Actions |
|---|---|
| 3 | Rewrite homepage and key pages for the winning angle. Draft updated pitch deck, call script, and email templates. Add 2–3 use-case examples. |
| 4 | Split the sales team. Half use the new script and half use the old one, then compare demo-to-trial conversion. Train CS on the narrative so existing customers aren't confused. |
| 5 | Collect AE feedback ("is this easier to use?"). Segment who responds by persona and company size. Check that nothing in the docs contradicts the new story. |
Go/No-Go (end of week 5): Sales says the new messaging is easier to use. Engagement and CTR beat the incumbent. No notable customer confusion.
Week 6: Decision gate (Run readiness)
- Review pipeline volume, demo-to-trial, and early win-rate data by positioning angle.
- Decide: proceed to Run (dedicated landing pages per use case, full material update, announcement), iterate with a new angle, or keep current positioning and fix something else.
- Win rate and retention need a longer window than six weeks. Treat week 6 as a decision on leading indicators, and keep tracking win rate and CAC during Run.
Pitfalls to avoid
- Deciding by internal consensus. Your team isn't the buyer.
- Claiming you're "better" at what everyone already does.
- Positioning on a feature a competitor can ship in a quarter.
- Running one message for every finance persona.
- Waiting for the product to catch up. The skill says product should follow positioning, but don't claim anything you can't deliver today.
What I need from you
To turn this into something concrete, send me any of these:
- Your current homepage headline and subhead, plus the competitors' headlines.
- Current funnel numbers: CTR, reply rate, demo-to-trial.
- Who your best customers are (role, company size) and why they bought.
With those I can draft the two candidate positioning statements and the A/B copy.
Real run in an isolated folder with only this skill installed. Only the Skill and Read tools were enabled, so nothing was fetched from the web and no file was written. The example is fictional. The model answered from SKILL.md alone and said it had no real site or funnel data.
하는 일
약한 포지셔닝을 진단하고 안전하게 바꾸는 계획을 세우도록 모델을 돕습니다. 경쟁사 메시지 감사, 방어 가능성 평가(구조적 강점, 시장 지위, 제품 기능 중 무엇인지), 3계층 포지셔닝 구조(시장 맥락, 포지셔닝 문장, 서사), 헤드라인과 서브헤드라인 형식, 표현 테스트를 다룹니다. 단어 하나를 바꿔 기업 고객과의 계약 진행이 빨라진 사례도 들어 있습니다.
동작 방식
- 모델이 제품, 구매자, 현재 메시지를 확인합니다.
- 우리 표현이 경쟁사와 얼마나 비슷한지, 따라 하기 어려운 강점이 무엇인지 점검합니다.
- 'Crawl-Walk-Run' 단계적 적용을 제안합니다. A/B 테스트로 검증(1~2주), 제품과 영업 정렬(2~3주), 확장 순서이며 단계마다 진행 여부를 가르는 기준이 있습니다.
이런 때 좋습니다
다른 회사와 똑같이 들리는 메시지, 인지도는 높은데 전환이 약할 때, 리포지셔닝이나 신제품 출시.
지침만 담긴 패키지입니다. 스크립트가 없고 네트워크 접속, 파일 쓰기, 계정이 필요 없습니다. 예시와 기준값(예: 20% 개선을 진행 신호로 삼는 것)은 저자의 경험에서 나온 경험칙이며 보편적인 벤치마크가 아니므로, 자사 구매자 데이터로 검증하세요. 모델이 자사 제품용으로 쓴 표현은 공개하기 전에 직접 확인하세요.