Craft Message
impact_craft_messageTurns your target customer, key benefit, and differentiation into a positioning statement, message hierarchy, audience versions, objection handling, and testing ideas.
Instructions
Helps you decide what your core message is, and how to test it. You give your target customer, the key benefit and what sets you apart, plus optional product name, customer need, category, main competitor and business model. You get a positioning statement (full and one sentence), a message hierarchy from tagline to three supporting pillars, versions for different audiences, objection handling and ways to test the message. It writes from your own words, in whole sentences. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of impact_translate_execution when you need the core positioning statement and message hierarchy.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"target_customer": "<target_customer>",
"key_benefit": "<key_benefit>",
"differentiation": "<differentiation>"
},
"name": "impact_craft_message"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| competitor | No | Primary alternative/competitor. Format is text. For example, "the current manual review process". | |
| key_benefit | Yes | Primary benefit/reason to buy. Format is text. For example, "resolve invoice exceptions before month-end". | |
| your_sector | No | Your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech". | |
| product_name | No | Your product name. Format is text. For example, "invoice review service". | |
| customer_need | No | The need they have, written as an action (for example "lose days chasing low-risk cloud alerts"). Format is text. | |
| business_model | No | How you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used to choose the cost and proof lines; read from your inputs when not given. Format is text using one of the listed labels. For example, "saas". | |
| differentiation | Yes | Your unique differentiation. Format is text. For example, "checks invoice exceptions before approval". | |
| target_customer | Yes | Target customer description. Format is text. For example, "manufacturers with 200 to 500 employees". | |
| product_category | No | Your product category, written as a noun phrase (for example "cloud security monitoring platform"). Format is text. |