Google debuts Engineering Support for cloud services, charging a flat fee based on response time; plans start at $100/user per month for 4-8 hour response time
Alex Konrad / Forbes :
Context & Ripple Effects
In March 2017 Google turned its own engineers into a billable product: Engineering Support for cloud services, sold as a flat per-seat subscription where the price buys a response-time guarantee — $100/user per month gets a 4-8 hour turnaround. It is an early move to monetize human expertise, not just infrastructure, on Google Cloud.
The pattern held and escalated: later that year Google moved to per-second billing on compute, sharpening how usage itself is priced, and by January 2020 it had layered a $12.5K-per-month Premium Support plan on top with 15-minute response for mission-critical incidents. The 2017 launch is the base tier of what became a full support-pricing ladder.
First-order effects
- Enterprise Google Cloud customers now face a direct trade-off between seat cost and incident latency — teams that need sub-day answers must budget $100/user monthly or accept slower queues.
Second-order effects
- Once response time is a priced SKU, Google has an incentive to build higher-priced tiers above it, which is exactly what the 2020 Premium plan did — support becomes a segmented revenue line rather than a bundled cost.
Third-order effects
- If support keeps scaling as a subscription product, cloud competition shifts partly from raw compute pricing to guaranteed access to engineers, making human expertise a differentiated, tiered offering across major clouds.
The trend: Cloud vendors are converting engineering time into tiered, response-time-priced subscriptions that sit alongside usage-based compute billing.