One AI toolkit forproduct marketing managers
Shipped tickets turned into release notes. Launch copy polished in the tool where you write it. Competitor pages captured as text, a timeline slide from a milestone list, and one local memory per launch from kickoff to announcement.
The launch is Tuesday,
and the release notes are still ticket titles
A launch is a translation job under deadline: engineering ships tickets, and someone has to turn them into release notes, an announcement, a launch brief, a deck slide, and an email, each in a different tool, each in the house voice. The usual answer is a browser chatbot and twenty rounds of copy-paste, with the ticket list in one tab and the draft in another, and none of it remembering the launch you are actually running.
Khint keeps the whole loop behind one shortcut, inside the tools you already use. Pull the shipping tickets from Jira into one Memory session per launch, run your saved AI Actions on any selected text in place, turn the ticket list into release notes grounded in what actually shipped, capture competitor pages as working text, and file the results to Confluence, Notion, Slack, and Gmail through explicit palette writes.
One launch,
kickoff to announcement
Every stage below is a shipped feature, not a roadmap slide.
- SessionOne Memory session per launchA launch runs for weeks and touches everything: tickets, positioning drafts, competitor notes, the announcement itself. Start a Memory session named after the launch and make it active. Every ticket you pull, every capture you take, and every draft you run through Khint lands in that session and is compacted into one launch context, kept in a local database on your machine. Two launches in flight never blur together, because only the active session rides along.
- PullThe shipped tickets, into the sessionThe launch story starts with what actually shipped. With Jira connected, Pull issue and Active sprint in the palette bring the release's tickets into the launch session. No exporting, no tab hopping: the raw material for the release notes now sits in the same compacted context your drafting actions read from.
- DraftTicket language → customer languageSelect the pulled ticket text, or your rough list of what's in the release, and run a release-notes Action: engineering phrasing becomes benefit-first copy in your format, grouped and ordered the way your changelog reads. Because the launch session rides along, the draft knows the whole release, not just the paragraph you selected. The full walkthrough lives on the release notes page.
- PolishMessaging tightened where you write itPositioning one-pagers, web copy, the announcement post: select the draft in whatever tool it lives in, hit the shortcut, and run your polish Action in place. The first-party Doc Polish starter pack ships ready-made actions for exactly this, and a translation Action turns the finished announcement into each launch language while keeping product names intact.
- WatchCompetitor pages → text you can work withPositioning means knowing what the other side claims. Extract text draws a region over a competitor's pricing page or feature grid and puts the on-screen text on your clipboard, ready for your battlecard. Capture & ask goes further: draw the region and ask questions about it in a chat, like what plan gates a feature or how their tiers differ from yours.
- DeckA launch timeline slide from plain textFor the go-to-market deck, select your milestone list in PowerPoint and run Transform to diagram: Khint classifies the text and renders a clean editable diagram, with a timeline layout that marks done and pending milestones on a date axis. Preview it, restyle it, and save it back as native PowerPoint shapes. macOS only, switched on from the MCP page.
- ShipThe announcement lands everywhere it needs toFrom the same palette: Create page files the launch brief into Confluence or Notion, a Slack post tells the launch channel, and Send email drafts the customer announcement in Gmail, with a preview behind a confirm before anything goes out. Every write is logged back into the launch session, so the session ends as a complete record of the launch.
Unannounced products need a tool
that doesn't archive them elsewhere
Until the announcement goes out, the launch is confidential by definition: unreleased features, dates, pricing moves, positioning against named competitors. Pasting that into a browser chatbot builds a searchable archive of your launch inside someone else's product. Khint keeps the surface small: an Action only ever sees the text you selected, plus the active launch session's compacted summary if you opted that Action in, and nothing else on your screen or disk. Launch sessions live in a local database on your machine and are never synced to a server. What reaches your team is what you deliberately file: the Confluence brief, the Slack post, the Gmail draft, each one an explicit action you trigger yourself, never a background sync.
The four pieces of the toolkit
Launch workflows, one page each
The parts of the loop, in depth: how each one works with real Khint features.
Common questions from product marketers
How does Khint know what engineering actually shipped?
You pull it. With Jira connected, the palette has Pull issue and Active sprint rows: pick the issues or the board and the ticket content lands as entries in your active Memory session. From then on, any Action you run with session context on, like a release-notes draft or an announcement outline, is grounded in the real tickets you pulled, not in what you remember shipping. The pulls need an active session, which is the point: the launch's facts accumulate in one place.
Can it keep my launch copy in our house tone?
The prompt is yours, so the tone is yours. Write an Action once, with the voice rules, banned words, and structure your team uses, and run it on any selected text behind one shortcut. If you don't want to write the prompt yourself, type a one-line description in the Action editor and press Generate, then refine it with Improve. The first-party Doc Polish starter pack is a ready-made starting point for tightening copy, and you can Share your pack so the whole team runs the same messaging prompts.
Our launch plans are confidential. What does the AI actually see?
Only what you act on: the text you selected, plus the compacted summary of your active launch session if you ticked that option on the Action. Khint does not read your other windows or files, and there is no background capture. Launch sessions live in a local database on your machine and are never synced to a server. When something does leave, a Confluence page, a Slack post, a Gmail draft, it is because you triggered that write yourself from the palette.
Is there a free plan?
Yes. The free tier includes 10 AI actions per day and 5 screen captures per day, no credit card. Paid plans start at €7/month: Pro at €29/month gives 100 AI actions a day, and every plan includes all the work integrations. Khint runs on macOS 13+ and Windows 10 22H2+.
Bring it to your next launch
Free with 10 AI actions and 5 captures per day. No credit card; it runs on your own machine, next to the tickets and the drafts you already have open.