Compliance Drives Revenue. Here's What to Count | Guest: Laura Sawka

From The GRC Engineering Club's AntiCheckBox Podcast · 00:46:41

Show by Dr. Omar Sangurima

Compliance can drive revenue. Laura Sawka, founder and GRC executive of Sawka Advisory Group, says it is possible in the first two minutes, then lays out how to measure it. Laura led GRC globally at a Fortune 500 company and started her career at a Big Four firm. Today she helps companies transform their GRC programs so they scale and strategically support the business.Her case runs on two paths. The direct one: a certification or regulatory requirement is your ticket into a market, and once you have it, every customer in that market can buy. The indirect one: customers renew because they trust you, and a lot of that trust is built from your SOC report, your ISO report, your trust center and the questionnaires you answer. She is upfront that some of this is a straight line to revenue and some of it is "we enabled" or "we influenced."From there Omar asks where the checkbox reputation comes from. Laura ties it to GRC being treated as a cost center, and argues that requirements exist to reduce risk, so the work is integrating them into policy, controls and monitoring instead of proving compliance at a single point in time. We also get into AI and the wave of overnight GRC experts, why telemetry has to come before any AI answer, and why the breadth of GRC across the business is a strength.KEY TAKEAWAYSCompliance opens markets. A certification or regulatory requirement can be the only thing standing between real demand and a closed deal.Renewals are revenue. Your reports, trust center and questionnaire answers build the trust customers keep paying for.Track it: report downloads, questionnaires tied to deals, meetings that support new business or renewals, and contractual commitments.The checkbox reputation comes from being treated as a cost center with unclear business value.Policies reviewed once a year and risk assessments left on the shelf are the checkbox approach. Policies as code, monitored controls and risk assessments that drive investment are the alternative.If you know a system's availability, you should know the same about your controls.AI does not replace your GRC person. It should augment GRC so practitioners can be better advisors to the business.Without telemetry and continuous monitoring, an AI answer is not an answer. That is where hallucinations come from.Durable skills come first: communicating in business terms and influencing action. Pair them with an engineering mindset.Stakeholders who stall usually have competing priorities, not indifference. Find where their priorities and yours meet.GRC sees the whole organization. Use that data to influence architecture: streamline, share services and cut duplicate controls.FIND LAURA SAWKASawka Advisory Group: https://www.sawkaadvisorygroup.comLinkedIn: https://www.linkedin.com/in/laura-sawka/

More episodes of The GRC Engineering Club's AntiCheckBox Podcast

More episodes

PodSearch is a free, independent podcast search engine. Read about PodSearch, the privacy policy or contact us.