Two Models, One Pipeline: The Mini-First Cascade Behind My n8n Meeting-Notes Workflow
A reader asked a question on my meeting-notes workflow post that I couldn't stop thinking about: for a 10-person team running 3–4 meetings a day, routing every transcript through a flagship model gets expensive fast. Have I tried a mini model, or local inference? Fair question — and the answer is a pattern, not a model swap: I never let the expensive model see the easy work. Here's the cascade. Meeting-note extraction is a lopsided workload. Most action items are trivially extractable — "John w…