In any case, after following up a number of times, they finally indicated they decided to build it internally instead. The funny part was through the demos they kept pushing for a source code review which seemed highly premature considering we had nothing signed at that point. I am glad we didn't hand over the source. Perhaps I am not in the most objective position, but their implementation is incredibly weak. There is a build at all costs culture which leads internal teams to build vs buy even when the PMs see the value of buy.

In any case, take this story as a cautionary note to pursue parallel paths even if things are very far along on one path and the stakeholders are highly enthusiastic.

We have been looking at other major partners and had some success with some; but, for Yahoo we hit a wall of first level routing which seems somewhat impenetrable. I am not wanting to attack the individuals that man the first level email routing since they are just doing their job, but they don't have a technical understanding of what is being presented--we got replies that completely misunderstood the message more than 4 times in a row--and are only able to route requests as secretary would. So we were finally directed to http://add.yahoo.com/fast/yahoo/technology/cgi_form which is no doubt a spam honeypot where submissions never reaches the appropriate team or get reviewed in any time sensitive manner.

So, I would like to ask if anyone has any contacts within Yahoo, ideally within Yahoo Finance on the development side. We actually did our usability testing with google / yahoo / x so we have some good data there.

Thanks for any help you can offer getting in contact with the right team lead at Yahoo!