One AI toolkit forsolutions engineers
Discovery call notes to a product request. The prospect's screen to text without retyping it. One work session per deal. All of it behind a single shortcut, in whatever app you are already in.
Your evidence lives on
somebody else's screen
A presales day is spent inside systems you do not own. A prospect shares a stack trace, an identity provider config, a licence table, and thirty seconds later the call has moved on. Then the follow-up starts: the product gap becomes a request for your engineers, the scoping becomes a page your account executive reads, the recap becomes a post in the deal channel. Khint keeps all three attached to the call they came from, so the write-up happens while you still remember the objection.
A real workflow: one set of notes, an agent that reformats them, then three tool writes dispatched together.
Two ways to write up a discovery call
The call gave you the same material either way. What differs is whether it survives the twenty minutes after the call ends.
Notes in one place, evidence in none
The screen share is the best record of the prospect's environment you will ever get, and it is the one thing you cannot take away with you.
- The exact error is on screen for half a minute. Screenshots pile up in a folder and the text inside them is never searchable.
- The follow-up is four write-ups of one conversation: the request for product, the scoping page, the channel recap, the email. Each one is retyped from the same notes.
- A chat tab knows nothing about this account, so every prompt reopens with the architecture, the objection and the stage the deal is at.
- Two weeks later the second call starts from whatever you can still remember, because nothing kept the first one.
Khint, on the call you just had
Drag a box over the shared screen and the text is yours. Write the notes up once, and one run puts them in every tool that needs them.
- Select any notes, anywhere, and press ⌘⇧K. The rewritten version lands back in place, in the app you were already in.
- Capture turns the region you framed on the shared screen into text you can paste, search and quote in the ticket.
- A Memory session named after the deal holds the captures and the drafts, so the second call's write-up already knows the first call's answer.
- Nothing is filed that you have not read: every integration write opens its picker and asks before it runs.
Jira request
Confluence pageThe four pieces a
presales engineer presses
Not a product tour. These are the four pages behind the loop above, in the order a call and its follow-up meet them, and each one is a shipped feature rather than a roadmap slide.
Capture
The prospect shares a stack trace, an SSO config, a licence table. Drag a box over it and the text is copyable, no retyping and no asking them to send it.
Memory
One session per deal. Thursday's scoping page starts from what Tuesday's call left behind, and the session file never leaves your machine.
Workflows
Write the call up once. Up to five steps, ending in as many as four tool writes dispatched together, each returning the link it created.
Integrations
Jira, Confluence, Linear, Notion, Slack and Gmail, with your own API token in your OS keychain and a picker before every write.
What changes in the hour after a call
Three things, and none of them is another browser tab to keep open.
- StopsRetyping what was on their screenThe version number, the error string and the quota table come out of the screen share as text, so the request you file quotes the environment instead of paraphrasing it.
- LandsThe follow-up, in every tool at onceOne workflow files the product request, publishes the scoping page and posts the recap, and each step hands back the key or the URL it created.
- Gets backThe twenty minutes after every callThe write-up stops being an evening task. It happens while the objection is still fresh, which is also when it is worth the most to the deal.
Common questions from presales and solutions engineers
What does a solutions engineer actually do with Khint?
Three things, all from one shortcut. Select rough call notes anywhere (your notepad, a Slack thread, an email) and run an agent on them in place, so they come back as a scoped request or a summary in your usual format. Capture any region of your screen to text, which is how the prospect's error message or config screen becomes quotable evidence. Then chain the two into a workflow that files the product gap in Jira or Linear, publishes the scoping page in Confluence or Notion, and posts the recap in the deal channel.
Can I capture what a prospect shares during a call?
You capture your own screen, and a shared window is on your screen like anything else. Nothing happens until you pick Capture from the palette and drag a box yourself: one trigger, one region, one image. On macOS the selection is done by the system's own screenshot UI, so Khint never asks for the Screen Recording permission. Only that region is sent to be read, and the text comes back on your clipboard. There is no recording, no meeting bot and no participant to notify.
How does Khint keep one deal separate from another?
Start a Memory session named after the account, for example 'Acme POC'. Every capture, draft and filed ticket lands in it and is compacted into a short running context, which later agents can read, so the scoping page you write on Thursday already knows what the architect said on Tuesday. Switch the active session and the context switches with it. Sessions live in a local SQLite database on your machine and are never synced to a server, and Claude Desktop or Codex can read the same live session over the bundled MCP server.
Can it help with an RFP or a security questionnaire?
Yes, from the document itself. An agent can take a file as its input rather than a selection: point it at the questionnaire in Word, Excel, PowerPoint or PDF and it drafts the answers as text you review before anything is sent. An agent can also give you the same file back edited, with styles, layout and images untouched and your original left in place. Nothing about the document is uploaded to Khint or kept after the run.
Is there a free plan, and does it include the integrations?
Yes to both. The free tier includes 300 credits a month, about 10 AI actions a day, no credit card, and every work integration is available on it: plans sell volume, not features. Paid plans start at €7/month, and Pro at €29/month gives 4,000 credits a month. Khint runs on macOS 13+ and Windows 10 22H2+.
Write up your next discovery call with it
Free with 300 credits a month, about 10 AI actions a day. No credit card. Connect Jira, Confluence or Slack when you are ready: it takes an API token, not an admin.