Company Product Launch
/company-product-launchCheck any company domain for its most recent official product and feature launches, each with a name, a ship date and a one-line summary.
Overview
company-product-launch takes a company domain and returns that company's most recent official product and feature launches, each with a name, a date and a short summary of what shipped. It runs on the SyncGTM MCP `company_product_launch` tool at a flat 1 credit per domain, and the optional `details` parameter narrows the search to a theme or a time window. A recent launch is a timing signal: a company that just shipped has budget, an active roadmap and a reason to take the call.
What it does
- 1
Takes one company website domain per call, e.g. `stripe.com`. There is no company-name or LinkedIn-URL lookup and no multi-domain mode.
- 2
Returns each recent launch with a name, a date and a summary of what shipped.
- 3
`details` focuses the search on a theme or a window — "AI product launches", "launches in 2024", "security features". Max 2000 characters, and the main lever on response quality.
- 4
Covers official product and feature announcements only. It is not a general news feed, and it does not return funding rounds, hiring news or press mentions.
- 5
Returns no people, emails or phone numbers. Chain `find_people_within_company` (1.5 credits) and `find_work_email` (1 credit) to get contacts.
- 6
Costs 1 credit per lookup, flat — the same whether the company shipped ten features or nothing at all.
How to use it
- 1
Download the skill file — it saves as company-product-launch.zip.
- 2
In Claude, open Settings → Capabilities → Skills and upload the .zip (or unzip the company-product-launch/ folder into .claude/skills/ for Claude Code).
- 3
Connect the SyncGTM MCP server — browser sign-in, no API key — then paste in the domains you want checked, one per line.
- 4
Trigger it by typing /company-product-launch with a domain list, e.g. '/company-product-launch stripe.com, ramp.com, mercury.com'.
- 5
Tune the `details` parameter — it is the one setting worth changing. "launches in the last six months" or "AI product launches" cuts a large company's response down to the slice you can act on.
Use cases
Launch-triggered outreach
Open a cold email with the feature the account shipped last month instead of a generic congratulations. The launch name and ship date become the first line.
Competitor release tracking
Run competitor domains weekly and log what each one shipped, so battlecards and objection handling stay current instead of drifting a quarter behind.
QBR and renewal prep
Before a customer call, check what the account has shipped since the last conversation so the meeting opens on their roadmap, not your agenda.
Territory triage by timing
Sweep an account list and work the companies that shipped in the last 90 days first. Silence is a valid answer and de-prioritizes the rest.
GTM workflow examples
Launch-triggered outbound sequence
- 1Run `company_product_launch` on 25 target domains with `details` set to "launches in the last six months" (25 credits) and cut every domain that returns nothing.
- 2Call `linkedin_page_posts` (0.3 credits flat, `max_posts` 1–100) on each surviving company to pull their own announcement wording for the launch.
- 3Call `find_people_within_company` (1.5 credits flat per call) on those domains with `job_title: ["VP Product Marketing", "Head of Growth"]` to name the people who own the launch.
- 4Call `find_work_email` (1 credit) on each shortlisted profile's LinkedIn URL, then `verify_email` (0.3 credits) — find_work_email finds an address, it does not check that the address is deliverable.
- 5Write one opener per account: sentence one names the launch and its ship date, sentence two ties it to the gap your product fills.
Outcome: A send-ready list of roughly a dozen accounts, each with a named contact, a work email checked through verify_email, and a first line that quotes a real feature and the date it shipped.
Monday competitor release log
- 1Run `company_product_launch` on your 8 competitor domains with `details` set to "launches in the last 30 days" (8 credits).
- 2Call `linkedin_page_posts` (0.3 credits, `max_posts: 10`) on each competitor that shipped to capture the positioning language they used in the announcement.
- 3Call `b2b_ads_search` (0.5 credits) with `company_domain` on the same domains to see whether the launch is backed by paid spend or is a quiet release.
- 4Rewrite the affected battlecard rows with the new feature name, its ship date and the one-line counter your reps say on a live call.
Outcome: A battlecard updated every Monday listing each competitor feature shipped in the last 30 days, its date, and the counter-position written beside it.
Pre-call brief across the renewal book
- 1Run `company_product_launch` on the 20 accounts with a QBR or renewal in the next 60 days, `details` set to "launches in the last 6 months" (20 credits).
- 2Call `enrich_organization` (2 credits, domain only) on every account that shipped to see whether industry, size, funding and technologies moved alongside the roadmap.
- 3Call `newly_hired_executives` with `max_results: 5` on the same accounts — it takes `company` as a name or LinkedIn company URL, not a domain — to see whether a new leader arrived around the launch. It bills 0.5 credits per profile, so 5 profiles is 2.5 credits per account.
- 4Assemble one page per account: what they shipped and when, who joined, and the expansion motion that maps to it.
Outcome: A one-page pre-call brief per account that opens on the customer's own roadmap and names the expansion play tied to what they shipped.
Prompts
Paste any of these into Claude once the skill is installed and the SyncGTM MCP is connected.
What has stripe.com launched recently? Show each launch with its name, date and a one-line summary.Find AI product launches for databricks.com. Pass "AI product launches" as the details parameter.Check these 20 domains for recent launches. Pass "launches in the last six months" as details, stop after 20 domains, list only the companies that actually shipped, and report credits used at the end.Pull ramp.com launches from 2024 using details "launches in 2024", then run linkedin_page_posts with company_url "linkedin.com/company/ramp" and max_posts 10, and quote what they said about the biggest one.Run company_product_launch on my top 15 accounts, cap it at 15 domains, then write one cold-email opener per company naming the launch and its ship date. If a company has no launches, say so — do not summarize their homepage.Best practices
Set `details` on every call to a large company. A bare call on an enterprise domain returns everything it can find; "launches in 2024" or "security features" returns the slice you can act on. Max 2000 characters.
Pass a bare domain: `stripe.com`, not `https://www.stripe.com/pricing`. One domain per call — there is no multi-domain mode.
Add "if there are no launches, say so — do not summarize the homepage" to every batch prompt. An empty response is a valid result, and clients pad empty responses with blog posts and homepage copy dressed up as launches.
Always ask for dates. A launch with no date is not a timing signal and cannot be sequenced.
When you mainly want personalization copy rather than a timeline, use `linkedin_page_posts` at 0.3 credits instead — the company's own announcement writes a better opener than a summary.
Cap the batch and run `check_credits` (free) first. Credits equal domains, so a 200-account sweep costs 200 credits whether or not anyone shipped.