IMPACT report
IMPACT Full Audit: your result
This answer uses a made up example company. Change the details above and press Run to see your own result.
IMPACT Full Audit
Score how complete your positioning inputs are
For CMOs and founders. The decision: is our positioning working, and what do we fix first?
Give it what your product does, who you serve and the problem you solve, and you get an input completeness score out of 100, the areas to work on next, tagline options and a 30 day plan.
What you get
This sample is a made up example, built from the inputs behind Fill in an example. It shows part of one section of the answer.
Input detail checklist
Input completeness score: 77/100
This is not a positioning quality grade. It is a rule tally based on input length, supplied fields and matched words. Buyer evidence is needed to assess the positioning.
Inputs: Mostly complete: a few inputs could be more specific
What this score measures: how complete and specific your inputs are, not whether your positioning is right. Longer inputs and certain words (such as only, unique, unlike, employees, revenue and Series) raise it.
| Phase | Input rule score | Input detail | Priority |
|---|---|---|---|
| I: Identify Champions | 85/100 | Detailed | Low |
| M: Map Alternatives | 80/100 | Detailed | Low |
| P: Pinpoint Value | 70/100 | Detailed | Low |
| A: Anchor Market | 65/100 | Partial | Low |
Most detailed inputs
Craft (85/100)
Your current positioning is long and states a contrast.
See the full example answer or run it with your own details.
Result
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
What next? Work with Shashwat Try another tool See all 85 tools and skills
Example answer
Generated on 2 November 2026 from this branch, with the inputs behind Fill in an example. Your own inputs give a different result.
IMPACT report
Example: IMPACT Full Audit
Show the full result
IMPACT Positioning Audit
You gave thin detail on 0 of 6 areas (77 of 100). This counts how much you told us, not how good the positioning is.
Company Overview
Company: our product
Product: Cloud security monitoring for companies on AWS, Azure and Google Cloud
Target: CISOs at mid-size fintech and SaaS companies running on two or more clouds
Problem: Too many cloud alerts with no clear order to fix them
Differentiation: Exposure-based ranking of every misconfiguration, across AWS, Azure and Google Cloud
Competitors: your first competitor; your second competitor; periodic manual audits
Current Positioning: our product shows which cloud risks matter first, unlike long rule lists.
Customer Feedback: Critical exposures down 70% in one quarter; audit preparation down from 3 weeks to 4 days
Sector: read from your inputs as cybersecurity, cloud security. Business model: not stated. Tell us how you charge and the plan will adjust.
Billing dependent steps are conditional: trials, seats and recurring renewals require a subscription; a statement of work requires a services contract; site or link commitments require connectivity billing. Confirm the applicable choice before using those steps.
Input detail checklist
Input completeness score: 77/100
This is not a positioning quality grade. It is a rule tally based on input length, supplied fields and matched words. Buyer evidence is needed to assess the positioning.
Inputs: Mostly complete: a few inputs could be more specific
What this score measures: how complete and specific your inputs are, not whether your positioning is right. Longer inputs and certain words (such as only, unique, unlike, employees, revenue and Series) raise it.
| Phase | Input rule score | Input detail | Priority |
|---|---|---|---|
| I: Identify Champions | 85/100 | Detailed | Low |
| M: Map Alternatives | 80/100 | Detailed | Low |
| P: Pinpoint Value | 70/100 | Detailed | Low |
| A: Anchor Market | 65/100 | Partial | Low |
| C: Craft Message | 85/100 | Detailed | Low |
| T: Translate Execution | 75/100 | Detailed | Low |
Most detailed inputs
Craft (85/100)
Your current positioning is long and states a contrast.
Identify (85/100)
Your target customer ("CISOs at mid-size fintech and SaaS companies running on two or more clouds") is long and specific enough for a high score in this area.
Sentences read by score rules
- Differentiation: No affirmative differentiator was clear.
- Target specificity: No employee, sales or funding fact was clear.
- Positioning: our product shows which cloud risks matter first, unlike long rule lists
Areas to work on next
Anchor (65/100)
Input: Your target customer does not mention employees, revenue or a funding series. What makes a company ideal for you?
Action: Describe the target segment and why those buyers are a fit.
Possible input score change: +14 points to this area when you add the detail above (Example figure: replace with your own)
Pinpoint (70/100)
This input is already detailed: sharpen it next.
Action: State the difference and add a customer outcome you can support.
Possible input score change: +13 points to this area when you add the detail above (Example figure: replace with your own)
Proof You Already Have
Customer feedback you supplied, as proof points (use each only if it is real and you can show it):
- Critical exposures down 70% in one quarter
- audit preparation down from 3 weeks to 4 days
What a good proof point looks like in cybersecurity, cloud security: Exposures found and closed during the proof of value, with the time it took to fix them.
Your Current Positioning, Checked in Words
These checks read your words only. They are not part of the score above.
| Word check on your current positioning | Result |
|---|---|
| Names the buyer (shares a word with your target customer) | No |
| Names an alternative or says what it replaces | Yes |
| States a result (a number or a result word) | No |
| Uses generic words | No |
Recommended Positioning
Based on your inputs, here's a generated positioning statement:
For CISOs at mid-size fintech and SaaS companies running on two or more clouds
Problem described: "Too many cloud alerts with no clear order to fix them"
What our product is "Cloud security monitoring for companies on AWS, Azure and Google Cloud"
That delivers the result your customers describe: "Critical exposures down 70% in one quarter"
Unlike your first competitor, your second competitor or periodic manual audits
Difference described: "Exposure-based ranking of every misconfiguration, across AWS, Azure and Google Cloud". Use this claim only if you can support it.
Tagline Options
- [Only if true and provable: "Too many cloud alerts, solved."]
- "Exposure-based ranking of every misconfiguration,"
- "Built for CISOs"
- "Our product shows which cloud risks matter first"
30-Day Action Plan
Week 1: Foundation
- [ ] Confirm who champions and who signs: SOC or cloud security lead and CISO (this sector's usual committee)
- [ ] Document 5+ weaknesses of your first competitor, your second competitor and periodic manual audits from customer research
- [ ] Check each supplied result against its source, period and permission before using it as proof
Week 2: Positioning
- [ ] Finalize positioning statement (3 variations)
- [ ] Test with 5 existing customers
- [ ] Refine based on feedback
Week 3: Execution
- [ ] Update your hero section, sales deck and case study, in the words this sector's buyers use (attack surface, exposure, misconfiguration, alert fatigue, mean time to detect, mean time to respond)
- [ ] Prepare answers to this sector's usual objections: "We already have a tool for this"; "We have too many alerts already"; "Integration with our SIEM and ticketing"; "We need proof before budget"
- [ ] Be ready to discuss what buyers weigh in a business like yours: term, scope and price
Week 4: Validation
- [ ] A/B test messaging in outreach
- [ ] Track mean time to detect, mean time to respond, critical exposures open
- [ ] Gather qualitative feedback from prospects
Measures To Track
Fill the cells with your own numbers; this tool adds none.
| Measure | Baseline (yours) | Target (yours) |
|---|---|---|
| mean time to detect | ||
| mean time to respond | ||
| critical exposures open | ||
| alerts per analyst |
Investment: decide how many hours your team can give to positioning work; this tool does not estimate it.
Next actions
- Describe the target segment and why those buyers are a fit.
- State the difference and add a customer outcome you can support.
Suggested timings, lengths and counts: adjust them to your own.
If your team disagrees on the inputs above, run the B2B Positioning Workshop in your browser to compare four or five role views and save a baseline JSON file.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
How to read the answer
The Input completeness score out of 100 (and the six phase scores for Identify, Map, Pinpoint, Anchor, Craft, and Translate) is a rule tally based on input length, supplied fields, and matched words (such as only, unique, unlike, employees, revenue, and Series); it explicitly states that it is not a positioning quality grade. Below the checklist, the tool prints Most detailed inputs, Sentences read by score rules, Areas to work on next, Proof You Already Have, Your Current Positioning, Checked in Words (not part of the score), Recommended Positioning with Tagline Options, a week-by-week 30-Day Action Plan, and a blank Measures To Track table for your own baseline and target numbers.
What to do next
- Founder: Check Areas to work on next and Sentences read by score rules to add missing employee, revenue, or funding specifics to your target customer and sharpen your differentiator.
- CEO: Review Proof You Already Have and verify every supplied customer feedback figure against its source, measurement period, and written permission in Week 1 before using it publicly.
- CMO: Fix any "No" in Your Current Positioning, Checked in Words (make sure your positioning names the buyer, names the alternative it replaces, and states a measurable result without generic words), then test three variations with five existing customers in Week 2.
- CRO: Prepare the sales team in Week 3 with answers to your sector's usual objections and the commercial terms (term, scope and price) buyers weigh.
- Demand generation head: Run Week 4 validation by A/B testing the updated positioning in outreach and filling your own baselines and targets into the Measures To Track table.
Why come back
Re-run the audit after adding the missing segment specifics and verified customer outcomes to check your updated input completeness score and generate a sharper 30-day positioning plan. The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.
Who is the IMPACT Full Audit tool not ideal for?
- Anyone who cannot give the inputs listed above, because the answer is built only from them.
- Teams that need buyer research done for them: IMPACT structures your positioning as hypotheses, and you test them with buyers.
- Anyone who needs live competitor data: the tools do not look anything up. They work from what you type about your market and rivals, and anything they add themselves (such as common complaints in a category) is marked as something to check with buyers.
How do I use the IMPACT Full Audit tool with an AI assistant?
Add IMPACT once (see Use it in Claude, ChatGPT or Gemini), then ask in plain words. Here is a prompt built from the tested example:
My role is not stated. Ask me for my role first. Use the IMPACT Full Audit tool in IMPACT. company name: our product; product description: Cloud security monitoring for companies on AWS, Azure and Google Cloud; target customer: CISOs at mid-size fintech and SaaS companies running on two or more clouds; problem solved: Too many cloud alerts with no clear order to fix them; key differentiation: Exposure-based ranking of every misconfiguration, across AWS, Azure and Google Cloud; competitors: your first competitor, your second competitor, periodic manual audits; current positioning: our product shows which cloud risks matter first, unlike long rule lists; customer feedback: Critical exposures down 70% in one quarter; audit preparation down from 3 weeks to 4 days. If this tool is unavailable, ask me to open its web page; do not invent its output. In Gemini CLI or Antigravity, use the Helix GTM Suite skills package for related guidance, without claiming to run this connector.
How does the IMPACT Full Audit tool work?
You do not need to sign in. A web browser is enough, and the answer comes back in a second or two.
- Fill in the form above, or press Fill in an example.
- Press Run IMPACT Full Audit.
- Read the result on this page, then copy it and edit it before you use it.
It applies fixed rules in the IMPACT code to the inputs above and returns text. It does not call an AI model, does not look anything up, and does not store what you type. The web form and the AI assistant connector run the same tool code, so the same input gives the same answer in both.
For developers
MCP tool name: impact_full_audit. REST: POST https://impact.gtmhelix.com/api/tools/impact_full_audit with this JSON body (see How it works):
{
"input": {
"company_name": "our product",
"product_description": "Cloud security monitoring for companies on AWS, Azure and Google Cloud",
"target_customer": "CISOs at mid-size fintech and SaaS companies running on two or more clouds",
"problem_solved": "Too many cloud alerts with no clear order to fix them",
"key_differentiation": "Exposure-based ranking of every misconfiguration, across AWS, Azure and Google Cloud",
"competitors": [
"your first competitor",
"your second competitor",
"periodic manual audits"
],
"current_positioning": "our product shows which cloud risks matter first, unlike long rule lists.",
"customer_feedback": "Critical exposures down 70% in one quarter; audit preparation down from 3 weeks to 4 days"
}
}
Choose your app
Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh