TRANSCRIPT 🔗
WEBVTT
00:00:16.640 --> 00:00:21.199
Alrighty then, ladies and gentlemen, welcome back to another episode of Privacy Please.
00:00:21.280 --> 00:00:24.800
I'm Cameron Ivey alongside my friend Gabe Gums.
00:00:25.039 --> 00:00:27.920
And Gabe, we got a we got a special guest today.
00:00:28.079 --> 00:00:29.440
I'm pretty excited about this one.
00:00:29.679 --> 00:00:31.280
We've got a great guest today.
00:00:31.519 --> 00:00:38.479
We promised at the top of the year that we were gonna unveil a couple of really exciting um folks out in the industry.
00:00:38.640 --> 00:00:41.280
And we've got our first one on today's show.
00:00:41.600 --> 00:00:42.880
Yeah, we got uh Girish.
00:00:43.039 --> 00:00:46.799
Girish, thanks for so much for the time, first of all, for joining the show.
00:00:46.960 --> 00:00:51.840
Really appreciate it, and we're excited to understand where you came from and how you got to where you are today.
00:00:52.000 --> 00:00:54.479
So I don't want to like steal too much time.
00:00:54.560 --> 00:00:59.039
I'll just kind of let you open the floor and kind of tell us a little bit about yourself.
00:00:59.679 --> 00:01:00.640
Thanks, Cameron.
00:01:00.799 --> 00:01:01.359
Thanks, Cape.
00:01:01.439 --> 00:01:04.560
Uh, thanks for the warm welcome, and I'm excited to be here as well.
00:01:04.640 --> 00:01:05.680
Uh, thanks for having me.
00:01:05.840 --> 00:01:07.200
So, yeah, a little bit about me.
00:01:07.280 --> 00:01:08.159
I'm Guriesh.
00:01:08.239 --> 00:01:13.200
I'm uh one of the co-founders and also the CEO of a company called Sprinto.
00:01:13.519 --> 00:01:19.200
At Sprinto, our goal is to help other companies build trust with their stakeholders.
00:01:19.359 --> 00:01:23.680
And I specifically mean trust with respect to the security and privacy.
00:01:23.920 --> 00:01:36.159
You know, fundamentally, um, you know, every business that exists out in the world, in some way or the other, depends on other businesses to run its operations, and that dependency has a digital trail.
00:01:36.239 --> 00:01:42.319
And what's becoming increasingly important that let's say I as a company am dealing with you, Cameron, or with you, Gabe.
00:01:42.400 --> 00:01:53.519
And if I have a digital trail with you, I want to make sure that uh, you know, you give me certain assurances about the fact that you're going to treat the data that I share with you with safety, with security, and with privacy.
00:01:53.680 --> 00:02:06.799
And we're in the business of helping companies make sure that they can have the right practices and also be able to showcase the fact that they have right practices so that it reduces the friction in these con uh in these transactions that happen between businesses.
00:02:06.959 --> 00:02:12.240
So if we do our job well, uh, we actually believe we'll increase the GDP of B2B commerce.
00:02:12.319 --> 00:02:15.520
Uh, that sounds lofty, but that's exactly what we go after.
00:02:15.680 --> 00:02:18.560
Um, and personally, about me, I'm a programmer first.
00:02:18.639 --> 00:02:20.960
I'm happiest when I'm writing code and building product.
00:02:21.120 --> 00:02:24.400
Though as the company grows, I admittedly get to do less and less of that.
00:02:24.560 --> 00:02:26.240
But that's where I'm most comfortable at.
00:02:26.319 --> 00:02:28.080
Uh, Sprinto isn't my first startup.
00:02:28.159 --> 00:02:29.520
I did a startup before this.
00:02:29.759 --> 00:02:35.120
And funny, it was during the course of growing that startup that uh I landed on the problem that we solved today.
00:02:35.280 --> 00:02:39.120
Uh, you know, as an engineer, I was trying to build a security and privacy program.
00:02:39.360 --> 00:02:42.000
Long story short, I hated the way it works.
00:02:42.159 --> 00:02:44.960
Uh, thought there should be a better way of making that happen.
00:02:45.039 --> 00:02:47.120
And that was kind of the germination of Sprinto.
00:02:47.360 --> 00:02:52.400
So that's a little bit about me and the company, but happy to answer more questions as we as we go along.
00:02:52.719 --> 00:02:56.479
You know, Guresh, you've got a very interesting and story background.
00:02:56.560 --> 00:03:09.120
And in particular, I really want to dive into a bit about what you've seen firsthand in the difference between what it means to pass a SOC2 or an ISO audit and how that compares to actually being secure.
00:03:09.360 --> 00:03:15.199
I think one of the things that the trust that you build up between organizations is exactly that, right?
00:03:15.280 --> 00:03:18.879
Like not just saying it, not just talking the talk, but walking the walk.
00:03:19.039 --> 00:03:27.840
But before we get there, I'm always fascinated when I speak to founders like yourself, technical founders, that love to be hands-on keyboard.
00:03:27.919 --> 00:03:36.960
And I've I've gone through some of this growth, call it uh an emotional struggle sometimes where you you find yourself getting further away from the technology as the company grows.
00:03:37.120 --> 00:03:41.360
Tell me though, what's that journey in particular been for you as that company has grown?
00:03:41.439 --> 00:03:52.159
And specifically, because AI is such a hot topic these days, has it allowed you to get a better balance of being able to still code, right?
00:03:52.319 --> 00:03:58.240
Do the things that that really just bring you joy while also being able to run a business?
00:03:58.479 --> 00:04:01.039
Yeah, I think uh what you said at the end is exactly right.
00:04:01.120 --> 00:04:13.039
Uh, you know, AI has sort of produced the barrier of what it actually takes to do something productive, even in a company that has like uh, you know, massive code base that runs into millions of lines of code.
00:04:13.120 --> 00:04:24.560
So there was a point in time where I was actually scared of contributing anything to the company code in the with the fear that I might actually break something because uh you know the the
Load full transcript
software has grown to a size where it can't where I can't hold it in my hand anymore.
00:04:24.720 --> 00:04:29.279
And you have like a bunch of checks and balances to make sure we we ship something right.
00:04:29.360 --> 00:04:42.079
And so the the uh the the time cycle between you actually thinking about something and working on it and and actually making it production ready just keeps on having more and more steps in between.
00:04:42.240 --> 00:04:43.680
And that is kind of frustrating.
00:04:43.759 --> 00:04:46.560
Uh, what AI has done is that it has compressed that a lot.
00:04:46.720 --> 00:05:03.279
So now uh you know, I'm again in a zone where I can actually contribute meaningfully or at least uh do some side projects that can attach to our main code base, but it it actually has given back the joy of actually doing something that would otherwise seem uh you know a little daunting.
00:05:03.439 --> 00:05:10.399
So I, my co-founder and the gentleman who currently uh heads by engineering, we wrote most of the early code at Sprinto.
00:05:10.639 --> 00:05:19.680
But as a company grow, we sort of grew farther and farther away from the actual code that's been written and sort of get drowned into more of the operational aspects of running a business.
00:05:19.839 --> 00:05:22.399
But yeah, AI has actually made it more accessible.
00:05:22.639 --> 00:05:32.000
You know, it just uh allows us to sort of get back our hands on the keyboard on more than sending emails and drafting spreadsheets, but actually writing code again.
00:05:32.319 --> 00:05:33.439
Right on, right on.
00:05:33.600 --> 00:05:38.480
So let me bring that full circle to kind of what your organization does.
00:05:38.800 --> 00:05:54.959
And one of the things that comes up in a lot of my conversations is, you know, as it pertains to the frameworks that exist around security and privacy, SOC2 and ISOs, how do you see AI changing those frameworks?
00:05:55.040 --> 00:06:04.079
And how do we still maintain trust between organizations as they essentially implement things that some people might think of as a black bar?
00:06:05.439 --> 00:06:05.839
Yeah.
00:06:06.319 --> 00:06:08.560
I think the second part of what you said is really important.
00:06:08.800 --> 00:06:17.120
Think of compliance with certain frameworks more as a way of saying that there are certain practices at the bare minimum that you have in place.
00:06:17.279 --> 00:06:21.040
But the existence of those practices doesn't necessarily mean that you're completely safe or secure.
00:06:21.120 --> 00:06:23.279
It's definitely better than not having anything.
00:06:23.519 --> 00:06:27.519
It does give a certain degree of comfort, uh, but it doesn't go the entire way.
00:06:27.600 --> 00:06:29.839
So compliance doesn't necessarily mean trust.
00:06:29.920 --> 00:06:41.519
Uh, and I think the simplest analogy of this is uh, you know, uh you could be a straight A student and you have like high SAT scores, but that doesn't necessarily mean that uh, you know, you understand the topic.
00:06:41.680 --> 00:06:43.120
You can actually implement it in a real one.
00:06:43.360 --> 00:06:48.480
That's the difference between being compliant and actually being uh you know trustworthy to work with.
00:06:48.639 --> 00:06:50.079
Uh A doesn't imply B.
00:06:50.160 --> 00:06:54.160
It's it's a good stepping stone towards it, but it doesn't mean the entire thing as well.
00:06:54.319 --> 00:07:13.439
So I think what tends to happen as companies mature is your first goal is typically that, hey, can I at least do the baseline things, the foundational things that are important uh in order for me to be um uh in order for me to have some sort of a formal security and privacy program.
00:07:13.759 --> 00:07:16.240
And I think that's baseline, that's foundational, that's important.
00:07:16.399 --> 00:07:20.319
Uh, you can't go from where you are to where you want to be without passing that step.
00:07:20.399 --> 00:07:26.399
And you of course get an additional advantage that uh, you know, these are some industry recognized practices.
00:07:26.560 --> 00:07:28.560
So once you do them, you get the benefit of them.
00:07:28.720 --> 00:07:32.000
It helps you build trust with your customers along that.
00:07:32.399 --> 00:07:34.959
But that's the beginning and not the end of it all.
00:07:35.120 --> 00:07:43.279
So as companies grow more mature, they start asking a question about hey, I run these practices and I'm able to prove out these practices every time somebody looks at me.
00:07:43.439 --> 00:07:48.560
But what would it mean for me to be able to run these practices irrespective of somebody's looking at you?
00:07:48.800 --> 00:07:57.040
So that's the next step that companies go to, which is what we call as continuous compliance, in the sense that, hey, the fact that somebody's looking at you is just incidental.
00:07:57.120 --> 00:07:58.800
You you're running these anyway.
00:07:59.040 --> 00:08:00.959
It doesn't matter whether somebody looks at you or not.
00:08:01.120 --> 00:08:06.079
And so an audit or uh or due diligence that happens by a customer is just business as usual.
00:08:06.160 --> 00:08:11.439
It doesn't even clock as a blip on your radar, it's it's something that's that's completely fine.
00:08:11.680 --> 00:08:20.160
And then you go on from there to basically getting to a stage where, hey, I'm running all of these practices, uh, but can I actually stop bad things from happening?
00:08:20.240 --> 00:08:29.680
Uh, which requires you to go like another step ahead, which is saying that, hey, uh I'm I'm sort of uh avoiding bad things from happening.
00:08:29.759 --> 00:08:34.639
I sort of have all of these right things in place, but can I sort of uh foresee some of these things?
00:08:34.799 --> 00:08:36.000
Can I stop them in tracks?
00:08:36.080 --> 00:08:40.240
And if they do happen, do I have the right uh mechanisms to be able to react to it?
00:08:40.320 -->
00:08:55.600
Uh and and that is what basically what we call as resilience, uh, which is fundamentally a way of saying that hey, I can avoid bad things from happening in the first place, but if they do happen, I have like shorter reaction cycles and I know how to do that, and you sort of become stronger as a business.
00:08:55.759 --> 00:09:06.240
So you go from a point where you did the foundational stuff to a point where you actually doing the things irrespective of who's looking at you, to a place where you're actually stopping bad things from happening.
00:09:06.399 --> 00:09:08.720
And every company sort of goes through this cycle.
00:09:08.960 --> 00:09:15.600
It is a long trust, isn't a on-off switch, or it's it's not like you're whether you're trustworthy or not.
00:09:15.679 --> 00:09:29.440
There's a spectrum, and as a company grows and has more resources to sort of spend on this, and as it becomes more and more important for a business to lie on the right hand side of this spectrum than on the left-hand side, we see naturally companies go in that direction.
00:09:29.679 --> 00:09:31.440
And that's what we support companies to do.
00:09:31.679 --> 00:09:35.840
You know, you get started here, but you go the full mile, you know, but you need to.
00:09:36.159 --> 00:09:38.559
I love your statement about resilience.
00:09:38.720 --> 00:09:40.399
I love it for a particular reason.
00:09:40.559 --> 00:09:42.000
I'm a hacker by trade.
00:09:42.159 --> 00:09:43.279
I break things for a living.
00:09:43.600 --> 00:09:54.240
When I'm not breaking things, I'm helping other people make their environment resilient because ultimately, in all of my years of being an ethical hacker, I haven't found many things that I can't break.
00:09:54.559 --> 00:09:56.399
Or someone else can't break.
00:09:56.559 --> 00:10:04.720
And so you'd mentioned offline that you know you found it's been to after realizing that compliance was essentially broken at its core somewhere, right?
00:10:04.799 --> 00:10:05.919
Like along the way.
00:10:06.159 --> 00:10:09.279
What did you observe that made you come to that realization?
00:10:10.159 --> 00:10:13.279
So I'll share a little bit about specifically how my experience was.
00:10:13.519 --> 00:10:17.679
We had to become compliant with a couple of frameworks like SOC2 and ISOCRINES and Tabson 1.
00:10:17.759 --> 00:10:26.480
Uh the first place where there was a problem was that these seemed like walls of text that was just undecipherable for a normal human.
00:10:26.559 --> 00:10:29.919
Like I could read it, but I couldn't make sense of what it means for my business.
00:10:30.000 --> 00:10:31.279
What do I really need to do?
00:10:31.600 --> 00:10:36.879
So translating something like a framework to what I need to do on the ground as a business.
00:10:37.039 --> 00:10:38.320
Like, what do I really need to do?
00:10:38.480 --> 00:10:41.440
Do I need to make sure that my employee laptops are safe?
00:10:41.600 --> 00:10:42.480
If yes, how?
00:10:42.639 --> 00:10:43.919
What specifically do I need to do?
00:10:44.080 --> 00:10:46.399
Do I need to do something on my AWS environment?
00:10:46.720 --> 00:10:47.840
If yes, what?
00:10:48.159 --> 00:10:52.240
Do I need to change some of my employee onboarding and offboarding practices?
00:10:52.399 --> 00:10:53.519
If yes, what?
00:10:53.600 --> 00:11:02.320
And it just seems like a lot of degrees of freedom, a lot of opinions, and just uh, you know, uh nobody quite sure what exactly needs to be done.
00:11:02.639 --> 00:11:03.600
Very subjective.
00:11:03.840 --> 00:11:14.080
It was very subjective, and and the the honest truth is that uh, you know, a technology startup looks very different internally than let's say a services company, which would look very different from a manufacturing company.
00:11:14.240 --> 00:11:17.759
And these these frameworks are written in a manner that they're universal.
00:11:17.840 --> 00:11:25.440
Like you could take them and apply them in any context, and and therein lies part of the problem because then you don't know what it means for me specifically.
00:11:25.679 --> 00:11:26.879
And somebody needs to do that.
00:11:26.960 --> 00:11:31.679
And what we had to do at the time was we we hired a consultant to help us sort of make sense of it all.
00:11:31.759 --> 00:11:41.679
Uh, the second problem that was there is even if you did understand what needs to happen, uh actually doing it seemed like a lot of manual work.
00:11:41.840 --> 00:11:45.440
Uh so uh the people were supposed to actually audit you.
00:11:45.600 --> 00:11:59.120
Uh, they're literally at the end of the day, proving to them that you're doing the right thing was about passing pieces of paper, uh, a screenshot, a spreadsheet, uh a PDF, and and you literally like uh doing the right thing was one part.
00:11:59.200 --> 00:12:10.320
Uh, but then uh, you know, after doing that, taking evidence of all of that and then then showing it to them, and and they may or may not get what they want, which means they come back to you and then you're doing that whole thing again.
00:12:10.480 --> 00:12:16.879
By the time this whole cycle is over, sometimes it becomes stale, and and you're you you know you're back at the horse again and you have to start the whole thing again.
00:12:17.039 --> 00:12:25.840
It just seemed like you know, um, knowing what to do was a problem, then doing the thing itself was a problem, and then proving that you did the right thing itself was another problem.
00:12:25.919 --> 00:12:30.879
It just seemed to be a lot of just manual busy work, and that didn't sit right with me.
00:12:31.039 --> 00:12:34.159
It seemed like the important thing was to do to do the right thing.
00:12:34.399 --> 00:12:47.519
Everything else just sort of automatically falls into place, and especially as a as a young startup, where by definition you have very few resources uh as compared to large companies, and and you really got to pick your
battles to fight.
00:12:47.679 --> 00:12:54.240
This seemed like something where uh you know you were just spending a lot of time and energy and effort and not much coming out of it.
00:12:54.399 --> 00:13:00.879
Long story short, we spent, I think, more than six months and tens of thousands of dollars uh in this entire exercise.
00:13:01.440 --> 00:13:03.440
You know, we barely got through.
00:13:03.679 --> 00:13:11.039
And it just seemed like uh, hey, if we had to do this again next year and year and year after, this was just going to be untenable.
00:13:11.200 --> 00:13:13.919
It didn't seem like a right way of running the process.
00:13:14.000 --> 00:13:20.000
It just was barely put together thing with the duct tape and and it would just collapse at any moment.
00:13:20.240 --> 00:13:20.799
Yeah.
00:13:21.120 --> 00:13:30.080
So you point out that compliance and audits tend to be this point-in-time documentation exercise, the way I understand it from what you just described there.
00:13:30.159 --> 00:13:31.039
And I'd agree with that.
00:13:31.200 --> 00:13:32.559
They do often feel like that.
00:13:32.639 --> 00:13:34.799
I I personally go through one myself, right?
00:13:34.879 --> 00:13:36.000
Through it at a regular basis.
00:13:36.080 --> 00:13:42.799
Our organization is SOC2 compliant, and we too have to go through what is essentially a very heavy documentation process.
00:13:43.120 --> 00:13:55.279
We have a number of practices, because we are a security organization, where I feel that we have an advantage over folks that, you know, maybe it's not intrinsic to their business, but it's not intrinsic to most businesses.
00:13:55.440 --> 00:14:07.519
So, how do you take someone from a point-in-time documentation exercise to something that is meaningful, to something that you can trust?
00:14:09.200 --> 00:14:11.039
Actually, uh, that's a great question.
00:14:11.200 --> 00:14:15.519
And uh, this is what we spent uh most amount of time figuring out as a company.
00:14:15.600 --> 00:14:22.480
Uh, for context, uh, one of the favorite pastimes that we did at the beginning of Sprinter was we used to just go to auditors and say, hey, auditors.
00:14:22.720 --> 00:14:25.279
And uh we were building a product along the way.
00:14:25.440 --> 00:14:32.159
So we got audited about a dozen times, and every time we were sort of dark fooding a product to understand how this actually works.
00:14:32.240 --> 00:14:44.159
Uh, but I think there are fundamentally three things that you need to do right uh in order to sort of go from a place where this becomes like a point-in-time document-based exercise to something that's just the way your business runs.
00:14:44.480 --> 00:14:50.960
The first thing that uh you need to be able to do well is map your program to the actual realities of your environment.
00:14:51.279 --> 00:14:58.000
Every business is very different internally, even though let's say the company that you work at and I work at are both technology
companies.
00:14:58.159 --> 00:15:04.720
I'm pretty sure there are like many differences underneath about the way we use certain tools, what do we use them for?
00:15:04.960 --> 00:15:06.559
The business processes we have.
00:15:06.720 --> 00:15:12.080
Maybe we have some employees that are completely remote, some of them are on site, maybe a hybrid situation.
00:15:12.240 --> 00:15:16.320
And a bunch of these business realities have implications on what your program ought to be.
00:15:16.480 --> 00:15:23.440
Um, and the most important thing to realize is that it's not just about knowing what your program is today, your business realities are changing over time.
00:15:23.600 --> 00:15:34.399
So you might be using, I don't know, let's say you're on AWS today and you realize that some part of your organization needs to ship a new product, or you realize that some service extra needs to be on Azure tomorrow.
00:15:34.639 --> 00:15:35.679
You started that service.
00:15:35.759 --> 00:15:39.120
How does your compliance program know and the auditor know that this change happened?
00:15:39.279 --> 00:15:43.440
Your program could be in a completely different planet as compared to your business realities.
00:15:43.679 --> 00:15:50.720
And the the the first problem that you need to solve is how do you sort of make sure that your program evolves as your business evolves?
00:15:50.960 --> 00:15:56.240
And how do you even set up your program in the first place, which are which is true with your aligned with your business practices?
00:15:56.399 --> 00:16:03.759
And our approach for that at Sprint is to make sure that we talk to your underlying systems instead of depending on humans to tell us this happens.
00:16:04.000 --> 00:16:12.240
So, for example, when Sprinto connects with a bunch of underlying systems, uh, we'll talk to uh AWS and Azure and all the services that you might be using.
00:16:12.320 --> 00:16:15.919
And that's when you start picking up breadcrumbs of hey, something's changed in your environment.
00:16:16.000 --> 00:16:19.840
A new person joined your company, we'll see a trace of that in your HRMS system.
00:16:19.919 --> 00:16:22.480
Um, you started using a new service on AWS.
00:16:22.559 --> 00:16:26.240
We start seeing that within your AWS, and we can ask you, hey, by the way, I see this.
00:16:26.399 --> 00:16:27.519
Is this part of your program?
00:16:27.600 --> 00:16:28.639
What are you using this for?
00:16:28.799 --> 00:16:30.799
And the program sort of evolves on top of that.
00:16:30.960 --> 00:16:32.159
That's step number one.
00:16:32.240 --> 00:16:44.000
Uh, step number two, you need to make sure that uh whatever you are uh, whatever changes that happen to your environment, they uh to be just helping you point out the gaps on a continuous basis.
00:16:44.080 --> 00:16:51.919
It doesn't require a human to look at something, look at a database and say, hey, this doesn't look like it's encrypted and we it should be.
00:16:52.080 --> 00:16:54.320
This doesn't look like it's been backed up, but it should be.
00:16:54.480 --> 00:16:56.480
This is all happening programmatically in SprintO.
00:16:56.559 --> 00:17:06.000
So Sprintto is sort of encoding all the rules that you need to adhere to and automatically and continuously measuring those for you without a human having to uh be in the loop at all.
00:17:06.079 --> 00:17:26.079
Uh, so you're across all the all the entities in your environment that have an implication to your program, directly or indirectly, people, servers, machines, uh, code repositories, whatever you have, Sprinto is continuously monitoring them and telling you that, hey, this is where this thing seems to be out of compliance or it seems to be out of where it's supposed to be.
00:17:26.160 --> 00:17:27.440
And we're telling you that.
00:17:27.599 --> 00:17:30.559
Uh, number three, we're not just telling you this is a problem.
00:17:30.640 --> 00:17:37.680
Uh I think uh one of the common gripes I have with a lot of software is that they just create more homework for humans to do.
00:17:37.839 --> 00:17:44.160
Uh uh and uh then it sort of becomes this game where it's humans feeding the software rather than the other way around.
00:17:44.319 --> 00:17:50.720
Um, so we we're not just uh tell you where the gaps are, we actually go the one step ahead and tell you how you can fix those gaps.
00:17:50.799 --> 00:17:54.559
And in some cases, we have actually have agents that actually fix those gaps for you as well.
00:17:54.720 --> 00:17:55.519
So do that.
00:17:55.680 --> 00:18:08.960
And the last bit, which is uh after doing all of this, we also help you get all of that data, all of the evidence that SprintOS collected behind the scenes in order to do this in a manner that the auditor will be happy with it.
00:18:09.119 --> 00:18:14.880
Because at the end of the day, there's a human at the other end who's looking at all of this and saying everything is okay, not okay, et cetera, et cetera.
00:18:15.200 --> 00:18:18.400
But this again should not be a human process.
00:18:18.640 --> 00:18:32.640
So it's it sort of automatically collects all of these things, puts it in the right format that the auditor can look at it so that they actually can do the job better rather than doing all the chasing around saying that, hey, I don't have this document, this doesn't seem right, you need to rework this, etc.
00:18:32.799 --> 00:18:33.119
etc.
00:18:33.359 --> 00:18:38.240
They can actually spend the time on looking at the data and saying that, okay, this looks good, this looks good, this looks good, and so on.
00:18:39.119 --> 00:18:50.240
In fact, one of the most common things that we see with our auditors is that um if the amount of time that they actually spend on an audit is about 10% of what it would be if they were not using something like Sprinter.
00:18:50.720 --> 00:18:56.160
And the reason that happens is because 90% of the time is just chasing people and
documents.
00:18:56.559 --> 00:18:58.880
The 10% is the actual value adding time.
00:18:58.960 --> 00:19:02.880
The the everything else is just uh you know busy work that happens around it.
00:19:03.039 --> 00:19:05.599
So that's fundamentally how we work our data at the sprinter.
00:19:06.000 --> 00:19:06.400
Interesting.
00:19:06.640 --> 00:19:10.400
One more question, and I promise I'll I'll I'll I'll let Cam get in there.
00:19:10.480 --> 00:19:14.079
I have a bad habit sometimes of just No, let me let me jump in.
00:19:14.400 --> 00:19:15.359
Yeah, you go, you go.
00:19:15.599 --> 00:19:16.480
Well, just one more.
00:19:16.640 --> 00:19:18.400
This one's a thought exercise.
00:19:18.720 --> 00:19:19.759
We're gonna resurrect.
00:19:19.920 --> 00:19:21.279
Cam probably knows where I'm going.
00:19:21.359 --> 00:19:24.319
It's an old thought exercise that we like to ask guests on the show, right?
00:19:24.480 --> 00:19:36.960
But startups do have they have this intrinsic challenge of there's a limited amount of resources, namely time and money, and there are very lofty goals to be reached.
00:19:37.119 --> 00:19:43.440
And so you really have to, it is a constant battle every second of the day to bounce those things.
00:19:43.599 --> 00:19:45.440
So here's the thought exercise.
00:19:45.759 --> 00:19:47.279
You've got a hundred bucks.
00:19:47.519 --> 00:19:48.240
100.
00:19:48.319 --> 00:19:49.599
That's all you've got.
00:19:49.839 --> 00:20:00.960
If the only you had was a hundred dollars, what would you use it for to move the needle in moving away from a simple point-in-time documentation exercise to something more meaningful?
00:20:01.039 --> 00:20:01.359
That's it.
00:20:01.519 --> 00:20:03.039
100 bucks.
00:20:03.759 --> 00:20:05.039
It's a hypothetical.
00:20:05.200 --> 00:20:12.720
In the real world, of course, one would expect that 100 bucks is uh is not really much to do anything, but that's it.
00:20:12.799 --> 00:20:13.759
I've got a hundred dollars.
00:20:13.839 --> 00:20:14.960
What do I do?
00:20:18.319 --> 00:20:24.799
Um actually, uh if you had a hundred dollars a month, let's assume that.
00:20:24.880 --> 00:20:26.799
I'm just gonna stand that a little bit.
00:20:27.839 --> 00:20:30.559
Yeah, every everything is subscription based nowadays.
00:20:30.799 --> 00:20:31.200
I love that.
00:20:31.599 --> 00:20:33.359
Guriff just turned it into$1200.
00:20:35.440 --> 00:20:35.759
Go.
00:20:37.200 --> 00:20:37.839
All right.
00:20:38.000 --> 00:20:52.319
Um, I think the most important thing that I'll do over there is uh, you know, spend 80 of those hundred bucks and just uh making sure um whatever it is that I do at a point in time, um, can I just automate that bit?
00:20:52.400 --> 00:21:03.920
Uh I don't care whether you use something like Sprinter, you use Cloud Code and sort of build your own version of it together, uh, or or just uh you know, in whatever manner that's possible for you.
00:21:04.079 --> 00:21:11.279
Uh and I think the the most important chasm to jump over is that this this doesn't require humans.
00:21:11.440 --> 00:21:14.319
You you said that uh you said a very important point.
00:21:14.480 --> 00:21:18.960
I think the the toughest battle for a startup to fight is which battle to pick.
00:21:19.119 --> 00:21:22.000
There are always a hundred things that go wrong, which is the one that I fix right now.
00:21:22.160 --> 00:21:24.640
And it's a hundred competing for that hundred bucks.
00:21:24.880 --> 00:21:25.200
Yes.
00:21:25.359 --> 00:21:37.359
And I think that the simplest way I look at this is that I I look at doing compliance well as not as a back office operation, but something that actually helps you win more customers.
00:21:37.519 --> 00:21:41.519
So this to me competes with, let's say, your advertising budget.
00:21:41.759 --> 00:21:44.000
Because what you don't want to happen is what you want.
00:21:44.079 --> 00:21:50.720
Like what what I've really seen companies do well is like when they actually do the programs well, they put it front and center on the sales tech.
00:21:50.880 --> 00:21:59.759
So you're you're saying upfront, not at a later point in your sales cycle, saying that, hey, by the way, you know, we we do right by your data, but it's it's upfront front and center on your on your sales.
00:22:00.079 --> 00:22:06.319
Stack where you're saying that hey, uh you know, we treat your data as a first-class citizen, we're going to make it secure and private.
00:22:06.559 --> 00:22:14.400
Here's what we do for it, and and you should be able to make that claim so that this doesn't become uh something that you're just playing defensively, like you can play offensively on that.
00:22:14.640 --> 00:22:24.799
And so I I personally uh I've seen like some of the best startups treat this as like the ad budget rather than thinking of this as a back office budget and just saving time and money.
00:22:24.880 --> 00:22:32.400
So that's the that's mentorship that I do, and then spend all of that money, at least 80% of that money, in just uh you know automating this.
00:22:32.640 --> 00:22:43.519
I don't care how you do it, but but at least as a as a technology startup, where the simplest way to think about it is engineering resources are the most most valuable commodity inside of your company.
00:22:43.680 --> 00:22:49.599
If that's the goal, then I'd try to say how much of that engineering resources are being spent on compliance today and just get it down to zero.
00:22:49.759 --> 00:22:52.960
They should be building product for your business, not worrying about all of these things.
00:22:53.039 --> 00:22:54.240
This should just happen for you.
00:22:54.559 --> 00:22:55.279
Right on.
00:22:56.640 --> 00:22:57.440
That's really good.
00:22:57.519 --> 00:23:00.480
I'm very intrigued so far.
00:23:00.640 --> 00:23:20.160
I have so many questions, but I want to kind of keep hitting on where we're at, and maybe you've already given an example of this,
but let's put let's put the mindset, and I'm sure most of us here deal with, at least you two deal with uh CISOs and CIOs when it comes to purchasing security or even privacy software.
00:23:20.319 --> 00:23:23.200
They're usually the ones that uh give the green light and say yes.
00:23:23.759 --> 00:23:25.359
This is for the CISO listening too.
00:23:25.599 --> 00:23:35.279
How do you move a CISO's mindset from let's get a PDF for the sales team and to let's use this framework to actually harden the infrastructure?
00:23:35.519 --> 00:23:36.720
Does that make sense?
00:23:37.039 --> 00:23:40.079
Yeah, I think that's uh that that's a very important point, Cal.
00:23:40.240 --> 00:23:44.319
And I think uh, which is again goes through the three stages of maturity that I talked about.
00:23:44.400 --> 00:24:02.000
Uh whether you're a CISO or uh, you know, or or somebody who's just like at a senior position in the organization, you sort of climb the Maslow's hierarchy of needs in a way, like in the sense that at the base minimum, what you want to be able to do is arm your sales folks with whatever's necessary for them to build confidence.
00:24:02.319 --> 00:24:03.920
So that's that's what you need to do.
00:24:04.400 --> 00:24:06.079
But you do need to go to the next level.
00:24:06.160 --> 00:24:10.480
And the reason you need to do that is you and your competition and everybody is doing the same thing.
00:24:10.720 --> 00:24:20.319
And what is, in spite of you just being subto-compliant, I've seen many companies still spend weeks and weeks in proving that to their customers.
00:24:20.480 --> 00:24:27.440
So let's say you're suck to compliant, but it's it's rarely that here you show your SOC2 certificate and the company on the other side is, yeah, this looks okay.
00:24:27.599 --> 00:24:33.200
And what ends up happening is they still send you a security questionnaire that goes into you know hundreds, if not thousands of questions.
00:24:33.279 --> 00:24:35.200
I've been at the receiving end of some of those.
00:24:35.359 --> 00:24:39.200
I wouldn't wish them one of my worst enemies, but that's a reality of the space.
00:24:39.359 --> 00:24:39.920
That happens.
00:24:40.000 --> 00:24:46.960
And then tomorrow, God forbid, there is a there's a preach, your name is in the papers for the wrong reasons, uh, and that's such an erosion of trust.
00:24:47.039 --> 00:24:51.599
And you know, there's there's basically uh such a large amount of problems that happen as a result of that.
00:24:51.759 --> 00:25:08.960
So I think um as a as a CISO, uh they're they're reasonably aware that the job isn't just to get a rubber stamp, uh, but the job is to actually make the business more uh more resilient uh and be able to actually prove the fact that they're becoming more resilient to their customers as well.
00:25:09.119 --> 00:25:20.240
So I think uh what the really good CISOs are good at is when they make this jump in maturity from being just compliant to being more
resilient, they're actually able to sell the fact that they are more resilient to their customers as well.
00:25:20.400 --> 00:25:39.440
So just not like, hey, I'm just doing this for internal hygiene reasons or because I'm the good guy and I believe in doing the right thing, but they're actually able to prove to their customers that, hey, by the way, uh we and a bunch of our competitors are all going to tell you that he are software compliant, but by the way, these are the actual things that we do over and over what compliance needs us to do to actually take care of the data.
00:25:39.519 --> 00:25:41.440
And here's a proof points to prove how.
00:25:41.759 --> 00:25:50.799
And when I was saying that these things eventually make it to your sales tech or they make it publicly on your website, that goes a long way uh in actually how can you win more businesses.
00:25:51.039 --> 00:26:01.119
So, in fact, uh really great CSOs are uh, you know, they think about their trust posture as a marketable asset and not just something that helps you check a box.
00:26:01.279 --> 00:26:10.079
And you're now thinking and you're flipping your brain in a manner that you're thinking about this is a this is something that actually helps me get more leads.
00:26:10.319 --> 00:26:14.319
It is actually something that actually helps me expedite my sales cycle.
00:26:14.400 --> 00:26:20.079
So they're actually thinking from a revenue standpoint and not just from a standpoint of hey, it helps me check the box and we are good over there.
00:26:20.160 --> 00:26:26.400
So thinking contracting the revenue cycle, they're thinking building more trust, and and that's the language that good CISOs are able to use.
00:26:26.640 --> 00:26:38.319
I think it was the Levi's CISO, Steve Zaleski, if I remember his name, right, who first framed this phrase that he he basically said, how does this help me sell more genes?
00:26:38.480 --> 00:26:44.640
Uh and his idea about is like I I could do anything within my organization, within my CISO organization.
00:26:44.720 --> 00:26:48.160
If I can't answer this question, you know, it's it's not useful for my board.
00:26:48.319 --> 00:26:55.839
So when I'm going to my CEO, when I'm going to my board and then talking about this, what I really need to answer in one way or the other is how does this help me sell more genes?
00:26:56.160 --> 00:27:00.880
And I think that's a that's an incredibly simple and powerful way of thinking about it.
00:27:01.119 --> 00:27:06.640
So when a CISO goes from you know meeting compliance to becoming more resilient, how does it help me sell more genes?
00:27:06.720 --> 00:27:08.319
Uh and a CISO needs to answer that.
00:27:08.400 --> 00:27:10.319
And there are many ways that CISOs are answering that.
00:27:10.400 --> 00:27:20.880
In fact, one of the things that we do at Sprinto is to be able to arm the CISOs with uh a bunch of things that helps them position and answer this question for their business.
00:27:22.079
--> 00:27:22.880
Love that.
00:27:23.359 --> 00:27:25.680
You said you said sell more genes.
00:27:26.079 --> 00:27:27.920
Yes, fully wise.
00:27:28.319 --> 00:27:33.759
Yeah, as long as your butt looks good and if everybody's butt can look good enough, that's gonna sell more genes for sure.
00:27:34.400 --> 00:27:36.079
You haven't seen my butt.
00:27:37.680 --> 00:27:39.279
Jeans aren't gonna help.
00:27:39.599 --> 00:27:41.599
That's uh thanks for going into that.
00:27:41.680 --> 00:27:43.279
That was that was helpful for me.
00:27:43.440 --> 00:27:47.440
Okay, so we real quick, there's there's the term technical debt.
00:27:47.599 --> 00:27:50.079
Have we ever heard of something called like compliance debt?
00:27:50.160 --> 00:27:50.880
Is there such a thing?
00:27:51.039 --> 00:27:51.839
What what does that mean?
00:27:52.000 --> 00:27:54.400
What what's uh how do we kind of not get there?
00:27:54.480 --> 00:27:57.359
Like, do companies really fake it for years and years?
00:27:57.839 --> 00:28:04.720
So uh it's a very real term, uh, and I don't think it necessarily happens because of companies faking it or because of bad intentions.
00:28:04.799 --> 00:28:14.799
Uh, but I think uh the reality is that the business runs at a certain speed, which is dictated by their environment, the competition, the the revenue needs to go at a certain pace, etc.
00:28:15.200 --> 00:28:19.200
And compliance is traditionally seen as the folks as a department of no.
00:28:19.519 --> 00:28:22.960
They're always saying, Don't do this, this is wrong, this is banned.
00:28:23.200 --> 00:28:28.400
And you know what happens as a result is the business eventually finds a way to circumvent it.
00:28:28.480 --> 00:28:43.519
Like you start doing things without asking or without necessarily ratifying and yes, compliance uh deck happens despite best intentions rather than somebody having any having any malintent, in all honesty.
00:28:43.599 --> 00:28:46.640
Uh, I'm sure there are cases where uh the opposite is true as well.
00:28:46.720 --> 00:28:57.359
But in in majority of the cases that I've actually seen is that everybody means well, uh, but the fact is that the business runs at a certain pace, uh, and compliance isn't just uh you know fast enough to catch up.
00:28:57.599 --> 00:28:59.680
And that's because of a bunch of things that I said.
00:28:59.920 --> 00:29:14.880
Your program is manually run, it's point in time, it's it's it's it's sort of uh divorced from the the business realities that you're happening, and your business realities are changing at such a pace that compliance never got a chance to keep up, and now you're like on just different planets.
00:29:15.200 --> 00:29:36.480
And uh the only way, uh especially as we move into a world where AI is a reality, and what that is only gonna mean is that the amount of software, whether it's built by the business internally or it's it's sort of bought externally, the amount of software that a business is going
to use, it's just going to massively and exponentially increase.
00:29:36.640 --> 00:29:44.079
And what that means is the the gap between the speed at which the business runs and the compliance runs is only going to get wider.
00:29:44.240 --> 00:30:04.000
So if you don't move to a place where your compliance is sort of in sync with the business, it is allows it to run at the same pace, where uh you know different business leaders start looking at compliance as not a way for uh, you know, uh for that that stops them from doing what they really want to do, but it's sort of a way that it actually supports what they're doing.
00:30:04.160 --> 00:30:06.319
This is this gap is only going to get wider.
00:30:06.480 --> 00:30:15.920
And uh I think one of the flips that uh really good CISOs uh are able to do is they're able to sort of position themselves as somebody who helps the business rather than the department of no.
00:30:16.160 --> 00:30:18.559
That's a that's a simplest way to think about it.
00:30:18.720 --> 00:30:24.640
The most common experience that everybody has with the compliance department is the department of no.
00:30:24.960 --> 00:30:29.920
All they seem to do is say, don't do this, this is wrong, uh, this requires this additional thing.
00:30:30.079 --> 00:30:32.640
They keep coming back to us for some documentation, etc.
00:30:32.880 --> 00:30:41.200
So the compliance has to work in a manner where it just happens behind the scenes for you rather than you having to do something specifically for it.
00:30:41.519 --> 00:30:43.920
I think most people in the company want to do the right thing.
00:30:44.079 --> 00:30:54.880
What they don't want to do is the overhead that comes with doing the right thing, which is if if I'm a person uh who runs the HR department or I'm running the customer service department, et cetera, I would like to do the right thing.
00:30:55.119 --> 00:31:02.640
What I don't want is everybody to do, spend 20% of the time filing the right pieces of paper so that you know the compliance team gets what they want.
00:31:02.720 --> 00:31:09.680
So if the compliance team can get what they want, while the business functions do what they need to do, everybody's aligned, everybody's on the same page.
00:31:09.759 --> 00:31:13.200
And that's the only way to deal with the world which is going to be AI first.
00:31:13.279 --> 00:31:20.880
Otherwise, this gap just gets wider and wider until it sort of becomes like termites in a house, where until you figure it out, it's too late.
00:31:20.960 --> 00:31:24.160
Uh you know, you sort of shook the foundation.
00:31:24.799 --> 00:31:35.440
So you have you have a unique perspective going back to your first startup, or I don't maybe you had other startups, but recruiter box, you you were able to grow over 3,500 customers.
00:31:35.599 --> 00:31:41.279
I guess I don't know if you hit the compliance wall and decided what was the turning point there that made you go to that next thing.
00:31:41.359 --> 00:31:49.200
Like you're like, I need I have this other vision for something bigger, or maybe you didn't at the time, but what was that switch there at the end of Recruiter Box?
00:31:50.160 --> 00:31:54.480
Um, so yeah, the uh the answer, uh, to be honest, is closer to the second.
00:31:54.640 --> 00:31:57.839
It didn't occur to me at the time that, hey, I want to do a company about this.
00:31:57.920 --> 00:32:02.880
Uh, you know, as a founder, we started getting asked for compliance of the security questionnaires.
00:32:03.039 --> 00:32:08.480
I did the first thing, which was kick the can down the road as much as I could until it became like a bottleneck.
00:32:08.720 --> 00:32:11.920
At some point, it became clear that hey, we need to do this, we need to buy the bullet.
00:32:12.160 --> 00:32:13.440
And we said, okay, fine.
00:32:13.519 --> 00:32:20.960
So we hired the consultant, like I said, we went around the whole nine yards, we spent months and tens of thousands of dollars on it.
00:32:21.119 --> 00:32:25.119
We we got the compliance eventually, but just weren't happy with the entire process.
00:32:25.200 --> 00:32:29.279
And I think it was a year later or so that we successfully exited the company.
00:32:29.359 --> 00:32:32.160
Uh, you know, uh we sold it to a private equity firm.
00:32:32.319 --> 00:32:37.839
And I was uh, I and my co-founder were uh you know taking a break before deciding what to do next.
00:32:38.000 --> 00:32:41.759
And we had about three or four ideas that we thought you know we could work on.
00:32:41.839 --> 00:32:42.720
This was one of them.
00:32:42.960 --> 00:32:52.000
And I think the the most intriguing part about this idea work for us was that this is one of those boring and sexy problems that nobody wants to touch with a 10-foot pole.
00:32:52.240 --> 00:32:54.400
Uh like nobody wants to think about compliance.
00:32:54.480 --> 00:33:01.359
Uh, you know, but at the same time, it's so valuable in the sense that it actually helps unlock revenue for uh for you as a company.
00:33:01.680 --> 00:33:11.119
So it's it's one of those very unique problems in the sense that it's it's not something that somebody wakes up from the sleep and says, hey, it's an exciting problem to solve.
00:33:11.279 --> 00:33:15.839
Uh uh, neither is uh, but at the same time, it's it's it's a very valuable problem to solve.
00:33:15.920 --> 00:33:29.839
And I sort of uh I remember we what we did was uh you know we had like about 20 interviews with uh other folks uh and just trying to figure out if this is a problem that they really face or is this something that's just in our heads.
00:33:30.000 --> 00:33:33.680
Um and we realized that yes, this was a it was a common enough problem.
00:33:33.759 --> 00:33:38.880
It wasn't something that we just personally faced, it seemed seemed to be something that that others were seeing as well.
00:33:39.039 --> 00:33:43.599
And that's how we sort of slowly gathered the confidence
that hey, this was something that was worth working on.
00:33:43.759 --> 00:33:45.519
So it was a rather gradual process.
00:33:45.599 --> 00:33:49.920
There wasn't like one light bulb moment where it went that, hey, there's a company here.
00:33:50.079 --> 00:33:51.680
It just happened over time.
00:33:52.480 --> 00:33:53.039
Interesting.
00:33:53.279 --> 00:34:11.119
So one of the more fascinating things I I find about uh your organization and your background is you mentioned offline that what you guys spend over a year, year and a quarter or so, just getting audited, going through the audit process, having conversations around it before you wrote the first line of code.
00:34:11.360 --> 00:34:12.880
We wrote the first line of code.
00:34:13.039 --> 00:34:16.079
What was the primary takeaway you had from that exercise?
00:34:17.599 --> 00:34:20.800
So here's the um I think there's some personal background to that.
00:34:20.880 --> 00:34:22.159
So I'll get to that first.
00:34:22.239 --> 00:34:26.880
Uh, you know, as an engineer, the most comfortable thing for me to do is to write code.
00:34:26.960 --> 00:34:34.000
Uh in fact, uh to an extent that it is harmful in the sense that I've been guilty of making a mistake in my previous startup.
00:34:34.079 --> 00:34:38.159
That any problem that the business had, I thought I thought I could code my way out of it.
00:34:38.320 --> 00:34:45.280
Um it was at times an excuse to not be in front of a real customer and actually understand what's what's really wrong.
00:34:45.440 --> 00:34:54.719
Uh maybe what's wrong is not a feature, but uh you know, there's a there's a way we need to change a process about how we deal with the customer or the way we actually take our product to market or how we talk about it.
00:34:54.880 --> 00:34:56.079
There were a bunch of other problems.
00:34:56.159 --> 00:35:02.800
But I I think as an engineer, I'm I'm just happiest when you know I could solve a problem by building more product.
00:35:02.960 --> 00:35:16.239
Um, and one of the uh things that I did, like I was saying, I was I had a break between uh you know selling my previous startup and and starting the next one, is we were just retrospecting on how do we do this better the next time around.
00:35:16.400 --> 00:35:30.000
And one of the promises uh sort of both I and my co-founder made to ourselves was hey, uh, you know, we're gonna do the uncomfortable thing, which is to go and talk to people, talk to businesses, understand if this is a real problem before we write a line of code.
00:35:30.079 --> 00:35:34.159
That was that was going to be like uh it's it's kind of like a pact that we made with ourselves.
00:35:34.400 --> 00:35:35.840
This is what we really wanted to do.
00:35:36.000 --> 00:35:37.360
And that's the reason why.
00:35:37.440 --> 00:35:47.599
Uh, you know, that I I think the the previous version of me, as soon as I realized that, hey, here's an interesting problem that we should go after, it would be
right in front of a uh computer and they say let's let's code away.
00:35:47.679 --> 00:35:52.320
But but we said no, we're gonna actually talk to 20 people, evaluate if this is a real problem.
00:35:52.639 --> 00:35:54.559
There's a book, I don't know if you've come across it.
00:35:54.639 --> 00:35:55.920
It's called The Mom Test.
00:35:56.000 --> 00:35:56.719
Have you read it?
00:35:57.199 --> 00:35:59.760
No, but we'll definitely put that one in the show notes.
00:35:59.840 --> 00:36:00.239
One more time.
00:36:00.320 --> 00:36:01.039
What's the name of the book?
00:36:01.119 --> 00:36:02.719
And do you happen to know the author?
00:36:03.039 --> 00:36:04.719
I don't remember the name of the author.
00:36:04.800 --> 00:36:05.920
It's the mom test.
00:36:06.639 --> 00:36:07.440
The mom test.
00:36:07.840 --> 00:36:09.760
Yes, and it's it's quite a simple book.
00:36:09.840 --> 00:36:10.719
It's a very small book.
00:36:10.800 --> 00:36:13.119
I think it's about 7200 pages.
00:36:13.280 --> 00:36:19.360
Uh and the book is quite simply an engineer's perspective of how to interview prospective customers.
00:36:19.519 --> 00:36:26.719
And the idea and the reason the book is titled the way it is that a lot of customers or prospects, they tend to be nice to you the same way your mom would be.
00:36:26.800 --> 00:36:31.920
You're trying to do something, they all want to be encouraging, they want to be polite, and they say that, hey, this sounds like a great idea.
00:36:32.000 --> 00:36:35.840
But if you do build that and you take it to them, they won't necessarily buy that off you.
00:36:36.000 --> 00:36:37.679
So that's when the reality hits.
00:36:37.840 --> 00:36:42.960
And how do you really understand if what you're building is valuable enough before actually building that?
00:36:43.039 --> 00:36:51.840
And how you actually do this in a manner where people are not just humoring you or just being nice to you, uh, you know, to really realize that you're solving a problem.
00:36:51.920 --> 00:36:58.480
And I came across that book uh during the break, and it had a big influence on me as to how I wanted to go about solving this.
00:36:59.519 --> 00:37:02.719
So that was that was an impure.
00:37:02.960 --> 00:37:10.159
Yeah, so that was one of the um uh you know turning points in the way how I wanted to approach the business.
00:37:10.320 --> 00:37:21.280
Like I sort of did the the most comfortable thing last, which was writing code and building the product, because that I won't say it was easy, but it was still something that I backed myself to be able to do well.
00:37:21.840 --> 00:37:26.079
Gabe, you got anything else before we head to the uh some of the fun questions?
00:37:26.719 --> 00:37:28.800
No, no, I want to be respectful of time.
00:37:28.880 --> 00:37:30.400
This has been an amazing interview so far.
00:37:30.639 --> 00:37:31.679
I'll be honest, Gresh.
00:37:31.760 --> 00:37:33.760
I I 100% want to talk to you offline.
00:37:34.079 --> 00:37:38.639
Some of the things that you're saying resonate with me deeply for what we do as an organization.
00:37:38.800 --> 00:37:43.199
And I I want to make sure we connect after this and have a deeper conversation.
00:37:43.519 --> 00:37:46.960
But before that, you've got to get through the hot seat.
00:37:48.719 --> 00:38:08.159
Well, well, actually, before the hot seat, uh Gresh, if there's anything that we didn't touch on about Sprinto uh that you want to talk about, anything that you want to mention, or if you just want to mention, you know, where folks can find you and find or connect with Sprento or yourself or anything like that that you want to kind of call out.
00:38:09.440 --> 00:38:13.519
Uh yeah, I won't take much of your time, but uh quite simply we are at Sprinto.com.
00:38:13.599 --> 00:38:15.519
I am at Griesh at Sprinter.com.
00:38:15.599 --> 00:38:16.480
So very easy to remember.
00:38:16.559 --> 00:38:21.360
If there's anything you would like to check out about us or want to write to me, please feel free to free to do that.
00:38:21.519 --> 00:38:32.079
One of the things that uh we didn't necessarily talk a lot about, but I'm increasingly passionate about is we passingly mentioned about this thing about software creating more homework for humans.
00:38:32.320 --> 00:38:34.239
And I and I deeply feel that.
00:38:34.400 --> 00:38:44.880
You know, I've I've seen and used a lot of software, and then most of the times it's uh you know it feels like we are feeding the software, you're just putting things in the software in the right format, yeah, uh, and just storing it for us.
00:38:44.960 --> 00:38:48.159
And our vision with Sprinto is to make it more autonomous.
00:38:48.239 --> 00:38:52.400
And what I mean by that is that software should be doing work for you rather than the other way around.
00:38:52.559 --> 00:38:58.000
You shouldn't be working for the software, and that's something that we are uh we take very seriously at Sprinto now.
00:38:58.079 --> 00:39:08.320
You know, the leaps that have happened in AI actually enable us to build something where you could go as a company from describing business objectives that, hey, I want to become compact or I want to become more resilient.
00:39:08.480 --> 00:39:22.320
And Sprinto finds a way for you to get there rather than uh you know it just keeping on asking you that, hey, uh tell me this information, put this in this box and put this into that pigeonhole and so on and so forth, uh, which I think is an older way of doing it.
00:39:22.400 --> 00:39:27.199
So I'm really excited about you know how trust management is going to work in the future.
00:39:27.280 --> 00:39:34.800
Uh, and I believe like every company under the sun is going to need this, and the only way to make it more accessible is by making it more autonomous.
00:39:34.960 --> 00:39:44.079
Uh, you can't do that by uh saying that here's a software, here are the boxes in it, and here's what you need to feed in those
boxes for me to get started.
00:39:44.960 --> 00:39:45.760
That's great.
00:39:46.159 --> 00:39:52.719
That actually rolls into my first hot seat question, which I think you kind of answer, but this is just fun.
00:39:52.880 --> 00:40:04.480
So on a scale of one to the Terminator, how do you think AI is actually going to help with compliance, or is it just going to generate more paperwork for us in the future?
00:40:05.679 --> 00:40:08.639
We actively working on making sure it's not more paperwork.
00:40:08.719 --> 00:40:12.559
Uh, you know, I I'd really, really hate to be in a world where it just creates more paperwork for us.
00:40:12.719 --> 00:40:15.599
If Sprinter does what it is supposed to do, uh, we should not get there.
00:40:15.760 --> 00:40:19.280
It should actually be a lot less less paperwork.
00:40:19.840 --> 00:40:27.840
Is there one app in your phone that you use frequently or daily or weekly or whatever that you dislike?
00:40:28.639 --> 00:40:30.320
But you have to use it.
00:40:32.719 --> 00:40:33.840
But I have to use it.
00:40:34.000 --> 00:40:38.960
Yeah, let me just quickly alarm clock is a is a very viable answer.
00:40:39.199 --> 00:40:40.639
That's a good one, yeah.
00:40:41.199 --> 00:40:43.280
Yeah, that's that's probably not a bad answer.
00:40:43.519 --> 00:40:47.760
I think that in the calendar is is probably the uh the one that I use a lot.
00:40:48.000 --> 00:40:51.920
I just feel like it it could work differently, uh though I'm not really sure how.
00:40:52.159 --> 00:40:55.280
But but the way it currently works is just extremely hard.
00:40:55.360 --> 00:41:02.960
It it again leaks of the problem where it just shows you stuff and you can put stuff in the right box, but it is actually not helping you manage your day.
00:41:03.039 --> 00:41:05.360
Uh and I wish that could become a little better.
00:41:05.679 --> 00:41:07.280
Yeah, that's a good answer.
00:41:07.599 --> 00:41:17.519
If you could uh sit down at a private dinner with any guest, any famous person, dead or alive, this really shows us who you kind of are underneath.
00:41:17.599 --> 00:41:19.760
What who would you have at that dinner with you?
00:41:21.039 --> 00:41:21.599
Wow.
00:41:21.840 --> 00:41:25.280
Uh that's a tough one.
00:41:27.519 --> 00:41:28.320
It's tough.
00:41:28.480 --> 00:41:28.719
Right.
00:41:29.039 --> 00:41:30.960
We did see the answer is gonna be said hot.
00:41:31.840 --> 00:41:35.679
Yeah, I think the answer is gonna be somebody in the technology field.
00:41:35.760 --> 00:41:42.239
And I think, yeah, if I had to pick one in a short span of time, I I'd probably pick this guy called Rich Hickey.
00:41:42.320 --> 00:41:47.760
He is the creator of this very esoteric programming language called Clojure.
00:41:48.000 --> 00:41:52.880
Uh, and I feel like it's it's pretty much the best thing that's that a programmer has ever built.
00:41:53.039 --> 00:42:05.280
And pardon me for picking something that's uh that's that's not something
that's out there in the uh, you know, as popular, but I really feel like uh he has some really, really good ideas about how software ought to get built.
00:42:05.440 --> 00:42:11.039
You know, I I've lapped up every talk that he's ever given, and he's kind of semi-retired right now or completely retired.
00:42:11.119 --> 00:42:11.440
I don't know.
00:42:11.599 --> 00:42:18.800
He's he's not really so much in the public domain, but but I would love to get an hour of his time just to riff about how to build software.
00:42:18.960 --> 00:42:23.440
What's uh you know, what does he think the future is gonna look like, especially with AI?
00:42:23.840 --> 00:42:24.639
That's really cool.
00:42:24.800 --> 00:42:26.800
And just a coincidence, we have him on the other line.
00:42:26.880 --> 00:42:27.599
Let's bring him in.
00:42:28.719 --> 00:42:29.840
He's not he laughed.
00:42:30.000 --> 00:42:31.039
I tell you what.
00:42:33.519 --> 00:42:36.400
I'm gonna reach out to him, see if we can't have you both back on the show.
00:42:36.800 --> 00:42:38.000
Seriously, that sounds awesome.
00:42:38.079 --> 00:42:39.039
What was his name again?
00:42:39.360 --> 00:42:40.239
Rich Hicking?
00:42:40.480 --> 00:42:42.960
R-I-C-H-I-C-K-E.
00:42:44.719 --> 00:42:45.679
Shout out to Rich.
00:42:45.920 --> 00:42:47.920
Okay, we'll try to we'll try to reach out to him.
00:42:48.000 --> 00:42:48.480
That's awesome.
00:42:48.639 --> 00:42:51.280
One more quick fun one before you we let you go.
00:42:52.719 --> 00:42:54.239
This is a pretty important question.
00:42:54.320 --> 00:42:55.920
We we ask a lot of our guests this.
00:42:56.079 --> 00:43:05.679
With uh in regards to toilet paper in your bathroom, is the toilet paper on the bottom or the top to grab it from?
00:43:09.039 --> 00:43:11.360
It's it's about I don't know what you call it.
00:43:11.440 --> 00:43:13.679
Like it's it's about this height if I'm on the toilet.
00:43:13.840 --> 00:43:17.679
Like sort of like is the is the um is the toilet paper on the top.
00:43:18.000 --> 00:43:21.920
Do you put it on the top or bottom?
00:43:22.159 --> 00:43:23.119
Like do you grab it from underneath?
00:43:27.440 --> 00:43:29.599
I have no idea, honestly.
00:43:31.440 --> 00:43:32.320
You know what?
00:43:32.559 --> 00:43:38.960
That explains Yeah, that's a good answer because it means you don't pay attention to silly things like that.
00:43:39.119 --> 00:43:48.719
And you're obviously, you know, you're a serious uh too busy to to be that focused on whether or not the total paper is put on the right way in the role.
00:43:48.800 --> 00:43:49.360
That's good.
00:43:49.519 --> 00:43:50.079
Yeah.
00:43:50.320 --> 00:43:56.960
No, I think uh yeah, that's that's definitely much lower in the in the hierarchy of things, including the stuff that I wear.
00:43:57.119 --> 00:43:59.760
My wife just puts those things there, I just picked what's at the top.
00:44:00.159 --> 00:44:02.480
And and that's that's what I'm waiting for today.
00:44:05.039 --> 00:44:08.800
Well, uh Garish, this has been this has been awesome.
00:44:08.960 --> 00:44:11.760
Seriously, thank you for taking the time to join the show.
00:44:11.920 --> 00:44:17.920
Thanks for what you're doing, what you're trying to do for companies and for compliance.
00:44:18.079 --> 00:44:20.639
Uh I mean we need more companies like this.
00:44:20.719 --> 00:44:25.599
We need more, you know, founders that are passionate and also technical.
00:44:25.840 --> 00:44:29.440
Um so thanks for what you do and really appreciate you.
00:44:29.679 --> 00:44:30.320
Thanks, Cameron.
00:44:30.480 --> 00:44:30.880
Thanks, Kate.
00:44:31.440 --> 00:44:32.320
I really enjoyed being here.
00:44:33.119 --> 00:44:33.599
Thanks, Fox.
00:44:33.760 --> 00:44:35.360
Uh it was it's really enjoyable to be here.
00:44:35.440 --> 00:44:36.559
Uh love the conversation.
00:44:36.639 --> 00:44:36.960
Thanks.
00:44:37.119 --> 00:44:38.400
Thanks for having me.