IMO, there may be a chance that CLFD will be involved in Google's municipal fiber build in Kansas City and here are several reasons why:
1. Google recently hired Atlantic Engineering Group to oversee their fiber project. Atlantic has chosen CLFD for many projects in the past including quite a few prominent municipal FTTH projects such as CDE Lightband, Opelika Power and Light and Salisbury. Atlantic's name popped up in a couple of CLFD PR's in the past. Atlantic obviously is comfortable with CLFD's cassette/panel technology.
2. Google released this document deatailing the issues encountered in building a state of the art FTTH network:
On page 12 they detail the problems of space constraints in the C/O and the inability of modern patch panels to terminate more than 6300 users per rack in home run fiber architectures (direct connection from C/O to premise). If you read CLFD's recent PR about their new MPO patch panels, this product seems to address exactly the C/O issues that Google was talking about in terms of a cost saving/high density solution:
My sense is the goal behind the whole Google fiber project was to push the envelope not only in terms of performance but also in terms of technological innovation and network efficiency. According to the CLFD PR this is the first product of its kind with this type of density in a 1RU footprint.
3. Sonic.Net, the San Francisco ISP who was hired by Google to oversee their initial FTTH trials at Stanford University subsequently chose CLFD for their own FTTH deployment in Sebastapol CA. which started last year. One would have to think that since Sonic's and Google's FTTH architectures are similar, if there was a better or more effecient fiber management platform being trialed at Google, Sonic would have used it.
Not only would being connected to Google's high profile FTTH build be a PR coup, that network will be delivering fiber to upwards of 500K homes. That would be a very significant project from a revenue standpoint for CLFD.