CRAFT GTM: 8 go to market strategy tools by Helix GTM Consulting
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Takes your product and the competitors you name, and returns one battle card per competitor built from your strengths, weaknesses, competitor details, objections, wins and losses. Each competitor detail goes to the competitor it names, each objection gets its own answer, and strengths and gaps taken from wins and losses are your own words.
Competitor names, comma-separated. You get one battle card for each competitor named
Your product name and brief description
Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read
Why customers chose you over competitors: used as your strengths when none are given
Optional: 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.
Why you lost deals to competitors: used as your gaps when none are given
Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it
Optional: what you do better, comma-separated. Taken from your wins, in your own words, if not provided
Optional: where competitors beat you, comma-separated. Taken from your losses, in your own words, if not provided
Sales objections you hear (comma-separated). E.g., 'too expensive, missing X feature, competitor has better Y'
Optional: Any known details about competitors, one per line or separated by semicolons. E.g., 'Competitor A is cheaper; Competitor B targets enterprise'. Each detail goes to the competitor it names
Takes your product and the competitors you name, and returns one battle card per competitor built from your strengths, weaknesses, competitor details, objections, wins and losses. Each competitor detail goes to the competitor it names, each objection gets its own answer, and strengths and gaps taken from wins and losses are your own words.
| Argument | Type | Description |
|---|---|---|
| industry | string | Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read |
| competitors* | string | Competitor names, comma-separated. You get one battle card for each competitor named |
| recent_wins | string | Why customers chose you over competitors: used as your strengths when none are given |
| your_sector | string | Optional: 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. |
| your_product* | string | Your product name and brief description |
| recent_losses | string | Why you lost deals to competitors: used as your gaps when none are given |
| business_model | string | Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it |
| your_strengths | string | Optional: what you do better, comma-separated. Taken from your wins, in your own words, if not provided |
| your_weaknesses | string | Optional: where competitors beat you, comma-separated. Taken from your losses, in your own words, if not provided |
| common_objections | string | Sales objections you hear (comma-separated). E.g., 'too expensive, missing X feature, competitor has better Y' |
| competitor_details | string | Optional: Any known details about competitors, one per line or separated by semicolons. E.g., 'Competitor A is cheaper; Competitor B targets enterprise'. Each detail goes to the competitor it names |
{
"type": "object",
"required": [
"your_product",
"competitors"
],
"properties": {
"industry": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read"
},
"competitors": {
"type": "string",
"description": "Competitor names, comma-separated. You get one battle card for each competitor named"
},
"recent_wins": {
"type": "string",
"description": "Why customers chose you over competitors: used as your strengths when none are given"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: 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."
},
"your_product": {
"type": "string",
"description": "Your product name and brief description"
},
"recent_losses": {
"type": "string",
"description": "Why you lost deals to competitors: used as your gaps when none are given"
},
"business_model": {
"enum": [
"saas",
"services",
"connectivity",
"transactions",
"marketplace",
"hardware_software",
"investment"
],
"type": "string",
"description": "Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it"
},
"your_strengths": {
"type": "string",
"description": "Optional: what you do better, comma-separated. Taken from your wins, in your own words, if not provided"
},
"your_weaknesses": {
"type": "string",
"description": "Optional: where competitors beat you, comma-separated. Taken from your losses, in your own words, if not provided"
},
"common_objections": {
"type": "string",
"description": "Sales objections you hear (comma-separated). E.g., 'too expensive, missing X feature, competitor has better Y'"
},
"competitor_details": {
"type": "string",
"description": "Optional: Any known details about competitors, one per line or separated by semicolons. E.g., 'Competitor A is cheaper; Competitor B targets enterprise'. Each detail goes to the competitor it names"
}
}
}Takes the text of a GTM document or plan and returns an analysis against the CRAFT framework, with a score for each dimension. Each dimension is scored only on what the plan contains (Timeline counts real dates, durations and quarters), the tool shows the plan's own line for each, names only the elements that are missing and suggests sections to add.
| Argument | Type | Description |
|---|---|---|
| industry | string | Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read |
| your_sector | string | Optional: 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. |
| document_type* | string | Type of document (shown in the analysis) |
| desired_outcome | string | Optional: What action should this document drive |
| document_content* | string | The GTM document or plan to analyze. Paste the full text: the tool reads it and scores it against the framework |
| intended_audience | string | Optional: Who will read/approve this document |
Takes your company, industry, customer base and data sensitivity, and returns crisis playbooks with a response team and notification steps for each crisis. Name the crises you know of to get those playbooks. If you leave them out, the tool uses a default set of common crises for your sector (not ranked by likelihood). Each compliance item you list is used in the notification steps.
| Argument | Type | Description |
|---|---|---|
| company* | string | Company name |
| industry* | string | Industry affects which crises to prioritize |
| your_sector | string | Optional: 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. |
| company_size | string | Affects response team structure |
| customer_base* | string | Customer type affects communication approach |
| business_model | string | Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it |
Takes the interview type, the product context and the person you are interviewing, and returns an interview guide that fits the interview type, the sector (chosen, or read from your inputs) and the product complexity. Questions use the sector's own language, your hypotheses are kept whole, and synthesis templates are included.
| Argument | Type | Description |
|---|---|---|
| industry | string | Industry affects terminology and context. Leave it out and the sector is read from your other inputs |
| your_sector | string | Optional: 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. |
| business_model | string | Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it |
| interview_type* | string | Type of interview determines question focus |
| key_hypotheses | string | Optional: Hypotheses to validate during interview, one per line or separated by semicolons |
| target_persona* | string |
Takes what you are launching, the launch type, your target segments and your goals, and returns a phased launch plan with tasks, a messaging table and success metrics. Give a date for a dated timeline, or enter 'TBD' or a quarter such as 'Q2 2027' for a flexible plan. Tasks and the messaging table follow the sector and business model read from your inputs, and each goal is filed under its own metric.
| Argument | Type | Description |
|---|---|---|
| goals* | string | Launch success metrics (for example '40 qualified meetings, $300K pipeline, 5 reference customers') |
| industry | string | Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read |
| team_size | string | Marketing/GTM team size affects task distribution |
| launch_date | string | Target launch date. Accepts: 'YYYY-MM-DD', 'Q1 2027', 'March 2027', or 'TBD' for planning mode |
| launch_type* | string | Type of launch determines plan complexity |
| your_sector | string | Optional: 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. |
Takes your company, product, partner model, partner goal and deal size, and returns a partner program with tiers, example commission amounts and KPIs, with a different structure for resellers, referrals, integrations, agencies, affiliates and white label. Uses your stated goal, existing partners and deal size, and names the partner types that fit your sector's buying committee.
| Argument | Type | Description |
|---|---|---|
| company* | string | Your company name |
| product* | string | Product partners will sell/integrate |
| industry | string | Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read |
| your_sector | string | Optional: 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. |
| partner_goals* | string | Revenue/growth targets from partners (shown as the target of the first KPI row) |
| partner_model* | string | Partner type determines program structure |
Takes your product, target market and current metrics (MRR, ACV, churn, NPS, CAC, LTV, retention, activation and similar) and returns a product-market fit scorecard that scores each dimension against example benchmark ranges. Reads the business model from your inputs and leaves the activation score out for services, connectivity and investment businesses. Quotes your customer feedback and answers it.
| Argument | Type | Description |
|---|---|---|
| product* | string | Product name and brief description |
| your_sector | string | Optional: 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. |
| target_market* | string | Target market segment (for example enterprise SaaS, telecom or logistics tech) |
| business_model | string | Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it |
| time_in_market | string | How long the product has been in market (shown in the scorecard) |
| current_metrics* | string |
Takes your customer segment, business model and current churn rate, and returns a retention playbook with health signals, interventions and an email draft for each churn reason. If you do not know why customers leave, leave the churn reasons out and you get a churn discovery kit with a framework for finding out. Health signals and interventions follow the business model, each churn reason gets its own answer, and your current interventions and data signals are used.
| Argument | Type | Description |
|---|---|---|
| product | string | Optional: Your product or company name, used in the title and the email drafts |
| industry | string | Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read |
| your_sector | string | Optional: 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. |
| cs_team_size | string | CS team capacity affects intervention strategy |
| churn_reasons | string | Optional: known churn reasons, comma-separated. If you do not know them, leave this blank and you get a churn discovery kit with a framework for finding the reasons |
| business_model |
{
"type": "object",
"required": [
"document_content",
"document_type"
],
"properties": {
"industry": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: 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."
},
"document_type": {
"enum": [
"gtm_strategy",
"launch_plan",
"campaign_brief",
"quarterly_plan",
"project_proposal",
"marketing_plan"
],
"type": "string",
"description": "Type of document (shown in the analysis)"
},
"desired_outcome": {
"type": "string",
"description": "Optional: What action should this document drive"
},
"document_content": {
"type": "string",
"description": "The GTM document or plan to analyze. Paste the full text: the tool reads it and scores it against the framework"
},
"intended_audience": {
"type": "string",
"description": "Optional: Who will read/approve this document"
}
}
}| data_sensitivity* |
| string |
| Data sensitivity affects security protocols |
| potential_crises | string | Optional: crisis types to plan for, comma-separated. If not provided, the tool uses a default set of common crises for your sector (not ranked by likelihood). Options: data_breach, service_outage, sla_breach, regulatory_action, fraud_incident, ai_wrong_action, pr_incident, executive_departure, security_vulnerability, customer_data_exposure, product_safety |
| compliance_requirements | string | Optional: Relevant compliance, comma-separated (for example ISO 27001, SOC 2, GDPR). Each item is named in the notification steps |
{
"type": "object",
"required": [
"company",
"industry",
"customer_base",
"data_sensitivity"
],
"properties": {
"company": {
"type": "string",
"description": "Company name"
},
"industry": {
"enum": [
"fintech",
"saas",
"logistics_tech",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"ecommerce",
"enterprise",
"consumer",
"other"
],
"type": "string",
"description": "Industry affects which crises to prioritize"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: 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."
},
"company_size": {
"enum": [
"startup_under_50",
"scaleup_50_200",
"midsize_200_1000",
"enterprise_1000_plus"
],
"type": "string",
"description": "Affects response team structure"
},
"customer_base": {
"enum": [
"b2b_enterprise",
"b2b_smb",
"b2c_consumer",
"mixed"
],
"type": "string",
"description": "Customer type affects communication approach"
},
"business_model": {
"enum": [
"saas",
"services",
"connectivity",
"transactions",
"marketplace",
"hardware_software",
"investment"
],
"type": "string",
"description": "Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it"
},
"data_sensitivity": {
"enum": [
"high_pii_financial",
"medium_business_data",
"low_general"
],
"type": "string",
"description": "Data sensitivity affects security protocols"
},
"potential_crises": {
"type": "string",
"description": "Optional: crisis types to plan for, comma-separated. If not provided, the tool uses a default set of common crises for your sector (not ranked by likelihood). Options: data_breach, service_outage, sla_breach, regulatory_action, fraud_incident, ai_wrong_action, pr_incident, executive_departure, security_vulnerability, customer_data_exposure, product_safety"
},
"compliance_requirements": {
"type": "string",
"description": "Optional: Relevant compliance, comma-separated (for example ISO 27001, SOC 2, GDPR). Each item is named in the notification steps"
}
}
}| Who you're interviewing (role/title) |
| product_context* | string | Product/service being researched |
| product_complexity | string | Affects technical depth of questions |
{
"type": "object",
"required": [
"interview_type",
"product_context",
"target_persona"
],
"properties": {
"industry": {
"enum": [
"saas",
"fintech",
"logistics_tech",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"ecommerce",
"marketplace",
"enterprise_software",
"consumer",
"other"
],
"type": "string",
"description": "Industry affects terminology and context. Leave it out and the sector is read from your other inputs"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: 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."
},
"business_model": {
"enum": [
"saas",
"services",
"connectivity",
"transactions",
"marketplace",
"hardware_software",
"investment"
],
"type": "string",
"description": "Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it"
},
"interview_type": {
"enum": [
"discovery",
"validation",
"feedback",
"churn",
"win_loss",
"persona_research"
],
"type": "string",
"description": "Type of interview determines question focus"
},
"key_hypotheses": {
"type": "string",
"description": "Optional: Hypotheses to validate during interview, one per line or separated by semicolons"
},
"target_persona": {
"type": "string",
"description": "Who you're interviewing (role/title)"
},
"product_context": {
"type": "string",
"description": "Product/service being researched"
},
"product_complexity": {
"enum": [
"simple",
"moderate",
"complex",
"highly_technical"
],
"type": "string",
"description": "Affects technical depth of questions"
}
}
}| budget_level | string | Budget affects recommended tactics |
| business_model | string | Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it |
| product_feature* | string | What you're launching (product/feature name and description) |
| target_segments* | string | Target customer segments (comma-separated) |
| available_channels | string | Optional: Marketing channels available (comma-separated). E.g., 'email, linkedin, blog, webinar, PR, paid_ads, community' |
{
"type": "object",
"required": [
"product_feature",
"launch_type",
"target_segments",
"goals"
],
"properties": {
"goals": {
"type": "string",
"description": "Launch success metrics (for example '40 qualified meetings, $300K pipeline, 5 reference customers')"
},
"industry": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read"
},
"team_size": {
"enum": [
"solo",
"small_2_5",
"medium_6_15",
"large_15_plus"
],
"type": "string",
"description": "Marketing/GTM team size affects task distribution"
},
"launch_date": {
"type": "string",
"description": "Target launch date. Accepts: 'YYYY-MM-DD', 'Q1 2027', 'March 2027', or 'TBD' for planning mode"
},
"launch_type": {
"enum": [
"major_release",
"feature_launch",
"beta_launch",
"product_update",
"market_expansion"
],
"type": "string",
"description": "Type of launch determines plan complexity"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: 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."
},
"budget_level": {
"enum": [
"bootstrap",
"moderate",
"well_funded"
],
"type": "string",
"description": "Budget affects recommended tactics"
},
"business_model": {
"enum": [
"saas",
"services",
"connectivity",
"transactions",
"marketplace",
"hardware_software",
"investment"
],
"type": "string",
"description": "Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it"
},
"product_feature": {
"type": "string",
"description": "What you're launching (product/feature name and description)"
},
"target_segments": {
"type": "string",
"description": "Target customer segments (comma-separated)"
},
"available_channels": {
"type": "string",
"description": "Optional: Marketing channels available (comma-separated). E.g., 'email, linkedin, blog, webinar, PR, paid_ads, community'"
}
}
}| business_model | string | Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it |
| your_deal_size* | string | Average deal size as one amount (e.g., '$5000 ACV', '$5K' or '$500/month'; a range is refused). It scales the example commission amounts; the example rates are fixed |
| existing_partners | string | Optional: Current partner types/count, one per line or separated by semicolons (listed in the plan) |
| partner_support_capacity | string | How much partner support can you provide? |
{
"type": "object",
"required": [
"company",
"product",
"partner_model",
"partner_goals",
"your_deal_size"
],
"properties": {
"company": {
"type": "string",
"description": "Your company name"
},
"product": {
"type": "string",
"description": "Product partners will sell/integrate"
},
"industry": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: 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."
},
"partner_goals": {
"type": "string",
"description": "Revenue/growth targets from partners (shown as the target of the first KPI row)"
},
"partner_model": {
"enum": [
"reseller",
"referral",
"integration_tech",
"agency_si",
"affiliate",
"oem_white_label"
],
"type": "string",
"description": "Partner type determines program structure"
},
"business_model": {
"enum": [
"saas",
"services",
"connectivity",
"transactions",
"marketplace",
"hardware_software",
"investment"
],
"type": "string",
"description": "Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it"
},
"your_deal_size": {
"type": "string",
"description": "Average deal size as one amount (e.g., '$5000 ACV', '$5K' or '$500/month'; a range is refused). It scales the example commission amounts; the example rates are fixed"
},
"existing_partners": {
"type": "string",
"description": "Optional: Current partner types/count, one per line or separated by semicolons (listed in the plan)"
},
"partner_support_capacity": {
"enum": [
"minimal_self_serve",
"moderate",
"high_touch"
],
"type": "string",
"description": "How much partner support can you provide?"
}
}
}| Your current metrics, written as text (the tool reads the figures from it). Include any of: MRR, ARR, ACV, churn rate, NPS, CAC, LTV, retention rate, activation rate, DAU/MAU, trial conversion, revenue growth. Example: 'MRR: $50K, Churn: 3%, NPS: 45, CAC: $500, LTV: $3000, Retention: 92%'. A figure that no rule scores is listed as not scored |
| customer_feedback | string | Optional: Qualitative feedback themes, one per line or separated by semicolons (for example 'Customers like X; they struggle with Y'). Each theme is quoted and answered |
{
"type": "object",
"required": [
"product",
"target_market",
"current_metrics"
],
"properties": {
"product": {
"type": "string",
"description": "Product name and brief description"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: 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."
},
"target_market": {
"enum": [
"enterprise_saas",
"smb_saas",
"consumer",
"marketplace",
"fintech",
"logistics_tech",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Target market segment (for example enterprise SaaS, telecom or logistics tech)"
},
"business_model": {
"enum": [
"saas",
"services",
"connectivity",
"transactions",
"marketplace",
"hardware_software",
"investment"
],
"type": "string",
"description": "Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it"
},
"time_in_market": {
"enum": [
"pre_launch",
"0_6_months",
"6_12_months",
"1_2_years",
"2_plus_years"
],
"type": "string",
"description": "How long the product has been in market (shown in the scorecard)"
},
"current_metrics": {
"type": "string",
"description": "Your current metrics, written as text (the tool reads the figures from it). Include any of: MRR, ARR, ACV, churn rate, NPS, CAC, LTV, retention rate, activation rate, DAU/MAU, trial conversion, revenue growth. Example: 'MRR: $50K, Churn: 3%, NPS: 45, CAC: $500, LTV: $3000, Retention: 92%'. A figure that no rule scores is listed as not scored"
},
"customer_feedback": {
"type": "string",
"description": "Optional: Qualitative feedback themes, one per line or separated by semicolons (for example 'Customers like X; they struggle with Y'). Each theme is quoted and answered"
}
}
}| string |
| Business model affects health score weighting. enterprise_contract is read further from your text when it names services, connectivity or investment |
| customer_segment* | string | Customer segment to focus on |
| current_churn_rate* | string | Current churn rate (e.g., '5%' or '5% monthly') |
| current_interventions | string | Optional: What retention tactics you already do (listed and compared with the playbook) |
| available_data_signals | string | What you can track (comma-separated). E.g., 'login frequency, support tickets, SLA attainment, QBR attendance' |
{
"type": "object",
"required": [
"customer_segment",
"business_model",
"current_churn_rate"
],
"properties": {
"product": {
"type": "string",
"description": "Optional: Your product or company name, used in the title and the email drafts"
},
"industry": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read"
},
"your_sector": {
"enum": [
"logistics_tech",
"fintech",
"saas",
"vertical_saas",
"ai_native",
"ites",
"telecom",
"software",
"cybersecurity",
"other"
],
"type": "string",
"description": "Optional: 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."
},
"cs_team_size": {
"enum": [
"no_dedicated_cs",
"small_1_3",
"medium_4_10",
"large_10_plus"
],
"type": "string",
"description": "CS team capacity affects intervention strategy"
},
"churn_reasons": {
"type": "string",
"description": "Optional: known churn reasons, comma-separated. If you do not know them, leave this blank and you get a churn discovery kit with a framework for finding the reasons"
},
"business_model": {
"enum": [
"saas_subscription",
"usage_based",
"marketplace",
"transactional",
"freemium",
"enterprise_contract",
"services_contract",
"connectivity_contract",
"investment_mandate"
],
"type": "string",
"description": "Business model affects health score weighting. enterprise_contract is read further from your text when it names services, connectivity or investment"
},
"customer_segment": {
"type": "string",
"description": "Customer segment to focus on"
},
"current_churn_rate": {
"type": "string",
"description": "Current churn rate (e.g., '5%' or '5% monthly')"
},
"current_interventions": {
"type": "string",
"description": "Optional: What retention tactics you already do (listed and compared with the playbook)"
},
"available_data_signals": {
"type": "string",
"description": "What you can track (comma-separated). E.g., 'login frequency, support tickets, SLA attainment, QBR attendance'"
}
}
}