<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Innovation PlayerCoach | Pinaki]]></title><description><![CDATA[Innovation PlayerCoach | Pinaki]]></description><link>https://pinaki.playercoach.me/perspectives</link><generator>RSS for Node</generator><lastBuildDate>Tue, 22 Sep 2026 18:26:27 GMT</lastBuildDate><atom:link href="https://pinaki.playercoach.me/blog-feed.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[Build? Buy? Borrow?]]></title><description><![CDATA[First thing first. If you're a CTIO or CDO, you've fought this battle before, usually over whether to license a platform or build the thing yourself on your own APIs. Fair fight. But this article isn't about that fight. There's another kind of Build vs. Buy conversation happening in the same boardrooms, and it has nothing to do with your tech stack. It's about who actually drives the innovation mandate that just landed on your desk. You've got board approval for it. A budget that sounds...]]></description><link>https://pinaki.playercoach.me/post/build-buy-borrow</link><guid isPermaLink="false">6ab29f06817ca0bac4e96fe1</guid><pubDate>Tue, 22 Sep 2026 18:05:54 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/83c564_0e085a21a5b04903b267455c0e3a9c0d~mv2.png/v1/fit/w_1000,h_691,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>Pinaki Bhowmick</dc:creator></item></channel></rss>