Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on Teams and technical leaders.
Teams and technical leaders
85 sources. These accounts focus on cost at production volume, model retirements, capacity, and which Google route teams buy through, from the accounts of teams and companies running Gemini in their products.
Individual builders
109 sources. These accounts focus on billing, free-tier use, multimodal work, and setup for developers building on the API on their own.
All practitioners
194 sources. This gives the broadest read, but combines side projects with production teams that can reach different conclusions.
194 sources from practitioners, by the context they work in. Filled rows count for this group.
- Individual builderDevelopers building on the platform on their own109 sources
Emphasizes Surprise bills and multimodal value
- Small product team2 to 10 engineers, or an unnamed startup team49 sources, counted here
Emphasizes Model retirements and price increases
- Product or platform team11 to 50 engineers, or a named company's team31 sources, counted here
Emphasizes Cost at volume and the Google Cloud route
- Technical leadershipLeaders setting model and platform choices across teams3 sources, counted here
Emphasizes Document extraction and coding quality, from CTOs and an AI research lead
- Organization-wideEnterprise or company-wide AI platform2 sources, counted here
Emphasizes Gateways that run Gemini beside other providers, and the cost of Gemini's yearly model retirements
What changes with scale. Individual builders focus on surprise bills, many from leaked or old API keys, and Flash's value for images, audio, and documents. Teams focus more on retirements, price increases between Flash generations and task speed. Company-wide gateways at DoorDash and Wealthsimple run Gemini beside other providers, and most team accounts use Google Cloud.
