Manager Memo podcast · Len Samborowski, MBA Associate Professor, Nichols College

Cybersecurity: Secure Cloud Innovations

·31 min·2 clips

A small company had $1.2 million in pipeline waiting on SOC 2, then closed $1.5 million after certification.

Leonard opens by introducing Caleb Mattingly as a cybersecurity professional, a Renaissance fan, and the founder of Secure Cloud Innovations. Caleb says he likes running a business because it lets him move between different kinds of work and stay busy. He talks about spending time on processes, finances, and website improvements in the same stretch of the day. The energy is practical from the start. Caleb is in the Virginia Beach area of Virginia, and the conversation settles into a relaxed local-business rhythm. The episode turns toward how his company finds work. Caleb says most of the leads come through referrals, including from auditors and current customers. That sets up the larger discussion about trust. Leonard asks him to break compliance down for listeners who are not steeped in SaaS or security language. Caleb answers with a simple idea: people want proof that their information is being handled responsibly. He uses the phrase trust, but verify and applies it directly to security. From there, he explains compliance as a verification process. A company says it can be trusted, and a third party confirms that claim through a report or certification. He frames that as more than paperwork. It is a sign that a business knows how to protect data and can show it. He also says compliance can matter in a crowded SaaS market because it helps a company stand out. In his view, the way a company handles compliance can become part of its differentiation. Leonard picks up on that and asks about the business upside of compliance. Caleb keeps the answer grounded in buyer trust and market positioning. He returns to the idea that customers want confidence before they share sensitive information. That makes the topic feel less like a regulatory burden and more like a sales reality. The conversation uses a familiar example involving a Social Security number to make the point immediate. The idea is not abstract. It is about whether a business can convincingly show that it handles responsibility well. The discussion then moves to frameworks like SOC 2 and ISO 2700. Caleb says the right choice often depends on go-to-market strategy and where a company plans to do business. If a company is focused on the US, he points to SOC 2 as the framework that usually fits. The exchange stays practical rather than academic. Leonard keeps asking for the plain version, and Caleb keeps translating. The result is a conversation about security that sounds like business operations, customer trust, and company positioning all at once. The episode also reflects the kind of work Caleb says he enjoys most: moving between process, finance, and website details. That thread gives the conversation a broader leadership feel. Security is not treated as a wall between teams. It is part of how a company operates. Caleb's comments about integrity and the kind of people he wants to do business with give the episode a moral edge without making it heavy-handed. It ends up being a conversation about how trust works in practice, not just in theory.

As heard by us

Compliance is framed as proof of trust and part of go-to-market strategy.

Cybersecurity is treated here as part of the business, not a separate technical lane. Caleb Mattingly makes the case that compliance is one way to show trust, and the discussion stays focused on how SaaS and tech teams handle data, judge credibility, and pick frameworks that…

Read the full review in PlayNext →

Why you'd press play

You want cybersecurity explained as a business decision, not a jargon dump.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from Manager Memo podcast