EOS and structured execution
Deliberate operational frameworks scale company values and decision-making quality as headcount grows, preventing chaotic growth
Podcast with Matthew Dares
The Truth About B2B Data with Matthew Dares
February 3, 2026 · 40:02
Watch on YouTube
About This Episode
Matthew Dares of Torque, a B2B digital services agency focused on master data management (MDM) and ecommerce implementations, brings an often-overlooked perspective: how internal operational excellence translates into customer delivery excellence. Torque implemented the Entrepreneurial Operating System (EOS), a business operating framework from the book Traction, which transformed how the company makes decisions, executes projects, and maintains quality as it scales. Matthew explains that growing from a small team with shared values to a larger organization requires deliberate processes to codify and replicate the "magic" that made the company successful initially. EOS provides a framework for this through structured planning (quarterly "rocks" inspired by Stephen Covey's Seven Habits), weekly scorecards, and explicit accountability structures that prevent decision ownership from accumulating indefinitely with founders and early leaders.
The implementation lesson most relevant to clients: "slow is smooth, and smooth is fast." Teams often plan ambitious quarterly initiatives (rocks) without realistic time-bound execution plans, leading to constant renegotiation and failure. Torque learned to right-size quarterly commitments, execute methodically, and accept that real change happens incrementally over quarters and years, not in single sprints. This operating discipline directly influences how Torque serves B2B clients—the company deliberately specializes in Pimcore (a flexible master data management platform) and Shopware (an enterprise B2B ecommerce platform built on similar tech stack) rather than sprawling across multiple platforms. This specialization allows deep platform expertise and consistent best practices.
Matthew clarifies the distinction between MDM and PIM: PIM focuses specifically on product information, while MDM (master data management) treats product data as one part of a broader golden record that might include customer data, location data, fleet data, and complex relationships. While PIM will evolve with AI, the need for structured, authoritative product data—a source of truth that feeds both commerce and agentic AI systems—remains critical. Matthew argues that skipping PIM/MDM in favor of pure AI is premature; instead, companies should use MCP (Model Context Protocol) servers to define how AI agents interact with structured product data, creating repeatable, grounded tools rather than hallucinating general-purpose LLMs.
Key Themes
Change management requires realistic timelines
Real organizational change happens slowly over quarters and years; quarterly goals should respect achievable scope
Platform specialization beats generalism
Deep expertise in fewer platforms delivers better outcomes than shallow capabilities across many
MDM provides foundation for AI
Structured master data acts as ground truth that enables agentic AI without hallucination risk; MDM and AI work together, not as alternatives
Notable Quotes
“The slow is smooth and smooth as fast approach to how you roll and implement projects, change within your organization." — Matthew Dares”
“We're seeing the PIMs are dead, long-lived PIM kind of mentality, but something has to be a source of truth somewhere." — Matthew Dares”
“I would bet on the PIM and custom e-commerce over not the PIM." — Matthew Dares”
Guest
Matthew Dares — Torque
Topics
Operations Eos Change Management Mdm Pim Implementation B2b Ecommerce Strategy
The B2B eCommerce Show
Real conversations with operators and leaders building digital commerce for B2B.