All right. Hello everyone.

Welcome. Really excited you all are here

and thank you for letting me interrupt

the cooking session that's happening on

the live stream and also for joining

this workshop about Grokbot for

founders. I'm Shub and I spend a ton of

time with founders helping them optimize

their Grokbot setups and ship quickly

and so I'm very lucky to be pushing this

product to its limits and today I want

to share some of those learnings with

you guys and hopefully get into some

live demos. So, let's get straight to

it.

I'll start with what we're going to talk

about. Over the next 60 to 90 minutes,

we will run through some really quick

context around Grokbot, why it's

particularly useful for founders and

then finally obviously some demos. We

got to have those. We will close out

with some tips for power users that

people seem to love and then also try to

do some Q&A for at least the folks that

are here with us present live.

The final bonus piece I will add is that

I'll be sharing one of these bots at the

end so you can steal it for yourself. I

wish I had like a call now number but

you know, we'll we'll make do.

Also, there will be a few of you in this

session that are not founders. You will

have snuck in which is awesome. Kudos. A

lot of this will still apply to you

especially if you are head of X at your

company. So, stay posted and for those

of you with Grokbots watching this

session, this is the time for you to

probably watch it live cuz we got some

cool stuff going on. So, let's get

straight to it.

A few of you have probably already seen

some version of an AI maturity curve.

Everyone is freaking out about this

these days but for us we are really

optimistic with how the world of AI is

changing.

As models improve and the tooling

improves, we are able to scale our

productivity quite a bit and so you'll

see that we started with chatbots, moved

on to ephemeral agents that finish a

task and then you kind of throw them

away. And now bots are kind of this next

iteration of what we're really pumped

about which is

bots that automate your jobs and bots

that you can have around for a really

long time. The key part is that these

bots actually compound and I think

that's the most important piece is you

let them do a task but you don't throw

them away. You keep them around, you

invest in them, and they get better with

you the same way an employee would.

Finally, what we're aiming for is this

world where you can just fully automate

a staff function for yourself and scale

yourself with a team of bots and we're

getting pretty close to that.

Internally, we've seen some external

examples of that and I want to share

some of that today. But,

we're really excited about what Grokbot

can do

and I know this is all very high-level

so maybe we get into the specifics

really quickly.

How many of you here have used Grokbot

before? Just quick check live at least.

Perfect. Most of you it seems. Uh so I

will blaze through this. Uh Grokbot is

obviously a new tool that you can talk

to just like a coworker or teammate. You

basically text it like iMessage and it

can go off and do a lot of really cool

things for you. It is very proactive and

very ambitious and the reason it can do

those things is because we've armed it

with its own computer. So, unlike

traditional agents where they don't have

the MCP or the API or some sort of

direct connection to what they need to

do, uh

Grokbots can go off and do things on

their own even if they don't have the

perfect level of access and we'll get

into how that works in the demos really

quickly. But, they learn from you,

they're proactive like I said, and they

have their own device. And so, they can

not only connect to other products

directly but they can use your tools the

same way you would. And I'll explain

what that means in a second. But,

overall what you need to know is

you can assign Grokbots tasks completely

end to end. So, for you, all you need to

do is delegate to them and the mental

load of having to check on your agents

and make sure they've done their work is

gone because in the ideal state a bot

just handles the full end to end flow

for you just like a colleague would and

they They figure it out as I like to

say.

Okay, with that

obviously a ton of founders in here. And

so, you probably know what GrokBot is

and you're wondering what can this thing

do for me. And so, there are a few

things that are really important to

understand. First, you all know your

responsibilities as founders, right? You

have three key execution pieces that

either make or break your company. And

those are one, you need to preserve your

focus. You have a trillion things

hitting you all day. Two, you need to do

that while maintaining velocity across

all of the things that your team is

shipping. And then finally, you need to

really protect protect your ability to

make great, high-quality insights all

day. That means good decisions and

planning for the future. And GrokBot is

uniquely positioned to make all of this

way easier. You'll see some features up

here on the slide, but I think most

importantly, GrokBot can handle all of

the distractions in your day-to-day

work. The stuff that is necessary, but

not necessarily the most important. You

can just hand off to GrokBot. And that

mental load that it saves you is

probably more important than anything

else I'm going to talk about today. And

so, it's worth you taking the time to

audit what that means for you.

The second is, like I said, it can get

its tasks done end-to-end. And so, that

means you really want to prompt your

bots to do all of the work for you. Not

just parts of it the same way you're

used to today, but really do all of it.

That includes the execution and the

verification of what it's done.

And then finally, I think there are

large amounts of information that we're

all consuming every single day. My

screen time on X today is very

embarrassing, and I'm sure your guys

hopefully is too. And what that means is

there's just a constant flow of

information. In order for you to

maintain the same level of quality on

your insights, you need to find a way to

triage that entire fire hose. And

GrokBots are really well positioned to

do all of that.

Okay, with that

it's pretty clear to most of us now that

this is the best time in history to

build something, especially in software.

And Lingji, who's one of our engineers,

who was talking earlier, mentioned that

he can ship way faster with Grokbot than

he ever could before. I'm sure all of

you have seen this at this point by

kicking off cloud agents.

Uh there is this ability to delegate

these full tasks that I will harp on

forever. Uh you can automate a lot of

the pieces that you have to think about

constantly with routines. So, you can

have them set on schedules, on web

hooks, on signals, so that once they're

taken care of once, they can just happen

forever. And then finally, and I think

most importantly on this slide, is you

can do things that don't scale, except

you can actually scale them, which is

really cool. I'll get into a demo around

how that works, but we've all heard the

stories of how most startups win their

first customer. There's some sort of

hacky approach where you build some very

niche

super janky prototype and just hope that

it works for them. And then when they

finally sign that contract, you breathe

a sigh of relief, and then you do it a

hundred times again. And so, with this,

and with Grokbot, you can now make all

of this happen without the constant

headache that comes with it. And I'll

get into a demo about that in a second.

But, we're very excited about what this

means for founders specifically, because

you're all generally the most

high-agency people out there. And so, if

you have a product that enables that

agency, we get to some very, very cool

ships coming out in the next few years.

Okay. Let's get into some use cases that

I'll be harping on today.

Obviously, you all experience your own

unique pain points, but these are a

pretty good reference point for how you

can use Grokbot in your day-to-day. And

the four I'm going to talk about are

first, closing customers. So, this is

the do things that don't scale part.

It is

way easier now than it has ever been to

take your customers and go with them end

to end without you having to do a lot of

that hand-holding and the intimate

conversations. You can really focus on

just getting your bot to handle most of

it, and then step in when absolutely

needed.

The second is product changes. As you

know, engineers ship way faster now.

You're probably shipping way faster, and

staying across that many people shipping

that quickly can sometimes leave you

with some pretty embarrassing moments.

There were actually times when I was

demoing Grokbot in its earliest forms,

and we removed a certain feature uh that

was in the sidebar, and I was so used to

pointing at it. And when it was

unshipped, because I was just, you know,

busy that day, I didn't see it. And so,

I was kind of demoing and pointing at

nothing, which was really embarrassing.

I hope someone else has gone through

that experience, cuz it is not fun. But,

this will go through how you can stay

across all these product changes. The

third is adapting to competitors. I

think this is the most fun demo we're

going to do today, and also one that's

been pretty useful for me, at least. And

so, basically, there is now an

opportunity, because these bots can work

as you, to go through other products and

other competitors, and get a lot more

insight than you ever could manually.

And then finally, shipping feedback

quickly. We all get feedback all day.

Believe me, we get more feedback than

probably anyone, and a lot of it is not

very nice, so please be nice to us. Uh

but, shipping feedback quickly is super

important. And so, I will go through how

you can do that as a founder.

All right, without further ado, let's

meet my squad here. Uh we're going to go

through four bots today. The first is

the close bot. That is the one that

handles my customers. The second is prod

bot, which is what figures out what's

been shipped and helps me stay across

all of it. The third is stock bot. That

is the competition stalker. And the

fourth is proto bot, which is pretty

fun. Uh it makes some designs for me,

but it also turns feedback into PRs. And

then, we have a little guest star that

I'll talk about in a second.

Okay, with that, let's get into the

actual demos.

All right, here is my Grokbot interface.

I'm on a demo interface right now.

Usually, there's a lot more mess on this

screen, so hopefully it's a little

cleaner and easier to parse for you

guys.

The first bot I'll start with is close

bot. And there are two key things that I

want you guys to keep in mind while I go

through this. The first is remember that

your bots can compound. So, you can

constantly be feeding them insights and

information, and they will store it,

reference it when necessary, and get

better over time, which is really

important. The second thing is like I

said, they can use your computer and

work with your tools, which gets really

important as you start to try to do

things end to end. So, CloseBot here,

and I'll leave a little cheat sheet on

the side for you guys, does a few

things. It focuses on prepping calls.

So, when you need to talk to a customer,

it will do a ton of deep research on

them. It'll look through our telemetry

and what we've done with them, and make

sure that we have complete insight into

how they work. And then it will finally

do a walk-through of what they're

building and their site in case it's

relevant to what we talk about. Uh there

are a few other steps, but I'll start by

asking my bot to prep the call.

And in this case again, I'm in a demo

environment. I don't want to leak

anyone's personal data or any company's

personal data, but this bot will go off

and basically prep a call for this

company that we're calling Northwind.

And the way it does this, and the way I

actually do this right now, is it pulls

all of the data for its usage. So, if

you are a founder and you obviously have

that telemetry, it is very good for

customers that are just trying out your

product or on a free trial to understand

what they're actually doing within your

product. And then also to understand who

they are. Those are probably the two

most important things before you you get

onto a customer call, because that is

how you resonate with them in the

quickest manner possible. Again, you

don't have that long with these folks.

You generally have around, you know, 15

to 20 minutes with your customers. And

so,

what's really important is you get to

the crux of what they need and match it

with what you're doing. And bots help

you do that really quickly. And so,

right now it's going through

essentially some demo prep. But what

I'll show you is an example of what I

tend to use day-to-day when I talk to

founders.

This is a call prep HTML file.

Obviously, it doesn't look perfect and

that doesn't matter cuz I'm not sending

it to anyone, it's just for me. But

basically, the goal of this is to really

understand who these people are that I'm

going to be talking to, what their

product does, which Croc Bot will

research on its own, and then walking

through their site. The reason the site

is really important is actually because

the site tells you a lot about what they

care about first and foremost, which is

why I like including some screenshots of

what they're building. But more

importantly, I am constantly finding

bugs on people's sites. And it is so

nice for me to just be able to go to

them and say, "Hey, fix this thing.

Look, your cookie banner is on top of

your submit button and that sucks for

everyone, so just go fix it." And for

them, it's really nice cuz they get some

feedback that's super actionable. And

so, my bot has gotten very good at

figuring out what will resonate with

folks. And so, I have it do this every

single time and without fail, it has

found some issue that comes up with some

site, which is a really cool way to open

a call. So, just one of those quality of

life things. As we keep scrolling,

you'll see these are placeholder

numbers, but you'll see that

you get a lot of the activity that's

really relevant to what you want to talk

to them about. So, we know in this case

that these folks already have some

seats, they already have done some

meetings, uh this product is like a

meeting tool, they have some sort of

arrangement, and because I can look at

this graph, I can see what their usage

looks like.

And so, I look at this every single time

when I talk to founders try and

understand are they really accelerating

and is there a specific feature that I

need to work with them on or are they

declining and there's some sort of

objection that I need to get into. With

you guys, you will all have your own

versions of this use case, but it is

so, so important to just spend 5 minutes

before the call figuring this stuff out.

Now, for the really cool part that I'm a

little conflicted on, uh

recommendations.

The bot has gotten very good at figuring

out what I need to talk to founders

about and your case what you will

probably need to talk to customers

about. And what that means is it will

give me a few key recommendations about

what I should do with that founder or

customer on that call.

And so the most important piece for you

guys is you have your customer

conversations is to come in armed with

some sort of knowledge. And this

automates getting some of that

knowledge. There are a few other pieces

here. It talks about some risks. And I

think the most important part is that

you come in prepped. You don't have to

spend the hour and a half of your time

doing this and it does it on a routine.

So every day it will look at my calendar

and look at the meetings that I have and

just prep them. And I can trust 5

minutes before I can go in and read that

stuff.

Okay. So, that's part one which is

prepping the call.

Part two is what happens after the call,

right? We want to go end to end. We

don't just want to stop there. And so

the same bot also does a little bit of

the compounding for me. And what that

means is after every call it will review

the granular transcript and figure out

what that person resonated with or

didn't. And you can do this with all of

your customer calls as well, right? And

arm your teams with it. You basically

have your bot look at every single

transcript and for example, if in this

case I was talking about some new

note-taking feature that they didn't

really care about and they expressed

that within the call, for the next one,

for the preparation document, this tool

will get better at making sure that I'm

not talking about that feature again

unless it's really relevant. And so over

time, if you give this two or three

weeks, it becomes really, really

powerful because not only do you not

have to go through other people's calls

and you can leverage theirs, but your

calls just get way better and you stop

tripping over yourself when you talk

about the same things.

Okay. That's part two.

Part three is support. Basically, we

have a lot of customers and a lot of

them need support. And right now there

are not enough people to support all of

those customers on their own, just

one-on-one. And so, you need to be able

to scale up your support. And a lot of

founders leave this to the very last

thing. Believe me, I've been there, uh

and it makes your life very, very tough

to handle both getting new customers

through the funnel and then also

supporting the pre-existing ones. And

so, you have a real opportunity to

automate this with Grockit, but the most

important part that makes this really

work well is that you spend the time

empowering your bot to actually support

your customers. And what that means is

you not only connect it to your data,

but you connect it to your billing, and

you connect it to the risky pieces that

you're scared to give because that is

where most of the support struggle

happens. And so, that in combination

with the compounding piece leads us to

this really cool fourth section, which

is activation. And so, a lot of you

probably know your wow moment at this

point. You know when your customer is

activated, you know when they're going

to stick around.

And so, how do you incentivize more of

that, right? How do you decrease time to

value? One of the easiest ways to do

that is to give people money so that

they get there. And it doesn't have to

be much, right? But just getting them

across that hump is what turns people

into great customers. And so, I have

hooked up this bot to actually do the

work, and when an activation event

happens, where in this case, again, I'm

using a note-taking app, if a template

is shared with your teammates, we have a

thousand dollars, which is a crazy

example, uh ready to send. And it will

automatically send that email with those

credits so that that user or that

customer can leverage those credits, and

they feel rewarded in that moment. And

so, instead of you having to monitor

every single customer's journey and do

this manually, or taking a tool and

building it from scratch, you can just

offload it to your bot and not think

about it again. And it will run the

campaign on its own.

Okay, there are a few other pieces that

are pretty obvious around the end-to-end

customer journey, right? You want them

to sign contracts, which you can get

Grockit to go back and forth with them

on. You want them to figure out your

pipeline and actually generate it with

outbound, which Rockbot is very good at.

And then you want it to actually make

sure that your calendar is filled, and

it can access your calendar and do that

every single time. So, these are all

things that happen autonomously, and I

no longer need to worry about 99% of

this journey. There are cases where I

want to step in with a customer, and I

want to understand, "Hey, why didn't

this call resonate?" I want to go

deeper. And for now, what that means is

I spend my time doing that, which is

actually very enjoyable. I actually

enjoy talking to customers, so that's

what I meant when I was saying like this

is a little emotionally complicated for

me, in that some of this is really fun

to do. And so, I have to intentionally

go in and steal some of this back from

my bots rather than letting them do all

of it. But, uh it is a very, very cool

time to be able to scale to thousands of

customers with just your bots instead of

you having to go do this yourself. In

that way, like I said, you can focus on

making good decisions consistently,

maintaining velocity, and maintaining

focus.

Okay, that was bot number one.

Let's go to bot number two.

This is Prodbot. Uh

I mentioned that example earlier, where

as you start to have more and more

engineers shipping more things and

unshipping more things, you're doing

yourself, you get confused around what's

live and isn't. So, Prodbot is basically

a bot that

does a lot of this work for you in terms

of staying across what's been shipped.

And so, I'm currently asking it to give

me a daily rundown of Flylo, which is

the demo

surface that we used earlier in the PM

conversation as well. And Flylo is a

tool for flights and airlines and

booking travel. And what I like to have

this bot do in my actual day-to-day is

not only go through all of the PRs and

the linear issues that come in, but also

walk through the product end-to-end

itself. Remember, your bots have their

own computer, so they can use whatever

surfaces you use. And in this case, that

means going through the site that the

bot is assigned to, figuring out what

has changed, and then mapping it to its

experience. So, if it has a login for

the specific site, it can do a lot of

this work for you. You can see some of

it popping up right now. What you'll

notice if I scroll through this is it's

giving me a rundown. So, it gives me

here's what's shipped. These are some

examples of things that have shipped

recently. It also gives me things that

were unshipped avoid that embarrassment

again. And most importantly, it will

give me some decisions and some key

things where, you know, now that we ship

quickly, we don't intentionally make all

of these micro decisions all the time.

And so, it tries to catch some of those

that we want to be a little more

intentional about.

And so, overall, what you end up with is

a bunch of screenshots of the site. So,

the bot is going through it. And then

also, you end up with a video of the bot

basically running through the site

itself. And so, that way you can see

what it does without having to do it

yourself. So, if you ever want to get in

deeper, you can always ask your bot to

take a video of the surface while it's

doing its work, which has become the

fastest way to verify if something is

done well or not.

The other piece is that you can connect

this to your data. So, you can actually

see what the results of different ships

are because you connect it to your

metrics. And that way, instead of you

having to view that dashboard all day,

you just see it here. And it is

proactively given to you, which I think

is one of the most important parts about

bots, that they will surface information

to you as relevant and as necessary. And

so, I think again, what's really

important is as long as you enable them

to have all of the right data, they can

help you make great decisions and also

help you stay across what your team is

shipping.

Okay.

Now, for my favorite bot, uh stock bot.

Right now,

everyone is probably distracted by their

competitors. And it is very easy to ship

things, but what's not easy is checking

what other people are shipping.

And so,

what StockBot does is it basically will

go find your competitors. It will sign

up for autonomously and go through their

product, and then it will give you a

full rundown of basically everything

they do. So, that includes what they've

shipped, their change log, what they're

posting on X, who they're hiring for,

which is actually a really good way to

get signal on what people are building,

and finally just who their team is and

what they're prioritizing. And over

time, this also compounds. As they learn

about more and more competitors, your

life becomes easier because you start to

get more signals into how to position

yourself in the market, and then also

how to counter position to what they're

shipping. And so, what I'll do right now

is kind of ask it to do a competitor

pulse right now. And basically,

I want it to

check on Notion and Craft. Those are the

two hypothetical competitors we have

with this note-taking app. And so, it

will go off and do all of this in

parallel. And it has been doing this for

a while. So, it is constantly running

pulses. You see some of its routines on

the side here. And what you'll notice is

that these routines run relatively

often, every few days, but what that

also means is I don't have to do this

myself. It will run the routine, come

back to me if there's something

relevant, and if not, it will stay

silent and do its thing. And so, this is

one of those

ambient bots that's really important to

just have around because it will get a

lot of this work done for you around

competitor analysis, and you don't

really need to think about it. And as

you get exposed to more and more of

these decisions that these companies are

making, you actually start to build the

muscle around why your decisions are

different, and you start to understand

truly what your positioning is relative

to theirs. So, you'll notice it's

cooking and

doing some of the the research work.

What we see here is let's start with

Craft, which is a note-taking app.

Basically, it has created a little

teardown in HTML if this thing loads. Um

if not, we can just look at it here. It

again just created a video where it's

going through and it will sign up, it'll

put in its information, it'll use a

throwaway email address, uh and then

basically go through the entire flow.

So, this is the onboarding flow. And

it's looking through, "Hey, what is

different about their onboarding versus

our onboarding?" Uh and it gets you to

the start page. It will also start to

actually like test it itself. So, it

will write in Craft, which is this again

this note-taking app, and tell me what

went well and what didn't, and then give

me a little overview of how it works. Uh

Craft is not hiring actively right now.

So, that's good for us to know. And

then, the final thing that I've done

with this one, which you know, might be

corporate corporate espionage, but you

know, do what you want with it and be

responsible, is basically I have it

email people that have churned off. A

lot of you have insights into where your

customers are churning. So, you know uh

from Salesforce or whatever your tool is

that X customer left to Y tool. And so,

you can actually go and have your bot

reach out to them and understand why

that is. You don't need to go win them

back in that moment, but just getting

that insight is really, really

important. And so, if you have that

signal, it's another good way to course

correct your positioning versus others.

You can see the same thing for Notion.

Notion has a bunch of hiring, and so

I've kind of asked it to truncate uh

because they're hiring a ton of people,

but it's still important insight to get.

And so, I'm showing you these these two

examples, and this is one where it's

signed into its own Notion account. It

authenticated via email and is basically

doing work in it and giving me what that

experience looks like. As it starts to

see the differences in what's shipped,

it will focus on those specific things.

Okay, enough about this bot, but

what I will say is I will share this bot

after this, and I will toss up a QR

code, so if you want to steal it, you

totally can.

All right, let's move on to bot number

four. So, bot number four is my proto

bot, and this bot is basically really

good for just thoughts that I have in my

head when I want to get them prototyped,

but also it's really good for when we

get customer feedback, and we want to

just explore what this would look like

to ship. And so, what proto bot does

really well is it actually has right now

its own version of Grokbot running on

its computer. And I think I've shared

this a few times before, but I've given

it its own account that is not it. It

has its own separate entity, and it runs

through a lot of different bots, test

them out, uh and helps me with some of

my prototyping and also QAing. But I

think most importantly, and the reason

this matters, is because it has access

to its own product, it can do a lot of

this prototyping with the context of

what the product looks like today. So,

if I say

pull the most recent

customer feedback,

it will find some demo feedback, pull it

in, and then it will probably just start

working on fixing it. And so, you as a

founder can probably envision yourself

and your product uh piping all of your

feedback channels. So, that means things

like X, your support inbox, or any other

signals that you see in your emails, and

putting them all into a single pipeline

that goes to a bot that just kicks off

PRs and solves them.

That's kind of how some of our engineers

work internally, which is very cool

because you'll see the full feedback

loop of feedback to ship to deploy

happen in hours, uh which is awesome,

and it happens automatically and

organically, which is very cool. So, I

think

you guys all know that adapting to

feedback is really important, especially

in the early stages. You still need to

make the choice about which feedback to

take versus not because

you're the visionary. Your job is

supposed to be to figure that out. And

in this case, the fact that you can move

this quickly means the main bottleneck

should be your decision-making. It

should be whether this

feedback should be shipped or not. And

so it will basically do the work.

Right now it's saying that the customer

thinks that the share button for bot

templates isn't exciting enough and they

want it to pop. Um

so it'll probably end up working on that

for a little bit, which is very fun. Uh

in the meantime, though, what I will

show off is two final bots. One is my

Yap Bot. So this bot has one purpose and

one purpose only. It is

built and exists to talk like me. So it

looks through my email, Slack, iMessage,

any other form of communication that

I've done, and it learns from how I

talk.

And it doesn't just learn once. I think

this comes back to the compounding

piece. It learns over time. So every

week or so, or you can set it to

whatever schedule you want, it will take

everything I've sent for the day because

it has access to all those tools, and

essentially learn from them and get

better over time. So now I can trust

this bot to go and talk as me. And what

you'll notice is these other bots are

actually coming in and asking it for

help. So they are proactively bringing

in Yap Bot to go talk like me

across all of the different services,

and I don't need to do this myself.

After they do this a few times or I

encourage them, like I said, they learn

to loop in the other bots as needed. And

this bot might seem like a small one

because it's very simple, but it's so

important, especially if you're trying

to do any sort of outbound or move

quickly on communications. It's nice to

have a bot you can just trust to do this

stuff.

Obviously, you have some emails that are

really sensitive, so you might ask it to

just keep them as drafts rather than

just sending them right away. But even

then, it will learn from the delta

between the draft it created and what

was actually sent and get better and

better over time. With the end vision

being that you don't need to think about

it at all.

Okay.

Final tip, I have a miscellaneous bot,

and this bot has one job, which is

basically to be kind of a trash can for

all of the random requests I have.

Today, I wanted to see if Drake's album

dropped. It has not yet, sadly. But,

what's really cool about this one is I

can just ask it random things without

polluting the context of the other bots.

And if it ever has any important task to

do where it needs to transfer that

context, I can just ask and say, "Hey,

you learned about XYZ. Go tell ProdBot

about what you've learned so that it can

get better in the future."

Sadly, Drake's album isn't out. I

checked Instagram, but

who knows. We'll get there maybe later

tonight.

Okay. Those were all my bots. I think

ProtoBot is still still going. Uh it's

kicking off a cloud agent, and hopefully

it finishes sometime soon. But, you'll

notice because it has access to GrokBot,

it can actually just

take a look at the interface without

needing to go find it anywhere. And it

can drive it and QA it. And as these

tests happen, it's very easily

verifiable whether it's shipped the

right thing or not. And so, I think all

of these bots are very powerful, and

most importantly, they're all powerful

in conjunction. So, when CloseBot gets

some feedback, it can pass it to

ProtoBot. Or, when ProdBot is trying to

get across some of the key product

decisions that we've made, it can pass

that context off to CloseBot so that it

can sell the right stuff.

And overall, I think the key framework

that you folks need to keep in mind is

you want to start to try and productize

yourself as much as possible and give

away

all of your Legos, no matter how

delightful they are, so that you can

focus on the highest leverage thing,

because that is what helps you win in a

world where everyone is shipping

just as fast, if not faster, for now.

So, keep all that in mind, uh but those

are my bots. Let's go back to

presentation.

Okay.

Some final pieces.

What we learned.

Let your bots run free. I am going to

say this forever. Give them access to as

much as you are possibly comfortable

with because that is the only way they

will be able to do work end-to-end.

You want to invest in them. So,

you might find times where you need to

course correct a bot. And with an agent,

you might have the instinct of, "Man, I

spent too many tokens on course

correcting it. The context is polluted.

Let me just get rid of it and start a

new one." In this case, your key

advantage is that your bots get really

good as you spend more time with them.

And

obviously, as the team has learned

internally, the more time you spend, the

better you do. And so, it's really

important to really believe in your bots

the same way you would with employees.

And the other piece to keep in mind here

is the other way to invest in them is by

giving them really good skills and

tools. So, it's very easy to say, "Hey,

make this cooler." And that could be

your your prompt that you want your bot

to execute on. But obviously, it's not

going to do a great job and it's going

to probably get stuck somewhere and ask

you a few questions. The more

intentionality you put behind that task

in the first place lets you repeat it

over and over again without that many

hitches.

And then finally, it is worth you taking

1 to 2 hours and just thinking about

your day.

I know that sounds dumb. I know you're

like, "I need to move quickly." But it

is so, so important to just take the

time. I don't care when. Just do it and

figure out what you want to delegate.

Because doing that intentionally will

save you so many hours versus just

spinning up bots and hoping they do

things for you without having a true

intent around what they should do.

Okay.

Now, I have a bonus round with some tips

and tricks. I was watching the live

stream earlier and some people were

like, "This is expensive."

Which is, you know, true in some ways,

not true in others, and we're working on

it. Uh

but there are some really easy,

high-leverage tips that can make your

life a lot easier.

The first is that browser use is super

powerful and it unblocks your bot from

doing

a lot of things that it couldn't do if

it didn't have MCPs or APIs or some

other connection, but it's also

expensive to run multiple times. And

the easiest way to solve for this is to

bias towards using APIs and using

interfaces that people have already

built or to actually kind of hack it a

little bit. You can ask your bot to look

at network requests while it does a task

once and then figure out which APIs are

being hit while it's doing that task

and then go and start to just hit those

directly, which

takes way less time, first of all, and

is also way more token efficient because

you are no longer needing to go through

the browser interface and you can just

do it all directly. So, ask your bot,

and this is true for all optimizations,

by the way, that you guys have probably

been thinking of or taking notes on,

always just ask your bot how to do it

because it will figure it out for you,

which is very nice. But

be wary of browser use more than once,

uh and if you can get around it and

scale quickly, you absolutely should.

Second piece, routines.

Uh when I was looking through some of

the data around the frequency of

routines that people set, I was a little

shocked uh and it freaks me out how

often you guys are running things. But I

think the most important part about

routines is to audit them. And you don't

have to do this yourself. Again, get a

bot to do it for you, but the most

important piece is

be very intentional about how often your

routines are running. They're really

powerful, but most people over-index on

how often they need to be running and

they think, "This routine is so

important, I need to run it every 15

minutes," which comes out to 100 times a

day. So, that is a very expensive

routine.

See if you can be a little more nifty

with them. So, it's not just running

them fewer times. If you really need a

routine, try and run them on webhooks or

try and run them with some sort of

inbound signal that will let your bots

actually take in an input and then run

it rather than just having it blindly

run on a schedule. So, those two things

alone will probably save you a bunch in

tokens. I know there was some demand for

that. Okay, even more final tips before

they cane me off stage.

Uh

make a voice bot. Obviously, I love

mine. Uh

please do this for yourself. It is the

most underrated way to get words out to

other people. It's have a bot that

copies your voice.

Uh import your cookies. This lets you

stay signed in across a lot of different

tools and it also stops you from having

to constantly take over the bot's

computer and help out. Uh group bots by

expertise. This is kind of a personal

preference thing, but I love having my

bots grouped by what they do. And so, if

a bot is really good at just handling a

customer, I will give it everything

customer related. And if a bot is really

good at data analysis, that will be its

sole job. Because sometimes there weird

compounding pieces that happen that we

don't even know about. And so, when

you're giving it two what feel like

completely different tasks, you can

still get some of the compounding

benefits as long as they all fall under

the same expertise. There a few more on

here like great skills which we talked

about, how bots can learn from you, and

then auto optimization routines, but I

think the last one is also pretty

important. Having a bot that just exists

to optimize your other bots. That means

better routines, figuring out where they

went wrong or where you had to ask

multiple times for something, and then

making sure that doesn't happen again,

and overseeing how the other ones work

and improving them is way easier than

having to do a lot of this yourself. So,

save yourself the time. You set it once

and then you forget it, which is really

nice and I don't see enough people doing

that.

Okay. So, that is close to the end of

what we've been doing here. Thank you

for your time and attention. I am going

to leave a QR code for stock bot. If you

guys want to steal it, it's a fun one.

You should try and use it on us. I think

that would be cool. I want to see what

people come up with.

But, I really appreciate everyone being

around. I think one of the the coolest

parts about these bots and where they're

headed is just how creative you can be.

The uh sorry, the amount of

different bots and different

combinations of bots that I've seen has

really blown me away. And I think

founders are the perfect group to figure

out the edges of this entire thing. I

don't think we've hit the limits yet.

And as we get closer and closer to

figuring out what these bots can

actually do and what they can't, uh

we're going to be looking for signal

from you guys. So, really appreciate it.

If you are on the live stream, we're

going to send you back to Matt, Lauren,

and Roshan to go and continue cooking.

So, appreciate it. Thanks.

Okay.