Crafting an Effective Governance Framework for Business Applications

Crafting an Effective Governance Framework for Business Applications

A conversation with Bill Vanderwall, VP of Business Applications at Cision.

data governance framework

In the SaaS-driven world, businesses rely on dozens, sometimes hundreds, of applications to run sales, marketing, finance, HR, and customer success. From forecasting platforms to customer success dashboards, SaaS powers every corner of go-to-market.

But there’s a hidden cost: sprawl. Too many tools. Too many overlapping features. Too many silos.

Bill Vanderwall, former VP of Business Applications at Cision, has seen this story unfold at companies like Netscape, Marketo, and Malwarebytes. He’s helped organizations tame chaotic tech stacks, rationalize spend, and align SaaS with business outcomes. In this episode of The Revenue Lounge, Bill breaks down what a SaaS governance framework really looks like, why companies need one, and how to make it stick.

Why Governance is No Longer Optional

Bill recalls a time when business units could buy tools without involving IT. Sales teams bought engagement platforms. Marketing bought automation. Customer success bought onboarding solutions. Each tool solved a problem, but together, they created a fragmented landscape.

“At Marketo and Malwarebytes, I walked into companies where SaaS applications were being managed by the business. Data didn’t flow. Processes broke down. IT had to step in to bring some order.”

Governance, Bill explains, isn’t about slowing people down. It’s about creating balance. A good framework ensures:

  • Tools align with business strategy.

  • Data flows across departments.

  • Costs are rationalized.

  • Priorities are set at the right level.

The Two-Tier Governance Model

The heart of Bill’s playbook lies in a two-level governance structure — one that balances strategy with execution.

1. C-Level Steering Committee (Quarterly)

At the top, governance happens at the C-suite. This steering committee meets quarterly to set priorities and allocate IT resources.

Bill recalls his time at Malwarebytes, where the CFO drove discipline with a three-year plan:

“We’d identify the company’s top goals for the year — say, improving retention — and then align technology investments to achieve them. The C-level team agreed on the priorities, which eliminated politics and kept us focused.”

Governance Flow:


Company Strategy → Annual Operating Plan → C-Level Priorities → IT & SaaS Execution


2. Operational Committee (Monthly)

Beneath the steering committee sits a monthly operational group. This team handles smaller projects, integrations, and SaaS purchases that don’t require C-suite oversight.

Example: When a business unit wanted to adopt Gong, the committee vetted it to ensure fit with Salesforce architecture and estimated IT effort. Once approved, the business team owned administration while IT ensured smooth integration.

This layered approach creates agility without losing alignment.

Buy vs. Build: Choosing the Right Path

For years, companies wrestled with the “buy vs. build” debate. Bill says the equation has shifted:

“With so many best-of-breed solutions available today, buying is usually smarter — unless the capability is core to your product strategy.”

Buy vs. Build Decision Matrix

CriteriaBuyBuild
Speed to Value
Cost Efficiency
Strategic Differentiator
Core Business Function
Maintenance Burden

Taming SaaS Sprawl: Rationalization in Action

When Bill joined Marketo, he discovered four separate survey tools in use. Governance turned that chaos into a deliberate choice: one enterprise-grade tool, better aligned with business needs.

“Having a lot of applications isn’t automatically bad. But you need to ask: who’s using it, what’s it costing, and is there overlap? Rationalization is about making those calls — ideally before renewal cycles.”

Best Practices for Rationalization:

  • Inventory applications bi-annually.

  • Track usage vs. spend with monitoring tools.

  • Consolidate overlapping tools.

  • Align consolidation with strategic priorities.

The SaaS Sprawl Funnel:


270 Requests → Group by Themes → Prioritize by Impact → Approve via Governance → Rationalized Roadmap

Measuring ROI: Beyond Vendor Claims

Every SaaS vendor promises sky-high ROI. Bill is skeptical.

“Vendor ROI models are fine directionally, but they’re packed with soft dollars. You need to separate hard savings from fuzzy benefits — and focus on time-to-value.”

Key ROI Factors:

  • Hard Dollars: License savings, reduced churn, FTE efficiency.

  • Soft Dollars: Productivity gains, collaboration, user satisfaction.

  • Time-to-Value: How quickly can benefits show up?

“A little revenue growth can cover a lot of expenses. Time-to-value often matters more than a perfect ROI model.”

Data Quality: The Hidden Governance Layer

Bad data is every company’s silent killer. Bill has seen organizations simply “live with it.”

But governance frameworks can elevate data quality through:

  • Preventing duplicates at the source.

  • Using enrichment vendors like ZoomInfo.

  • Creating data lakes (Snowflake, Redshift) for cleansing and harmonization.

Data Quality Levers:


Front-End Governance → Enrichment Tools → Data Warehouse → Analytics → Business Impact

Managing Change: From Chaos to Control

Introducing governance to a free-for-all environment isn’t easy. Bill’s advice:

  • Start with quick wins (fix broken data flows, automate manual processes).

  • Build trust through partnership (don’t be draconian).

  • Celebrate outcomes (show how governance accelerates, not blocks).

“At Marketo, we allowed certain groups autonomy as long as they communicated and aligned. Governance isn’t about control — it’s about achieving the same objectives together.”

AI, Legal, and the Future of Governance

AI adds a new dimension: vendors want access to customer data to train models. Legal wants to block everything. IT sits in the middle.

Bill’s advice:

  • Get legal, vendors, and engineers on the same call to negotiate.

  • Clarify data usage rights, anonymization, and safeguards.

  • Accept that not every situation is black and white.

AI Vendor Risk Checklist:

  • Will my data train your models?

  • Is data anonymized?

  • What security guarantees exist?

  • Can we opt out?

Best-of-Breed vs. Platforms: The Consolidation Tradeoff

With budgets tightening, platform consolidation is tempting. But Bill is cautious:

“Most companies are still best at the thing they started with. Platforms may catch up, but best-of-breed usually wins — unless platform efficiency outweighs the feature gap.”

Template: Platform vs Best-of-Breed Scorecard

CriteriaPlatformBest-of-Breed
Cost Savings
Feature Depth
Integration Ease
Scalability
Innovation Pace

Vendor Maturity: Balancing Risk and Innovation

Should companies bet on a young, innovative vendor? Bill says it depends:

  • Mission-critical tools → Choose mature, established vendors.

  • Efficiency-enhancers → Safer space to experiment with newer players.

 

Part of the governance model includes vendor maturity checks: D&B reports, leadership profiles, financial stability.

Final Takeaway: Governance as a Growth Enabler

Governance is often misunderstood as bureaucracy. Bill’s career proves otherwise.

“Don’t be heavy-handed. Governance is about trust, alignment, and impact. The right framework makes SaaS a growth enabler, not just a cost center.”

By combining strategic C-level oversight with tactical operational committees, organizations can control sprawl, improve data quality, manage risk, and align technology with their most important business outcomes.

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

More Resources

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 ProductTake 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 CRMUnderstand 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 InternallyEstablish 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 KPIsIt is important to ask you stakeholders about the KPIs that matter to understand their goals and what their expectations are.ii. Aligning KPIs Across TeamsDifferent 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 KPIsAs 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 AuditDeep 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 ToolsCompile a list of all tools used by teams, noting their purpose and how they work with the CRM.ii. Evaluate Use and CostDetermine 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 togetheri. Encouraging cross-team collaboration

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top

Just one more step