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

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 the end of one-size-fits-all software, 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.

Join us for new conversations with leading product executives every week. Roll through the highlights of this week’s event below, then head on over to our Events page to see which product leaders will be joining us next week.

Show Notes:

1. Customer expectations are about to shift more dramatically than at any point since mobile went mainstream. The tools available to product teams have fundamentally changed, which means the problems customers had when those tools were more limited need to be revisited from scratch. Understanding the customer is not a box you check once — it is a continuous act that requires re-examining assumptions made under different constraints.
2. The most important product strategy question is: what can we do that others can’t or won’t? At a mature company with existing assets and accumulated data, the right strategic question is not what does the customer need in the abstract — it is what are we uniquely equipped to build, and where does our history and infrastructure give us an answer that competitors with different business models or ICPs simply cannot replicate.
3. The three buckets never change: customer, product, and team. Everything else is context. At a new company, in a new role, amid a new wave of technology — the framework stays the same. Who is the customer, what do they need, what should the product be, and who are the people building it? All three are shifting simultaneously right now, which makes holding onto the framework more important, not less.
4. SaaS onboarding is about to become a vibe-coding session that configures the product to your company in real time. The future of CRM — and enterprise software broadly — is not a product that everyone gets the same version of. It is a platform that, at the moment of signup, builds the version your specific company and workflow require. The configuration that today is manual, cumbersome, and set for the whole org will become conversational, individual, and instant.
5. Every user will have their own version of the product. An SDR, an account exec, a sales manager, a support rep — they all have different workflows within the same tool. The platform layer that Joe is building at Pipedrive exists to make that infinite personalization possible without sacrificing security, reliability, or role-based permissions. That is the CPTO job in 2026 and beyond.
6. Learning to prompt is the new learning to Google. When the internet launched, people needed to be taught how to search. Now they need to be taught how to describe what they want to an AI system precisely enough to get it. That skill will become universal the same way search did. The companies that get there first — building products designed for natural language configuration — will have a structural advantage.
7. The lines between product, engineering, and design are dissolving into builders. In a five-day design sprint, a Pipedrive designer hand-prompted a fully working prototype by Friday that was shown to customers and validated. No engineer required. That is not a one-off — it is a preview of how cross-functional teams will operate when every role has access to tools that were previously only available to technical specialists.
8. Specialization will fluctuate. Conviction about the customer problem will not. Qual researchers, quant researchers, UX designers, engineers, product managers — those roles were created for good reasons. Some of that specialization will evolve, blur, or consolidate as AI handles more of the execution layer. What will always remain is the need for someone in the room who genuinely understands what the customer is trying to do.
9. The biggest mistake new CPOs make is trying to turn the new company into the old one. Coming in from a high-performing organization with a strong playbook and immediately applying it wholesale is how you alienate the team and misread the situation. The first 90 days are for understanding why the product is the way it is, what the team’s actual strengths are, and what the fresh-eyes insights are that need validation before anyone acts on them.
10. Resource constraints exist everywhere — including the largest companies in the world. The idea that scale solves the prioritization problem is a myth Joe has tested across Microsoft, eBay, Booking, and multiple scale-ups. The discipline of understanding which customer problem deserves the scarce resource is universal. What changes at smaller companies is the speed at which you can make the decision to find out if you were right.
11. Data turns internal political arguments into engineering problems. When Joe wanted to convince sales managers to adopt a unified global product approach, he did not argue the strategic case in a meeting. He built two versions of a sign-up flow, let the execs vote on which one they preferred, and then showed them the A/B test results. The version they would have chosen performed worse. Numbers replaced opinion. The conversation changed.
12. Building a single global product and then instrumenting it properly produces better outcomes than maintaining regional stovepipes. The parking marketplace at Joe’s first CPO role had separate products for the UK, Germany, the Netherlands, France, Italy, and the US — all run by regional GMs who believed their customers were unique. Collapsing that into one instrumented platform revealed universal patterns that the regional model had been hiding, and fixing them drove revenue.
13. If building gets compressed to near zero, the constraint becomes imagination. A prototype vetted by customers by Friday afternoon of a sprint week is already possible. If pressing a button could then make that production-ready, the bottleneck moves entirely to the question of what to build. More bets, more versions, maybe a platform with infinite versions — the implications for product team structure and cadence are enormous.
14. The CPTO role forces a product leader to reconnect with engineering instincts they may have set aside. Joe started as a developer and spent decades in product. Taking on technology alongside product at Pipedrive reactivated that part of his thinking. In a world where product and engineering are converging, leaders who can hold both perspectives simultaneously are better equipped to make the tradeoffs that determine what actually ships.
15. Notebook LM as an onboarding tool is underrated. Synthesizing large volumes of company documentation into an interactive knowledge base that you can prompt for summaries and infographics is one of the most practical applications of AI for an executive entering a new role. It compresses the information intake of the first 30 days in ways that reading alone cannot.
16. The access layer is expanding beyond the application. Wherever a salesperson is working — a document, a chat interface, Claude, Gemini, Perplexity — they should be able to ask what their most important deal is and get an answer. The CRM is no longer a destination you log into. It is a data layer that follows you into every tool in your workflow. Building for that reality is a fundamentally different product architecture.
17. Product-centric is a more useful frame than product-led. The term product-led carries political baggage — it implies product is winning a power struggle against sales or finance. Product-centric names a culture where decisions get made with the customer and the product as the reference point, without implying that any function is subordinate to any other. The word choice matters when you are trying to change a culture without creating enemies.
18. Founder-led companies can take risks that public companies structurally cannot. The quarterly reporting cycle forces public companies to optimize for predictability. A founder-led scale-up with one person to convince can make a bold bet in an afternoon. That asymmetry in decision speed is a genuine competitive advantage that product leaders at scale-ups should be using more aggressively and more deliberately.
19. The network of trusted ex-colleagues from across major companies is the CPO’s informal board. At the level where you cannot easily turn to peers inside the company, the people who know you from Microsoft, Meta, Amazon, Google — and who you can call for an under-the-radar conversation about best practices — are the thinking partners that fill the gap. Building that network over a career is not optional. It is infrastructure.
20. The future of software is not one product per company. It is one product per person. Every user, every workflow, every sales process is different. The platforms that win will be the ones that make that level of personalization not just possible but frictionless — configurable in plain language, adaptable over time, and still secure and reliable underneath. That is the product bet Joe is making at Pipedrive, and it is the direction the whole industry is heading.