# CPO Rising Series: Pipedrive CPTO on The End of One-Size-Fits-All Software

Page: https://stenobird.com/podcast/product-talk-216178/cpo-rising-series-pipedrive-cpto-on-the-end-of-one-size-fits-all-software
Text version: https://stenobird.com/podcast/product-talk-216178/cpo-rising-series-pipedrive-cpto-on-the-end-of-one-size-fits-all-software.md
Podcast: [Product Talk](https://stenobird.com/podcast/product-talk-216178)
Published: 2026-07-08T11:55:00+00:00
Episode link: https://productsthatcount.libsyn.com/cpo-rising-series-pipedrive-cpto-on-the-end-of-one-size-fits-all-software
Audio file: https://traffic.libsyn.com/secure/productsthatcount/Joe_Futty_Podcast_Audio_Version.mp3?dest-id=302280
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/product-talk-216178/episodes/cpo-rising-series-pipedrive-cpto-on-the-end-of-one-size-fits-all-software
Duration seconds: 2052

## Resource

What if your SaaS product built itself to fit every user the moment they signed up? In this episode of the CPO Rising series hosted by Products That Count Resident CPO Renee Niemi, Pipedrive CPTO Joe Futty will be speaking on why customer expectations are about to shift more dramatically than at any point since mobile went mainstream and what that means for how product teams build, hire, and think about personalization. He also shares his three-bucket framework for navigating any new CPO role, and why the lines between product, engineering, and design are dissolving into something new.

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/product-talk-216178/episodes/cpo-rising-series-pipedrive-cpto-on-the-end-of-one-size-fits-all-software/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/product-talk-216178/cpo-rising-series-pipedrive-cpto-on-the-end-of-one-size-fits-all-software.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.