MD FlowBlog
Real scenarios where an AI assistant produces something worth keeping — the prompt, the output, and where the file goes afterwards.
Have your AI write the proposal in sections, then send one PDF
You had a good call with a new client. They told you what's broken, what they want, when they want it, and roughly what they'll pay. You took notes fast: half sentences, a price list, a date with…
· 8 min read
End every AI chat with a handoff file
Some work doesn't fit in one chat. A price change, a move to a new supplier, a grant application, a product launch: it takes three or four sittings over a few weeks, and you do each of them with…
· 7 min read
Ask your AI to draw the process, not describe it
You're away for two weeks, and someone else is covering a job only you really know. Refunds, supplier orders, the monthly close, the release checklist: the process lives in your head, a few saved…
· 7 min read
Reading what Claude Code left behind
You ask Claude Code why something is broken. It reads a dozen files, follows the call path, checks the config, and gives you a good answer: five findings, file and line numbers, a fix in the right…
· 7 min read
A prompt that makes your AI write files, not replies
You finish a call and paste your rough notes into ChatGPT: turn this into something I'll keep. It does, and the result is good. Clear headings, the action items pulled out, the risks spotted.
· 6 min read
Where to keep what your AI writes
Two months ago you had a real question. Which of these two things should we use, which supplier should we sign, is this approach going to hold up. You gave an AI assistant the context, it did the…
· 7 min read
Have your AI write the email, not the answer
There is a topic you are working on and it has a folder. A client, a negotiation, a supplier, a project — whichever it is, the folder has the contract in it, the notes from the last call, the…
· 7 min read