HomeVideos

Can Lindy Replace OpenClaw? (CEO Interview)

Now Playing

Can Lindy Replace OpenClaw? (CEO Interview)

Transcript

988 segments

0:00

no longer a platform where you can build

0:02

AI agents. We are an AI agent. Like

0:04

technology should just work. You

0:06

shouldn't have to build an agent to get

0:07

stuff done. Using Lindy has changed my

0:09

relationship with the computer and I I

0:11

barely open G anymore. It's kind of

0:12

weird. I used to be glued to my inbox

0:14

like a real founder. Open is not real

0:17

weekend. Like technology is supposed to

0:18

be at your service, not the other way

0:20

around. I just sat down with the CEO of

0:22

one of the biggest AI automation

0:24

platforms to talk about OpenClaw, their

0:26

new competing product that you can set

0:28

up in under 60 seconds and why how we

0:31

think about AI automations and agents

0:33

just changed forever. So, grab a coffee

0:35

and strap in because this is going to be

0:37

a fun one. Flo, what is going on, man?

0:39

I'm stoked to have you on the podcast.

0:41

There's some pretty juicy things that

0:42

we're probably going to talk about

0:43

today. Anyways, I'm I've used your guys'

0:45

platform for years, probably 3, four

0:47

years now. I absolutely love it and a

0:49

lot of my audience loves it too. So, I'm

0:50

super stoked to have you on the podcast.

0:52

It's a full circle moment and stoked to

0:54

be talking to you today.

0:55

>> Yeah, thanks for having me, Brock. And

0:57

you have been with us from the very

0:58

beginning, haven't you? I'm really

1:00

appreciative.

1:01

>> Yeah. No, you guys have a great product

1:02

and I think one thing just diving into

1:04

this. Yeah, my audience is pretty

1:07

non-technical and I've always loved how

1:09

your platform is so easy to build out

1:12

different automations, you know, like

1:13

whether it's a meeting prep assistant or

1:15

autoleabeling emails. These are all

1:17

things that I've used your product for

1:19

for years to like help me run my

1:21

business. And I think you guys are

1:22

making an interesting transition

1:25

product-wise and I'm super excited to

1:26

talk about today. So yeah, give me kind

1:28

of a breakdown like early stages what it

1:31

is that you guys are trying to build and

1:32

then we can maybe dive a bit more into

1:34

like where you guys are evolving to in

1:36

the next couple of months or coming

1:37

years.

1:37

>> Yeah, 100%. So the way we've explained

1:40

who we are for the longest time has been

1:43

we are the easiest way to build AI

1:46

agents for nontechnical people and I

1:48

think we had an epiphany of sorts

1:49

sometime around last year where we

1:51

realized that especially as the

1:54

technology evolved and as the models get

1:56

better that the easiest way to build an

1:58

AI agent becomes almost a contradiction

2:00

in terms

2:01

>> you know it's almost like like I told

2:02

you like hey I'm the easiest way for you

2:04

to make yourself a burger at home a

2:06

cheeseburger and it's like hey like if

2:08

you really want the easiest way to make

2:09

yourself a cheeseburger. You're not

2:10

going to want to make yourself a

2:11

cheeseburger. You're going to go to

2:12

McDonald's.

2:13

>> Yeah.

2:14

>> So, that's kind of is a big big big

2:16

mental shift we've made where we are

2:18

going from no longer a platform where

2:21

you can build AI agents. We are an AI

2:23

agent. You don't have to build it. You

2:25

can just use it. So, what we just

2:27

released last week is called Mindy

2:29

Assistant. And the way the way I like to

2:30

describe it is like it's an AI work

2:32

assistant that helps you get rid of the

2:34

[ __ ] So like your email, your

2:36

calendar, your meeting scheduling, your

2:38

email triaging, your email drafting,

2:40

like it saves you one to two hours a day

2:42

from the excuse my French, like the

2:44

[ __ ]

2:46

>> right? No, I love that. And to give a

2:48

bit of my like to give a bit of context

2:50

to my audience, how are we interfacing

2:52

with this now? Is this something where

2:54

it's just like off in the back end

2:55

running all this automations and stuff?

2:56

You don't really see it. Like are you

2:58

texting this? Are you, you know, on the

3:00

Lindy interface? How's this conversation

3:02

going down with our Lindy assistant?

3:04

>> Yeah, I think that's a really good

3:06

illustration of the the really big

3:07

difference between this new product and

3:09

and the old one. I'll show my screen

3:10

real quick. I think like just showing

3:13

easiest. This is the old product and

3:14

this is one of the most common use cases

3:16

we had with the old product which is

3:19

daily digest. So receiving an email or a

3:22

message every morning that's like this

3:23

is who you're meeting with. This is the

3:25

context of your meeting. So what it did

3:26

in this case is like hey every morning

3:28

you wake up you look at my meetings for

3:30

the day and then for every meeting and

3:32

for every attendee of every meeting you

3:34

research them you look up their LinkedIn

3:36

you look up my past meeting notes with

3:37

them you look up my past emails with

3:39

them and then you bring together this

3:41

really big email of like all of this

3:42

context

3:43

>> right and that was very much like okay

3:45

once it does this step move on to the

3:47

next in this like it's pretty I don't

3:48

know the right word for it maybe like

3:49

programmatic of just like very

3:51

structured in the way that it operated

3:53

right

3:53

>> it was putting the AI on the leash M

3:56

>> and I [clears throat] think that as the

3:57

models have developed the leash has

3:59

become unnecessary and in fact has

4:00

become harmful because model loses in

4:02

flexibility when it's on a leash. The

4:04

new product the way it works I have a

4:06

bunch of screenshots here. I've had to

4:07

compile them ahead of time because it's

4:09

uh it's obviously uh potentially

4:11

sensitive information but I just receive

4:14

this kind of digest every morning and to

4:16

answer your question I receive it over

4:18

iMessage. So, it's just like texting a

4:20

human assistant. And so, every morning

4:21

it texts me and it's like, "Hey, morning

4:23

flow." Like, "Today's nice day. 61

4:25

degrees. You've got three meetings on

4:27

your calendar. By the way, you've got

4:29

timesensitive email from Brandon. You

4:30

might want to take a look at it."

4:31

>> Yeah. And I want to cut you off right

4:34

here. Or not cut you off, but like add

4:35

my add some input here. This texted you.

4:38

You didn't have to go and say, "Hey,

4:40

Lindy, what's on my email or what's on

4:41

my list for my calendar today?" if I'm

4:43

correct here. Lindy proactively reached

4:46

out to you to text you and say, "Hey,

4:48

it's the morning like let me just like

4:49

get you up to speed on everything

4:51

because like right that's kind of the

4:52

process of this now."

4:53

>> No, exactly. So, it's just it's it's

4:55

very proactive and I think the

4:57

proactiveness of it is is a really big

4:59

funding principle for this uh for this

5:02

product. For example, here I I'll I'll

5:04

use another example. It was uh whenever

5:05

I receive a timesensitive email, it'll

5:07

text me. Or for example, if I'm in a

5:09

meeting, Lindy joins the meetings as

5:11

well. She's like I use she pronouns. Uh

5:13

she's

5:15

>> she's taking notes during the meetings

5:17

and so forth. If during the meeting I

5:18

say something like hey awesome Brock

5:20

like let's meet again on Wednesday next

5:22

week and you're like sounds good. Lindy

5:23

will be will send me a text afterwards.

5:25

She's like nice meeting with Brock like

5:26

do you want me to send an invite for

5:28

Wednesday? Or if I say

5:29

>> reading the transcript of the meeting

5:31

then using that as context to then be

5:33

proactive and kind of create an action

5:35

list.

5:35

>> That's exactly right. And you know,

5:37

after almost every meeting, you have

5:39

these like tiny little action items. And

5:40

they're like paper cuts. You know, it's

5:42

like you need to send a follow-up email.

5:43

You need to like let Bob know about the

5:45

decision that was just made. You need to

5:47

like send a follow-up calendar invite.

5:48

And these things like they may not sound

5:50

like a lot, but the analogy I've heard

5:52

that that I've really liked is like, you

5:54

know, I don't know if you know, like 95%

5:56

of the airplane crashes happen during

5:59

takeoff and landing. So, it doesn't

6:00

matter if you're flying from like San

6:01

Francisco to Paris, which is like a

6:03

11-hour flight. It's the 10 minutes of

6:05

takeoff and landing that are by far the

6:07

most dangerous. Like, cruising is

6:09

actually really easy. And so, if you had

6:10

to fly from San Francisco to New York

6:13

and land and take off at every city

6:16

along the way, it would be a miserable

6:18

flight. It'd be very long and it'd be

6:19

very dangerous. And so, the analogy here

6:22

is like that is what we are asked to do

6:24

every day at work. We all want to be

6:25

cruising because that's smooth and

6:27

that's that's easier and that's less

6:28

dangerous. We want to think

6:29

strategically about our businesses like

6:31

at the 10,000 ft altitude but we are

6:33

asked to take off and land 50 times a

6:35

day. You want to think strategically but

6:36

ah [ __ ] I need to send a follow-up email

6:38

to B. Ah there's this calendar event I

6:40

forgot about. Ah I need to jump on this.

6:42

And so I think the opportunity that's

6:44

opened right now because the models have

6:45

become so good is like they can run

6:47

constantly in the background for you.

6:48

There can be your sidekick that's with

6:49

you all day that like is in your inbox

6:51

with you that is in your meetings with

6:53

you and that catches all of those

6:54

takeoff and landing moments and that

6:56

takes care that takes care of the the

6:57

take off and landing for you,

6:58

>> right? I love that. That's that's such a

7:00

good good analogy cuz it's just trying

7:02

to reduce that friction of like all the

7:03

manual busy work. And like one thing

7:05

I've been using the Lindy assistant

7:07

maybe the last like 5 6 days since you

7:09

guys released it. And one thing I've

7:10

been personally using it a lot for is

7:12

kind of just like as a second brain like

7:14

at the end of the day I'll literally not

7:16

even just like text it. I'll give it a

7:18

voice note and say, "Hey," like a voice

7:19

memo and be like, "Hey, here's what I'm

7:21

working on. Here are the thumbnails I

7:23

need to do for this, you know, for my

7:24

videos in the pipeline. Can you research

7:26

some titles based on my previous YouTube

7:28

titles?" And not only will it like get

7:30

creative and come up with the titles,

7:32

but it will proactively scrape my

7:34

YouTube, look at my previous videos,

7:36

find the high performing ones, and then

7:38

create titles based on that. So, like

7:40

for me, it has been the best thing ever

7:41

to basically just like give it a brain

7:43

dump at the end of the day or maybe in

7:45

the morning or even the middle of the

7:46

day when I'm stressed and say, "Hey,

7:47

what's on my to-do list that I really

7:49

need to get done now?" And it will just

7:51

go off and like do it for me because

7:52

it's connected to all these different

7:54

applications that I'm using, which has

7:55

just been the most amazing thing about

7:57

this.

7:57

>> 100%. I do that so much. So, one of my

8:00

favorite use cases is at the end of the

8:02

week, I message my Lindy and uh I I tell

8:05

her I have a message about it somewhere

8:07

here, for example. So every week I send

8:09

a message to my agent and I'm like hey

8:11

my priority for next week is to work on

8:13

X right now it's product I do a lot of

8:15

product work and I'm like can you please

8:17

let me know do perform a calendar audit

8:19

for me like look at my calendar next

8:20

week and let me know how many hours of

8:22

meetings do I have and how many fit into

8:24

this priority and then what do you

8:26

recommend I shuffle around what meeting

8:28

can I cancel what can I delegate what

8:30

can I just not attend in order to make

8:31

more room for like my actual priorities

8:34

also to your point about training it

8:35

like this partner that just like compile

8:38

this information and dispatches it down

8:40

to like different systems and different

8:42

notes files and so forth. This is one of

8:43

my favorite use cases whenever we have

8:45

like whiteboarding like brainstorming

8:47

sessions with the team and when we're

8:48

done I sent a picture of the the session

8:51

to Lindy and I sent a voice memo and I'm

8:53

like hey this was a brainstorm about X Y

8:55

and Z and it it can see the whiteboard.

8:58

So I'm like this was a brainstorm about

8:59

X Y and Z. Can you please just arrange

9:01

this messy whiteboard into like a clean

9:03

note and put it on notion? So yeah, go

9:06

ahead. No, I was just going to say

9:07

that's so crazy and I want to make a

9:09

point because this is it's a perfect

9:11

example because a couple of years maybe

9:12

like two years ago when I first

9:14

discovered like using using your

9:16

platform I had that same idea for a use

9:18

case. I was like okay I have this like

9:19

notepad. I'm going to paste this in and

9:21

I'm going to try to figure out an

9:22

automation that could automatically like

9:23

categorize this for me or you know do

9:26

what I needed to do on the back end. And

9:27

it was such a pain in the ass trying to

9:30

figure out like okay how do I get AI to

9:32

analyze the image? How do like what's

9:34

the process for that? And then what do I

9:35

do here? With the new Lindy assistant,

9:37

you don't need to configure all that

9:39

yourself. Like a AI is getting better.

9:41

So image models are able to extract text

9:43

from images to, you know, make that

9:45

actually possible now. But like the

9:47

whole fact that we don't need to build

9:48

the flow now to build this is the best

9:50

part about it cuz you just literally

9:52

just ask your assistant and it knows how

9:53

to build all this stuff.

9:55

>> 100%. It should just work.

9:56

>> Yeah.

9:56

>> Like technology should just work. You

9:58

shouldn't have to build an agent to get

10:00

stuff done,

10:00

>> right? I I 100% agree. So I guess this

10:03

brings me to maybe like one of my next

10:04

questions. So for the future of you guys

10:07

obviously because a lot of you know

10:09

platforms say like naden or make.com you

10:12

know they're visual interface builders

10:14

and so you think of like okay if I need

10:17

an automation built out I'm going to go

10:19

use Lindy and build it myself. Now that

10:21

that is not kind of necessary as much.

10:23

Where are you guys trying to position

10:25

yourself long term in being kind of like

10:27

that go-to AI assistant so to say?

10:30

>> Yeah. So the the workflow like Lindy

10:32

workflows are still around and you can

10:34

still you can still build them and

10:36

they're great for like a lot of use

10:38

cases for like much more technical

10:39

people who have time and and the

10:41

technical ability to build those for

10:42

certain use cases they're better they're

10:44

like more reliable because they're they

10:46

have the leash and they're more they're

10:47

more cost effective and and so forth but

10:49

right now you know this is really like a

10:52

return to our roots like we're really

10:53

building a Lindy AI assistant which is

10:55

where we started initially and I think

10:57

the technology was just not ready like

10:59

the model wasn't that good enough yet.

11:00

Man, when we started it was like before

11:02

GP4 it was GPT3.5 4,000 tokens context

11:05

windows. Uh it's it's just nothing

11:08

worked and even GPT4 at the time blew us

11:10

all away obviously but is nothing

11:13

compared to the latest frontier models.

11:15

That's where we fit. I think perhaps

11:17

like a a a comparison that we hear every

11:19

so often is uh it is hard in February

11:22

2026 not to mention open cloud. It's

11:25

just uh it's really been such a

11:26

phenomenon. And I think the way I I

11:28

compare it is like I compare it to like

11:29

Linux versus Mac OS. Like just like

11:32

Linux, Open Cloud is this like strange

11:36

vibrant explosion coming out of nowhere,

11:38

right? Like Linux came out of Linux

11:41

tovolt's bedroom. This like weird guy

11:44

out of Sweden, right? And then there's

11:46

like this huge excitement in the open

11:47

source community going on around it. And

11:49

and so engineers really sort of crown it

11:51

as the new standard. it really blew up

11:53

and and now it's interesting because

11:55

fast forward I don't know like three or

11:57

four four decades three decades Linux

11:59

won but in a very roundabout way like

12:02

everybody uses at least Unix without

12:05

realizing it like your iPhone your

12:06

Android devices run on on on Linux your

12:09

your Mac your Mac runs on on it's a Unix

12:11

operating system and so I think like

12:13

this is where I I draw the comparison is

12:15

like Linux and OpenCloud are just

12:18

wonderful pieces of technology they are

12:20

not products and it's not just about the

12:22

deployment that's a pain in the ass. The

12:23

deployment is a pain in the ass. But you

12:25

see a lot of those products that are

12:26

like deploy open cloud with one click

12:28

that still does not a product make. Once

12:31

you've deployed open cloud with one

12:32

click and it's still not an opinionated

12:34

product that does stuff out of the box

12:36

for you. You have to set it up and I

12:38

can't tell you how many people I have

12:39

heard tell me ah I still have to set up

12:41

open cloud like it feels like a chore

12:43

you know it's like and what I tell them

12:44

is like open cloud is not worth your

12:46

weekend man like technology is supposed

12:47

to be at your service not the other way

12:48

around you know. So most people they

12:51

have it on their to-do list. They don't

12:52

want to do it. It's a chore. They don't

12:53

want to set up Open Global. And I would

12:54

say so 90% of people I know want to do

12:56

it. They haven't done it. And then like

12:58

90% of the people left, they've they've

13:01

started and they've actually deployed

13:02

it. So like the problem is not the

13:03

deployment. It's just they're like ah

13:05

okay once it's deployed actually there's

13:07

a lot of crap to do now to like actually

13:09

get it to be useful.

13:11

And so I just think that again it's the

13:13

Linux and Mac OS thing like it is not a

13:16

finished product and I think that it's

13:18

it's an important new building block

13:20

that startups like ours might use to

13:23

build an end product.

13:24

>> Right. Yeah. 100%. I definitely agree.

13:26

Like personally I have set up OpenClaw.

13:28

I use it and you know I use both Lindy

13:32

and OpenClaw uh to be fully transparent.

13:35

But one thing I've noticed is I'm using

13:37

Lindy for more sensitive information. So

13:40

I'm using that I'm obviously texting it

13:42

over SMS, but like I'm using Lindy for

13:45

my emails. I'm not going to use OpenClaw

13:47

personally for that use case because I

13:50

just don't personally trust it. You

13:51

know, I don't I'm not technical. So I

13:53

still have the fear of like, man, did I

13:55

set this up improperly? Like am I going

13:57

to give it access to something that I

13:58

probably shouldn't give access to? Am I

14:00

going to give it the wrong prompt? I'm

14:01

not am I not going to set up the right

14:02

guardrails? Yeah, I'd be interested to

14:04

hear kind of where you guys want to

14:05

position yourself like as being maybe

14:07

that like I don't want to put words into

14:08

your mouth, but maybe being that safe

14:10

alternative that nontechnical people or

14:13

just anybody can use so they don't have

14:14

to like deal with the potential negative

14:16

downfalls of using something like

14:18

openclaw.

14:18

>> Yeah, I I think it's hard in like

14:20

February 2026 not to mention open cloud.

14:22

I think in a nutshell like we're more

14:24

secure and we'll turn king like a thous

14:27

you know. I think open cloud is is this

14:29

awesome thing but look it's it's 80 days

14:30

old. You know, we've been working on

14:32

this for three years and so there's been

14:33

a lot of security flaws coming out of

14:35

it. We spent a lot of time on security.

14:37

So we have this thing that we call like

14:38

an agent shield that protects you and

14:41

your data and the agent that builds like

14:43

many layers of protection between your

14:44

data and your agents such that no one

14:47

can prompt inject your Lindy agent. Like

14:49

people can't just email uh your Lindy

14:50

agent and get it to do stuff like

14:52

there's a lot of layers of protection in

14:54

the middle and then it's a lot easier to

14:55

use like open CLA. I often compare it to

14:58

Linux. It's like it's a beautiful piece

15:00

of technology. It is not an end product.

15:02

It's not about the deployment. You know,

15:04

there's a lot of products coming out to

15:05

let you deploy Openflow with one click.

15:07

But once you deploy it, you still need

15:08

to get it to do something useful for

15:10

you. It is not an opinionated turnkey

15:12

batteriesinccluded product. That's what

15:14

we are.

15:15

>> That's a good way to put it. Batteries

15:16

included product. Yeah, because again

15:18

like going back to what I was saying

15:19

earlier, I really use Lindy for all the

15:22

like sensitive information. I'm not

15:23

going to give open call access to my

15:25

emails, all that sort of stuff. But

15:26

yeah, I'd be interested to hear. So,

15:28

have you guys been working on reframing

15:31

and recreating this product and

15:32

repackaging it into the new Lindy

15:34

assistant? Have you guys been working on

15:35

this like the last couple of months or

15:37

is this something where you guys decided

15:38

to like change because you saw what

15:41

OpenClaw is doing? Cuz I'd assume this

15:42

is something you guys have had in the

15:44

pipeline and you guys have been like

15:45

envisioning for quite a while now.

15:47

>> Oh, 100%. Like we've been working on

15:49

this precisely for about 6 months, which

15:52

is like an eternity in AI and we really

15:54

wanted to take our time to like get it

15:56

right. really, you know, even before

15:58

these six months, it's building on all

16:00

of the infrastructure and the

16:02

scaffolding and the technology that

16:04

we've built over the last three years.

16:06

So, for example, out of the box today,

16:07

Lindy can use a web browser to like make

16:10

purchases for you on Amazon and like

16:12

look up information and all of that

16:14

stuff. That is an announcement we made

16:16

in nine months ago, which is browser use

16:18

and computer use. So, Lindy is able to

16:20

use all of those building blocks that

16:21

we've been build building over the

16:23

years.

16:23

>> Right. And that's actually something I

16:25

was going to bring up. you. I'm glad you

16:26

refreshed my memory. The browser use

16:28

because Claude I mean I guess it's top

16:30

of mind. Uh Claude Sonnet 4.6 just

16:32

released and apparently the browser use

16:34

is you know even just a little bit

16:35

better than Sonnet 4.5. So, I'd assume

16:38

the browser use you guys have is only

16:40

going to get better as these LLMs get

16:42

better and the AI technology behind it

16:44

gets better because that's what really

16:45

gets me excited is having an agent that

16:47

not only can, you know, book a meeting

16:50

for me because it's connected to, you

16:52

know, Google Calendar, but it's able to

16:54

go off and actually click inside of a

16:56

browser, you know, whether that's like

16:58

on an actual browser on my computer or a

17:00

virtual browser, which I believe is how

17:02

you guys do it. What are your thoughts

17:03

on the browser use capabilities? Is this

17:05

something you guys think is going to

17:06

really be the next big thing or is it

17:08

going to be more so just like connecting

17:10

those apps and only using browser use if

17:13

you can't connect to those apps?

17:14

>> Yeah, I think it's both. I think like

17:16

browser use is going to be like the

17:18

ultimate interface for LLMs. But I I

17:21

think uh yes, whenever you can use

17:23

direct integrations and APIs, uh it's

17:25

obviously a lot faster, a lot cheaper, a

17:27

lot a lot more reliable. So you should

17:29

you should default to that. But you

17:30

would be surprised just how few things

17:32

you can do with an API that you can do

17:34

with a browser. It's interesting like

17:36

you know about two years ago scheduling

17:39

has always been a big use case for us.

17:40

And it's interesting even when someone

17:42

sends me a Canonly link I'm kind of lazy

17:44

to like click and look at my times and

17:46

all of that stuff. I just want I just

17:48

want it to happen automatically. And so

17:50

we've been in touch with the team over

17:52

at Canonly actually just across the

17:54

street for a long time. in and we were

17:56

like, "Hey, can you guys please give us

17:57

an API so if someone sends a Canly link

18:00

to a Lindy user, Lindy can book times

18:03

through the API?" And Canly was like,

18:05

"Not really. We don't want to let you do

18:07

that." Like, we don't want to be

18:08

disintermediated. We don't want to offer

18:10

an API and by the way, it's going to

18:12

open butts and all of that stuff. And

18:13

and what I told them is, you know, look,

18:15

we're going to do this the easy way or

18:16

the hard way. [laughter] I like browser

18:18

use is coming, you know, and I think at

18:20

the time they didn't take me fully

18:22

seriously. I think now they do. And uh

18:24

yeah, you know, now when I have someone

18:25

fast forward to two years, like the

18:27

Canly UI is more than simple enough for

18:30

browsing agents to be able to handle it.

18:31

And so whenever someone sends me a

18:33

calendarly link, I don't even bother to

18:35

take a look at it. I just forward it to

18:36

my Lindy and she looks at my calendar.

18:38

She's got my booking preferences and she

18:40

just finds a time and books it on the

18:41

calendarly.

18:42

>> Yeah. No, I love that. I guess that kind

18:44

of takes me to my next question. Like

18:45

what are some maybe RAM use cases that

18:47

you're using the Lindy assistant for

18:48

that somebody might overlook?

18:50

>> Yeah, this one is is one of my favorite.

18:52

It's it's really strange. It's I would

18:55

say using Lindy and this is something I

18:57

hear from my friends as well and from

18:59

our users. Using Lindy has changed my

19:01

relationship with the computer. I'll

19:03

tell you exactly what I mean. This is a

19:05

daily use case for me. I just like

19:07

sometimes I'm in backtoback meetings and

19:09

I'm emering from meetings after like

19:10

five hours. And so I've not looked at my

19:12

inbox for five hours. And I usually like

19:14

to be very very responsive over email.

19:16

And so after these these five hours of

19:18

meetings, by the way, I don't even

19:19

really feel like looking at my email. I

19:20

just feel like going out and take a walk

19:22

after five hours of like straight calls.

19:24

And so I literally just go out and I

19:25

shoot a message to my Lindy and I'm

19:26

like, "Yo, is there anything urgent or

19:28

important in my inbox that I should take

19:29

a look at?" And Lindy responds and she's

19:31

like, "Yeah, three things." Boom, boom,

19:33

boom, boom. And then you see I I I

19:35

respond with a voice memo and it's

19:36

magical. It's like I'm talking to my

19:38

box. I'm like, "Okay, email number one,

19:39

it's actually not a big deal. Just

19:40

delete it." Email number two, yeah, tell

19:42

him it's okay. We can do this. And email

19:43

number three, can you forward it to our

19:45

accountant and ask him what to do? Same.

19:47

That's over. You know, and so this is

19:48

what I mean by my relationship with my

19:50

computer has has changed. I use my

19:53

computer a lot less. Honestly, I I use

19:55

my my mobile a lot more and I I barely

19:57

open Gmail anymore. It's kind of weird.

19:59

I used to be glued to my inbox like

20:00

every other founder. Now everything just

20:02

happens on MS through my mobile and it's

20:04

kind of weird. I'm looking at the office

20:06

right now and I see all of those

20:07

computers and those like large displays

20:09

and increasingly I view these things

20:12

almost as like it's almost like a

20:14

there's a little bit of wristfulness.

20:15

There's some something almost like

20:16

melancholic about it actually where I'm

20:18

like I view them as relics of the past.

20:20

I I view them as like I view a computer

20:23

and a big monitor and a keyboard and a

20:25

mouse. I view them as a tool that we use

20:27

to micromanage technology, right? You

20:29

need a keyboard and a mouse because you

20:30

need to micromanage your thing keystroke

20:32

by keystroke, click by click by click,

20:34

you know, and um and and and this is

20:36

you're almost like a factory worker.

20:38

You're a knowledge worker, but you're

20:39

almost a factory worker. And that's a

20:40

machine that you're using to produce

20:42

knowledge all day, right? It's a very

20:43

complicated machine. And I think that

20:45

when your computer becomes intelligent

20:46

enough, it's just like an employee like

20:48

you don't need to micromanage it

20:49

anymore. And so the smarter your

20:51

computer is, the more of a high level

20:53

code you can get, you can give it

20:54

instead of micromanaging it. You can

20:56

tell it, hey, go to my inbox, find that

20:58

email, put together a report on Google

21:00

Docs, convert it to a PDF, send it back

21:02

to him. And the all of the gluing

21:04

together of all of the apps, all of that

21:05

stuff, the computer's going to figure it

21:07

out by itself. I think a lot of it too

21:09

probably boils down to like how creative

21:10

you could get with the tasks that you

21:12

want to have it go off and do. So like

21:14

that's something for example with Claude

21:16

and Lindy that I've been experimenting

21:17

with of like okay how far could I take

21:19

this thing you know like of course like

21:20

I could maybe have it go through my

21:22

meetings and schedule a meeting and you

21:23

know that sort of stuff but like I've

21:25

been increasingly impressed at the stuff

21:27

that it can do and like to piggyback off

21:30

of what you're saying where it almost

21:31

feels like computers are a relic of the

21:33

past. I it's funny because we're both

21:34

like so immersed into technology and

21:36

we're so all about like man for me I

21:38

love new Apple products. I love a new

21:40

MacBook Pro. I love a new Mac Mac

21:42

Studio, Mac Mini, whatever. But like I

21:45

grow increasingly more and more just so

21:47

tired of looking at my computer and I

21:50

would like I I'm so excited for the

21:51

point in time when AI is good enough to

21:53

where I can give it a voice message, go

21:56

on a walk, and it could go off and do

21:57

all these different things for me. and

21:59

you know, it's doing maybe more work

22:00

than I would get done in maybe like 3 or

22:02

4 hours of sitting at my computer and

22:03

like doing my deep focus work, if you

22:05

even want to call it that. So, that's

22:06

why I've been so impressed with kind of

22:08

this new revolution that we're starting

22:09

to see of just these agents that we

22:11

could text or even, you know, I'd assume

22:14

at some point we could maybe have a

22:15

phone call or just like chat over voice

22:17

message and have it go and do these

22:18

things. That's why I've been really

22:19

loving this product that you guys

22:20

created because I could reconnect with

22:22

nature more. I could reconnect with my

22:24

friends instead of having to feel like I

22:25

need to grind all day and do these

22:27

things manually. It's just like it's

22:28

interesting how the dynamics are

22:30

changing.

22:30

>> 100%. I mean like the way we've always

22:32

expressed our mission is to free

22:34

humanity from work. Once humanity is

22:36

freed from work, leaving aside for now

22:38

the deep societal questions that is

22:40

asks, but like once humanity is freed

22:42

from work and and we figured out those

22:44

deep questions, you're not going to have

22:45

a computer. You know, you're just going

22:48

to be at the park in the sun hanging out

22:50

with your friends and family and you're

22:51

going to have your phone and maybe

22:53

there's a neural link at that point and

22:54

you can just talk to your phone. like,

22:56

can you bring me a broom? [laughter]

22:58

>> Right.

22:58

>> Oh, it'd be neat if if there was a

23:00

building there. And I I agree with you.

23:02

You sort of become bottlenecked by it's

23:04

a really surreal feeling because, you

23:06

know, we built this app and we ourselves

23:09

discover new use cases for it non-stop.

23:11

And once you start to make it a habit,

23:12

you start small. You start with like the

23:14

obvious stuff. Everyone wants help with

23:16

their email and and their their meetings

23:18

and their calendar. But then little by

23:19

little, you use it more and more. You

23:20

talk to it all day. And little by

23:22

little, you at your computer and you do

23:23

something and you feel silly. you're

23:24

like, "What? Why am I doing this?"

23:26

Probably probably Lindy can do this. And

23:28

so, I'll give you an example of

23:29

something that happened the other day.

23:30

Like, I I'm I'm working a lot on product

23:32

and you know, I I I file a lot of

23:34

tickets whenever I encounter an issue

23:36

with Lindy. And so, I'm talking with

23:38

Lindy. Something bad happened. I'm like,

23:39

"Ah, this sucks. I take a screenshot on

23:42

my phone. I send it to my computer. I

23:44

open linear. That's what we use for our

23:45

buck tracking. I create a ticket. I set

23:47

a priority. I assign it to someone. I

23:49

attach the thing. I just And I'm like,

23:50

wait a minute. Why am I doing this?"

23:52

>> [laughter]

23:52

>> And so I just sent this message to Lindy

23:54

and I'm like, "Hey, when I ask you to

23:56

file a ticket or report a bug, I want

23:58

you to just go on in the air and like

24:00

file it." And then if if I ask you, you

24:02

know, ping someone on Slack about it as

24:04

well. So that's what I mean by like

24:06

micromanaging the computer, you know,

24:08

like here this workflow is sort of split

24:10

between linear and and Slack. And so I

24:12

think there's almost no workflow that is

24:15

contained inside a single application.

24:17

It it always spans multiple

24:19

applications. you know, you bring

24:20

together a slide deck and then you

24:22

export it and you send it by email. And

24:23

you know, today the workflow has to be

24:26

orchestrated across all of those

24:28

applications. And the guy who's got to

24:29

do the orchestrating is the user. And

24:31

and no one thought to themselves as a

24:33

kid, when I grow up, I want to be a

24:35

workflow orchestrator. And and so that's

24:37

my point about the relationship with the

24:39

computers that's changing where you can

24:40

just give a goal to your computer and

24:42

it's going to orchestrate the workflow

24:44

for you.

24:44

>> Yeah, I think I 100% agree. I think

24:46

that's just a great way, you know, a new

24:48

direction we're moving in. And then I

24:50

guess like one question I have is how is

24:53

Lindy learning like how you operate for

24:56

example because I noticed that when I

24:57

was inside of my Lindy assistant that

24:59

there was this like I think it was

25:00

instructions part of it where I noticed

25:02

it was like my email agent and it

25:05

actually read through my emails,

25:06

understood my my language and how I

25:08

actually respond to specific emails. So,

25:10

I'd love to hear because obviously these

25:13

AI assistants are kind of bound to like

25:16

how good of a responses they give, you

25:17

know, but if they don't understand how I

25:19

actually respond, then what's the point

25:21

of having it go off and do it for me?

25:22

Nobody likes AI slop. But I want to know

25:24

your process for that, like how is Lindy

25:26

actually learning, you know, how we

25:28

speak, how we operate, and how we

25:29

actually perform different things.

25:30

>> Yeah. So this has really been like a

25:32

journey internally where like we spent a

25:34

lot of time developing this system so

25:36

that Lindy gets continuously better and

25:38

like learns your preferences and and it

25:41

becomes magical once it really works.

25:42

Like there is this example where Lindy

25:44

sent me this email. She's like hey your

25:46

lawyer just sent a counter offer to

25:48

these guys. And by the way I noticed in

25:50

the counter offer he uses this address

25:52

for your office. Is that the right

25:53

address? I thought this was your office

25:54

address. And I'm like oh yeah no you're

25:56

right. Like he got the address wrong.

25:57

Like please send him an email.

25:59

>> Hey that's crazy. That's actually

26:00

amazing.

26:01

>> And I I'm not lying when I say like

26:04

every day, including like a couple of

26:06

hours ago, I was meeting with an old

26:07

friend and Lindy sends me always a

26:09

message when I meet with someone with

26:11

like a prep for the meeting and the

26:12

agenda who I'm meeting with. And uh she

26:14

sends me this text message and she's

26:16

like, "Oh, you're meeting with Shukont

26:18

today. He's an old friend. You've worked

26:19

together for five years. He was like an

26:21

OG on the crew a while ago." And I'm

26:23

like, "How the [ __ ] did you [laughter]

26:24

know that? How did that how did that

26:26

happen?" And so what happened is like we

26:28

built this system. this like continuous

26:30

learning memory system. We iterated on

26:32

it for a long time. We really made it

26:33

shine like a beautiful jewel and and

26:35

we're like, "Oh my god, it works. It's

26:37

awesome. Little by little, it's learning

26:38

about me and it's it surprises me in how

26:40

much it knows about me." The only

26:41

downside is like you really only reap

26:43

these benefits after you've talked for a

26:45

while about about yourself, right? It's

26:47

a relationship you build over the long

26:49

term. And so I remember distinctly we

26:50

were at the office late at night when we

26:52

were like jamming about this, having

26:53

dinner with the team, and we were like,

26:55

"Wouldn't it be neat if Lindy could just

26:56

know about you from the get-go?" like

26:57

how might we get all of that data about

27:00

you, all of these preferences. And so

27:01

what we ended up doing is we we built we

27:03

called this the hydrator system. So it

27:06

hydrates your knowledge base and your

27:08

memory base. And so what we do is when

27:10

you sign up uh we we ask for access to

27:12

your inbox, we again suck to compliant,

27:16

HIPPA compliant, super safe. And if you

27:18

give us access to your inbox with your

27:20

permission, we look at your history of

27:22

emails. We look at thousands and

27:24

thousands of emails and we process them

27:26

using LLMs. Again, nothing is ever used

27:29

for training. We have agreements in

27:30

place with the labs and so forth, but we

27:32

we process all of that and we use it to

27:34

learn about you. And then it's true, you

27:36

can go to your settings and you can see

27:38

everything we've learned. And very often

27:40

people find it delightful actually to

27:41

learn to like read this report and we

27:43

use it then to do a lot of stuff

27:45

including drafting replies for you

27:47

because we've learned what you reply to

27:48

whom and and how you write. And I'm not

27:50

lying that at this point it's a daily

27:52

occurrence. You know, I I look at my

27:54

inbox and I look at a draft that's

27:56

sitting in my inbox to an email I

27:57

received. And at first I thought that

27:59

was I was going crazy. At first I

28:00

thought I was like, did I write this

28:01

draft? I have no recollection of writing

28:03

this. And it's just like it's Lindy who

28:05

wrote it. So yeah, that we've paid a lot

28:07

of attention to that. Like not just the

28:08

fact that it's proactive, but the fact

28:10

that it's personalized and keeps

28:12

learning about you and getting better.

28:13

>> Yeah, that's that's huge. And like you

28:15

said, the fact that you don't, you know,

28:16

of course it could learn the more and

28:18

more you chat with it, but the fact that

28:19

it already has that information just

28:21

because it's able to scrape it. Like for

28:22

me, I probably wouldn't have allowed it

28:24

to draft email responses for me if I if

28:27

it didn't already have that pre-existing

28:28

knowledge, but now it's just so good.

28:30

I'm like, "Okay, this is good enough to

28:31

actually use." So that's been, you know,

28:33

something um amazing for me when I've

28:35

been using it. Is there anything else

28:36

that you'd want to chat about or any way

28:38

that we could kind of end it?

28:39

>> It's available today. [laughter]

28:41

Yeah, absolutely.

28:43

>> Um and um no, you know, we all we are

28:46

hiring. If anyone is listening that's an

28:48

engineer who's excited about this kind

28:49

of stuff, we we are growing the team

28:51

rapidly.

28:51

>> Perfect. And then as for pricing, what's

28:53

what's pricing look like right now?

28:55

>> Yeah. Uh it cost $49 a month. Got it.

28:59

>> Huh?

29:00

>> No, I was going to say and how far does

29:01

that get you? Because I've been using

29:02

it. It's gotten me very far. I haven't

29:04

hit any limits. So I'd assume for the

29:06

majority of people that is probably

29:08

sufficient unless you're using tons and

29:10

tons of usage of this.

29:11

>> Exactly. It's enough for 98% of people.

29:13

There's like 2% of people who run into

29:15

limits and we just tell them like hit us

29:17

up and and usually what we do is like it

29:20

becomes like $100 a month, sometimes

29:21

$200 a month for like the very very

29:23

heavy users. Some people use for coding

29:25

which like never really intended but

29:27

like hey we can't really give you

29:28

infinity tokens for $50 a month and so

29:30

yeah it's enough for 98% of people.

29:32

>> Got it. Yeah 100%. Well, Flo, thank you

29:35

so much for coming on, man. It's again,

29:36

like I said, full circle. I've been

29:38

using your guys' product for years now.

29:39

Super stoked to chat about this and I'm

29:41

excited to see what you guys keep

29:42

building and hopefully I could have you

29:43

on again when you guys have another

29:45

groundbreaking kind of product release.

29:47

>> Be a pleasure. Yeah. Thank you so much

29:48

for having me, Brock. Cheers.

Interactive Summary

Lindy has pivoted from being a platform for building AI agents to being an AI agent itself, launching the "Lindy Assistant". This new product focuses on making technology "just work" by acting as a proactive and personalized work assistant, managing tasks such as email triaging, calendar management, and meeting follow-ups. The assistant communicates via iMessage, learns user preferences from past data (with user permission), and leverages browser capabilities to perform complex actions. Lindy differentiates itself from products like OpenClaw by offering a more secure, turnkey, and user-friendly experience, emphasizing that it's a finished, "batteries-included" product rather than a powerful but un-productized technology. The overarching mission is to free users from micromanaging their computers, allowing them to focus on higher-level strategic work. The Lindy Assistant is available for $49 per month for most users.

Suggested questions

5 ready-made prompts

Recently Distilled

Videos recently processed by our community