Shiren Vijiasingam
New York City Metropolitan Area
3K followers
500+ connections
View mutual connections with Shiren
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
or
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
View mutual connections with Shiren
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
or
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
About
A seasoned executive who builds culture and scales diverse product development, product…
Experience
View Shiren’s full profile
-
See who you know in common
-
Get introduced
-
Contact Shiren directly
Other similar profiles
Explore more posts
-
Varun Anand
OpenAI is one of the defining companies of our time. I can't actually believe we at Clay get to play an (extremely) small part in helping them grow. Here is that story. We met Keith Jones 🚴🏻♂️ — who leads OpenAI's GTM systems team — through Maggie Hott in December of 2023. To put it mildly, Keith was skeptical. He even gave us a test in our first demo. He had just joined OpenAI 3 weeks prior, so he was sure we wouldn't be able to accurately find him in Clay, but we successfully did during the demo — in just a few seconds. Now, more than a year later, Keith says: "In my professional opinion they have one of the most practical and exciting applications of AI, in a decades-old practice that has long been stale" What drove this conclusion? ▶️ More than doubling inbound lead enrichment quality from low 40% to high 80% during implementation ▶️ OpenAI used Clay’s AI web researcher to mimic and augment the research process of their best sales reps—at scale—leading to countless hours saved. ▶️ Instead of using a dozen tools, OpenAI's sellers can now get any enrichment they need—from contact info to account research—with one click in Salesforce. But we aren't stopping there. We're working with data science, marketing ops, and recruiting to help them harness the power of Clay for their workflows. And as their team (hi Scotty & Harsha!) continues to come up with new ideas to grow, we'll be there helping them bring those to life. Full case study link is in the comments!
286
21 Comments -
Tiara S.
Red flags I’ve learned to spot in customer relationships - from 12 years in the trenches: After years 12 in Customer Success, Product, and HealthTech I’ve learned that churn rarely happens overnight - it starts as a whisper. Here are the signs I listen for👇 🚩 "We’re too busy for onboarding right now.” At Blue Cross, I learned: customers who skip structured onboarding churn 3x faster. Now, onboarding isn’t optional - it’s mission-critical. 🚩 Low usage but "everything’s great.” Data doesn’t lie. At HCA, tracking telehealth logins helped me spot adoption issues early. Fixed one provider’s workflow and doubled virtual visits in 60 days. 🚩 The executive sponsor disappears after kickoff. If leadership isn’t engaged, the account is already at risk. I escalate this at Day 30, not at renewal time. 🚩 Recurring support tickets on the same issue. At Hypeline, I documented patterns and turned them into process improvements. Cut repetitive requests by 20% in two months. Band-aids don’t work - fix the wound. 🚩 Customer only reaches out when something’s broken. Reactive relationships don’t renew. I schedule proactive check-ins even when things are "fine.” 🚩 "Can you just add this feature?” without context. Feature requests are symptoms, not solutions. My go-to question: “What outcome are you trying to drive?” The fix is rarely just a feature. 🚩 Silence after delivery. The quietest customers churn the loudest. At Hypeline, gathering post-delivery feedback (4.7/5 avg. satisfaction) helped surface hidden risks early. The best CSMs treat early warning signs like smoke detectors - not fire alarms. By the time you’re fighting churn, it’s already too late. 12 years in, I’ve learned Customer Success is part detective, part therapist, part data analyst. What red flags have you learned to catch early? #CustomerSuccess #ChurnPrevention #CSM #HealthTech #SaaS #AccountManagement
200
29 Comments -
Kevin Spain
I’ve been talking with founders about how painful enterprise customization still is — even in 2025. David Dworsky and Gordon Ritter just put words to what we’ve been seeing: the age of point-and-click configuration is ending, and the next category winners will make customization conversational. For early-stage founders, this is the wedge: - Own one painful workflow - Capture the data - Build toward becoming a system of record If you’re building in this space, I’d love to hear how you’re approaching it. Link to the full article on this in the comments.
36
5 Comments -
Steven Larsen
The GTM playbook is being rewritten — and CROs are leading the charge. Last week, Scalestack co-hosted an unforgettable CRO Roundtable in San Francisco with our friends at The CRO Collective. 👥 20 revenue leaders 🌆 An iconic venue at the Transamerica Pyramid 🔥 Real, unfiltered conversation No panels. No pitches. No filler. Just honest conversation around what’s working, what’s not, and where we go next as GTM continues to shift beneath our feet. Some themes that stood out: 🚨 Misaligned incentives are killing revenue strategy 🎯 Marketing ≠ just lead gen — it’s about brand, education, and long-term growth 🧠 Millennial buyers demand a new approach 🤖 AI is non-negotiable — but hard to navigate 🏗️ CROs aren’t just sales leaders — they’re system architects Scalestack is building revenue engines that work with the GTM stack, not around it. That’s why these spaces matter: they cut through the noise and make room for clarity, curiosity, and collaboration. Big thanks to the leaders who showed up ready to challenge assumptions and push the conversation forward — and to our partner Warren Zenna, and the team at The CRO Collective for making it all happen. Looking forward to the next one! #Scalestack #CROCollective #AutonomousRevenueEngine #RevenueEngineMasters #CRORoundtable
50
7 Comments -
Ben Henson
GTM Engineer might be the hottest title in tech right now, but the work has always been there. Some wear the title. Others just do the work, connecting systems, stitching insights, enabling teams, and pushing go-to-market efforts forward without the fanfare. Whether your org calls them GTM Engineers, Revenue Ops, or just “the person who makes everything work,” they’re often the difference between activity and real impact. If that’s you, this asset will help. It’s a clear, no-fluff breakdown of what great GTM execution looks like and how to improve it. Built to support the people behind the motion. Enter Peel Playbook - GTM Engineer Edition (of course as a Talkable) Talk to it - steal the great ideas - link in comments
49
3 Comments -
Ashu Garg
I was recently asked whether AI will kill SaaS. My opinion is more nuanced than a simple "yes" or "no." I think the death of SaaS will happen slowly and then very suddenly and very dramatically. I'm talking particularly about mid-size SaaS companies (say between $100 million and $1B). If you're not AI-native right now, you're going to struggle. 9 out 10 of middle-market companies are seeing some churn, but the churn isn't dramatic yet. There's employee attrition. These companies are fighting a war, feature by feature, adding a little "AI pixie dust" here and there. But net: they're struggling. There will be a tipping point in the future where credibility tips to the new fast-growing startups and away from the incumbents. We can already see that people are buying for outcomes instead of buying for seats. The billion-dollar companies will have enough cash to spend their way out of this problem, and these mid-sized incumbents will get squeezed. The question isn’t if the tipping point comes. It’s who shows up with a product that actually does the job and evolves faster than the models. Right now, we should all be paying attention to the tiny AI-native startups that are growing like crazy - especially if you’re sitting in that middle-market range.
104
14 Comments -
Jonathan Pipek 🔱
most positioning dies in a Notion doc founders say they want crisp messaging, but what they really need is **confidence** 💪 confidence that GTM teams will *actually* use it 💪 confidence that it’s differentiated 💪 confidence that it scales confidence is what I aim for when I work with early-stage teams it’s not about who has the best positioning framework it’s about end-to-end frictionless adoption throughout your org p.s. what are your PMM tales of woe? (where your hard work sits on a digital shelf collecting dust)
52
35 Comments -
Hiten Shah
For years, SaaS meant control. Teams would delay launch for every round of QA and debate, pushing live only when everything felt predictable. You needed proof in hand before anyone saw your work, because reputation, retention, and revenue depended on minimizing every unknown. That old instinct to launch only when everything’s perfect? In AI, it’s the main reason teams fall behind. The classic SaaS approach worked because customers bought consistency. Sales pitches highlighted reliability, support played defense, and new features waited for a green light from every internal gatekeeper. Teams measured maturity by what they hid. Bugs, doubts and surprises. A good launch felt like closure. AI flips the table. Now, every release happens in public. Models change, data shifts, and product value doesn’t show up on launch day. It emerges after weeks of live interaction and blunt feedback. AI products stop pretending they’re finished. The ones that lead put their rough edges on display and treat every flaw as tomorrow’s advantage. Every SaaS team was trained to avoid mistakes in public. The teams thriving now are the ones showing the messy middle, letting users witness how the product changes under real pressure. They launch an early version, watch what users break, publish their limits, and ask for help naming what doesn’t work. While others polish and hesitate, these teams collect four cycles of hard-earned learning for every one release that the old guard ships. They turn error messages into feature requests and respond to friction faster than anyone else can copy them. Teams that hesitate for certainty fall further behind with every iteration. In AI, there’s no finish line. Only a faster cycle to discover what breaks next. The hardest part is unlearning the need for control. What really separates the winners now? They replace every instinct to control with the habit of chasing their own blind spots. You build momentum in AI by giving users a front row seat to your product’s evolution. Share the limits, welcome the awkward feedback, and treat every launch as an open invitation for your market to teach you faster. Teams who delay for certainty miss the next cycle of learning and let others set the standard. The old goal was certainty before launch. The new reality is you launch to earn it.
24
9 Comments
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content