
From CIO to CBO: Lenin's Journey Through Tech Evolution and the AI Revolution
Join us for an exclusive conversation with Lenin, CBO of Atomic Work, as he shares insights on the evolution from IT to business-driven technology, AI adoption challenges, and why most organizations will become obsolete by next decade.
Summary
Lenin, Chief Business Officer at Atomic Work and founder of the Global CIO Circle, shares his unique perspective on technology evolution, having transitioned from CIO to startup executive. In this candid conversation, he discusses the misconceptions between IT and business teams, why CIOs are risk-averse, the importance of building relationships over transactions, and his bold prediction that most existing organizations will become obsolete within the next decade. Lenin also reveals his networking secrets, explains why he maintains an open calendar, and offers actionable advice for founders navigating the AI era.
Description
This episode features an in-depth conversation with Lenin, a technology executive who has successfully bridged the gap between IT operations and business strategy. Currently serving as CBO at Atomic Work, Lenin brings three decades of experience across startups and enterprise organizations.
Key Topics Covered:
The evolution from "making technology work" to "making business work with technology"
Why CIOs appear risk-averse and the real constraints they face
The critical importance of trust in new technology adoption
Lenin's networking philosophy: always offer help first
Why most existing organizations will become obsolete by 2035
The three eras of technology: compute, processing, and intelligence
How AI is creating superhuman capabilities and new opportunities
Practical advice for founders building in the AI space
The Global CIO Circle vision and community building
Lenin's Background:
Lenin has held leadership positions across multiple functions - from data analytics to IT operations to business strategy. His unique journey from CIO (buyer of technology) to CBO (seller of technology) provides rare insights into both sides of enterprise technology adoption. He's also an active angel investor, startup advisor, and founder of the Global CIO Circle, bringing together 200+ CIOs from the world's largest companies.
This conversation offers practical wisdom for founders, technology leaders, and anyone interested in understanding how AI is reshaping business and organizational structures.
Transcription
1
00:00:00,000 --> 00:00:07,080
Challenge for these existing organizations by
next decade, most of these will become obsolete.
2
00:00:07,080 --> 00:00:11,620
With AI, there's just so much opportunity on the
table, which comes with a little bit of risk
3
00:00:11,620 --> 00:00:17,760
taking. So now we're at the point of creating
superhuman capabilities. Is AI actually driving
4
00:00:17,760 --> 00:00:23,060
some business values? What AI is giving right now
for people is to really rethink about the
5
00:00:23,060 --> 00:00:27,520
opportunity. It's the same old problem, your
solution. And that's what tech debt is. You're in
6
00:00:27,520 --> 00:00:31,880
the right era with the right time. If you're
building something now, you're building for the
7
00:00:31,880 --> 00:00:40,500
future. Hi, Lelein. Really nice to have you with
us. We're doing this for the first time, but you
8
00:00:40,500 --> 00:00:45,960
know, the idea is that, you know, like you've seen
the world in a lot deeper ways than we ever could
9
00:00:45,960 --> 00:00:50,620
have in terms of your experience across so many
different companies, including startups,
10
00:00:50,620 --> 00:00:58,420
across functions all the way from data analytics
to IT to now in your role as CBO of Atomic Work. And as
11
00:00:58,420 --> 00:01:02,800
a startup, we're just now trying to enter that
world, right? So we want to see the world from your
12
00:01:02,800 --> 00:01:09,720
perspective in sort of like quick, short 10
questions, right? We'll, Harsh will try to keep
13
00:01:09,720 --> 00:01:18,140
score to 10 so that we can manage time. But that's
sort of the idea. Yeah, no, thank you for having me.
14
00:01:18,140 --> 00:01:26,720
And I'm very excited for what it is that Trupea is
doing and happy to be here to engage with you guys.
15
00:01:26,720 --> 00:01:32,100
Great. I think, you know, the first question that
we all had on our minds is that yours is actually one
16
00:01:32,100 --> 00:01:36,760
of the most interesting career trajectories
we've seen, like in how your roles have evolved.
17
00:01:36,760 --> 00:01:42,100
And, you know, you've seen the IT side of the world,
and now you've seen the business side of the world,
18
00:01:42,100 --> 00:01:49,260
right? So what are some misconceptions that these
two sides of the world have about each other? Oh,
19
00:01:49,260 --> 00:01:57,620
great question. I think when I was in IT, in the
olden days when we first entered, it was not about
20
00:01:57,620 --> 00:02:03,440
business, it was more about technology. So we
wanted to make the technology work because, you
21
00:02:03,440 --> 00:02:09,880
know, everything was always about how to make
technology function for the business. But it was
22
00:02:09,880 --> 00:02:21,420
predominantly core is IT is segregated in its own
space. It was always thought as IT always have to do
23
00:02:21,420 --> 00:02:29,800
something. And and and the business is always
looking for IT to do something. So it's more like an
24
00:02:29,800 --> 00:02:39,220
enabler to some degree. So for the last three
decades, when the first time IT has become, you
25
00:02:39,220 --> 00:02:47,820
know, an important part to drive technology in the
organizations, it was not meant for employees to
26
00:02:47,820 --> 00:02:54,300
become highly productive or anything like that.
The idea was just make it work. Technology should
27
00:02:54,300 --> 00:03:00,200
work. That's the idea. And CIOs and others, all of
the people who are always building things and
28
00:03:00,200 --> 00:03:05,080
making things work. And if these things don't
work, they were like, okay, that's all I can do.
29
00:03:05,080 --> 00:03:12,320
Right. So there's a limitation. But what's
happening now that the tech is advanced, we as
30
00:03:12,320 --> 00:03:21,160
humans have matured, adopting to the changes,
learning faster, it's becoming more business
31
00:03:21,160 --> 00:03:26,940
driven. So that means if you bring a technology, it
has to be business friendly. It has to be employee
32
00:03:26,940 --> 00:03:33,600
friendly. It has to be justified for what it is
worth in the organization. Why do you need it? So
33
00:03:33,600 --> 00:03:41,400
that maturity also came with the technology
adoptions and also the evolution of technology
34
00:03:41,400 --> 00:03:48,800
itself made us really see the value of why we need
something in the organization to begin with. So
35
00:03:48,800 --> 00:03:56,640
I'm kind of seeing the trend of evolution of making
technology work to now making business with the
36
00:03:56,640 --> 00:04:04,860
technology to run. So we kind of went from crawling
to walking to now running. So eventually we'll
37
00:04:04,860 --> 00:04:10,900
also be flying with technology. So I think that is
where we are in the AI age, I would say as a maturity.
38
00:04:10,900 --> 00:04:17,920
Got it. And I think the other interesting angle
here is that you've also seen both sides of the coin
39
00:04:17,920 --> 00:04:25,040
in terms of you being a CIO as a buyer of technology,
which is now you are CBO of a startup and you need to
40
00:04:25,040 --> 00:04:30,840
sell technology. So what are you seeing in terms of
evolving vendor relationships and how has your
41
00:04:30,840 --> 00:04:41,520
understanding changed about that? Yeah, so even
though I was a buyer and on the one side now I am on the
42
00:04:41,520 --> 00:04:49,320
other side to sell, the concept for me was the same
in the sense that you need to understand the buyer
43
00:04:49,320 --> 00:04:55,600
and if you're selling, that's important for you.
But if you are a buyer, you need to understand the
44
00:04:55,600 --> 00:05:02,660
seller because a negotiation of whatever you're
buying starts from the get go of why you need that
45
00:05:02,660 --> 00:05:09,940
and all of that stuff. So me being on one end really
helped. So I was only worried about why I am buying
46
00:05:09,940 --> 00:05:15,840
it for the organization. I never cared about the
other side because initially it was all about a
47
00:05:15,840 --> 00:05:20,100
transaction. But then when you start building a
relationship with people who are actually
48
00:05:20,100 --> 00:05:29,160
building those, the perception changed. So when
you are a startup and you've grown into a larger
49
00:05:29,160 --> 00:05:35,340
organization, your understanding is a bit
different from people who are actually
50
00:05:35,340 --> 00:05:40,860
entrenched themselves in a larger organization
might not be thinking what the other person is
51
00:05:40,860 --> 00:05:45,480
really going through. Why are they selling? Your
opinions might be different. I think why I'm
52
00:05:45,480 --> 00:05:52,640
advocating buyers now to spend more time with the
sellers, not for the transaction purposes, but
53
00:05:52,640 --> 00:05:58,380
building a relationship that is going to help them
understand why they're building something and
54
00:05:58,380 --> 00:06:05,600
how what they're building is actually going to be
useful to you, not now, but into the future. See the
55
00:06:05,600 --> 00:06:12,940
problem when you're buying a matured software,
you don't actually care about how it is built, who
56
00:06:12,940 --> 00:06:17,960
built it. Nobody really cares about it because you
just go and buy it and then use it and then that's it.
57
00:06:17,960 --> 00:06:26,500
There is no relationship. But when you're buying
software now from a founder in early stages, you
58
00:06:26,500 --> 00:06:35,720
now have to do a lot of scrutiny and understanding
who the founder is, how much money they have,
59
00:06:35,720 --> 00:06:43,200
viability, sustainability, growth and why are
they doing it, can I rely on them. So the CIO's
60
00:06:43,200 --> 00:06:50,100
tendency is typically, it's just risk covers.
Nobody wants to really buy something risky. And so
61
00:06:50,100 --> 00:06:57,920
now coming on the other side, I'm actually now
applying what I used to think in trying to work with
62
00:06:57,920 --> 00:07:04,020
CIOs, why it is important for them to build a
relationship with the founders and so that you
63
00:07:04,020 --> 00:07:09,100
don't have to really wait until the software
becomes better, where you're only doing a
64
00:07:09,100 --> 00:07:15,440
transaction. But if you now build that
relationship, you might also become an advisor.
65
00:07:15,440 --> 00:07:24,340
You could also help them grow and the credit will
become where you're giving back something and you
66
00:07:24,340 --> 00:07:29,180
could also grow with it. Also, there's a
satisfaction that I used to have whenever I used to
67
00:07:29,180 --> 00:07:35,580
help a founder before and going on the other side
now I'm expecting the CIOs to have the similar
68
00:07:35,580 --> 00:07:42,620
thing and that's something that I'm advocating
through my being a CBO and doing this start
69
00:07:42,620 --> 00:07:48,740
leadership and sitting down with the CIOs and
explaining to them why they should give time to the
70
00:07:48,740 --> 00:07:55,960
founders and learn a little bit more about why
they're building it and how that is going to help
71
00:07:55,960 --> 00:08:02,880
you. Absolutely, I can completely attest to that.
Like Lennon has actually been that conduit almost
72
00:08:02,880 --> 00:08:10,120
for the startup world to actually interface with
the CIO world and them getting to understand each
73
00:08:10,120 --> 00:08:15,780
other like you're saying. I think one of the things
like you mentioned, the CIO role is typically
74
00:08:15,780 --> 00:08:22,460
meant to be risk averse but with AI there's just so
much opportunity on the table and they obviously
75
00:08:22,460 --> 00:08:29,800
have to be open to innovation which comes with a
little bit of risk taking. So how are you seeing
76
00:08:29,800 --> 00:08:36,539
CIOs actually tackle that? Like is there actually
still a lot of risk aversion or are they open to? So
77
00:08:36,539 --> 00:08:43,200
what happened two decades ago when everything is
installed on the computers, there was nothing
78
00:08:43,200 --> 00:08:51,860
really leaving very small network controlled.
You do not have these many problems because the
79
00:08:51,860 --> 00:09:02,340
maturity or opportunity for anyone to really
penetrate those type of networks was hard. Once it
80
00:09:02,340 --> 00:09:12,480
has become open web, open network, global, we've
also opened a lot of doors that we didn't know open.
81
00:09:12,480 --> 00:09:18,560
So when the organizations are now introducing
technology, it's not about just use of the
82
00:09:18,560 --> 00:09:24,080
technology, it's also protecting your own
organization because by introducing that
83
00:09:24,080 --> 00:09:29,600
technology now you're introducing certain risk
that you don't know and that's why CIOs are more
84
00:09:29,600 --> 00:09:36,020
cautious around not just because they don't like
it, even if you like it sometimes you can't employ
85
00:09:36,020 --> 00:09:43,100
it, you can't deploy it and that's not because they
don't want it, it's just because they can't
86
00:09:43,100 --> 00:09:51,000
because of the restrictions, certain
guidelines, governance, compliance, so many
87
00:09:51,000 --> 00:09:59,340
things that needs to be part of the ecosystem that
is really why the CIOs are more methodical,
88
00:09:59,340 --> 00:10:05,700
conscious around why they should introduce
certain technology in the organization and
89
00:10:05,700 --> 00:10:11,040
that's really the thing but that is by nature
because their jobs are on the line if they
90
00:10:11,040 --> 00:10:18,560
introduce certain things, they have to justify
and that's one of the other reasons so many things,
91
00:10:18,560 --> 00:10:27,400
policies, other things were introduced to help
the CIOs to make those decisions not by taking
92
00:10:27,400 --> 00:10:32,340
ownership of all of these things on their own,
instead they're bringing an whole ecosystem to
93
00:10:32,340 --> 00:10:37,420
support them so that's where procurement comes
in, security comes in, the infrastructure teams
94
00:10:37,420 --> 00:10:43,740
come in, everybody is evaluating the viability of
a solution in so many different things,
95
00:10:43,740 --> 00:10:48,820
eventually the decision is going to be made. Makes
sense, makes sense and like when it comes to like
96
00:10:48,820 --> 00:10:53,160
viability, right, like that point around, you
know like there's still a lot of conversation
97
00:10:53,160 --> 00:11:01,320
around okay at the enterprise level is AI just good
enough for pilots or is it actually driving some
98
00:11:01,320 --> 00:11:09,660
business value so what are you seeing? So I was as I
was mentioning earlier the maturity is really
99
00:11:09,660 --> 00:11:17,840
critical, the maturity of both is critical, the
buyer and the seller, what is important in newer
100
00:11:17,840 --> 00:11:27,040
technologies is trust, trust that it works, trust
that it is secure, trust that it is reliable and
101
00:11:27,040 --> 00:11:34,720
also is going to make things better than worse and
that takes time, there is going to be hesitation,
102
00:11:34,720 --> 00:11:40,320
there is definitely going to be some sort of good,
bad and ugly situations of people taking the risk
103
00:11:40,320 --> 00:11:47,280
that didn't pay off, again if you make those
decisions with certain bad rails then people who
104
00:11:47,280 --> 00:11:52,980
are in that process protected on both sides,
otherwise things can be worse, right. So yeah I
105
00:11:52,980 --> 00:11:59,860
think more about what use case is because of early
stages and then what return on that investments
106
00:11:59,860 --> 00:12:06,900
that you're making then not everything is about
ROI, so that's why sometimes people talk about
107
00:12:06,900 --> 00:12:17,580
ROI, is this really a growth driver? How are you
going to justify employee empowerment? How are
108
00:12:17,580 --> 00:12:24,240
you going to justify something that is not
tangible for you to measure at this early? Are you
109
00:12:24,240 --> 00:12:29,360
going to sit out or are you going to try? That all
depends on the organizations and that's why I
110
00:12:29,360 --> 00:12:35,020
think startups need to understand that if a buyer
is hesitant not because they don't want it,
111
00:12:35,020 --> 00:12:40,620
potentially they just can't and what is that
factor is really important and that's why
112
00:12:40,620 --> 00:12:49,840
choosing the right ICP or in this case your ideal
customer and also product market fit what you're
113
00:12:49,840 --> 00:12:56,260
trying to work with, making it easy for them to
experiment, making it easy for them to use is
114
00:12:56,260 --> 00:13:01,740
really really critical and then learn fast and
then deploy fast. Like understand what matters to
115
00:13:01,740 --> 00:13:06,800
them and then deliver backwards. I'd like to
switch gears a little bit because there's this
116
00:13:06,800 --> 00:13:13,840
other side of you which is also very fascinating
about pulling together so many different people
117
00:13:13,840 --> 00:13:21,980
from different spheres of knowledge expertise
and just bringing them together on shared goals.
118
00:13:21,980 --> 00:13:29,640
So what's your vision for this global CIO circle
and how did it come about? I've always had this
119
00:13:29,640 --> 00:13:36,740
notion of bringing people together. I like
socializing, I like networking. So when I started
120
00:13:36,740 --> 00:13:44,620
interacting with founders, when I became an
investor, an advisor and I thought opportunity
121
00:13:44,620 --> 00:13:52,720
came not because somebody asked me, it's just
because I asked people like how can I do this and how
122
00:13:52,720 --> 00:13:59,900
can I become an investor, how can I advise. So same
thing is happening for people who did not have that
123
00:13:59,900 --> 00:14:04,580
opportunity to do and they didn't even know that
there is an opportunity exists for them to become
124
00:14:04,580 --> 00:14:09,360
an advisor to startup, they can invest into
startups. There is this notion of investing
125
00:14:09,360 --> 00:14:14,940
startups is a VC's business, let them do it but then
you are sitting out and everything else is
126
00:14:14,940 --> 00:14:20,260
happening around the world and how are you going to
get involved in some of these things and so I think
127
00:14:20,260 --> 00:14:25,780
there's a way to do that and so I wanted to really
understand what that is. So once I figured that
128
00:14:25,780 --> 00:14:33,140
out, I wanted to bring it to the people and that's
how it started. Initially we were just doing with
129
00:14:33,140 --> 00:14:40,540
one or two founders, it looks like this butterfly
loves the conversation that we're having here.
130
00:14:40,540 --> 00:14:50,340
She wants to be a part. So what happened is that
network started to create around me and once I came
131
00:14:50,340 --> 00:14:58,460
out from quotient I've kind of decided to go into it
just as a hobby in front of mind basically said
132
00:14:58,460 --> 00:15:04,980
let's start a syndicate and to bring and then start
helping startups and I was doing one-on-one but
133
00:15:04,980 --> 00:15:13,340
now it had become a movement and that picked up and
we started investing, advising and it picked up
134
00:15:13,340 --> 00:15:21,420
further and then you know then I started
syndicating it and now why not just create a circle
135
00:15:21,420 --> 00:15:31,000
and like-minded people that want to engage
founders and become advisors, angel invest and
136
00:15:31,000 --> 00:15:40,080
those are all the you know circle formation was. We
did it in a smaller way last year and there was
137
00:15:40,080 --> 00:15:46,500
significant interest so then I decided to create
the circle, why not bring all of them together and
138
00:15:46,500 --> 00:15:52,160
bring the portfolio of companies and VCs and who
share the same interests to come and that's what
139
00:15:52,160 --> 00:15:57,220
Global CIO Circle is. Yeah like we are also really
excited about being a part of this like we keep
140
00:15:57,220 --> 00:16:02,520
looking for such platforms right like where we can
actually tell people about what we're doing and
141
00:16:02,520 --> 00:16:11,400
how we're already helping CIOs so like 200 of the I
think 200 of the world's biggest companies CIOs
142
00:16:11,400 --> 00:16:18,800
are coming together here also it's really really
really interesting. So you know like one thing
143
00:16:18,800 --> 00:16:24,400
that the team was also really fascinated about was
the fact that you seem to know everybody and
144
00:16:24,400 --> 00:16:31,240
anybody right like you have such a wide and deep
network so what's the secret sauce there like how
145
00:16:31,240 --> 00:16:37,380
is it that you're able to build such a sustainable
relationships with so many different people?
146
00:16:37,380 --> 00:16:45,140
Yeah I mean it's not easy so it's a lot of energy a lot
of time goes into it but I did put it you know as part
147
00:16:45,140 --> 00:16:51,340
of my thing I always like to have it and I feel like
sometimes I'm not actually doing enough
148
00:16:51,340 --> 00:17:00,200
networking but I think what is important when you
when it becomes part of you you don't feel like
149
00:17:00,200 --> 00:17:08,240
you're doing it and it just naturally happens and
that is really what is going on now I think it's the
150
00:17:08,240 --> 00:17:19,880
LinkedIn ecosystem read you know had this vision
that the network impact from your first degree to
151
00:17:19,880 --> 00:17:26,339
second degree to third degree and that is really
where we are right now in LinkedIn evolution is
152
00:17:26,339 --> 00:17:34,980
really now paying off because all of those decade
to two decade old people who have been on LinkedIn
153
00:17:34,980 --> 00:17:43,480
that have not done anything with it are still the
same but those who understood how networking
154
00:17:43,480 --> 00:17:51,060
really works reaching out to people and offering
them help is the first thing to do and I always
155
00:17:51,060 --> 00:17:56,740
offered my help and I basically said hey you need
anything I never sought out anything else and
156
00:17:56,740 --> 00:18:02,600
that's how I started building my network
obviously the payback period will come where I
157
00:18:02,600 --> 00:18:08,780
could really ask for when I need something as a
favor but usually it's what's most important
158
00:18:08,780 --> 00:18:18,220
thing about this is when people understand you you
don't have to explain too much right the purpose is
159
00:18:18,220 --> 00:18:26,880
very simple the reason to network is very simple
and at some point they also see the value and
160
00:18:26,880 --> 00:18:32,380
self-explanatory yeah and I think that is the
reason the circle is evolving and that is the
161
00:18:32,380 --> 00:18:37,920
reason people are wanting to come to the network
and also to these events for me it's all about
162
00:18:37,920 --> 00:18:45,100
founders and I tell the same thing to all of the
executives joining we're here to just make sure
163
00:18:45,100 --> 00:18:52,880
that they benefit from us because we've seen it
they haven't how can we give back and in return you
164
00:18:52,880 --> 00:19:01,020
advise and you get to an opportunity to invest when
there is an opportunity to invest if not we'll
165
00:19:01,020 --> 00:19:08,100
continue to grow and open the doors and open the
opportunities for them because they're doing so
166
00:19:08,100 --> 00:19:15,600
much if we can speed up that acceleration of growth
by doing a little bit it goes a long way yeah
167
00:19:15,600 --> 00:19:22,680
absolutely and you know we also noticed that you
have an open calendar like anybody can just come
168
00:19:22,680 --> 00:19:28,220
and talk to you is there a reason why you did that so
the reason is because if you people don't know how
169
00:19:28,220 --> 00:19:34,800
to reach out to you then they're like waiting like
how am I supposed to talk to this guy what to do and so
170
00:19:34,800 --> 00:19:40,400
why not you know if you really want people to reach
you there's no point in keeping the calendar
171
00:19:40,400 --> 00:19:47,300
closed so one of the reasons I started doing that is
so that you know people can reach and then I'll find
172
00:19:47,300 --> 00:19:52,800
out you know what the purpose is and there's a
notion like you know you know within the five ten
173
00:19:52,800 --> 00:19:59,420
fifteen minutes is this something that you're
going to continue further or that's the end of the
174
00:19:59,420 --> 00:20:05,750
road And so I think it's important for them. And I
also know that rejection is another thing nobody
175
00:20:05,750 --> 00:20:11,150
wants. So if you reach out for a connection on
LinkedIn or you know, somebody that you want to
176
00:20:11,150 --> 00:20:18,850
talk to and they've never paid attention to you.
But if you do the same thing to others, they might be
177
00:20:18,850 --> 00:20:24,130
feeling the same way too. So I have this notion that
if I know somebody is doing this to me, I don't want
178
00:20:24,130 --> 00:20:27,830
to give the same thing to somebody else. That
doesn't mean I'm actually accepting everybody.
179
00:20:27,830 --> 00:20:32,790
It's also very deliberate and that's important
because at some point you want to make sure the
180
00:20:32,790 --> 00:20:41,470
quality, important conversations and time. So I
think why people tend to restrict themselves is
181
00:20:41,470 --> 00:20:47,770
they dedicate certain time of their calendar for
networking or doing things when they have, but
182
00:20:47,770 --> 00:20:52,990
then they're busy with other things. And so
eventually that takes over and you won't be able
183
00:20:52,990 --> 00:20:58,190
to. So give an example when I was just doing
investments and I was not really doing anything
184
00:20:58,190 --> 00:21:05,830
else. I was playing golf. So now I don't. It's just
because you're so busy with everything else. So
185
00:21:05,830 --> 00:21:11,850
you just have to give up something. So I think
people give up their time because they have to do
186
00:21:11,850 --> 00:21:17,830
other things. And so I think that is one of the
things naturally happened. Obviously this is
187
00:21:17,830 --> 00:21:23,750
open route, but eventually it probably won't.
Yeah, I guess a lot of people will just grab the
188
00:21:23,750 --> 00:21:31,870
opportunity after hearing this. But I think just
sort of like looking a little bit into the future,
189
00:21:31,870 --> 00:21:38,170
and we were just starting before this that you've
seen all the shifts in technology all the way from
190
00:21:38,170 --> 00:21:48,110
on-prem to the cloud, even social as a way with
gaming and now with AI. So what excites you the most
191
00:21:48,110 --> 00:21:54,950
about this and what is different about this time?
Yeah, so I was one of the luckiest in terms. And I say
192
00:21:54,950 --> 00:22:01,430
lucky. So there's a definition for luck is that you
need to be at the right time on the right place. Then
193
00:22:01,430 --> 00:22:07,990
things happen, then you ride the wave. So I think
that is exactly what happened with me. You know,
194
00:22:07,990 --> 00:22:16,070
obviously there is some work involved in it. But I
think the three decades that that I've had in my
195
00:22:16,070 --> 00:22:27,770
career, I think I've seen how I've matured. I've
seen how organizations matured. I've seen also
196
00:22:27,770 --> 00:22:38,490
the employees have matured. And then I've also
seen how technology matured, and also how people
197
00:22:38,490 --> 00:22:48,230
who build companies have also matured. It's just a
natural evolution. It's just because when you
198
00:22:48,230 --> 00:22:57,110
have nothing, you're ended up being a lot of it. But
when you start putting the reinforcements around
199
00:22:57,110 --> 00:23:08,810
repeatability and simplification, automation,
and then ultimately reusing the resources that
200
00:23:08,810 --> 00:23:17,930
you already built. So we've become much more
efficient as humans in doing what we're doing. And
201
00:23:17,930 --> 00:23:25,930
that is actually what is helping us go faster. And
we're always looking to improve. And this is by
202
00:23:25,930 --> 00:23:35,350
nature. And now technology is enabling that. And
now we're at a point where we've laid the
203
00:23:35,350 --> 00:23:41,870
foundation of chips, which actually propelled
processing capabilities. Then we use them to
204
00:23:41,870 --> 00:23:50,950
build the compute so that we're processing more.
Then we understood how important data is in order
205
00:23:50,950 --> 00:23:59,470
to process the information. And now we understood
how important it is to have intelligence. So that
206
00:23:59,470 --> 00:24:06,930
means you have data, but now you need to build
intelligence from that information or that data.
207
00:24:06,930 --> 00:24:15,110
And that's where AI is. So now we're at the point of
creating superhuman capabilities, where human
208
00:24:15,110 --> 00:24:24,190
capabilities are limited. We're adding and
augmenting with AI. Now we need to learn how to use
209
00:24:24,190 --> 00:24:34,950
that. So this is the new power that is in your hands.
So or in your reach, how do we then use it for the
210
00:24:34,950 --> 00:24:41,490
better of the world and better of the society and
organizations and for people? And now the
211
00:24:41,490 --> 00:24:48,770
responsibility kind of shifts from not from
innovating, not from just inventing and just
212
00:24:48,770 --> 00:24:58,730
deploying, but how to use it to make it useful. And I
think that is really what I'm excited about is that
213
00:24:58,730 --> 00:25:05,250
there's so much changing now. The third era that I
was talking about this decade is where it is
214
00:25:05,250 --> 00:25:10,510
creating so many opportunities with AI,
disrupting the existing architectures. It's
215
00:25:10,510 --> 00:25:17,170
creating new categories. It's creating new
opportunities for existing players to either to
216
00:25:17,170 --> 00:25:24,270
go into it. I strongly believe most of the existing
incumbents will understand that AI is a
217
00:25:24,270 --> 00:25:29,950
completely different beast of architecture.
They won't be able to really take what they have.
218
00:25:29,950 --> 00:25:36,470
They have to augment also. At some point, they see
that it cannot really sustain and M &As will happen
219
00:25:36,470 --> 00:25:46,270
just because they needed that new blood and new
innovation, invention, so that they can move from
220
00:25:46,270 --> 00:25:50,710
here to the new ones, rather than trying to
basically change the existing one. Because at
221
00:25:50,710 --> 00:25:58,950
some point, you can't remodel a house. After three
remodels, I'm like, I'm done. I'm done. I'm tired.
222
00:25:58,950 --> 00:26:05,630
And you're breaking things then, you're actually
fixing it. So that's when the new things will come
223
00:26:05,630 --> 00:26:11,910
and extensions and other things. And so that's how
acquisitions happen. Smart entrepreneurs and
224
00:26:11,910 --> 00:26:19,210
executives are making those M &A decisions. And I
tell all of these startup founders now, be very
225
00:26:19,210 --> 00:26:24,710
positive around and have that attitude that
they're building something completely new and
226
00:26:24,710 --> 00:26:29,990
opportunities will come. Actually, that was
going to be my last question just to wrap this up.
227
00:26:29,990 --> 00:26:36,690
That as founders who are actually building in this
space, what would be your likey actionable tips
228
00:26:36,690 --> 00:26:41,530
for them to actually make the most of it? And
especially from an enterprise perspective,
229
00:26:41,530 --> 00:26:47,210
there's just so much opportunity, but there's
obviously like a gap in terms of their
230
00:26:47,210 --> 00:26:53,610
understanding of that opportunity. Yeah, so what
everybody's worried about, and I think there's a
231
00:26:53,610 --> 00:27:01,930
reason why we're all worried about it is, is that
when cloud and data and capabilities came in the
232
00:27:01,930 --> 00:27:07,450
last decade, we've started creating a lot of
applications. Obviously, everything is use case
233
00:27:07,450 --> 00:27:14,070
based and people start building these apps and
applications to solve one certain problem. So
234
00:27:14,070 --> 00:27:21,510
that created a swath of applications that are
sanctioned, unsanctioned usage is happening in
235
00:27:21,510 --> 00:27:29,290
the organizations. There's some maturity came in
towards the last end of the decade to this new
236
00:27:29,290 --> 00:27:37,570
decade is that the sprawl of these applications
created a lot of risks. And that risk averse that I
237
00:27:37,570 --> 00:27:46,350
was talking about in the organizations is
continuing. But with AI, it's becoming 10x, maybe
238
00:27:46,350 --> 00:27:54,990
100x more. It's because number of applications or
apps and agents that we're talking about
239
00:27:54,990 --> 00:28:01,850
deploying is multiplying. And now, if you're a
founder building these small, agentic
240
00:28:01,850 --> 00:28:09,930
applications that aren't necessarily
sustainable, then you need to think about it. Yes,
241
00:28:09,930 --> 00:28:16,970
you can build something, but is it something
sustainable, longevity and ability? And that's
242
00:28:16,970 --> 00:28:23,490
what investors are looking at. The other
important thing is, are you building a category
243
00:28:23,490 --> 00:28:29,570
defining product? What problem are you trying to
solve? Because opportunity for building
244
00:28:29,570 --> 00:28:35,390
something like this is not going to come for every
time. It's a generational thing. What AI is giving
245
00:28:35,390 --> 00:28:41,630
right now for people is to really rethink about the
opportunity. It's the same old problem, new
246
00:28:41,630 --> 00:28:48,750
solution. Every organization, see, the thing is,
is that problems already exist. We've already put
247
00:28:48,750 --> 00:28:56,450
a solution to it. But if that solution isn't
evolving, as businesses evolving and the people
248
00:28:56,450 --> 00:29:00,730
are evolving in the organization, new
opportunities get created. That means the
249
00:29:00,730 --> 00:29:07,810
problem didn't go away. The problem actually
perpetuated into a different state. And that's
250
00:29:07,810 --> 00:29:14,570
what tech debt is. Everybody thinks tech debt is
somehow magically and nobody cares about. The
251
00:29:14,570 --> 00:29:21,570
tech debt happened is because you had a problem,
you deployed a solution. The solution didn't
252
00:29:21,570 --> 00:29:30,270
evolve, but the problem evolved. The business
evolved. And now how are you going to solve it? You
253
00:29:30,270 --> 00:29:35,770
can't solve it in an existing problem solution. So
that's why you're finding a new solution. And the
254
00:29:35,770 --> 00:29:40,630
newer solution happens to be with a newer
architecture, more capabilities, much better
255
00:29:40,630 --> 00:29:47,250
efficiency, able to do a lot more. And that's why
there is an opportunity for founders to go. So that
256
00:29:47,250 --> 00:29:53,890
is exactly what happens every decade. I think that
is why this is a decade where opportunities are
257
00:29:53,890 --> 00:30:02,730
plenty. And I think if you're building something
for an existing problem, this is the time to do it.
258
00:30:02,730 --> 00:30:11,570
Because this is going to really transform the
following two decades because we're in an
259
00:30:11,570 --> 00:30:19,570
intelligence era. Up until now, we're in a
foundational era. We're only in the first era was
260
00:30:19,570 --> 00:30:27,970
compute being better, networking being better,
communications being better. Then came the usage
261
00:30:27,970 --> 00:30:41,090
of those, processing of those. Now the byproduct
of those two is data. Now you're using the
262
00:30:41,090 --> 00:30:48,970
intelligence of how to use that to become that
intelligent beings. I think that is why this is
263
00:30:48,970 --> 00:30:55,850
going to be even more interesting. Because now
we're rewriting the chapter. See, we kind of came,
264
00:30:55,850 --> 00:31:02,090
now we're going to make a full circle to go back and
fix everything that we did with this new
265
00:31:02,090 --> 00:31:08,310
intelligence that we got. To say, oh, did we, oh,
now I could do this much easier, much more
266
00:31:08,310 --> 00:31:17,090
efficiently, then why not? So now the challenge
for these existing organizations, these
267
00:31:17,090 --> 00:31:25,070
existing solutions and technologies is what is
their lifespan look like? By next decade, most of
268
00:31:25,070 --> 00:31:33,370
these will become obsolete. And the new ones come
in and they will become now primary systems. These
269
00:31:33,370 --> 00:31:39,090
becomes the secondary. Right. Right. That's
exactly what is going to happen. So that's why I'm
270
00:31:39,090 --> 00:31:44,990
telling every founder, you're in the right era
with the right time. If you're building something
271
00:31:44,990 --> 00:31:52,170
now, I think you're building for the future.
Absolutely. Like the patterns will just repeat,
272
00:31:52,170 --> 00:31:59,550
but the scale and complexity will just be another
level. Yeah. For me, so the question is like, how do
273
00:31:59,550 --> 00:32:07,990
I see TruePair in this ecosystem of new
opportunity and why is this going to be better for
274
00:32:07,990 --> 00:32:15,270
you guys? What I liked about TruePair when I first,
you know, saw, first of all, Pratish reached out to
275
00:32:15,270 --> 00:32:20,630
me after the CIO event that I had and he loved it and
he said, like, I really want to talk to you. I
276
00:32:20,630 --> 00:32:25,950
ignored him for almost two months, basically,
because I didn't know much about it. I didn't have
277
00:32:25,950 --> 00:32:31,590
the time, not to, it's not because I didn't have the
time and that was the reason I was traveling and
278
00:32:31,590 --> 00:32:38,330
whatnot, but he was persistent. And so I was able to
meet with him and do and I think I encourage every
279
00:32:38,330 --> 00:32:43,230
founder, if you, if people are ignoring you, not
because they didn't want, I mean, they want to
280
00:32:43,230 --> 00:32:50,850
ignore you just because they didn't have time. So I
think what I liked about it is that the ease of
281
00:32:50,850 --> 00:33:00,650
product use is number one. See, the problem could
be there already. I think what is important is, is
282
00:33:00,650 --> 00:33:12,970
the solution easy to use? That's number one. And
number two is, is the adoption of that solution is
283
00:33:12,970 --> 00:33:24,510
viral in nature. Yeah. Right. And three, is the
capability scalable in the sense that whatever
284
00:33:24,510 --> 00:33:33,270
you built as a platform and as an architecture as a
solution, is that going to amplify the use in the
285
00:33:33,270 --> 00:33:40,470
organization? That means you land and then you
expand into places where that is opening more and
286
00:33:40,470 --> 00:33:45,230
more opportunities for organizations to
leverage that capability and that use. And I think
287
00:33:45,230 --> 00:33:48,750
these are the three things that I saw as an
opportunity and then that's why I'm excited about
288
00:33:48,750 --> 00:33:56,970
it because the product does something unique. And
that's why I was telling British that, you know,
289
00:33:56,970 --> 00:34:06,990
the, when we were having, I think I also shared with
you, is make it easy to use, make it simple for
290
00:34:06,990 --> 00:34:19,449
growth and scale and then start seeing the scale
with adoption and then you can adapt to the use and
291
00:34:19,449 --> 00:34:26,330
then build the pricing, build the product
capabilities because I think when you're doing
292
00:34:26,330 --> 00:34:30,810
something new, it's always like you don't know
what you don't know and you will only build what
293
00:34:30,810 --> 00:34:38,270
customers are asking and that's the best thing for
founders is that list that you have is by seeking
294
00:34:38,270 --> 00:34:44,630
that from the customer, seeking that from the
experts and build it into the product. I think
295
00:34:44,630 --> 00:34:50,969
having talented team is really the one of the other
attraction and why I'm confident that you guys can
296
00:34:50,969 --> 00:34:59,250
do it. So yeah, these are the four things like, you
know, I would say team, the ease of use, the
297
00:34:59,250 --> 00:35:08,410
problem, expansion capabilities. I think these
are all very, very attractive key elements for
298
00:35:08,410 --> 00:35:17,430
Truepeer. So my philosophy is you always have to
punch up. You don't know what you don't know. It's
299
00:35:17,430 --> 00:35:25,950
important to try, but trying should have some
method. Why do you want to go into that? So that
300
00:35:25,950 --> 00:35:34,090
means you do some research to figure out, is this
the market segment that has the pain? Are they your
301
00:35:34,090 --> 00:35:39,890
primary? Because everybody wants to go to the easy
route. There are certain problems you could solve
302
00:35:39,890 --> 00:35:46,690
easiest way, but then is that, you know, you don't
want to get addicted to it because then, you know,
303
00:35:46,690 --> 00:35:51,770
as you're growing, eventually you'll hit the
wall. And because your focus was only uni
304
00:35:51,770 --> 00:35:58,250
direction, you didn't figure out how to set
yourself as expansion. So then by the time you hit
305
00:35:58,250 --> 00:36:03,710
the wall, you have no capability to expand
anymore. And I think it's very important to know
306
00:36:03,710 --> 00:36:12,910
that as a founder, to try and create that expansion
capabilities as you're growing so that you can
307
00:36:12,910 --> 00:36:25,310
pivot as you build when things hit to a wall. And
that means you've reached a capability that does
308
00:36:25,310 --> 00:36:32,470
not have much market fit or a category fit or a
customer fit. Then you need to change the
309
00:36:32,470 --> 00:36:37,310
direction to figure out what that would look like.
So I think this is important. So that's why you
310
00:36:37,310 --> 00:36:42,670
build work-alive solutions and horizontal
solutions, what play you are in. And the most
311
00:36:42,670 --> 00:36:52,710
important thing is really making sure this
understanding of who your ICP is and also
312
00:36:52,710 --> 00:37:01,470
constantly checking that and evolving. But you
need to know where you want to be and how are you
313
00:37:01,470 --> 00:37:13,350
getting there. Right? And if your only target is
Fortune 10,000, not Fortune 100, then you need to
314
00:37:13,350 --> 00:37:24,450
build from a Fortune 2000 to 5000 rather than
building it for 10,000 because then you can go up.
315
00:37:24,450 --> 00:37:30,510
So always target the middle of the ground.
Otherwise you will end up building something of a
316
00:37:30,510 --> 00:37:37,910
smaller capability that is requiring a lot more
velocity and a lot more scale. By the time you spend
317
00:37:37,910 --> 00:37:45,110
a decade, you would only reach the mid-market. And
you get tired and you run into a situation that you
318
00:37:45,110 --> 00:37:51,790
hit the market penetration problem. And I mean,
that's okay. If that's what you targeted, it's
319
00:37:51,790 --> 00:37:59,110
fine. But if you want to become a bigger company and
longer, you need to start punching yourself from
320
00:37:59,110 --> 00:38:09,650
the middle of the ground to up. And that only comes
when you make that pivot very quickly. You enter,
321
00:38:09,650 --> 00:38:16,130
but don't spend too long in market. You need to kind
of be able to adopt that and then just go from there
322
00:38:16,130 --> 00:38:23,170
to the mid-market and then stay there to mature the
product, then start punching up so to go. So that's
323
00:38:23,170 --> 00:38:32,850
important for this strategy. Makes sense. I have
just one last question. So from a CIO perspective,
324
00:38:32,850 --> 00:38:38,790
how do you see, like you've seen, through peer
closing, right? Like what we are doing. So how do
325
00:38:38,790 --> 00:38:44,650
you see through peer fit into the CIO agenda? Like
in terms of how CIOs look at digital
326
00:38:44,650 --> 00:38:51,090
transformation, change management, adoption of
software at the deepest level? See, with AI
327
00:38:51,090 --> 00:38:58,130
products, the organizational maturity has
already came to a point where CIOs are now become
328
00:38:58,130 --> 00:39:04,670
shepherds of technology. There are only three
main buyers of technology in the organization.
329
00:39:04,670 --> 00:39:17,030
CIOs, CISOs, CTOs. I mean, predominant in their
teams. The CIOs are in the CISOs right in the
330
00:39:17,030 --> 00:39:23,290
middle. The business technology,
customer-based, customer-facing technology,
331
00:39:23,290 --> 00:39:31,850
and security being a byproduct of both, and those
are the three. True peer can fit in all of them. And
332
00:39:31,850 --> 00:39:39,970
the idea for you to build a product that has the
usage in every department, that has the
333
00:39:39,970 --> 00:39:47,550
capability to have an impact across the
organization, has a huge potential. And it's very
334
00:39:47,550 --> 00:39:53,130
difficult to have that. In an enterprise that is
even more difficult, because you could do, you
335
00:39:53,130 --> 00:39:59,810
could see this in the B2C and start somewhere small
and then scale in customers and all of that stuff.
336
00:39:59,810 --> 00:40:07,410
But in the B2B, you're labeled already, and you
have a limited scope of what you can do. But I think
337
00:40:07,410 --> 00:40:17,210
true peer being a content, creation, and enabling
capabilities of what you have to offer to your
338
00:40:17,210 --> 00:40:23,090
customers, or what you have to offer to your
employees. And because that is where the product
339
00:40:23,090 --> 00:40:31,750
fits. So it's fitting for employees. It fits into
the systems, applications. It also fits into the
340
00:40:31,750 --> 00:40:37,030
products that are actually being shipped by the
organizations for their customers. So that's why
341
00:40:37,030 --> 00:40:50,730
true peer has broader potential. And I think, and
that's one of the reasons why you, the CIOs, have
342
00:40:50,730 --> 00:40:56,190
being the shepherds in this area, then can
transition into security products and
343
00:40:56,190 --> 00:41:02,830
applications, or even to the technology and the
product of products that are being shipped and
344
00:41:02,830 --> 00:41:11,310
where you could also use true peer for that. I think
that's why I'm excited about it. It's a broad swath
345
00:41:11,310 --> 00:41:17,870
of organizational use. Great. Thanks so much,
Levan, for doing this. I know you've been, you
346
00:41:17,870 --> 00:41:23,420
already had a long day, but like, this has been
super insightful and lots of takeaways for us. And
347
00:41:23,420 --> 00:41:28,170
hopefully, whoever is watching this. So thank you
so much. No, no, I'm really having fun and I really
348
00:41:28,170 --> 00:41:33,650
appreciate you guys having me here. I'm actually
very excited for what you have and meeting all the
349
00:41:33,650 --> 00:41:41,410
team. And I'm really, now part of the success for
you and I would love to be. I'm looking forward to
350
00:41:41,410 --> 00:41:43,810
it. Absolutely. Awesome. Thank you.