When Technical Products Struggle to Win, It's Rarely an Engineering Problem
I build systems and artifacts that turn a strong product into commercial traction.
I build systems and artifacts that turn a strong product into commercial traction.
Microsoft Ecosystem · Governance SaaS
Transportation · Regulated Industries
Enterprise IoT · Hardware+SaaS+Services
A new feature ships. The blog post goes up. Sales gets the new deck. And the pipeline doesn't change. The product is good, the launch was busy, and somehow the deals don't follow.
A buyer hears one thing from a sales rep, reads something different on the website, and gets a third version from their CS contact post-purchase. Internally, your teams aren't disagreeing. They just don't have the same source of truth.
Sales wants to know what's shipping next quarter. Marketing wants positioning input on a campaign. CS wants to know what to tell customers about the roadmap. All of it routes through product, and product is trying to build the actual product.
Your product is technically equal or better. Your pricing is fair. The deals still go the other way. Sales says "we lost on positioning" or "they out-messaged us," and nobody has a structured answer for what to change.
Most PMM engagements deliver decks, frameworks, and recommendations. I deliver artifacts your sales, marketing, customer, and product teams actually use to do their work.
Every artifact is built with a specific partner and for a specific consumer. The artifact delivers the value. The act of building it earns the cross-functional alignment that makes the value stick. Most engagements start with one artifact and expand from there. Where you start depends on where you're stuck.
What I push back on: requests for a quick positioning refresh, a deck for a sales kickoff, or a one-time messaging exercise. These rarely solve the problem they're brought in for, because the problem is almost never the deck. It's that the artifacts your teams use every day don't exist yet or don't align. I'd rather build one real artifact with you than ship five polished decks that get forgotten.
Built with PM. For sales, CS, demand gen, and leadership. The product roadmap as a communication artifact, not just a planning artifact. PM owns what's shipping and when. PMM owns who it's for, why it matters, and how the field talks about it. The two halves live in one document. Start here if your field is guessing at what's coming next, or if your product team is being pulled into every sales and marketing question about the roadmap.
Built with the founder, sales, and PM. For the whole company. The defining work of who the product is for, what the buying committee looks like (including the influencers who shape decisions without signing), and how buyers actually move from problem to purchase. Validated through win/loss as deals close. Start here if your team is misaligned on who you sell to, or if you're entering a new market. See the $1.5M Market Investment Secured result above.
Built with sales and leadership. For strategic decision-making. Not a battlecard exercise. The operating cadence for understanding where your market is moving, what your competitors are doing, and where your positioning needs to flex. Sales feeds it. Leadership consumes it. PMM runs it. Start here if your team is reacting to competitors instead of anticipating them.
Built with sales, customer marketing, demand gen, content, and CS. For those same teams. The single source of truth that captures the buyer, the value drivers in buyer language, the proof points, the competitive frame, pricing and packaging, and what the product is not. The document every customer-facing team uses to do their work, so the company sounds like one company. Start here if your launches aren't landing or your teams are using different language for the same product. See the 15 Deals in 60 Days result above.
Built with the exec sponsor, PM, sales, leadership, and the customer-facing teams. For the whole company. The synthesis artifact that captures what PMM means at your company, what it owns, what it influences, and how it works with everyone else. Written after the first four exist, not before, because you can't define a function you haven't yet shaped. This is the founding PMM build-out: all five artifacts, sequenced over three to six months. See the 25% Customer Retention Lift result above.
The artifacts. The relationships built around them. A team that knows how to use them, update them, and extend them. If your team is using the artifacts six months after the engagement ends, the engagement worked. If they're not, it didn't, regardless of what the kickoff deck said.
Typical engagements run six to twelve weeks per artifact, or three to six months for a full founding PMM build-out. If you're hiring a senior PMM rather than engaging one, the same artifacts are how I'd operate as a leader on your team.
Steven Chan, VP of Product, Transoft Solutions

Most companies I work with aren't struggling because their product is weak. They're building ambitious, technically strong solutions. The engineering is solid. The roadmap is thoughtful. The team is working hard. And yet growth feels harder than it should.
I've spent my career at the seams between product, marketing, and revenue. Four founding PMM mandates in B2B SaaS and services, plus a senior role at a hardware-plus-services-plus-software business. Across all of them, the same pattern: technical products that need someone who can translate complex capabilities into commercial traction, and who can build the artifacts that make the translation last after the launch ends.
What I've learned across those mandates is that PMM looks different at every company. The discipline is the same. The function it becomes is shaped by the product, the buyer, the team, and the stage. My job in the first 90 days isn't to bring a generic playbook. It's to figure out what PMM needs to be at your company, and build the artifacts that make it real.
I take on project-based and retainer engagements (typically three to six months) and selectively explore senior PMM leadership roles. If either describes you, the contact form below is the fastest way to start.
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.