There's not much data to go on, but in the KC area the schedule for suburban build-outs looks like it's being driven by politics as much as by demographic or infrastructural factors. (Of course, the initial choices of the KC and Austin metros themselves suggest that sort of decision-making.)
In KC, Google's first announced suburban hook-ups were a couple of tiny, affluent suburbs adjacent to KCK and KCMO, likely due to the ease of negotiating the terms of construction. It then announced availability for Olathe, an large exurb on the Kansas side, skipping over the even larger suburb of Overland Park, which is home to Sprint and some other tech firms. Olathe has Garmin, etc., but I don't think corporate tech headquarters are a consideration.
Google has also so far left out North Kansas City, a municipality that's completely surrounded by KCMO, perhaps because it has its own municipal ISP that provides FTTH. I imagine that has made negotiations difficult.
Skipping over OP in favor of Olathe was indeed politically, as well as practically, motivated. The fiber is being hung on existing poles, but Overland Park relies heavily on buried lines to quite a few areas. Additionally, Olathe's city council was very willing to accommodate Google--Overland Park moves more slowly and is likely less accommodating.
In KC, Google's first announced suburban hook-ups were a couple of tiny, affluent suburbs adjacent to KCK and KCMO, likely due to the ease of negotiating the terms of construction. It then announced availability for Olathe, an large exurb on the Kansas side, skipping over the even larger suburb of Overland Park, which is home to Sprint and some other tech firms. Olathe has Garmin, etc., but I don't think corporate tech headquarters are a consideration.
Google has also so far left out North Kansas City, a municipality that's completely surrounded by KCMO, perhaps because it has its own municipal ISP that provides FTTH. I imagine that has made negotiations difficult.