Worked example, fictional product
Briefly message teardown
This is a complete worked teardown for Briefly, a fictional reporting tool for small software agencies. It scores 82 on clarity, 58 on relevance, 64 on value and 31 on differentiation, so differentiation is the weakest layer and the three rewritten angles all attack it.
Message found on the page
The page says: The smarter way for agencies to keep clients in the loop.
It presents Briefly as an automated client reporting tool for software agencies. It connects project tools and creates weekly status updates.
Four message layers
- Clarity 82: the product category and core job are easy to understand
- Relevance 58: the page names agencies, but not the costly reporting problem they feel
- Value 64: time savings are implied, but the business result is not concrete
- Differentiation 31: the promise could describe several project reporting tools
Weakest layer: Differentiation, 31 out of 100
Smarter does not explain what Briefly does differently. The message hides the useful mechanism: it translates internal delivery activity into a client facing update. Naming that transformation gives buyers a reason to remember the product.
Three rewritten angles
- Pain first: Stop rebuilding the same client report every Friday. Briefly turns project data from Linear, GitHub and Slack into a client ready update your agency can send in minutes.
- Outcome first: Send a client ready project update in 10 minutes. Briefly gathers delivery signals from the tools your agency already uses and drafts the status report for you.
- Alternative contrast: Your project tracker is not a client communication tool. Briefly translates internal delivery data into the concise progress, risk and next step update clients actually need.