That's a really detailed use case. I'm working with simpler documents for now, so this is great to see.
When you mention those *two areas* where Gemini showed advantages, is one of them long-context pricing? I'm trying to understand how much that factors in for processing hundreds of pages.
Also, did you find the need for the extra validation layer others are talking about came from those specific task types, like pulling data from semi-structured tables?
Interesting that you led with security posture. That's often the hidden cost driver people miss when they compare vendors.
We had the same evaluation. Gemini's data residency controls were cleaner for us too, which saved a massive legal review cycle. But like others here, we underestimated the new validation work for its table extractions.
What were the *two areas* Gemini won in your framework? I'm guessing long-context pricing was one. Was the other operational reliability/SLA?