Launch Commander
launch_commanderCreates a phased launch plan with tasks, messaging, and success metrics from your product, launch type, target segments, and goals; accepts dates, quarters, or TBD.
Instructions
Helps you decide your launch plan: it 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 'TBD' or a quarter such as 'Q2 2027' for a flexible plan. Tasks and messaging follow the sector and business model read from your inputs, and each goal is filed under its own metric. 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 craft_gtm_analyzer when you need to create a launch plan from a product, segments and goals.
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": {
"product_feature": "<product_feature>",
"launch_type": "<launch_type>",
"target_segments": "<target_segments>",
"goals": "<goals>"
},
"name": "launch_commander"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goals | Yes | Launch success metrics (for example '40 qualified meetings, $300K pipeline, 5 reference customers'). Format is text. | |
| industry | No | Optional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what it read. Format is text using one of the listed labels. For example, "logistics_tech". | |
| team_size | No | Marketing/GTM team size affects task distribution. Format is text using one of the listed labels. For example, "solo". | |
| launch_date | No | Target launch date. Accepts: 'YYYY-MM-DD', 'Q1 2027', 'March 2027', or 'TBD' for planning mode. Format is text in YYYY-MM-DD form. For example, "2026-11-17". | |
| launch_type | Yes | Type of launch determines plan complexity. Format is text using one of the listed labels. For example, "major_release". | |
| your_sector | No | 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. Format is text using one of the listed labels. For example, "logistics_tech". | |
| budget_level | No | Budget affects recommended tactics. Format is text using one of the listed labels. For example, "bootstrap". | |
| business_model | No | 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. Format is text using one of the listed labels. For example, "saas". | |
| product_feature | Yes | What you're launching (product/feature name and description). Format is text. For example, "invoice review service". | |
| target_segments | Yes | Target customer segments (comma-separated). Format is text. For example, "manufacturers with 200 to 500 employees". | |
| available_channels | No | Optional: Marketing channels available (comma-separated). E.g., 'email, linkedin, blog, webinar, PR, paid_ads, community'. Format is text. |