Pinpoint Value
impact_pinpoint_valueGenerates believable value statements and ranked proof points from your target customer, key outcome, and unique capability, plus audience/channel versions and test questions.
Instructions
Helps you decide what you can claim that buyers will believe. You give your target customer, the main outcome they get and what you do that others do not, plus optional product name, category, customer results and business model. You get value statements in three versions, a value matrix for your own figures, proof points ranked from customer results to social proof, versions for different audiences and channels, and questions to test the value. 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_craft_message when you need outcome and proof statements before writing the core message.
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_outcome": "<key_outcome>",
"unique_capability": "<unique_capability>"
},
"name": "impact_pinpoint_value"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Product category. Format is text. For example, "manufacturing". | |
| key_outcome | Yes | The main result customers achieve. 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/company name. Format is text. For example, "invoice review service". | |
| business_model | No | How you sell (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Used to choose proof types; read from your inputs when not given. Format is text using one of the listed labels. For example, "saas". | |
| target_customer | Yes | Who you serve (e.g., "cloud security leads at mid-size fintech companies"). Format is text. | |
| customer_metrics | No | Any customer results data (e.g., "critical exposures down 70% in one quarter; audit preparation from 3 weeks to 4 days"). Format is text. | |
| unique_capability | Yes | What you do that others cannot/don't. Format is text. For example, "checks invoice exceptions before approval". |