One AI toolkit forimplementation consultants
Config workshop notes to filed decisions. The client's scoping document read where it sits. One work session per rollout, so Tuesday's client does not answer Thursday's client's question. All of it behind one shortcut.
Three rollouts at once,
and each wants all of you
A delivery week is not one project. Monday is a config workshop where twelve decisions are made out loud and none of them are written down. Tuesday is a 40-page scoping document the client sent as a PDF. Wednesday is a UAT defect demoed on a legacy screen you cannot select text from. Khint puts the AI where that material already is: on the selection you highlight, on the document you point it at, on the region you drag over their screen, and it keeps each rollout in its own work session.
Describe it in the idea bar
Type what you want in plain language. Khint builds a plan out of your own agents and your connected tools, shows it to you, and runs nothing until you confirm.
Say it out loud
Tap your voice key, speak, tap again. The text lands at your cursor in any app, cleaned up in the same pass. An agent or a workflow can listen on its own key.
Point at your screen
Draw a region over anything on screen, even an image or a video call. Khint reads the text into your clipboard, or opens a chat you can keep asking questions in.
The three ways a run actually starts on a delivery day: type the ask, speak it after a workshop, or frame a region of the client's screen.
Two ways to write up a config workshop
The workshop produced the same twelve decisions either way. What differs is how much of the client's context you retype before anything gets written.
Every prompt reopens with the briefing
A chat tab knows nothing about this client, so the phase, the entities and the scope get restated before every single ask, and they drift a little each time.
- Decisions made out loud in a workshop live in your notepad until someone asks for them in writing, usually a week later.
- The client's scoping document is a PDF or a Word file, so working on it means copying paragraphs out and pasting the answer back by hand.
- The legacy screen in the UAT call holds the exact error string, and a screenshot in a folder is not searchable or quotable.
- Switching client at 11am means re-establishing the whole context, in your head and in the model's.
Khint, on the rollout you have open
One session per client holds the workshop notes, the drafts and the tickets you filed, compacted into a running context later runs can read.
- Select notes anywhere and press ⌘⇧K. The written up version lands back in place, in the app you were already in.
- Point an agentat the client's file instead of a selection: Word, Excel, PowerPoint, PDF and OpenDocument are read locally on your machine.
- Capture turns the region you framed on the legacy screen into text you can quote in the defect, no retyping.
- Nothing is filed that you have not read: every integration write opens its picker and asks before it runs.
FiledThe four pieces a
delivery consultant presses
Not a product tour. These are the four pages behind a delivery week, in the order a rollout meets them, and each one is a shipped feature rather than a roadmap slide.
Memory
One session per rollout. Thursday's cutover plan starts from what Monday's workshop decided, and the session file never leaves your machine.
Documents
The client's scoping doc, config workbook or signed spec becomes the input. Word files can also come back edited, with their styles and layout intact.
Capture
The legacy screen, the error dialog, the config table nobody will export. Drag a box over it and the text is yours to paste and quote.
Integrations
Jira, Confluence, Linear, Notion, Slack and Gmail, with your own credentials in your OS keychain and a picker before every write.
What changes in a delivery week
Three things, and none of them is another tab to keep open next to the client's tracker.
- StopsRe-briefing the model on every clientThe active session carries the phase, the scope and the decisions already locked in, so an agent opens knowing which rollout you are on rather than being told again.
- LandsThe workshop decision, in the client's trackerA workflow turns the raw notes into a written decision and files it in Jira, Confluence or Notion, and the step hands back the key or the URL it created.
- Gets backThe hour after every workshopThe write-up happens while the room's wording is still fresh, which is also when it is worth the most to a client who will sign off on it.
Common questions from implementation and delivery consultants
What does an implementation consultant actually do with Khint?
Four things, all from one shortcut. Select rough workshop notes anywhere (your notepad, a Teams chat, the client's ticket) and run a saved agent on them in place, so they come back as written config decisions in your firm's format. Point an agent at a client file instead of a selection, so a scoping document or a config workbook is the input. Capture a region of a legacy screen to text when the client demos a defect. Then let a workflow file the result in the client's Jira, Confluence, Linear or Notion, with a picker before the write.
Can it work on the client's scoping document without me copying it out?
Yes. An agent can take a file as its input: Word, Excel, PowerPoint, PDF, OpenDocument, RTF and EPUB are read on your machine, and an image or a scanned page goes through Capture instead. Long files are summarised into a compact digest first, so a 40-page spec does not have to be pasted anywhere. A Word, PowerPoint or Excel file can also come back as the same file edited, with styles, layout and images untouched and your original left where it is, so a marked-up client spec stays a client spec.
How do I keep one client's context out of another's?
Each rollout gets its own Memory session, for example 'Meridian Bank phase 2'. Every agent you run inside it is logged there and compacted into a short running context, which agents can read only if you check the box on that agent. Switch the active session and the context switches with it, so the client you have open is the only one an agent sees. Sessions live in a local SQLite database on your Mac or PC and are never synced to Khint's servers. Claude Desktop or Codex can read the same live session over the bundled MCP server if you want them to.
Does it write into the client's Jira or Confluence?
Yes, with credentials you provide: an API token for Jira, Confluence, Linear, Notion and Slack, or a Google sign-in for Gmail, all kept in your OS keychain rather than on a server. Writes are deliberate by design. The palette opens the picker (project, issue type, space, page, channel) before the model call, so cancelling costs nothing, and a workflow's integration step returns the issue key or the page URL it created. You can pause an integration without deleting its credentials when you rotate off an account.
The client is under NDA. What leaves my machine?
Only the text you act on. An agent sees what you selected or the document text you pointed it at, plus the compacted session summary if you opted that agent in. The file itself is never uploaded, and Khint keeps no copy of it. A per-agent redaction switch replaces email addresses, phone numbers, national ID numbers and IBANs with placeholders before the request leaves. If your firm has its own provider account, you can run the billable actions on your own API key instead.
Write up your next config workshop with it
Free with 300 credits a month, about 10 AI actions a day. No credit card. Connect the client's Jira or Confluence when you are ready: it takes an API token, not an admin.