Winnie Chen

🚀 HubSpot is now the first CRM to launch a connector for Claude HubSpot's new Claude connector does something powerful: it grounds Claude's responses in real context from your CRM. No more generic responses. No more starting from scratch. Your marketing team can instantly ask: "Show me contacts who engaged with our last campaign but didn't convert" and get a visual breakdown ready for action. Your sales team can pull deal summaries by stage and priority—contextualized to your actual pipeline. But here's what makes this different: the insights don't live in isolation. You take them right back into HubSpot where the work happens. We built this connector because context is everything. When Claude can access your business context in real-time—your contacts, your deals, your actual pipeline—it becomes exponentially more useful. This is just the beginning. AI that knows your business —no matter how big or small—isn't just better AI, it's AI that actually moves the needle. If you want smarter answers from Claude, start with HubSpot. 🧡

2,042

131 Comments

The fastest-growing SaaS companies don’t start with messaging. They start with reality. Not personas. (Seems like a joke but no shortage of personas out there like "Digital-First Dave" and "Cost-Conscious Carla") The best companies go straight to the source: their target market. What’s actually happening in their target customers’ world? I’ve seen it play out across 200+ buyer research projects at Wynter. The companies that nail positioning and marketing? They ask sharper questions: → What slows you down in your workflow? → What’s the trigger that gets you searching for a solution? → What would actually make your job easier? They don’t assume. They investigate. The quality of your decisions comes from the quality of your information. And the results show up fast because now you’re speaking to real problems, in real language, with real stakes. It’s not just tighter messaging. It's marketing that finally lands. Stop guessing what matters to your buyers, ask them. It's the only way to know, really. Use tools like Wynter to get insights straight from the source. Run a target customer survey with Wynter to learn what your ICPs want https://wynter.com

103

48 Comments

Want ChatGPT to start giving you better product marketing advice? Feed it this definition of "Use Case" 👇🏻 There is no phrase that Robert Kaminski and I have argued about over the last three years MORE than "use case." I kid you not, we have spent hundreds (maybe thousands) of hours trying to nail this down. There's a lot at stake. The "use case" of a product is THE way that people understand it. And there's dozens of ways to get this wrong that send you down all sorts of bad paths leading to nonsense messaging. Here's our definitive definition (intentional alliteration to get it to stick in your brain). Upload this into your LLM and correct it when breaks these rules, and you'll be on a way better path towards stronger positioning and messaging!

413

115 Comments

Two weeks ago, I spoke with a RevOps leader who has hired 25 people in the last six months. She now leads a 40-person team. Her secret to scaling RevOps fast? Run it like a product + engineering org. This is how Mollie B., SVP of Operations at Engine (1,000+ people), built and scaled one of the most forward-thinking RevOps orgs I've seen. The best part? Mollie broke it all down on the latest episode of the RevOps Lab. Listen here: getweflow.com/revops-lab My top takeaways from this episode: 𝟭. 𝗨𝘀𝗲 𝗮 𝗽𝗼𝗱 𝗼𝗿𝗴 𝗱𝗲𝘀𝗶𝗴𝗻 Each GTM team at Engine gets a cross-functional pod (including sales ops, enablement, analysts, and systems). One team, one roadmap, one weekly sync. 𝟮. 𝗧𝗿𝗲𝗮𝘁 𝗥𝗲𝘃𝗢𝗽𝘀 𝗹𝗶𝗸𝗲 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 + 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 Asana boards and sprint cycles replace endless 1:1 side convos. Everyone sees priorities. Everyone knows the trade-offs. Salesforce becomes your internal product. Your team = dev team. 𝟯. 𝗛𝗶𝗿𝗲 𝗳𝗼𝗿 𝗮𝘁𝘁𝗶𝘁𝘂𝗱𝗲, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 Mollie looks for “how hard can it be?” people - those who are coachable, cross-functional, and eager to learn new tools. RevOps changes fast. Your people need to keep up. What else we cover:  • Centralized vs. decentralized RevOps orgs  • How to prevent systems chaos in pod models  • How to run RevOps like product/engineering  • Traits to look for in RevOps hires Listen wherever you get your podcasts.

170

22 Comments

Positioning mistakes cost more than product mistakes. Here’s what I'm seeing over and over again in SaaS: 1. 50-75% of your leads aren’t ICP? That’s not a lead quality issue — it’s a positioning quality issue. Bad inputs = bad funnel. 2. Killer UX doesn’t matter if buyers don’t get your category. Education comes before differentiation. Always. 3. Value-based pricing? Smart in theory. But if customers start gaming the metric, your incentives are broken. Behavior follows pricing — not the other way around. 4. More features ≠ more value. Without clear context, capabilities become clutter. Use frameworks like the Value Matrix to separate the noise from what actually drives willingness to pay. 5. Four tiers is often one too many. Three gives you a “Goldilocks” middle. Two forces trade-offs. (Okta recently simplified their tiers — and conversions improved.) 6. Don’t call it ‘Enterprise’ unless it acts like one. Slapping a label on your highest plan isn’t strategy — it’s theater. You need true enterprise readiness (support, SLAs, integrations, etc.). 7. Stuck between SMB and Enterprise? That’s a roadmap problem, not a sales one. If leadership pushes upmarket without resources to match, you’ll alienate both sides. Pick a lane. Commit. 8. Trying to be everything to everyone? You’ll end up irrelevant to most. Positioning isn’t about being better — it’s about being different enough that comparisons break down. Your product can be perfect. But if your positioning is off, it’s like shouting into a void. Get it right, or nothing else matters.

44

13 Comments

Loox is losing clients to Judge.me. Why? Because on-the-spot support matters. A lot. I just saw this post today highlighting a common frustration in the Shopify ecosystem: merchants asking to “connect with a human” and getting an automated “we’ll email you” response instead. In Shopify, that delay can cost you a customer. Or several. For over 8 years, at eFoli, we’ve built a strong support team and provided support for our merchants as app developers ourselves. And if there’s one lesson we’ve learned, sometimes the hard way, it’s this: ❤️ Merchants value instant, human support more than we think. It’s not just about resolving tickets. It’s about trust, retention, and delivering the kind of experience that keeps merchants from switching to competitors. We’ve made it a core principle to invest heavily in real, skilled human support, and it has paid off in loyalty, growth, and long-term customer relationships. Whether you’re an app developer, support manager, or merchant, this isn’t just a “support issue.” It’s a business issue. 👉 Support is your frontline. Make it human.

38

19 Comments