Bridging the Gap Between Data and Action: A Strategic Guide for GTM and RevOps Leaders
A conversation with Sarah Flaccavento, SVP Strategic Initiatives at Alphasense.
“Data is only as good as the insights it drives.” – Sarah Flaccavento
In an age where data flows through every department, dashboard, and decision, organizations still struggle to turn that abundance into action. While most teams claim to be data-driven, the truth is that data often ends up siloed, unused, or misunderstood.
Sarah Flaccavento, SVP of Strategic Initiatives at AlphaSense, believes that the ability to translate data into actionable insight is what separates good companies from great ones. In this detailed guide, drawn from her episode on The Revenue Lounge, we unpack the frameworks, prioritization techniques, and change management strategies she uses to create force-multiplying change in complex organizations.
Section 1: From Gut Instinct to Insight-Driven Execution
“Insight is the answer to a question—and it’s actionable.” – Sarah Flaccavento
Data by itself is just noise. The real magic happens when teams identify patterns, contextualize them, and act on them. Sarah defines an insight as something that not only tells you what is happening but also guides what to do next.
| Data | Insight |
|---|---|
| Raw numbers, metrics, activity logs | Meaningful answers to questions |
| Requires interpretation | Tells you what to do next |
| Often siloed and overwhelming | Cross-functional and directional |
| Measures what happened | Predicts or influences what will happen |
Key takeaway: Without connecting data to context and action, teams risk analysis paralysis. Real transformation starts when leaders ask better questions and turn patterns into priorities.
Section 2: Prioritization Framework – WSJF (Weighted Shortest Job First)
One of the core methodologies Sarah uses is WSJF—a prioritization framework from Agile’s Scaled Agile Framework (SAFe). It helps identify high-impact projects based not only on ROI but also on urgency and effort.
“The most important piece WSJF adds is time criticality. ROI alone isn’t enough.” – Sarah Flaccavento
How WSJF Works:
WSJF = (Size of Prize / Difficulty) x Time Criticality
| Component | Explanation |
| Size of Prize | What’s the potential upside (revenue, customers, impact)? |
| Difficulty | How complex is the execution? |
| Time Criticality | If you wait, does the opportunity disappear? Will competitors get there first? |
Example:
Instead of targeting trillion-dollar law firm opportunities (high ROI, low urgency), Sarah’s team focused on launching generative AI search. Why? Because the need was immediate, the pain was clear, and nobody else was solving it yet.
Sarah asks her team to independently score initiatives using the Fibonacci sequence for each parameter. This fosters debate and forces thoughtful decision-making.
Section 3: Strategic Planning in 3 Tiers
“You should be planning for three horizons at any given time.” – Sarah Flaccavento
Sarah outlines a three-level planning model that balances execution with vision:
Infographic: Strategic Planning Tiers
| Horizon | Focus | Examples |
| Quarterly | Fully fixed execution plans | Launch AI search, Expand into HK |
| Biannual (6M) | Defined problems, flexible on how | Solve pricing friction, Partner launches |
| 1-3-5 Year | Big bets and long-term missions | Become the insights platform of record |
She recommends:
Locking in execution for 1 quarter
Having flexible priorities for 6 months
Planning vision 1, 3, and 5 years out
Reviewing monthly, publishing quarterly
To track this, Sarah uses an Excel-based WSJF matrix and hides past columns until it’s time to review. This avoids emotional decisions and encourages accountability through data.
Section 4: Creating a Culture of Data Ownership
“You should never walk into a meeting with a question. You walk in with a recommendation—based on data.” – Sarah Flaccavento
Sarah has built a culture at AlphaSense where data ownership is democratized, not centralized. Everyone—from reps to execs—is expected to:
Bring hypotheses, not open questions
Make recommendations, not just escalate problems
Own inputs to company-wide decision-making
The result? Data becomes everyone’s responsibility. People come prepared, speak with clarity, and decisions move faster.
[Data Entry] → [Insight Generation] → [Recommendation] → [Execution] → [Feedback Loop]
Sarah enforces this through:
Visible use of rep-generated data in strategy meetings
Celebrating usage of Salesforce notes and Gong insights
Running pre-meetings with dissenters to ensure open discussion and buy-in
Section 5: Salesforce: A Directional Input, Not the Whole Truth
“Salesforce is a powerful, directionally accurate input to decision-making.” – Sarah Flaccavento
Sarah acknowledges Salesforce as a valuable, but not infallible, data source. It excels at tracking pipeline stages and opportunity hygiene. But when it comes to customer segmentation or behavior, it often lacks nuance.
Instead, her team triangulates insights from:
Salesforce reports
Gong transcripts
Product usage data
QBR feedback
Pro Tip: Make the rep’s input meaningful by closing the loop. Highlight the impact of win/loss notes in company-wide decisions.
Section 6: Case Study – Rethinking Pricing & Packaging
AlphaSense’s pricing model originally reflected the cost of aggregating premium data. However, the market wanted flexibility—not rigid per-seat pricing.
“Fear drives a lot of detraction. But data addresses that fear.” – Sarah Flaccavento
Sarah’s team:
Started with one FS customer segment
Validated demand with usage and growth data
Adjusted pricing to align with value delivered
Result: AlphaSense closed the largest FS and corporate deals in company history. Each segment got a tailored model based on data-backed buying behavior.
Section 7: Failing Fast in GTM
“Failing fast is about making problems smaller and smaller.” – Sarah Flaccavento
Instead of big bets that take quarters to prove, Sarah advocates:
Breaking big hypotheses into tiny experiments
Testing assumptions early (e.g. Do they have this problem? Will they pay to solve it?)
Learning if it’s a true failure or just “not now”
[Big Idea] → [Micro-Test] → [Data Validation] → [Fail / Scale / Postpone]This mindset saves time, protects resources, and keeps momentum high.
Section 8: Data as a Cultural Operating System
“If data isn’t in your company DNA, it will get in your way.” – Sarah Flaccavento
Sarah closes with this imperative: data must be part of the cultural fabric. Not just a RevOps job. Not just a dashboard. But something that:
Informs every strategic bet
Validates every resource allocation
Shapes every customer interaction
Whether it’s pricing, personas, geographies, or product roadmap, data should drive:
Company priorities
Customer success
Career development
If your team doesn’t have data in their DNA, you’ll feel the friction as you scale.
Final Word: What Makes Data Strategic?
“Insight is data that answers a question and drives action.” – Sarah Flaccavento
Sarah reminds us that:
Data is raw material
Insight is the product
Execution is the output
And at the end of the day, the true role of data is to unlock insight and enable better decisions—at every level of the business.
Want to hear more stories from revenue leaders? Subscribe to The Revenue Lounge podcast to never miss an episode!
More Resources
Sales Development in the Era of Buying Groups
Learn how revenue teams are operationalizing buying groups to escape lead-based inefficiency, multi-thread deals & improve pipeline conversion.
How to Strategically Engage and Conquer Buying committees
Delve into the complexities of engaging buying groups and unveiling strategic approaches to conquer the challenges that arise. In Sales, the key to accelerating deals lies in understanding the nuances of buying group dynamics.
5 Steps to Navigate Buying Groups in 2025: A RevOps Guide
5 Steps to Navigate Buying Groups in 2025: A RevOps Guide RevOps 10 min In today’s business environment, B2B buying is never just one person. According to Forrester Research, more than half of global business buyers purchase in complex buying scenarios that include more people, more departments, and generally higher price points. And this buying group can be made up of 7 to 20 people! Unlocking the power of buying groups is a crucial aspect of the B2B landscape. This blog is a synopsis of our conversation with revenue operations leader, Nandini Karkare. She is currently the SVP of RevOps at Zywave. Nandini suggests strategic steps to navigate through the realms of Revenue Operations and helps uncover the strategies, insights, and best practices that constitute a comprehensive guide to mastering the dynamics of buying groups. Read on to get actionable tips on how you can navigate buying groups in 2025 (and beyond). And implement the learnings to create a winning GTM motion. Here are the 5 steps Nandini recommends: 1. Decode Your Buying Groups The buying groups typically consist of members from departments and they all contribute different aspects. It is critical to understand the scope of decision-making including the people who play the most significant roles in making the call. Gartner’s report on B2B Buying highlights that 77% of B2B purchases involve a buying group of four or more people. PS: The key stakeholder can turn out someone altogether different from who you had building a relationship with all along. a. Capturing Buying Group Members Effective buying group management means considering not just decision-makers but influential stakeholders across departments. Misidentifying key players or focusing solely on the main contact risks derailing the sale. (i) How can you map the entire buying group efficiently? Leverage internal and external data to identify the key players Segment the Group by Role and Influence (ii) Not everyone in the buying group holds equal power or influence. Segment them into categories: Decision-makers (who give the final heads-up) Influencers (who sway the decision) Users (who use the product and provide feedback) Budget owners b. The Role Transition Within a Buying Group Moving the focus from a buying group to a renewal or expansion committee includes knowing precisely who remains in the relationship, as well as who becomes more active as an account grows. (i) New roles may emerge in a Buying Group Technical or operational leaders may become more influential post sale, since they are now using the product. (ii) The focus shifts from buying to renewal The interaction should be more about the return on investment (ROI) of the product placed on the market, ongoing value delivery, and ongoing needs. (iii) Alignment between the buying groups and renewal committee Leveraging the same enthusiasm and relationships generated at the first-buying stage helps in anchoring the transitions and preventing any drop-offs in engagement. Related Resource: Navigate Enterprise Buying Committees: Strategies for Driving Alignment c. Understand the Personal and Collective Priorities of a Buying Group As per McKinsey & Company, B2B buying decisions increasingly require engagement across departments, with 60% of purchasing committees including members from outside traditional procurement, like IT and HR. (i)Alignment Between C-Suite and Technical Teams Decisions aren’t Made in a Vacuum Collaboration between C-suite and technical teams ensures a holistic approach to solving customer problems, creating stronger, more sustainable relationships Their cross departmental collaboration can help with: (ii) Alignment on Strategic Goals C suite executives need technical assistance to translate their strategic vision to reality that also aligns with company-wide objectives. (iii) Technical Validation These insights guide the C-suite in making informed decisions that fit technical infrastructure and future-proofing. (iv) Cross-functional Communication Bridging the gap between these two groups involves continuous, open communication, ensuring that technical evaluations don’t delay business goals but instead support them cohesively. iii. Understand the Product Take product demos, listen to sales calls, and use tools that show how the product is sold. This helps in understanding the customer needs better. iv. Dive into Your CRM Understand your CRM (whether Salesforce or HubSpot) to assess how the data is organized. This is to check whether it’s easy to use, and identify immediate improvements. The CRM should be the central source of truth, with other tools supporting it. The data should be unified with easier adoption for the teams. v. Build Trust Internally Establish trust within your teams by listening carefully, asking questions about how RevOps can help, and addressing quick fixes to show you’re there to help. Having this trust shows them that you’re here to support their success. Quick wins, such as small fixes that make people’s jobs easier, helps in establishing credibility early. 2. Establish Clear KPIs i. Understanding Team KPIs It is important to ask you stakeholders about the KPIs that matter to understand their goals and what their expectations are. ii. Aligning KPIs Across Teams Different departments oftentimes work in silos. RevOps should strive to align these departments and check if these KPIs match the overall business objectives. Gaps must be closed if their KPIs don’t align. iii. Setting RevOps KPIs As you approach the end of the first 30 days, start establishing RevOps-specific KPIs that match company goals, which may involve metrics like revenue increase, conversion rates, or improvements in overall efficiency. 3. Tech Stack Audit Deep dive into the existing tools that your company is using. Identify all redundancies, and find opportunities to streamline the entire tech stack. i. Map Out Tools Compile a list of all tools used by teams, noting their purpose and how they work with the CRM. ii. Evaluate Use and Cost Determine if tools are actively used or if there are duplicates. Look for cost-saving opportunities by consolidating tools when possible. https://www.youtube.com/watch?v=sVDJ9KI1tGw&t=869s Next 30 days – Alignment and Control The next 30 days marks a shift from discovery to alignment. The goals should be to create cohesion between departments (e.g., Sales, Marketing) and laying down effective controls. The improvements need to be implemented without overwhelming the teams. This phase combines