Route text and image work deliberately.
The right model for one task may be wrong for the next. Make the exceptions visible.
What changed
DeepSeek’s August 13 update announced V4-Pro general availability with adjustable reasoning and Responses compatibility. Its August 21 release introduced V4-Flash-Vision-Exp for mixed text and image inputs. The vision branch is experimental; ordinary V4-Pro and V4-Flash are not vision models. Compatibility also has limits, so integration needs testing.
Where businesses stumble
A team may send all incoming work down one route and discover that scanned forms, images and text need different handling. Treating experimental capability as an established service can transfer uncertainty to staff and customers.
The CBA response
C: classify incoming work and map normal and exception paths. B: assemble representative text and image examples with accepted answers and source records. A: route only supported tasks to the appropriate model, validate the result and retain human review for uncertain or unsupported cases. Train staff to recognize and escalate exceptions.
One practical takeaway
Run a limited test on one document or request type. Compare accepted results, review time and missed exceptions. Keep the experimental vision path isolated until evidence supports broader use.
Right-sized for small technical & midsize
A small technical firm can start with a manually reviewed pilot. Midsize teams need a shared routing owner and support process. Neither should assume a model change removes validation work.
Sources and editorial context
Business implications are SFG editorial analysis. Provider examples are context, not endorsements or proof of results.