Unlocking Revenue Intelligence: Bridging Data Gaps with AI & GTM Strategies

Unlocking Revenue Intelligence: Bridging Data Gaps with AI & GTM Strategies

A conversation with Uday Sharma.

Executive Summary

Data trust is not a reporting problem. It’s an operating system problem. In this episode, Uday Sharma (Head of GTM Analytics, RevOps at Postman) breaks down why most revenue issues don’t start in dashboards. They start in fragmented systems, shifting definitions, and human behavior.

From preparing Cloudflare’s IPO metrics to building internal revenue intelligence platforms used by hundreds of sellers, Uday shares what it actually takes to build a true “revenue truth layer” that can support forecasting, experimentation, and AI.

Readers will learn:

  • Clean dashboards don’t equal clean revenue: if entity mapping, definitions, and snapshots are broken, forecasts are fiction.
  • Everything should be measured, but few metrics should be monitored: signal filtering is a leadership discipline.
  • Snapshots are non-negotiable: without historical state tracking, you cannot debug forecasting misses.
  • Centralize standards, decentralize expertise: data teams should enforce consistency, but business teams must own meaning.
  • Self-serve analytics must be governed: access without role-based security creates risk, not leverage.
  • Shared incentives beat functional optimization: misaligned comp structures destroy GTM experiments.
  • AI needs two pillars: data hygiene and a semantic layer with documented definitions.
  • Changing behavior is harder than fixing data: scripts can clean anomalies. Only incentives can clean habits.
  • Small AI pilots win funding: start with one constrained workflow, prove value, then scale.
  • Revenue intelligence is not about more dashboards. It’s about better decisions.

Clean Dashboards Don’t Guarantee Clean Revenue

Most GTM issues don’t start in analytics.

They start earlier:

  • Duplicate accounts
  • Broken CRM ↔ product mapping
  • Manual spreadsheet patches
  • Shifting metric definitions
  • No historical tracking

If those foundations are unstable, everything built on top becomes fragile.
You can operate at 80 percent accuracy for a while. But eventually the blind spots surface.

In a public company, that surface is earnings. In a private company, it’s hiring plans, spend allocation, and missed forecasts.
And by the time leadership notices, the root cause is buried under months of accumulated noise.

The Hidden Breakpoint: Definitions and Snapshots

Even clean raw data is not enough.
  • Definitions drift.
  • Pipeline changes meaning.
  • Attribution logic evolves.
  • Activation criteria shift.

“Despite having clean data, if your definitions continue to fluctuate and you don’t have versioning, applying it to historicals is not feasible.” — Uday Sharma

Without version control, every quarterly comparison becomes a debate. Without snapshots, you cannot answer the simplest post-mortem question: What did we believe at that time?

Uday’s rule is firm: It’s really important to snapshot every object that is important to you!

  • Opportunities
  • Accounts
  • Stages
  • Amounts
  • Product signals

Snapshotting is not a nice-to-have. It’s your ability to debug reality.

From Reporting to Revenue Driver: The Cloudflare Story

At Cloudflare, Uday’s team built something most RevOps teams aspire to but rarely execute well: an internal analytics product.

It started small.

 – A prototype during COVID.
– Warehouse-backed queries.
– A custom interface for sellers.

Within months, it was rolled out across the company. And immediately shut down!

“It was too risky to have all this information at the fingertips of every employee,” Uday recalls.

“It was too risky to have all this information at the fingertips of every employee.” — Uday Sharma

That moment changed everything. Instead of retreating, the team rebuilt with:

  • Role-based access
  • Customer-level security rules
  • Aggregated views only
  • Strict governance

They relaunched. Adoption surged.

  • 500+ daily active users.
  • Used live in customer calls.
  • Attribution north of $100M per quarter.

The real validation?

“We would walk in to the sales floor and see our product lit up on their screens.” — Uday Sharma

Revenue intelligence became operational leverage.

Centralized Data vs Embedded Analytics

Where should analytics live?

At Cloudflare, it sat within Finance. At Postman, Uday operates between the central data team and revenue leadership.

His stance is nuanced.

Central teams provide:

  • Standardization
  • Security
  • Pipeline reliability
  • Platform consistency

Embedded teams provide:

  • Context
  • Business alignment
  • Speed
  • Strategic influence

The centralized team can become the gatekeeper. Also, fully decentralizing creates chaos.

His rule:

“Centralize where you need consistency. Decentralize where you need subject matter expertise.” — Uday Sharma

Structure should accelerate clarity, not politics.

Everything Should Be Measured. Few Things Should Be Monitored.

Modern GTM teams measure everything. But measurement without prioritization creates noise.

Signal filtering is a leadership skill. He highlights one metric that exposes truth quickly: Dollar-Based Net Retention.

“Great companies have it north of 130 to 140 percent.” — Uday Sharma

If you’re hovering near 100 percent, you don’t have a reporting problem. You have a structural problem.

  • Churn.
  • Expansion gaps.
  • Customer misalignment.

DBNR forces alignment because it touches every function.

The Real GTM Failure Point: The Handoff

Most revenue breakdowns don’t happen within teams.
They happen between them.

Marketing → Sales
Sales → Post-Sales

“If marketing only has a goal of creating pipeline, they can pour millions into events and generate MQLs. But are these effective leads?”” — Uday Sharma

Comp plans create behavior. Behavior creates data. Data creates decisions.
And customers experience none of those internal boundaries.

To a customer, it doesn’t matter whether you’re from marketing or post-sales. You’re one product!
Shared incentives beat siloed metrics. Every time!

The Analytics Leader Shift: From Report Factory to Strategy Partner

Dashboards are getting easier to build. AI agents can generate visualizations.

That is not the moat. The real differentiator?

“Context”.

“Producing a report is going to become much easier,You don’t want a factory of people just creating reports without understanding what they mean.” — Uday Sharma

He screens for one thing above all: Can you articulate what the chart means and how it should be used?

Analytics leaders must:

  • Filter noise
  • Frame tradeoffs
  • Influence action

Otherwise, they become slide generators.

AI in GTM: Two Pillars or Don’t Bother

Everyone is deploying AI. Few are ready.

Uday outlines two prerequisites.

1. Data Hygiene

“You can’t really build any intelligent AI system on bad data.” — Uday Sharma

  • Product usage
  • CRM
  • Billing
  • Opportunity objects

If these are inconsistent, AI multiplies confusion.

2. A Semantic Layer with Defined Ontology

Uday emphasizes this repeatedly:

“We need to teach the AI which resource to query.” — Uday Sharma

That requires:

  • Documented definitions
  • Consistent entity mapping
  • Clear business logic

This is not prompt engineering.

It’s architecture. Without structure, AI guesses.
Guessing inside revenue systems is expensive.

Funding Data Work: Think Like a Founder

CFOs fund evidence, not ambition.
Uday’s advice is practical.

“Trying to boil the ocean with an AI agent is not going to succeed.” — Uday Sharma

Instead:

  • Pick a small workflow.
  • Teach an agent one skill.
  • Ship fast.
  • Measure time saved.

Prototypes unlock budget. Vague transformation decks do not.

The Takeaways

Uday Sharma’s playbook is not about dashboards.

It’s about foundations.

  • Versioned definitions
  • Historical snapshots
  • Governed access
  • Shared incentives
  • Clear semantic layers
  • Disciplined experimentation

Modern revenue teams don’t need more metrics. They need metrics they trust.

They don’t need more tools. They need systems that align.

Because when data is wrong, AI does not fix it. It accelerates it.

And acceleration without direction is just faster chaos.

Want to hear more stories from revenue leaders? Subscribe to The Revenue Lounge podcast to never miss an episode!

More Resources

Top 15 Guided Selling Tools for 2025

Top 15 Guided Selling Tools for 2025 RevOps 10 min Imagine that you are planning to build a new house but are unsure where to start. You have a basic idea of what you want but are not an expert in home construction or design. In such a situation, you would need a skilled architect who understands your needs, preferences, and budget and then guides you through designing your dream home. The architect would help you make informed decisions about your new home’s design, materials, and features. Similarly, a guided selling tool uses customer data and sales expertise to help customers navigate the purchasing process and make informed decisions. It can provide personalized recommendations based on the customer’s needs and preferences, answer questions, and offer advice to help them choose the right product or service. What is Guided Selling? Guided selling is a strategy involving a structured approach to lead potential customers through the sales process. It is the process of analyzing current sales, historical sales, and customer data to help sales reps provide tailored product recommendations to customers and increase the likelihood of conversion.  Let’s say you are shopping for a new laptop. You visit a website that offers guided selling, and you’re prompted to answer a series of questions. The questions might include things like: What will you primarily use the laptop for? Do you need a large screen or a lightweight design? How important is battery life to you? What is your budget? Based on your responses, the website would then recommend a few different laptops that meet your needs. It might provide detailed information about each laptop, such as the processor, RAM, and storage capacity, as well as customer reviews and ratings. The website might offer additional guidance, such as recommending accessories or providing information on warranties and support. Throughout the process, the focus is on helping you make an informed decision based on your unique needs and preferences. Guided selling can be particularly effective for complex or high-value products or services where customers may require more personalized guidance and support to make informed purchasing decisions. By providing a more consultative sales approach, guided selling also helps to establish long-term customer relationships. How Does Guided Selling Work in B2B SaaS In B2B SaaS, guided selling typically involves a sales representative or a customer success manager who guides the customer. The process usually begins with the customer expressing their needs and goals and the guide using that information to suggest relevant products or services. The guide may use various tools, such as a software demo, to help the customer understand the features and benefits of each option. In addition, guided selling often involves providing educational resources to the customer to help them better understand the product or service and how it can help them achieve their goals. This may include case studies, white papers, or other content that provides valuable insights into the benefits and use cases of the product. Let’s have a look at the guided selling process in detail: The Process of Guided Selling Tools The guided selling process is a customer-centric approach to sales that involves guiding potential customers through the buying process by providing personalized recommendations, advice, and support. The following are the general steps involved in a typical guided selling process: 1. Gathering customer information The first step of the process involves collecting data on the customer’s needs, preferences, budget, and any other relevant information that can help the sales process. 2. Identifying customer pain points In this stage, the sales team uses the information gathered in the previous stage to identify the customer’s pain points or areas of concern.This is typically done through a series of questions or a needs assessment. 3. Providing product recommendations Based on the customer information and pain points identified, the sales team provides recommendations on the products or services that best meet the customer’s needs. 4. Presenting solutions At this stage, the sales team presents the recommended products or services to the customer and explains how they address the customer’s pain points. The sales representative provides information about the recommended products or services, including their features, benefits, and pricing. 5. Handling objections If the customer has any objections or concerns, the sales team addresses them and provides additional information or alternative solutions as needed.  6. Closing the sale Once the customer is satisfied with the recommended product or service, the sales team closes the sale by facilitating the purchase process. 7. Follow-up and customer support After the sale is complete, the sales team provides follow-up support to ensure the customer is satisfied with their purchase and offers any additional assistance or support as needed.   Examples of Guided Selling Tools in Businesses Here are some examples of techniques of guided selling tools:  1. Automate sales playbook To ensure consistent performance, sales playbooks should be automated. Guided selling relies on a solid foundation of methodologies, blueprints, and plays that facilitate the sales process. It’s important to choose a solution that simplifies the playbook for sellers, allowing them to follow the plan and consistently advance deals easily. 2. Identify specific needs In some situations, customers may need a clearer idea of what they are looking for when they visit your website. In such cases, a brief questionnaire can be used to determine and guide their specific requirements. For instance, if you run an online clothing store, you could ask customers questions about their preferred fit and fabric to steer them toward products that best match their preferences. This approach can increase the likelihood of a purchase by helping customers make informed decisions based on their needs. 3. Real-time response For a guided selling software to be effective, it needs to be adaptable and flexible, able to react to changing circumstances in real time. At a fundamental level, ensuring that sales representatives remain attentive to communication and other sales activities can reduce the time it takes to close deals and result in higher revenue velocity. In other cases,

A 30-60-90 Day Guide for First-Time Directors of Revenue Operations

A 30-60-90 Day Guide for First-Time Directors of Revenue Operations RevOps 10 min Starting a new job as a Director of Revenue Operations is an exciting opportunity to make a significant impact on a company’s revenue growth. To ensure success in this role, it’s essential to have a strategic plan that guides your actions during the crucial first three months. Here’s a 30-60-90 day plan that will help you strategically manage revenue operations and drive sustainable growth. We recently spoke to Hassan Irshad, Director of RevOps at FEVTutor. He shared his approach to this powerful framework, demonstrating how each phase (30, 60, and 90 days) builds strategically upon the last to deliver alignment, trust, and sustained improvement. By breaking down complex goals into achievable milestones, the 30-60-90 day approach empowers RevOps leaders to initiate meaningful change without overwhelming teams. For all the RevOps leaders, it’s a way to approach change with purpose, driving measurable impact and laying the groundwork for long-term success.  The 30-60–90 day framework must be an indispensable tool and here is how you can implement progressive, sustainable growth strategies from day one. First 30 days for a Director of Revenue Operations The purpose should be to gather insights and understand the organization, especially the needs and challenges of different teams. 1. Goals for first 30 days:   i. Meet Key Stakeholders Meet with cross departmental teams like Finance, HR, and Sales to understand their goals, challenges, and priorities. ii. Document Everything Create a “lay of the land” document summarizing findings on different team goals, challenges, and processes.   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 further exploration with actionable improvements with the primary task being bringing the teams into sync.   1. Ways to bring your teams together i. Encouraging cross-team collaboration by addressing silos and ensuring all teams work toward shared quarterly or company-wide goals. ii. By creating alignment, you help teams see RevOps as a support system rather than an enforcer. This keeps communication channels open and creates buy-in. iii. Based on your findings, introduce controls wherever needed to improve workflow. Example: If close dates aren’t being recorded properly, this could skew reports. Meet with sales, identify the root cause (e.g., manual data entry that is taking too much of a reps’ time), and provide solutions or tools to make their tasks easier. Ensure that controls are practical and developed with the trust built in the first 30 days. Foster internal consensus within teams so that these improvements are adopted seamlessly. 2. Navigate Organizational Politics (i) Barrier Removal Larger organizations may have internal politics or ingrained processes that resist change. Find an internal “sponsor” who trusts and supports RevOps initiatives and can authorize actions to navigate any resistance. (ii) Trust and Consistency As you implement changes, make sure your efforts consistently demonstrate how RevOps can make work easier and more efficient for everyone. 3. Evolving the Tech Stack (i) Assessing Tech Needs If tools aren’t fully integrated (e.g., a tool not writing data back to the CRM), identify their gaps and consider evolving the tech stack. (ii) Holistic View Use insights from the discovery and alignment phases to start envisioning necessary tech improvements that align with company goals. Beginning of the 90-Day Phase: Vision and Execution This phase, described as “Vision and Execution,” involves shaping and executing a strategy based on insights gathered from the discovery and alignment phases. a. Roadmap Creation Create a roadmap covering the next two quarters, focusing on long-term, high-impact changes that align with business goals. Use learnings based on stakeholder needs, organizational goals, and the findings from the first 60 days i. Set Priorities Collaborate with end users (Sales, Marketing, Customer Success) to understand their pressing needs and align the roadmap with these needs. ii. Strategic Execution Prioritize initiatives that will have immediate revenue impact or

Scroll to Top

Just one more step