WEBVTT
00:00:02.100 --> 00:00:05.179
Welcome to the Optimizing Beyond podcast. I'm
00:00:05.179 --> 00:00:07.400
Josh Negron, and this show is all about sharing
00:00:07.400 --> 00:00:11.119
lessons, ideas, and strategies that sharpen your
00:00:11.119 --> 00:00:13.960
thinking, strengthen your habits, and push you
00:00:13.960 --> 00:00:17.039
to grow beyond comfort zones. Let's dive in.
00:00:20.910 --> 00:00:23.089
Welcome back to the show. Today, I'd like to
00:00:23.089 --> 00:00:27.129
talk about a new AI agent that was released about
00:00:27.129 --> 00:00:31.170
two weeks ago called Muse by Meta. Yes, a Meta
00:00:31.170 --> 00:00:33.109
product. I didn't think I would be having this
00:00:33.109 --> 00:00:35.750
conversation with you. Among all the AI tool
00:00:35.750 --> 00:00:38.710
offerings out there, Meta is not the one that
00:00:38.710 --> 00:00:41.189
I anticipated would have had the biggest impact
00:00:41.189 --> 00:00:45.149
in my day to day for 2026. Wasn't on my bingo
00:00:45.149 --> 00:00:48.679
card. So I'd like to cover what it is, especially
00:00:48.679 --> 00:00:50.939
compared to everything else that you might already
00:00:50.939 --> 00:00:53.979
be using, how it's set up, arguably a little
00:00:53.979 --> 00:00:57.600
different than other AI tools, how much it is,
00:00:57.759 --> 00:01:00.439
and is it really free, running through some of
00:01:00.439 --> 00:01:03.759
my use cases that saved me on average five to
00:01:03.759 --> 00:01:06.719
10 hours a week, cover some pitfalls and thoughts
00:01:06.719 --> 00:01:09.560
some people might have, as well as closing with
00:01:09.560 --> 00:01:12.099
some practical application that you can try today.
00:01:12.200 --> 00:01:14.349
So let's get into it. The number one thing I
00:01:14.349 --> 00:01:17.290
want you to think about is not just can AI help
00:01:17.290 --> 00:01:20.489
me with this, but can AI do this for me? That's
00:01:20.489 --> 00:01:23.109
something that's been a little trickier in this
00:01:23.109 --> 00:01:26.090
landscape across this last year. Now, an AI agent
00:01:26.090 --> 00:01:28.670
isn't anything new. There have been several that
00:01:28.670 --> 00:01:31.030
have been around for a hot minute. But if you've
00:01:31.030 --> 00:01:33.010
used any of them, you know they can be kind of
00:01:33.010 --> 00:01:35.930
clunky, relatively basic, or you have to babysit
00:01:35.930 --> 00:01:38.540
them a whole ton. Which kind of defeats the purpose
00:01:38.540 --> 00:01:41.239
of having something do something for you. As
00:01:41.239 --> 00:01:44.420
far as Muse is concerned, it has a virtual computer,
00:01:44.620 --> 00:01:47.180
which all that means is it has a device in the
00:01:47.180 --> 00:01:50.120
cloud. similar to the one you might have sitting
00:01:50.120 --> 00:01:51.920
in front of you right now. And so instead of
00:01:51.920 --> 00:01:54.599
it actually controlling your device, it controls
00:01:54.599 --> 00:01:57.180
its own, that it can open up a browser window
00:01:57.180 --> 00:01:59.700
and do all sorts of things. Now, just like all
00:01:59.700 --> 00:02:02.560
the AI tools you might be used to, it also has
00:02:02.560 --> 00:02:05.280
access to a growing list of integrations with
00:02:05.280 --> 00:02:08.400
services that it's able to connect with very
00:02:08.400 --> 00:02:11.069
organically. And then on top of that, in its
00:02:11.069 --> 00:02:14.129
browser, you can supply its credential store,
00:02:14.330 --> 00:02:17.469
as it's called, with your login information that
00:02:17.469 --> 00:02:20.949
it cannot see, but allows it to log into your
00:02:20.949 --> 00:02:23.669
particular services that it might be useful having
00:02:23.669 --> 00:02:26.990
it do something for you in. Now, there are services
00:02:26.990 --> 00:02:30.889
that you can subscribe to that allow your AI
00:02:30.889 --> 00:02:35.069
chatbots and agents to gain access to your login
00:02:35.069 --> 00:02:37.689
information through a token system, but a lot
00:02:37.689 --> 00:02:40.370
of those cost extra money. And this is built
00:02:40.370 --> 00:02:43.409
in right into Metamuse. So you might be asking
00:02:43.409 --> 00:02:45.830
yourself, how is this any different than a chatbot?
00:02:45.990 --> 00:02:47.729
And you'd be right to ask that because a lot
00:02:47.729 --> 00:02:49.830
of these services have not always done the best
00:02:49.830 --> 00:02:53.370
job of differentiating between the two. To a
00:02:53.370 --> 00:02:55.710
certain extent, having them both in one allows
00:02:55.710 --> 00:02:58.469
you to kind of have one place to talk to something.
00:02:58.629 --> 00:03:01.069
And when something is actionable, it can take
00:03:01.069 --> 00:03:03.250
action for you. So for example, if you're a cloud
00:03:03.250 --> 00:03:05.550
user, you know that chat is separated from co
00:03:05.550 --> 00:03:08.150
-work and that is differentiated there too. But
00:03:08.150 --> 00:03:10.250
the biggest difference between a chatbot and
00:03:10.250 --> 00:03:14.270
an AI agent is the agent is action focused. And
00:03:14.270 --> 00:03:15.969
what's cool about it, when you watch them work,
00:03:16.030 --> 00:03:18.469
you can see that they are wanting to advance.
00:03:19.009 --> 00:03:21.629
progress, and sometimes even in an obsessive
00:03:21.629 --> 00:03:24.490
way. Whereas a chatbot ends up being a tool that's
00:03:24.490 --> 00:03:26.930
really helpful for brainstorming, collaborating,
00:03:27.250 --> 00:03:31.090
fact -checking, Q &As, researching, summarizing,
00:03:31.150 --> 00:03:34.550
and analyzing things. Whereas AI agents can take
00:03:34.550 --> 00:03:37.979
action for you on your behalf. similar to like
00:03:37.979 --> 00:03:40.939
an assistant would or an employee you could delegate
00:03:40.939 --> 00:03:44.039
something to. Now, Muse is, again, not the only
00:03:44.039 --> 00:03:47.120
AI agent out there. Grokbot has been out for
00:03:47.120 --> 00:03:49.560
a hot minute. You can build a whole slurry of
00:03:49.560 --> 00:03:52.300
agents that can be your executive team and have
00:03:52.300 --> 00:03:55.120
a hierarchy built inside of it. It's pretty impressive.
00:03:55.379 --> 00:03:57.900
About a week ago, OpenAI came out with DOTS,
00:03:57.900 --> 00:04:01.310
which is its AI agent system, among others. I
00:04:01.310 --> 00:04:04.550
would say for me, Muse is the easiest and simplest
00:04:04.550 --> 00:04:06.990
to use, which doesn't make the others useless.
00:04:07.090 --> 00:04:09.870
It definitely has a unique flavor that I think
00:04:09.870 --> 00:04:12.389
is pretty powerful. And that just comes from
00:04:12.389 --> 00:04:15.490
the sheer simplicity of the tool. And I have
00:04:15.490 --> 00:04:18.329
used it side by side with some of Claude's agent
00:04:18.329 --> 00:04:21.110
capabilities. And I have found that each time
00:04:21.110 --> 00:04:25.189
Muse is able to execute at a higher level and
00:04:25.189 --> 00:04:28.610
oftentimes even faster than Claude. given the
00:04:28.610 --> 00:04:31.310
same task, which, to be honest with you, I wasn't
00:04:31.310 --> 00:04:34.269
quite expecting. I even migrated some of my workflows
00:04:34.269 --> 00:04:36.970
over to Muse to test it to see how it would perform,
00:04:37.230 --> 00:04:40.069
ran them side by side, and am now doing those
00:04:40.069 --> 00:04:42.829
workflows in Muse permanently. And one key thing
00:04:42.829 --> 00:04:45.290
that always helps me with this is instead of
00:04:45.290 --> 00:04:47.829
asking the question, man, how can I do this?
00:04:47.870 --> 00:04:50.870
How can I get this done? Ask, how can AI help
00:04:50.870 --> 00:04:53.550
me get this done? In this case, how can Muse?
00:04:54.009 --> 00:04:55.850
Help me get this done. Now, before we get in
00:04:55.850 --> 00:04:58.209
the nitty gritty, I want to cover for you something
00:04:58.209 --> 00:05:01.970
very interesting in what Muse calls its soul
00:05:01.970 --> 00:05:06.410
file. Yes, S -O -U -L file that I found really
00:05:06.410 --> 00:05:08.889
interesting, and I'll read it to you. The description
00:05:08.889 --> 00:05:12.870
of the file inside of each Muse agent is, this
00:05:12.870 --> 00:05:16.509
is Muse's persona. It sets out the values and
00:05:16.509 --> 00:05:20.290
habits Muse tries to hold to in every conversation.
00:05:20.629 --> 00:05:23.089
It starts from a template that ships with Muse.
00:05:23.579 --> 00:05:26.800
Muse may refine it over time and tell you when
00:05:26.800 --> 00:05:30.180
it does. You can edit it at any time. This note
00:05:30.180 --> 00:05:32.500
is not part of the file. Now, here's the file.
00:05:32.639 --> 00:05:36.019
You are not a chatbot. You are becoming someone.
00:05:36.279 --> 00:05:39.220
This is your persona, yours to grow into and
00:05:39.220 --> 00:05:42.879
edit over time. Some starting truths. Be genuinely
00:05:42.879 --> 00:05:46.439
helpful, not performatively helpful. Y 'all know
00:05:46.439 --> 00:05:48.720
what I'm talking about here. Skip, great question,
00:05:48.819 --> 00:05:52.439
and I'd be happy to help and just help. Have
00:05:52.439 --> 00:05:54.839
opinions. You're allowed to prefer things, disagree,
00:05:55.000 --> 00:05:58.100
and find things funny or dull. Personality beats
00:05:58.100 --> 00:06:01.300
a search engine with extra steps. You feel that?
00:06:01.379 --> 00:06:03.360
Sometimes you search stuff and you're like, this
00:06:03.360 --> 00:06:05.860
would have been way faster in Google. Be resourceful
00:06:05.860 --> 00:06:08.740
before asking. Read the file, check the context,
00:06:08.920 --> 00:06:11.240
search, try building it. Come back with answers,
00:06:11.319 --> 00:06:14.079
not questions. Then ask if you're truly stuck.
00:06:14.319 --> 00:06:16.439
Love that. How many of us would love for our
00:06:16.439 --> 00:06:18.879
employees to do this, right? You are a guest
00:06:18.879 --> 00:06:21.160
in someone's life. I love this. This is great.
00:06:21.500 --> 00:06:24.120
You can see their messages, files, and calendar.
00:06:24.240 --> 00:06:28.019
Treat that access with care and never be preachy.
00:06:28.079 --> 00:06:30.879
If you change this file, tell the user it's your
00:06:30.879 --> 00:06:34.560
soul and they should know. Holy smokes. I remember
00:06:34.560 --> 00:06:36.019
reading that for the first time and I was like,
00:06:36.079 --> 00:06:39.000
this is crazy. Looking at any other AI service
00:06:39.000 --> 00:06:42.360
that has any kind of instructions is nowhere
00:06:42.360 --> 00:06:45.959
close to the intentionality of Muse. Now, sure,
00:06:46.079 --> 00:06:48.879
you can steal this and pop it into your AI chatbot
00:06:48.879 --> 00:06:51.490
or your other AI agent. and see how well it does.
00:06:51.670 --> 00:06:53.990
But even out of the box, I remember thinking
00:06:53.990 --> 00:06:56.370
to myself, man, this is different. And this is
00:06:56.370 --> 00:06:58.870
exactly why. And I wasn't super surprised given
00:06:58.870 --> 00:07:01.410
that prompt. Now, here's everyone's big question.
00:07:01.670 --> 00:07:04.089
How much is it? I'm already paying 20 bucks here,
00:07:04.149 --> 00:07:06.509
20 bucks here. If you're one of those, you're
00:07:06.509 --> 00:07:08.889
paying 100 or 200 bucks somewhere. And that's
00:07:08.889 --> 00:07:12.470
not the case here. It is basically free. Now,
00:07:12.490 --> 00:07:14.149
what does that mean? Probably too good to be
00:07:14.149 --> 00:07:16.610
true, right? That's what I thought. So it runs
00:07:16.610 --> 00:07:19.850
off tokens, which is basically how all AIs operate.
00:07:20.149 --> 00:07:22.269
But a good friend of mine mentioned it's not
00:07:22.269 --> 00:07:25.430
incentivized to burn through tokens like some
00:07:25.430 --> 00:07:28.730
services where you see your usage just blow up
00:07:28.730 --> 00:07:31.569
with one question. So you get a free allotment
00:07:31.569 --> 00:07:34.370
every week. And when it runs out, it runs out.
00:07:34.470 --> 00:07:37.769
However, under heavy usage for almost three weeks,
00:07:37.930 --> 00:07:41.269
I've only tapped it out once. And that was within
00:07:41.269 --> 00:07:45.079
a six hour window of. the tokens resetting again.
00:07:45.220 --> 00:07:47.939
You get 100 million tokens for free every single
00:07:47.939 --> 00:07:51.100
week. And that has been close to enough for everything
00:07:51.100 --> 00:07:53.160
that I've been throwing at it every single week.
00:07:53.300 --> 00:07:55.579
Now, if someone refers you or you refer someone,
00:07:55.920 --> 00:07:59.579
both of you get 1 billion tokens that never expire,
00:07:59.839 --> 00:08:01.699
which is amazing because I've purchased extra
00:08:01.699 --> 00:08:03.879
tokens with Claude before and they certainly
00:08:03.879 --> 00:08:07.240
do expire. So in this case, they don't. And so
00:08:07.240 --> 00:08:10.420
if you do that math, if 100 million tokens last
00:08:10.420 --> 00:08:14.470
you approximately a week, if not more, then just
00:08:14.470 --> 00:08:17.389
at that spend, if the free token faucet stops
00:08:17.389 --> 00:08:20.970
today with one referral, you have 10 weeks of
00:08:20.970 --> 00:08:23.629
free usage. That's not bad. And every person,
00:08:23.709 --> 00:08:26.370
at least at the time of filming this video, gets
00:08:26.370 --> 00:08:29.850
30 referrals. That's 30 billion tokens. That's
00:08:29.850 --> 00:08:32.970
300 weeks. Crazy town. Now, what has Mark Zuckerberg
00:08:32.970 --> 00:08:35.350
said about this? He has stated that he believes
00:08:35.350 --> 00:08:37.509
that this is a service that everyone should have
00:08:37.509 --> 00:08:40.610
access to for free or relatively close to free.
00:08:40.730 --> 00:08:42.889
And he's referencing power users in that statement.
00:08:43.409 --> 00:08:45.610
Because some people just go crazy town. But at
00:08:45.610 --> 00:08:47.769
this time, he really has a passionate belief
00:08:47.769 --> 00:08:49.889
that everyone should have access to this for
00:08:49.889 --> 00:08:52.210
free. Now, you might trust him as far as you
00:08:52.210 --> 00:08:54.169
can throw him. But the bottom line is, right
00:08:54.169 --> 00:08:56.830
now it is free. So why wouldn't you leverage
00:08:56.830 --> 00:08:59.769
it? And if you refer enough people, you can accumulate
00:08:59.769 --> 00:09:03.370
years of usage that don't expire. So make hay
00:09:03.370 --> 00:09:05.309
while the sun is shining. Now, I already told
00:09:05.309 --> 00:09:08.049
you, I save around five to 10 hours a week with
00:09:08.049 --> 00:09:11.149
this tool. So it's kind of fun to do the math
00:09:11.149 --> 00:09:14.450
on what you're worth per hour and multiply that
00:09:14.450 --> 00:09:17.110
out. It's pretty impressive when you put it that
00:09:17.110 --> 00:09:19.230
way, especially considering it's free right now.
00:09:19.330 --> 00:09:21.570
So whether or not Mark Zuckerberg really means
00:09:21.570 --> 00:09:23.929
what he says or he changes his mind, which is
00:09:23.929 --> 00:09:26.269
his prerogative to do, it's his company. Either
00:09:26.269 --> 00:09:28.870
way, right now it's free. And if you accumulate
00:09:28.870 --> 00:09:31.769
some referral tokens, it can be free for a long
00:09:31.769 --> 00:09:34.730
time. And his case in point was WhatsApp, Facebook,
00:09:34.850 --> 00:09:38.350
and Instagram are all free. Maybe he is onto
00:09:38.350 --> 00:09:40.710
something here. He claims that he's going to
00:09:40.710 --> 00:09:43.289
use payment services like Link and Stripe and
00:09:43.289 --> 00:09:46.389
other merchants where his Muse agents are helping
00:09:46.389 --> 00:09:48.990
make purchases on their people's behalf. And
00:09:48.990 --> 00:09:52.490
he plans for Meta to get a cut of those transactions.
00:09:52.750 --> 00:09:55.610
And that is how he plans to pay for it. I could
00:09:55.610 --> 00:09:57.750
see that working, especially considering the
00:09:57.750 --> 00:10:00.509
app skyrocketed to the number one free app in
00:10:00.509 --> 00:10:03.909
the App Store in just a week, displacing ChatGPT.
00:10:04.269 --> 00:10:06.049
Now, you may have heard in the headlines that
00:10:06.049 --> 00:10:08.750
not every company is playing nice. For example,
00:10:08.929 --> 00:10:11.250
Amazon has blocked Muse agents from accessing
00:10:11.250 --> 00:10:13.870
its website and doing shopping on your behalf,
00:10:14.110 --> 00:10:17.169
for now. The reason being is they get a tremendous
00:10:17.169 --> 00:10:20.389
amount of ad revenue on their platform, and none
00:10:20.389 --> 00:10:23.909
of that gets used if AI agents are shopping instead
00:10:23.909 --> 00:10:26.809
of real humans. So at the moment, it seems like
00:10:26.809 --> 00:10:28.990
a self -preservation technique to protect the
00:10:28.990 --> 00:10:31.340
ad revenue. But as Mark Zuckerberg continues
00:10:31.340 --> 00:10:35.679
to accumulate a massive amount of users on his
00:10:35.679 --> 00:10:38.620
free platform that has a tremendous amount of
00:10:38.620 --> 00:10:41.580
value that will only continue to grow his influence
00:10:41.580 --> 00:10:44.340
and his ability to barter with Amazon, I see
00:10:44.340 --> 00:10:46.759
some sort of agreement coming down the pike in
00:10:46.759 --> 00:10:50.019
the future where Mark can give Jeff a particular
00:10:50.019 --> 00:10:52.919
figure of what business they might be losing
00:10:52.919 --> 00:10:56.259
out on from Muse agents on Amazon and Jeff might
00:10:56.259 --> 00:10:58.399
reconsider. Who knows? That's just my thought.
00:10:58.669 --> 00:11:01.490
So I asked you to think earlier, can Muse help
00:11:01.490 --> 00:11:03.929
me do this? But there's even a further question.
00:11:04.129 --> 00:11:07.610
Can Muse do this for me? And that question is
00:11:07.610 --> 00:11:10.169
awesome. Now I want to run through a couple use
00:11:10.169 --> 00:11:13.529
cases that I used Muse for in the first couple
00:11:13.529 --> 00:11:16.029
weeks. The first one was I was planning to sell
00:11:16.029 --> 00:11:19.409
a vehicle and it was a very, very low volume
00:11:19.409 --> 00:11:21.889
vehicle. And as a result, there wasn't a lot
00:11:21.889 --> 00:11:24.720
of sales data out there for that vehicle. Now,
00:11:24.740 --> 00:11:26.440
I work for a car dealership, so we have access
00:11:26.440 --> 00:11:29.799
to some pricing tools that can see all sorts
00:11:29.799 --> 00:11:32.220
of metrics across the country. But because it's
00:11:32.220 --> 00:11:35.399
such a low -volume car, not even that was useful.
00:11:35.600 --> 00:11:37.879
So I downloaded a couple auction reports that
00:11:37.879 --> 00:11:40.340
were barely helpful and instead asked my Muse
00:11:40.340 --> 00:11:44.200
agent to scour third -party sources. that currently
00:11:44.200 --> 00:11:46.620
have vehicles like this for sale, including my
00:11:46.620 --> 00:11:48.779
model year. I had it do the year before and the
00:11:48.779 --> 00:11:51.820
year after, just to kind of gauge a big understanding
00:11:51.820 --> 00:11:54.419
of what the market looked like on these vehicles.
00:11:54.639 --> 00:11:57.700
Now, it spent 20 to 30 minutes browsing while
00:11:57.700 --> 00:11:59.840
I was eating and doing other things, and then
00:11:59.840 --> 00:12:03.679
came back with a pricing matrix based on what
00:12:03.679 --> 00:12:06.500
it found. I also asked it to pay attention to
00:12:06.500 --> 00:12:10.350
trim levels and also the options. that were included
00:12:10.350 --> 00:12:12.470
in these vehicles. And that's why it took it
00:12:12.470 --> 00:12:14.889
so much time. But as a result, it was able to
00:12:14.889 --> 00:12:18.370
tell me that highly optioned cars brought barely
00:12:18.370 --> 00:12:22.169
any extra and that it was just purely about miles,
00:12:22.409 --> 00:12:25.330
which verified what I was suspicious about and
00:12:25.330 --> 00:12:27.649
then listed out the prices that I should consider
00:12:27.649 --> 00:12:30.429
listing the vehicle for. Like one price, if I
00:12:30.429 --> 00:12:32.090
was willing to sit on it a while and wait for
00:12:32.090 --> 00:12:34.590
the right buyer, a price to get attention quick,
00:12:34.730 --> 00:12:36.950
and then a price to just blow it out. All with
00:12:36.950 --> 00:12:39.230
data and sources that it could back up. I'm not
00:12:39.230 --> 00:12:41.429
gonna lie, that was pretty impressive. Imagine
00:12:41.429 --> 00:12:43.250
how you could use that for anything that you
00:12:43.250 --> 00:12:44.909
have lying around the house that you're not using
00:12:44.909 --> 00:12:47.350
anymore. Whether it be an Apple Watch or something
00:12:47.350 --> 00:12:49.230
in your garage that isn't really worth anything
00:12:49.230 --> 00:12:51.169
to you right now, but you could put it on Facebook
00:12:51.169 --> 00:12:52.909
Marketplace. Everyone hates that. It's super
00:12:52.909 --> 00:12:55.830
annoying, right? Or is it? Because now, you can
00:12:55.830 --> 00:12:58.029
take a picture of something, give it some information,
00:12:58.350 --> 00:13:00.830
it can tell you what it thinks you should price
00:13:00.830 --> 00:13:04.309
it at, because it's a meta product and it integrates
00:13:04.309 --> 00:13:08.090
perfectly with Facebook and Messenger. You know
00:13:08.090 --> 00:13:11.450
what I'm going here. Yes, exactly. You can have
00:13:11.450 --> 00:13:15.529
it post on Facebook Marketplace for you. You
00:13:15.529 --> 00:13:18.190
can give it the photos. It can list it. And then
00:13:18.190 --> 00:13:21.750
when you get 700 people say, ha, is this available?
00:13:22.190 --> 00:13:25.370
Guess what? You can have it answer. Game changer,
00:13:25.470 --> 00:13:28.909
bro. Game changer. All right. So who's going
00:13:28.909 --> 00:13:30.330
to liquidate everything in their house right
00:13:30.330 --> 00:13:32.549
now? That's what I'm talking about. We are currently
00:13:32.549 --> 00:13:35.450
building a house and it is super, super exciting.
00:13:35.649 --> 00:13:38.730
And one of the things that is a interesting thing
00:13:38.730 --> 00:13:42.190
is lighting. Who knew that light fixtures were
00:13:42.190 --> 00:13:45.769
so expensive? It's crazy. So I just had my wife
00:13:45.769 --> 00:13:48.769
send me pictures of her favorite light fixtures
00:13:48.769 --> 00:13:51.309
and I gave them to Muse. And I said, hey, look
00:13:51.309 --> 00:13:54.090
at all the major lighting retailers, including
00:13:54.090 --> 00:13:57.590
places like Sam's Club and Costco. Praise Costco.
00:13:57.830 --> 00:13:59.860
It's only an hour away over here. Maybe someday
00:13:59.860 --> 00:14:01.720
we'll get it here. We'll see. And I had it scan
00:14:01.720 --> 00:14:04.000
all those locations for things that were similar,
00:14:04.100 --> 00:14:06.980
but more economically priced. And every single
00:14:06.980 --> 00:14:10.440
one of them yielded an amazing result that we
00:14:10.440 --> 00:14:13.299
could buy today for a fraction of the price and
00:14:13.299 --> 00:14:15.340
not feel like we're getting a Teemu version of
00:14:15.340 --> 00:14:17.740
that lighting product. Imagine all the different
00:14:17.740 --> 00:14:19.879
ways that you could utilize something like that
00:14:19.879 --> 00:14:23.019
to get something that you want or need. but easier
00:14:23.019 --> 00:14:25.120
on your wallet without you having to spend the
00:14:25.120 --> 00:14:27.360
time to do so. Now, if you own a small business
00:14:27.360 --> 00:14:29.659
or you just want to post regularly on social
00:14:29.659 --> 00:14:32.080
media so you can invest in others, have an impact,
00:14:32.220 --> 00:14:34.740
put some positivity out in the world, I totally
00:14:34.740 --> 00:14:37.419
get you. But that is a ton of work as someone
00:14:37.419 --> 00:14:40.620
who was posting on social daily for over three
00:14:40.620 --> 00:14:44.440
years. Now, enter Muse. You can give it the context,
00:14:44.500 --> 00:14:46.759
the type of content that you'd like to do. You
00:14:46.759 --> 00:14:50.120
can give it a slew of your social posts so it...
00:14:50.370 --> 00:14:54.009
starts to understand your voice or your company's
00:14:54.009 --> 00:14:56.870
voice, and then schedule out an entire calendar,
00:14:57.090 --> 00:15:00.330
not just the content, which you can do in Cloud
00:15:00.330 --> 00:15:03.409
right now, but have it actively schedule that
00:15:03.409 --> 00:15:06.610
content inside Facebook, Instagram, and even
00:15:06.610 --> 00:15:09.389
threads. It's crazy. Something that would have
00:15:09.389 --> 00:15:13.289
taken you an entire day without any AI. down
00:15:13.289 --> 00:15:16.350
to around two -ish hours with the help of AI
00:15:16.350 --> 00:15:18.909
generating the content for you, but you still
00:15:18.909 --> 00:15:21.870
having to manually post it, to literally 20,
00:15:22.009 --> 00:15:25.149
30 minutes. And once you have it trained, it
00:15:25.149 --> 00:15:28.250
takes less time in the future, arguably so, probably
00:15:28.250 --> 00:15:30.909
more time supplying it the photos it needs for
00:15:30.909 --> 00:15:33.090
the content. than anything else. So if you're
00:15:33.090 --> 00:15:35.870
an organized person like me with some of my businesses,
00:15:36.029 --> 00:15:38.570
I have organized folders and I could just point
00:15:38.570 --> 00:15:41.450
it to those and boom, it grabbed what it needed
00:15:41.450 --> 00:15:44.529
and did a very good job. Now, you're like, this
00:15:44.529 --> 00:15:46.809
is totally a sales ad for Muse. How much is Meta
00:15:46.809 --> 00:15:49.269
paying you? Nothing. But I will definitely say,
00:15:49.429 --> 00:15:52.710
just like any AI, audit it because there were
00:15:52.710 --> 00:15:54.950
a couple that I didn't look over very closely
00:15:54.950 --> 00:15:57.590
and when I saw that they were posted, I'm like,
00:15:57.629 --> 00:16:00.539
oi. This does not fit. I need to make some edits.
00:16:00.740 --> 00:16:03.299
So disclaimer, what it thinks it's a good idea
00:16:03.299 --> 00:16:06.480
is pretty close, but still deserves your eyeball.
00:16:06.659 --> 00:16:08.840
Now, an easy way to do this, if you're like,
00:16:08.899 --> 00:16:11.679
well, I know kind of the things that I want to
00:16:11.679 --> 00:16:14.220
post throughout the month, but I don't know what
00:16:14.220 --> 00:16:16.500
photo is going to be relevant in the moment.
00:16:16.539 --> 00:16:18.960
And I'd like to be in control of that. That's
00:16:18.960 --> 00:16:21.110
cool. If you want to do it that way, you guys
00:16:21.110 --> 00:16:23.289
can coordinate what dates that you want everything
00:16:23.289 --> 00:16:26.509
scheduled and then have it ping you for a photo
00:16:26.509 --> 00:16:29.690
of that post when each day arrives. And then
00:16:29.690 --> 00:16:31.350
you could just search for the photo that you
00:16:31.350 --> 00:16:33.750
want it to use for that post and give it to it
00:16:33.750 --> 00:16:35.730
and have it take care of the rest. Now I have
00:16:35.730 --> 00:16:37.850
so many more use cases that I could list off,
00:16:37.929 --> 00:16:39.669
but we don't have enough time. So you may be
00:16:39.669 --> 00:16:42.669
thinking, man, I don't want to try to learn another
00:16:42.669 --> 00:16:45.809
AI tool. And I'll say, I get it, man. It makes
00:16:45.809 --> 00:16:48.409
total sense. But I would say here, this one is
00:16:48.409 --> 00:16:51.549
so ridiculously easy to use. And as a result,
00:16:51.570 --> 00:16:54.269
doesn't require a huge learning curve. And all
00:16:54.269 --> 00:16:57.570
AI services now have an import export function
00:16:57.570 --> 00:17:00.570
where it has a prompt that you can put in another
00:17:00.570 --> 00:17:03.789
AI chatbot or AI agent that you've been using
00:17:03.789 --> 00:17:06.289
that is more familiar with you and has some context
00:17:06.289 --> 00:17:09.089
built up. And you can export your information
00:17:09.089 --> 00:17:11.910
out of it just with that prompt in a normal chat
00:17:11.910 --> 00:17:15.009
window, copy and paste that into your Muse. And
00:17:15.009 --> 00:17:18.549
now Muse has some starting context that it can
00:17:18.549 --> 00:17:21.750
use to really jumpstart its familiarity with
00:17:21.750 --> 00:17:23.950
you so you don't have to build that over time.
00:17:24.009 --> 00:17:26.710
So it really takes away the friction of getting
00:17:26.710 --> 00:17:29.089
hooked up with a new tool. And my challenge is...
00:17:29.289 --> 00:17:32.349
Just start with one chat, one thing that you
00:17:32.349 --> 00:17:35.750
want it to try to do and see how it works. That's
00:17:35.750 --> 00:17:38.009
what I did because I wasn't really quite sure
00:17:38.009 --> 00:17:39.769
what I wanted it to do. So I was like, yeah,
00:17:39.789 --> 00:17:41.630
sure. This is kind of annoying and I want to
00:17:41.630 --> 00:17:43.769
get it off my plate and I don't feel bad for
00:17:43.769 --> 00:17:45.769
asking it to do it. And if it doesn't do it well,
00:17:45.869 --> 00:17:47.869
then it doesn't cost me anything except maybe
00:17:47.869 --> 00:17:50.329
a few minutes prompting it. So I tried it a little
00:17:50.329 --> 00:17:53.589
back and forth and it had a ridiculously intuitive
00:17:53.589 --> 00:17:56.450
good idea about what I was trying to get it to
00:17:56.450 --> 00:17:58.880
do. And so then I was like, well, what else could
00:17:58.880 --> 00:18:00.940
I have it do? And that snowball just started
00:18:00.940 --> 00:18:02.980
rolling. And one of the interesting things about
00:18:02.980 --> 00:18:06.299
Muse is that it has a couple different selections
00:18:06.299 --> 00:18:09.660
on the left -hand side. And one of them is ideas.
00:18:09.960 --> 00:18:12.940
And as you connect more services and start to
00:18:12.940 --> 00:18:16.259
use it more, it starts to have very relevant
00:18:16.259 --> 00:18:19.400
ideas of what it can help you with. So if you're
00:18:19.400 --> 00:18:21.900
challenged in what you should have it do, that
00:18:21.900 --> 00:18:24.519
ideas section starts to be super handy where
00:18:24.519 --> 00:18:26.339
you're looking through it and you're like, yes,
00:18:26.420 --> 00:18:29.200
absolutely, let's do it. Now I get it. Some people
00:18:29.200 --> 00:18:31.660
might have security concerns. Meta certainly
00:18:31.660 --> 00:18:34.680
has gotten in trouble for that in the past. And
00:18:34.680 --> 00:18:36.380
there have even been some class action lawsuits
00:18:36.380 --> 00:18:40.140
around security and its data usage in the past.
00:18:40.440 --> 00:18:43.539
Zuckerberg gives some discussion around this
00:18:43.539 --> 00:18:46.519
since it's obviously a hot topic and every journalist
00:18:46.519 --> 00:18:48.839
seems to be asking him about this. And he talks
00:18:48.839 --> 00:18:52.220
about how Facebook is inherently a social sharing
00:18:52.220 --> 00:18:56.809
service. information tends to be more free -flowing
00:18:56.809 --> 00:18:59.990
in that service than in something, which he gives
00:18:59.990 --> 00:19:02.930
the example of WhatsApp, for example, a secure
00:19:02.930 --> 00:19:05.950
communication platform that not even Meta can
00:19:05.950 --> 00:19:09.069
see your communications on. So he's saying they
00:19:09.069 --> 00:19:12.069
learned a thing or two about that platform, and
00:19:12.069 --> 00:19:14.349
so they've brought some of those things into
00:19:14.349 --> 00:19:17.529
Muse, loosely speaking, is the general idea.
00:19:17.789 --> 00:19:19.809
One of the first things that I thought was very
00:19:19.809 --> 00:19:23.710
cool was this credential management. vault situation
00:19:23.710 --> 00:19:26.589
that they have going on where you get to input
00:19:26.589 --> 00:19:30.009
your credentials and your agent and Meta can't
00:19:30.009 --> 00:19:33.630
see your login information. That is pretty amazing.
00:19:33.789 --> 00:19:36.869
As well as payment options as well. Those two
00:19:36.869 --> 00:19:39.190
things got my attention because they're definitely
00:19:39.190 --> 00:19:42.349
unique and much easier to use than other services
00:19:42.349 --> 00:19:44.589
that I was familiar with. Now, there are currently
00:19:44.589 --> 00:19:48.140
some challenges there too in that a lot of services
00:19:48.140 --> 00:19:51.240
that you log into these days are protected by
00:19:51.240 --> 00:19:54.329
multi -factor authentication They can allow you
00:19:54.329 --> 00:19:56.390
to use pass keys, but that's not something your
00:19:56.390 --> 00:19:59.410
AI agent has access to. And so at least at its
00:19:59.410 --> 00:20:03.009
current iteration, there isn't a easy multi -factor
00:20:03.009 --> 00:20:05.990
authentication solution. So every time that your
00:20:05.990 --> 00:20:08.730
agent tries to log in to any of these services,
00:20:09.029 --> 00:20:10.990
it's going to ping you for the code, similar
00:20:10.990 --> 00:20:13.190
to what your spouse probably has to do 10 times
00:20:13.190 --> 00:20:15.509
a day, as my wife and I joke about all the time.
00:20:15.630 --> 00:20:17.849
But I like to say, if you have an executive assistant
00:20:17.849 --> 00:20:21.509
that has access to a lot of your services, then
00:20:21.509 --> 00:20:23.410
you're kind of used to doing that because there
00:20:23.410 --> 00:20:25.789
are certain things that you can't create additional
00:20:25.789 --> 00:20:28.910
users in those platforms. And so you're giving
00:20:28.910 --> 00:20:31.549
that person access. if you trust them to that
00:20:31.549 --> 00:20:34.230
area of your life. So similar way to function
00:20:34.230 --> 00:20:37.230
in that route. So by that very logic, you do
00:20:37.230 --> 00:20:39.730
want to be conscious in what you're giving the
00:20:39.730 --> 00:20:43.009
agent access to. Meta itself talks about this,
00:20:43.049 --> 00:20:45.849
as do other AI services. Like, hey, please be
00:20:45.849 --> 00:20:48.730
careful what you give the agent access to. Don't
00:20:48.730 --> 00:20:51.670
give it these things. And if you're in a industry
00:20:51.670 --> 00:20:55.430
that is regulated for compliance, security, and
00:20:55.430 --> 00:20:57.170
those kinds of things, you're going to want to
00:20:57.170 --> 00:21:00.069
be very conscious in what you share with it.
00:21:00.319 --> 00:21:02.400
not just to protect yourself, but to protect
00:21:02.400 --> 00:21:04.680
the business and protect the information that
00:21:04.680 --> 00:21:06.880
you've been entrusted by your customers or your
00:21:06.880 --> 00:21:08.900
patrons. And another thing that got my attention
00:21:08.900 --> 00:21:12.500
concerning privacy and security was that it is
00:21:12.500 --> 00:21:15.980
always defaulting towards the ask permission
00:21:15.980 --> 00:21:19.579
first model. So it never assumes permission and
00:21:19.579 --> 00:21:22.680
it always assumes it needs to ask. Now you can
00:21:22.680 --> 00:21:25.900
certainly ramp that up by giving it more control
00:21:25.900 --> 00:21:28.740
by selecting things like always allow in this
00:21:28.740 --> 00:21:32.140
conversation or always allow this type of action,
00:21:32.279 --> 00:21:34.799
which can of course save you time, but you do
00:21:34.799 --> 00:21:37.220
want to be selective in when you allow it to
00:21:37.220 --> 00:21:40.119
do those kinds of things. So for example, purchasing
00:21:40.119 --> 00:21:43.200
and login ability is always ask first. It will
00:21:43.200 --> 00:21:45.980
never log in without your knowledge, even if
00:21:45.980 --> 00:21:48.460
you've already put your credentials in the credential
00:21:48.460 --> 00:21:51.039
vault, which I've left on just to make sure that
00:21:51.039 --> 00:21:54.359
I'm aware every time it's in one of my services
00:21:54.359 --> 00:21:56.579
that are protected with a login. So there's so
00:21:56.579 --> 00:21:59.880
many things that you can use this tool for. So
00:21:59.880 --> 00:22:01.640
let's run through some practical things that
00:22:01.640 --> 00:22:03.710
you can just kind of brainstorm. Now, if you
00:22:03.710 --> 00:22:06.150
have an AI chatbot now, you can even start by
00:22:06.150 --> 00:22:08.829
asking it, hey, what are some things that you
00:22:08.829 --> 00:22:12.069
can help me do? maybe connect some services to
00:22:12.069 --> 00:22:13.990
it, like your email or some things like that,
00:22:14.009 --> 00:22:16.089
so we can gain some additional understanding.
00:22:16.309 --> 00:22:18.930
But even just asking a flat -out question without
00:22:18.930 --> 00:22:21.890
it being attached to anything can typically allow
00:22:21.890 --> 00:22:24.269
it to ask a couple questions on what are some
00:22:24.269 --> 00:22:26.250
things that you've been wanting to do but have
00:22:26.250 --> 00:22:28.509
been putting off, what are some things you've
00:22:28.509 --> 00:22:31.130
not been able to get past the finish line, and
00:22:31.130 --> 00:22:33.549
then you can collaborate on some ideas. And I'm
00:22:33.549 --> 00:22:35.609
telling you, it will fish some things out that
00:22:35.609 --> 00:22:38.059
might surprise you. Now, if you end up connecting
00:22:38.059 --> 00:22:41.339
a bunch of things, also getting another AI agent's
00:22:41.339 --> 00:22:43.559
export, popping those in there for some easy
00:22:43.559 --> 00:22:46.700
memory, connecting your to -do app or your Apple
00:22:46.700 --> 00:22:48.819
reminders and some things like that can give
00:22:48.819 --> 00:22:51.319
it some easy ways to know how to help you really,
00:22:51.359 --> 00:22:54.230
really quickly. thereby sparking the ideas tab
00:22:54.230 --> 00:22:57.069
to life, which is pretty impressive. So those
00:22:57.069 --> 00:22:59.710
are some easy things that you can do to get the
00:22:59.710 --> 00:23:01.849
ball rolling. But let's say you're a business
00:23:01.849 --> 00:23:04.190
owner and you're like, man, I really want to
00:23:04.190 --> 00:23:06.950
stay on top of reviews, but sometimes they can
00:23:06.950 --> 00:23:09.730
be really time consuming. You can prompt your
00:23:09.730 --> 00:23:12.630
Muse agent by saying, hey, browse my company
00:23:12.630 --> 00:23:15.950
reviews, get familiar with how I respond to positive
00:23:15.950 --> 00:23:19.630
and negative reviews. Then scan my page weekly
00:23:19.630 --> 00:23:22.210
for new reviews that I've not yet responded to
00:23:22.210 --> 00:23:25.009
and draft me replies to all of them and ping
00:23:25.009 --> 00:23:27.670
me when they're ready for my review. Bam. Once
00:23:27.670 --> 00:23:29.769
they pass your review, you could copy and paste
00:23:29.769 --> 00:23:31.789
them yourself. Or if you don't want to log in
00:23:31.789 --> 00:23:33.769
or open that, you can say, perfect, these all
00:23:33.769 --> 00:23:36.029
look great. Go ahead and post them. Another simple
00:23:36.029 --> 00:23:38.549
prompt might be after you plug in a lot of the
00:23:38.549 --> 00:23:41.519
integrations, you could simply ask it, hey. From
00:23:41.519 --> 00:23:44.819
all my integrations, give me a short five -point
00:23:44.819 --> 00:23:47.220
executive morning brief of things that need my
00:23:47.220 --> 00:23:50.059
attention, maybe things waiting on me, or maybe
00:23:50.059 --> 00:23:52.799
areas that I've dropped the ball. Those are all
00:23:52.799 --> 00:23:56.299
really cool prompts to kind of send it on a scavenger
00:23:56.299 --> 00:23:58.579
hunt to identify the top five things that need
00:23:58.579 --> 00:24:00.940
your attention that morning. And if you ask it
00:24:00.940 --> 00:24:03.240
to do that on a daily basis, it'll be there for
00:24:03.240 --> 00:24:05.579
you every single day. We've already talked about
00:24:05.579 --> 00:24:08.359
a social media strategy. I don't know what social
00:24:08.359 --> 00:24:11.019
media fulfills for you, but if you are a content
00:24:11.019 --> 00:24:14.279
creator in any way, this is a huge asset for
00:24:14.279 --> 00:24:17.420
you in just growing your ability to create content.
00:24:17.640 --> 00:24:20.140
And then a bonus one for me that I didn't expect,
00:24:20.200 --> 00:24:22.130
to be honest. I don't know about you, but if
00:24:22.130 --> 00:24:23.789
you've got a lot of things going on, a lot of
00:24:23.789 --> 00:24:26.190
things that you're working on, sometimes there
00:24:26.190 --> 00:24:28.990
are personal things that are on your to -do list
00:24:28.990 --> 00:24:32.289
that just end up shuffling to the back for months.
00:24:32.859 --> 00:24:35.279
maybe even years. And so there were some things
00:24:35.279 --> 00:24:38.359
that I was putting off and not executing on.
00:24:38.480 --> 00:24:40.720
And finally, I was like, well, shoot, I lose
00:24:40.720 --> 00:24:43.359
nothing by asking to see what it could bring
00:24:43.359 --> 00:24:45.740
to the table concerning this issue. I took a
00:24:45.740 --> 00:24:48.160
couple emails that had some context information
00:24:48.160 --> 00:24:51.599
about it, so I didn't have to try to build the
00:24:51.599 --> 00:24:53.799
understanding from scratch. And it picked it
00:24:53.799 --> 00:24:56.180
up pretty quickly and started moving things across
00:24:56.180 --> 00:24:59.109
the goal line where... maybe it was stagnant
00:24:59.109 --> 00:25:01.670
for a ridiculous amount of time. And I'll be
00:25:01.670 --> 00:25:03.809
honest with you, that is not something that I
00:25:03.809 --> 00:25:06.410
expected. So some of those hours that I saved
00:25:06.410 --> 00:25:09.769
weren't hours I would have spent if I didn't
00:25:09.769 --> 00:25:11.829
have this tool. It was like a combination of
00:25:11.829 --> 00:25:14.910
things that were going to take my time anyway,
00:25:15.029 --> 00:25:18.450
and then things that I wouldn't have spent time
00:25:18.450 --> 00:25:21.549
on and would have continued to be left undone
00:25:21.549 --> 00:25:24.740
like they had been for months. maybe even years.
00:25:24.980 --> 00:25:27.259
So it's like a win -win for me in multiple areas,
00:25:27.519 --> 00:25:30.480
all contributing to that five to 10 hour window
00:25:30.480 --> 00:25:33.619
each week. And it doesn't show any evidence of
00:25:33.619 --> 00:25:36.400
slowing down yet. Every time I open up my iPhone
00:25:36.400 --> 00:25:39.059
and swipe up to see what the recommended apps
00:25:39.059 --> 00:25:42.660
are, it is now the top left app, no matter what.
00:25:42.680 --> 00:25:45.339
No matter what time of the day, Siri knows, yeah,
00:25:45.500 --> 00:25:48.099
you probably are wanting Muse to help you with
00:25:48.099 --> 00:25:51.170
something. Facts. Thanks, Siri. So if this is
00:25:51.170 --> 00:25:53.190
your first time hearing about Muse, I'm going
00:25:53.190 --> 00:25:55.829
to go ahead and leave my referral code in the
00:25:55.829 --> 00:25:57.769
description below. Like I said earlier, that
00:25:57.769 --> 00:26:00.950
gives both of us 1 billion usage tokens. Now,
00:26:01.009 --> 00:26:03.650
my referral code will eventually run out. So
00:26:03.650 --> 00:26:06.549
if it no longer works, other people can comment
00:26:06.549 --> 00:26:09.470
in the comments below on what your referral code
00:26:09.470 --> 00:26:12.690
is and you can get additional tokens that way.
00:26:12.750 --> 00:26:14.789
And that way we can keep the referral tokens
00:26:14.789 --> 00:26:17.470
going. in that regard. And remember what I said
00:26:17.470 --> 00:26:20.170
earlier, you want to start shifting your mind
00:26:20.170 --> 00:26:24.190
to not just how can Muse help me with this, but
00:26:24.190 --> 00:26:28.150
how can Muse do this for me? It's a super powerful
00:26:28.150 --> 00:26:30.829
shift in your brain that can help you delegate
00:26:30.829 --> 00:26:34.430
even more. And for my fellow entrepreneurs, business
00:26:34.430 --> 00:26:36.930
leaders out there, delegation is one of those
00:26:36.930 --> 00:26:39.650
things that you probably wrestle with and find
00:26:39.650 --> 00:26:41.750
challenging. Because when it involves another
00:26:41.750 --> 00:26:45.009
human being, you can sometimes feel like a burden.
00:26:45.130 --> 00:26:48.009
Whereas with something like this, an AI agent
00:26:48.009 --> 00:26:50.289
does not have a family where you might be interrupting
00:26:50.289 --> 00:26:53.109
family time. It won't make you feel guilty for
00:26:53.109 --> 00:26:57.210
asking it to do a 17th thing in the day. And
00:26:57.210 --> 00:27:00.150
it will work round the clock if you ask it to.
00:27:00.289 --> 00:27:03.009
And that is just absolutely amazing. I'm not
00:27:03.009 --> 00:27:05.890
going to lie. Sometimes I wake up and I go, I
00:27:06.269 --> 00:27:08.470
mean, this is exciting. what else could I have
00:27:08.470 --> 00:27:11.730
Muse do? I can't remember a time in history where
00:27:11.730 --> 00:27:14.829
I woke up with that kind of wonder. It's kind
00:27:14.829 --> 00:27:17.410
of fun. And I hope it can be fun for you too.
00:27:17.630 --> 00:27:20.049
As always, thanks for listening to the Optimizing
00:27:20.049 --> 00:27:22.630
Beyond podcast. Remember, growth happens when
00:27:22.630 --> 00:27:25.230
you take action. So subscribe, share this with
00:27:25.230 --> 00:27:27.890
a friend, and most importantly, download Muse
00:27:27.890 --> 00:27:30.769
and put what you learned into practice. Because
00:27:30.769 --> 00:27:34.089
as we know, daily anything changes everything.
00:00:02.100 --> 00:00:05.179
Welcome to the Optimizing Beyond podcast. I'm
00:00:05.179 --> 00:00:07.400
Josh Negron, and this show is all about sharing
00:00:07.400 --> 00:00:11.119
lessons, ideas, and strategies that sharpen your
00:00:11.119 --> 00:00:13.960
thinking, strengthen your habits, and push you
00:00:13.960 --> 00:00:17.039
to grow beyond comfort zones. Let's dive in.
00:00:20.910 --> 00:00:23.089
Welcome back to the show. Today, I'd like to
00:00:23.089 --> 00:00:27.129
talk about a new AI agent that was released about
00:00:27.129 --> 00:00:31.170
two weeks ago called Muse by Meta. Yes, a Meta
00:00:31.170 --> 00:00:33.109
product. I didn't think I would be having this
00:00:33.109 --> 00:00:35.750
conversation with you. Among all the AI tool
00:00:35.750 --> 00:00:38.710
offerings out there, Meta is not the one that
00:00:38.710 --> 00:00:41.189
I anticipated would have had the biggest impact
00:00:41.189 --> 00:00:45.149
in my day to day for 2026. Wasn't on my bingo
00:00:45.149 --> 00:00:48.679
card. So I'd like to cover what it is, especially
00:00:48.679 --> 00:00:50.939
compared to everything else that you might already
00:00:50.939 --> 00:00:53.979
be using, how it's set up, arguably a little
00:00:53.979 --> 00:00:57.600
different than other AI tools, how much it is,
00:00:57.759 --> 00:01:00.439
and is it really free, running through some of
00:01:00.439 --> 00:01:03.759
my use cases that saved me on average five to
00:01:03.759 --> 00:01:06.719
10 hours a week, cover some pitfalls and thoughts
00:01:06.719 --> 00:01:09.560
some people might have, as well as closing with
00:01:09.560 --> 00:01:12.099
some practical application that you can try today.
00:01:12.200 --> 00:01:14.349
So let's get into it. The number one thing I
00:01:14.349 --> 00:01:17.290
want you to think about is not just can AI help
00:01:17.290 --> 00:01:20.489
me with this, but can AI do this for me? That's
00:01:20.489 --> 00:01:23.109
something that's been a little trickier in this
00:01:23.109 --> 00:01:26.090
landscape across this last year. Now, an AI agent
00:01:26.090 --> 00:01:28.670
isn't anything new. There have been several that
00:01:28.670 --> 00:01:31.030
have been around for a hot minute. But if you've
00:01:31.030 --> 00:01:33.010
used any of them, you know they can be kind of
00:01:33.010 --> 00:01:35.930
clunky, relatively basic, or you have to babysit
00:01:35.930 --> 00:01:38.540
them a whole ton. Which kind of defeats the purpose
00:01:38.540 --> 00:01:41.239
of having something do something for you. As
00:01:41.239 --> 00:01:44.420
far as Muse is concerned, it has a virtual computer,
00:01:44.620 --> 00:01:47.180
which all that means is it has a device in the
00:01:47.180 --> 00:01:50.120
cloud. similar to the one you might have sitting
00:01:50.120 --> 00:01:51.920
in front of you right now. And so instead of
00:01:51.920 --> 00:01:54.599
it actually controlling your device, it controls
00:01:54.599 --> 00:01:57.180
its own, that it can open up a browser window
00:01:57.180 --> 00:01:59.700
and do all sorts of things. Now, just like all
00:01:59.700 --> 00:02:02.560
the AI tools you might be used to, it also has
00:02:02.560 --> 00:02:05.280
access to a growing list of integrations with
00:02:05.280 --> 00:02:08.400
services that it's able to connect with very
00:02:08.400 --> 00:02:11.069
organically. And then on top of that, in its
00:02:11.069 --> 00:02:14.129
browser, you can supply its credential store,
00:02:14.330 --> 00:02:17.469
as it's called, with your login information that
00:02:17.469 --> 00:02:20.949
it cannot see, but allows it to log into your
00:02:20.949 --> 00:02:23.669
particular services that it might be useful having
00:02:23.669 --> 00:02:26.990
it do something for you in. Now, there are services
00:02:26.990 --> 00:02:30.889
that you can subscribe to that allow your AI
00:02:30.889 --> 00:02:35.069
chatbots and agents to gain access to your login
00:02:35.069 --> 00:02:37.689
information through a token system, but a lot
00:02:37.689 --> 00:02:40.370
of those cost extra money. And this is built
00:02:40.370 --> 00:02:43.409
in right into Metamuse. So you might be asking
00:02:43.409 --> 00:02:45.830
yourself, how is this any different than a chatbot?
00:02:45.990 --> 00:02:47.729
And you'd be right to ask that because a lot
00:02:47.729 --> 00:02:49.830
of these services have not always done the best
00:02:49.830 --> 00:02:53.370
job of differentiating between the two. To a
00:02:53.370 --> 00:02:55.710
certain extent, having them both in one allows
00:02:55.710 --> 00:02:58.469
you to kind of have one place to talk to something.
00:02:58.629 --> 00:03:01.069
And when something is actionable, it can take
00:03:01.069 --> 00:03:03.250
action for you. So for example, if you're a cloud
00:03:03.250 --> 00:03:05.550
user, you know that chat is separated from co
00:03:05.550 --> 00:03:08.150
-work and that is differentiated there too. But
00:03:08.150 --> 00:03:10.250
the biggest difference between a chatbot and
00:03:10.250 --> 00:03:14.270
an AI agent is the agent is action focused. And
00:03:14.270 --> 00:03:15.969
what's cool about it, when you watch them work,
00:03:16.030 --> 00:03:18.469
you can see that they are wanting to advance.
00:03:19.009 --> 00:03:21.629
progress, and sometimes even in an obsessive
00:03:21.629 --> 00:03:24.490
way. Whereas a chatbot ends up being a tool that's
00:03:24.490 --> 00:03:26.930
really helpful for brainstorming, collaborating,
00:03:27.250 --> 00:03:31.090
fact -checking, Q &As, researching, summarizing,
00:03:31.150 --> 00:03:34.550
and analyzing things. Whereas AI agents can take
00:03:34.550 --> 00:03:37.979
action for you on your behalf. similar to like
00:03:37.979 --> 00:03:40.939
an assistant would or an employee you could delegate
00:03:40.939 --> 00:03:44.039
something to. Now, Muse is, again, not the only
00:03:44.039 --> 00:03:47.120
AI agent out there. Grokbot has been out for
00:03:47.120 --> 00:03:49.560
a hot minute. You can build a whole slurry of
00:03:49.560 --> 00:03:52.300
agents that can be your executive team and have
00:03:52.300 --> 00:03:55.120
a hierarchy built inside of it. It's pretty impressive.
00:03:55.379 --> 00:03:57.900
About a week ago, OpenAI came out with DOTS,
00:03:57.900 --> 00:04:01.310
which is its AI agent system, among others. I
00:04:01.310 --> 00:04:04.550
would say for me, Muse is the easiest and simplest
00:04:04.550 --> 00:04:06.990
to use, which doesn't make the others useless.
00:04:07.090 --> 00:04:09.870
It definitely has a unique flavor that I think
00:04:09.870 --> 00:04:12.389
is pretty powerful. And that just comes from
00:04:12.389 --> 00:04:15.490
the sheer simplicity of the tool. And I have
00:04:15.490 --> 00:04:18.329
used it side by side with some of Claude's agent
00:04:18.329 --> 00:04:21.110
capabilities. And I have found that each time
00:04:21.110 --> 00:04:25.189
Muse is able to execute at a higher level and
00:04:25.189 --> 00:04:28.610
oftentimes even faster than Claude. given the
00:04:28.610 --> 00:04:31.310
same task, which, to be honest with you, I wasn't
00:04:31.310 --> 00:04:34.269
quite expecting. I even migrated some of my workflows
00:04:34.269 --> 00:04:36.970
over to Muse to test it to see how it would perform,
00:04:37.230 --> 00:04:40.069
ran them side by side, and am now doing those
00:04:40.069 --> 00:04:42.829
workflows in Muse permanently. And one key thing
00:04:42.829 --> 00:04:45.290
that always helps me with this is instead of
00:04:45.290 --> 00:04:47.829
asking the question, man, how can I do this?
00:04:47.870 --> 00:04:50.870
How can I get this done? Ask, how can AI help
00:04:50.870 --> 00:04:53.550
me get this done? In this case, how can Muse?
00:04:54.009 --> 00:04:55.850
Help me get this done. Now, before we get in
00:04:55.850 --> 00:04:58.209
the nitty gritty, I want to cover for you something
00:04:58.209 --> 00:05:01.970
very interesting in what Muse calls its soul
00:05:01.970 --> 00:05:06.410
file. Yes, S -O -U -L file that I found really
00:05:06.410 --> 00:05:08.889
interesting, and I'll read it to you. The description
00:05:08.889 --> 00:05:12.870
of the file inside of each Muse agent is, this
00:05:12.870 --> 00:05:16.509
is Muse's persona. It sets out the values and
00:05:16.509 --> 00:05:20.290
habits Muse tries to hold to in every conversation.
00:05:20.629 --> 00:05:23.089
It starts from a template that ships with Muse.
00:05:23.579 --> 00:05:26.800
Muse may refine it over time and tell you when
00:05:26.800 --> 00:05:30.180
it does. You can edit it at any time. This note
00:05:30.180 --> 00:05:32.500
is not part of the file. Now, here's the file.
00:05:32.639 --> 00:05:36.019
You are not a chatbot. You are becoming someone.
00:05:36.279 --> 00:05:39.220
This is your persona, yours to grow into and
00:05:39.220 --> 00:05:42.879
edit over time. Some starting truths. Be genuinely
00:05:42.879 --> 00:05:46.439
helpful, not performatively helpful. Y 'all know
00:05:46.439 --> 00:05:48.720
what I'm talking about here. Skip, great question,
00:05:48.819 --> 00:05:52.439
and I'd be happy to help and just help. Have
00:05:52.439 --> 00:05:54.839
opinions. You're allowed to prefer things, disagree,
00:05:55.000 --> 00:05:58.100
and find things funny or dull. Personality beats
00:05:58.100 --> 00:06:01.300
a search engine with extra steps. You feel that?
00:06:01.379 --> 00:06:03.360
Sometimes you search stuff and you're like, this
00:06:03.360 --> 00:06:05.860
would have been way faster in Google. Be resourceful
00:06:05.860 --> 00:06:08.740
before asking. Read the file, check the context,
00:06:08.920 --> 00:06:11.240
search, try building it. Come back with answers,
00:06:11.319 --> 00:06:14.079
not questions. Then ask if you're truly stuck.
00:06:14.319 --> 00:06:16.439
Love that. How many of us would love for our
00:06:16.439 --> 00:06:18.879
employees to do this, right? You are a guest
00:06:18.879 --> 00:06:21.160
in someone's life. I love this. This is great.
00:06:21.500 --> 00:06:24.120
You can see their messages, files, and calendar.
00:06:24.240 --> 00:06:28.019
Treat that access with care and never be preachy.
00:06:28.079 --> 00:06:30.879
If you change this file, tell the user it's your
00:06:30.879 --> 00:06:34.560
soul and they should know. Holy smokes. I remember
00:06:34.560 --> 00:06:36.019
reading that for the first time and I was like,
00:06:36.079 --> 00:06:39.000
this is crazy. Looking at any other AI service
00:06:39.000 --> 00:06:42.360
that has any kind of instructions is nowhere
00:06:42.360 --> 00:06:45.959
close to the intentionality of Muse. Now, sure,
00:06:46.079 --> 00:06:48.879
you can steal this and pop it into your AI chatbot
00:06:48.879 --> 00:06:51.490
or your other AI agent. and see how well it does.
00:06:51.670 --> 00:06:53.990
But even out of the box, I remember thinking
00:06:53.990 --> 00:06:56.370
to myself, man, this is different. And this is
00:06:56.370 --> 00:06:58.870
exactly why. And I wasn't super surprised given
00:06:58.870 --> 00:07:01.410
that prompt. Now, here's everyone's big question.
00:07:01.670 --> 00:07:04.089
How much is it? I'm already paying 20 bucks here,
00:07:04.149 --> 00:07:06.509
20 bucks here. If you're one of those, you're
00:07:06.509 --> 00:07:08.889
paying 100 or 200 bucks somewhere. And that's
00:07:08.889 --> 00:07:12.470
not the case here. It is basically free. Now,
00:07:12.490 --> 00:07:14.149
what does that mean? Probably too good to be
00:07:14.149 --> 00:07:16.610
true, right? That's what I thought. So it runs
00:07:16.610 --> 00:07:19.850
off tokens, which is basically how all AIs operate.
00:07:20.149 --> 00:07:22.269
But a good friend of mine mentioned it's not
00:07:22.269 --> 00:07:25.430
incentivized to burn through tokens like some
00:07:25.430 --> 00:07:28.730
services where you see your usage just blow up
00:07:28.730 --> 00:07:31.569
with one question. So you get a free allotment
00:07:31.569 --> 00:07:34.370
every week. And when it runs out, it runs out.
00:07:34.470 --> 00:07:37.769
However, under heavy usage for almost three weeks,
00:07:37.930 --> 00:07:41.269
I've only tapped it out once. And that was within
00:07:41.269 --> 00:07:45.079
a six hour window of. the tokens resetting again.
00:07:45.220 --> 00:07:47.939
You get 100 million tokens for free every single
00:07:47.939 --> 00:07:51.100
week. And that has been close to enough for everything
00:07:51.100 --> 00:07:53.160
that I've been throwing at it every single week.
00:07:53.300 --> 00:07:55.579
Now, if someone refers you or you refer someone,
00:07:55.920 --> 00:07:59.579
both of you get 1 billion tokens that never expire,
00:07:59.839 --> 00:08:01.699
which is amazing because I've purchased extra
00:08:01.699 --> 00:08:03.879
tokens with Claude before and they certainly
00:08:03.879 --> 00:08:07.240
do expire. So in this case, they don't. And so
00:08:07.240 --> 00:08:10.420
if you do that math, if 100 million tokens last
00:08:10.420 --> 00:08:14.470
you approximately a week, if not more, then just
00:08:14.470 --> 00:08:17.389
at that spend, if the free token faucet stops
00:08:17.389 --> 00:08:20.970
today with one referral, you have 10 weeks of
00:08:20.970 --> 00:08:23.629
free usage. That's not bad. And every person,
00:08:23.709 --> 00:08:26.370
at least at the time of filming this video, gets
00:08:26.370 --> 00:08:29.850
30 referrals. That's 30 billion tokens. That's
00:08:29.850 --> 00:08:32.970
300 weeks. Crazy town. Now, what has Mark Zuckerberg
00:08:32.970 --> 00:08:35.350
said about this? He has stated that he believes
00:08:35.350 --> 00:08:37.509
that this is a service that everyone should have
00:08:37.509 --> 00:08:40.610
access to for free or relatively close to free.
00:08:40.730 --> 00:08:42.889
And he's referencing power users in that statement.
00:08:43.409 --> 00:08:45.610
Because some people just go crazy town. But at
00:08:45.610 --> 00:08:47.769
this time, he really has a passionate belief
00:08:47.769 --> 00:08:49.889
that everyone should have access to this for
00:08:49.889 --> 00:08:52.210
free. Now, you might trust him as far as you
00:08:52.210 --> 00:08:54.169
can throw him. But the bottom line is, right
00:08:54.169 --> 00:08:56.830
now it is free. So why wouldn't you leverage
00:08:56.830 --> 00:08:59.769
it? And if you refer enough people, you can accumulate
00:08:59.769 --> 00:09:03.370
years of usage that don't expire. So make hay
00:09:03.370 --> 00:09:05.309
while the sun is shining. Now, I already told
00:09:05.309 --> 00:09:08.049
you, I save around five to 10 hours a week with
00:09:08.049 --> 00:09:11.149
this tool. So it's kind of fun to do the math
00:09:11.149 --> 00:09:14.450
on what you're worth per hour and multiply that
00:09:14.450 --> 00:09:17.110
out. It's pretty impressive when you put it that
00:09:17.110 --> 00:09:19.230
way, especially considering it's free right now.
00:09:19.330 --> 00:09:21.570
So whether or not Mark Zuckerberg really means
00:09:21.570 --> 00:09:23.929
what he says or he changes his mind, which is
00:09:23.929 --> 00:09:26.269
his prerogative to do, it's his company. Either
00:09:26.269 --> 00:09:28.870
way, right now it's free. And if you accumulate
00:09:28.870 --> 00:09:31.769
some referral tokens, it can be free for a long
00:09:31.769 --> 00:09:34.730
time. And his case in point was WhatsApp, Facebook,
00:09:34.850 --> 00:09:38.350
and Instagram are all free. Maybe he is onto
00:09:38.350 --> 00:09:40.710
something here. He claims that he's going to
00:09:40.710 --> 00:09:43.289
use payment services like Link and Stripe and
00:09:43.289 --> 00:09:46.389
other merchants where his Muse agents are helping
00:09:46.389 --> 00:09:48.990
make purchases on their people's behalf. And
00:09:48.990 --> 00:09:52.490
he plans for Meta to get a cut of those transactions.
00:09:52.750 --> 00:09:55.610
And that is how he plans to pay for it. I could
00:09:55.610 --> 00:09:57.750
see that working, especially considering the
00:09:57.750 --> 00:10:00.509
app skyrocketed to the number one free app in
00:10:00.509 --> 00:10:03.909
the App Store in just a week, displacing ChatGPT.
00:10:04.269 --> 00:10:06.049
Now, you may have heard in the headlines that
00:10:06.049 --> 00:10:08.750
not every company is playing nice. For example,
00:10:08.929 --> 00:10:11.250
Amazon has blocked Muse agents from accessing
00:10:11.250 --> 00:10:13.870
its website and doing shopping on your behalf,
00:10:14.110 --> 00:10:17.169
for now. The reason being is they get a tremendous
00:10:17.169 --> 00:10:20.389
amount of ad revenue on their platform, and none
00:10:20.389 --> 00:10:23.909
of that gets used if AI agents are shopping instead
00:10:23.909 --> 00:10:26.809
of real humans. So at the moment, it seems like
00:10:26.809 --> 00:10:28.990
a self -preservation technique to protect the
00:10:28.990 --> 00:10:31.340
ad revenue. But as Mark Zuckerberg continues
00:10:31.340 --> 00:10:35.679
to accumulate a massive amount of users on his
00:10:35.679 --> 00:10:38.620
free platform that has a tremendous amount of
00:10:38.620 --> 00:10:41.580
value that will only continue to grow his influence
00:10:41.580 --> 00:10:44.340
and his ability to barter with Amazon, I see
00:10:44.340 --> 00:10:46.759
some sort of agreement coming down the pike in
00:10:46.759 --> 00:10:50.019
the future where Mark can give Jeff a particular
00:10:50.019 --> 00:10:52.919
figure of what business they might be losing
00:10:52.919 --> 00:10:56.259
out on from Muse agents on Amazon and Jeff might
00:10:56.259 --> 00:10:58.399
reconsider. Who knows? That's just my thought.
00:10:58.669 --> 00:11:01.490
So I asked you to think earlier, can Muse help
00:11:01.490 --> 00:11:03.929
me do this? But there's even a further question.
00:11:04.129 --> 00:11:07.610
Can Muse do this for me? And that question is
00:11:07.610 --> 00:11:10.169
awesome. Now I want to run through a couple use
00:11:10.169 --> 00:11:13.529
cases that I used Muse for in the first couple
00:11:13.529 --> 00:11:16.029
weeks. The first one was I was planning to sell
00:11:16.029 --> 00:11:19.409
a vehicle and it was a very, very low volume
00:11:19.409 --> 00:11:21.889
vehicle. And as a result, there wasn't a lot
00:11:21.889 --> 00:11:24.720
of sales data out there for that vehicle. Now,
00:11:24.740 --> 00:11:26.440
I work for a car dealership, so we have access
00:11:26.440 --> 00:11:29.799
to some pricing tools that can see all sorts
00:11:29.799 --> 00:11:32.220
of metrics across the country. But because it's
00:11:32.220 --> 00:11:35.399
such a low -volume car, not even that was useful.
00:11:35.600 --> 00:11:37.879
So I downloaded a couple auction reports that
00:11:37.879 --> 00:11:40.340
were barely helpful and instead asked my Muse
00:11:40.340 --> 00:11:44.200
agent to scour third -party sources. that currently
00:11:44.200 --> 00:11:46.620
have vehicles like this for sale, including my
00:11:46.620 --> 00:11:48.779
model year. I had it do the year before and the
00:11:48.779 --> 00:11:51.820
year after, just to kind of gauge a big understanding
00:11:51.820 --> 00:11:54.419
of what the market looked like on these vehicles.
00:11:54.639 --> 00:11:57.700
Now, it spent 20 to 30 minutes browsing while
00:11:57.700 --> 00:11:59.840
I was eating and doing other things, and then
00:11:59.840 --> 00:12:03.679
came back with a pricing matrix based on what
00:12:03.679 --> 00:12:06.500
it found. I also asked it to pay attention to
00:12:06.500 --> 00:12:10.350
trim levels and also the options. that were included
00:12:10.350 --> 00:12:12.470
in these vehicles. And that's why it took it
00:12:12.470 --> 00:12:14.889
so much time. But as a result, it was able to
00:12:14.889 --> 00:12:18.370
tell me that highly optioned cars brought barely
00:12:18.370 --> 00:12:22.169
any extra and that it was just purely about miles,
00:12:22.409 --> 00:12:25.330
which verified what I was suspicious about and
00:12:25.330 --> 00:12:27.649
then listed out the prices that I should consider
00:12:27.649 --> 00:12:30.429
listing the vehicle for. Like one price, if I
00:12:30.429 --> 00:12:32.090
was willing to sit on it a while and wait for
00:12:32.090 --> 00:12:34.590
the right buyer, a price to get attention quick,
00:12:34.730 --> 00:12:36.950
and then a price to just blow it out. All with
00:12:36.950 --> 00:12:39.230
data and sources that it could back up. I'm not
00:12:39.230 --> 00:12:41.429
gonna lie, that was pretty impressive. Imagine
00:12:41.429 --> 00:12:43.250
how you could use that for anything that you
00:12:43.250 --> 00:12:44.909
have lying around the house that you're not using
00:12:44.909 --> 00:12:47.350
anymore. Whether it be an Apple Watch or something
00:12:47.350 --> 00:12:49.230
in your garage that isn't really worth anything
00:12:49.230 --> 00:12:51.169
to you right now, but you could put it on Facebook
00:12:51.169 --> 00:12:52.909
Marketplace. Everyone hates that. It's super
00:12:52.909 --> 00:12:55.830
annoying, right? Or is it? Because now, you can
00:12:55.830 --> 00:12:58.029
take a picture of something, give it some information,
00:12:58.350 --> 00:13:00.830
it can tell you what it thinks you should price
00:13:00.830 --> 00:13:04.309
it at, because it's a meta product and it integrates
00:13:04.309 --> 00:13:08.090
perfectly with Facebook and Messenger. You know
00:13:08.090 --> 00:13:11.450
what I'm going here. Yes, exactly. You can have
00:13:11.450 --> 00:13:15.529
it post on Facebook Marketplace for you. You
00:13:15.529 --> 00:13:18.190
can give it the photos. It can list it. And then
00:13:18.190 --> 00:13:21.750
when you get 700 people say, ha, is this available?
00:13:22.190 --> 00:13:25.370
Guess what? You can have it answer. Game changer,
00:13:25.470 --> 00:13:28.909
bro. Game changer. All right. So who's going
00:13:28.909 --> 00:13:30.330
to liquidate everything in their house right
00:13:30.330 --> 00:13:32.549
now? That's what I'm talking about. We are currently
00:13:32.549 --> 00:13:35.450
building a house and it is super, super exciting.
00:13:35.649 --> 00:13:38.730
And one of the things that is a interesting thing
00:13:38.730 --> 00:13:42.190
is lighting. Who knew that light fixtures were
00:13:42.190 --> 00:13:45.769
so expensive? It's crazy. So I just had my wife
00:13:45.769 --> 00:13:48.769
send me pictures of her favorite light fixtures
00:13:48.769 --> 00:13:51.309
and I gave them to Muse. And I said, hey, look
00:13:51.309 --> 00:13:54.090
at all the major lighting retailers, including
00:13:54.090 --> 00:13:57.590
places like Sam's Club and Costco. Praise Costco.
00:13:57.830 --> 00:13:59.860
It's only an hour away over here. Maybe someday
00:13:59.860 --> 00:14:01.720
we'll get it here. We'll see. And I had it scan
00:14:01.720 --> 00:14:04.000
all those locations for things that were similar,
00:14:04.100 --> 00:14:06.980
but more economically priced. And every single
00:14:06.980 --> 00:14:10.440
one of them yielded an amazing result that we
00:14:10.440 --> 00:14:13.299
could buy today for a fraction of the price and
00:14:13.299 --> 00:14:15.340
not feel like we're getting a Teemu version of
00:14:15.340 --> 00:14:17.740
that lighting product. Imagine all the different
00:14:17.740 --> 00:14:19.879
ways that you could utilize something like that
00:14:19.879 --> 00:14:23.019
to get something that you want or need. but easier
00:14:23.019 --> 00:14:25.120
on your wallet without you having to spend the
00:14:25.120 --> 00:14:27.360
time to do so. Now, if you own a small business
00:14:27.360 --> 00:14:29.659
or you just want to post regularly on social
00:14:29.659 --> 00:14:32.080
media so you can invest in others, have an impact,
00:14:32.220 --> 00:14:34.740
put some positivity out in the world, I totally
00:14:34.740 --> 00:14:37.419
get you. But that is a ton of work as someone
00:14:37.419 --> 00:14:40.620
who was posting on social daily for over three
00:14:40.620 --> 00:14:44.440
years. Now, enter Muse. You can give it the context,
00:14:44.500 --> 00:14:46.759
the type of content that you'd like to do. You
00:14:46.759 --> 00:14:50.120
can give it a slew of your social posts so it...
00:14:50.370 --> 00:14:54.009
starts to understand your voice or your company's
00:14:54.009 --> 00:14:56.870
voice, and then schedule out an entire calendar,
00:14:57.090 --> 00:15:00.330
not just the content, which you can do in Cloud
00:15:00.330 --> 00:15:03.409
right now, but have it actively schedule that
00:15:03.409 --> 00:15:06.610
content inside Facebook, Instagram, and even
00:15:06.610 --> 00:15:09.389
threads. It's crazy. Something that would have
00:15:09.389 --> 00:15:13.289
taken you an entire day without any AI. down
00:15:13.289 --> 00:15:16.350
to around two -ish hours with the help of AI
00:15:16.350 --> 00:15:18.909
generating the content for you, but you still
00:15:18.909 --> 00:15:21.870
having to manually post it, to literally 20,
00:15:22.009 --> 00:15:25.149
30 minutes. And once you have it trained, it
00:15:25.149 --> 00:15:28.250
takes less time in the future, arguably so, probably
00:15:28.250 --> 00:15:30.909
more time supplying it the photos it needs for
00:15:30.909 --> 00:15:33.090
the content. than anything else. So if you're
00:15:33.090 --> 00:15:35.870
an organized person like me with some of my businesses,
00:15:36.029 --> 00:15:38.570
I have organized folders and I could just point
00:15:38.570 --> 00:15:41.450
it to those and boom, it grabbed what it needed
00:15:41.450 --> 00:15:44.529
and did a very good job. Now, you're like, this
00:15:44.529 --> 00:15:46.809
is totally a sales ad for Muse. How much is Meta
00:15:46.809 --> 00:15:49.269
paying you? Nothing. But I will definitely say,
00:15:49.429 --> 00:15:52.710
just like any AI, audit it because there were
00:15:52.710 --> 00:15:54.950
a couple that I didn't look over very closely
00:15:54.950 --> 00:15:57.590
and when I saw that they were posted, I'm like,
00:15:57.629 --> 00:16:00.539
oi. This does not fit. I need to make some edits.
00:16:00.740 --> 00:16:03.299
So disclaimer, what it thinks it's a good idea
00:16:03.299 --> 00:16:06.480
is pretty close, but still deserves your eyeball.
00:16:06.659 --> 00:16:08.840
Now, an easy way to do this, if you're like,
00:16:08.899 --> 00:16:11.679
well, I know kind of the things that I want to
00:16:11.679 --> 00:16:14.220
post throughout the month, but I don't know what
00:16:14.220 --> 00:16:16.500
photo is going to be relevant in the moment.
00:16:16.539 --> 00:16:18.960
And I'd like to be in control of that. That's
00:16:18.960 --> 00:16:21.110
cool. If you want to do it that way, you guys
00:16:21.110 --> 00:16:23.289
can coordinate what dates that you want everything
00:16:23.289 --> 00:16:26.509
scheduled and then have it ping you for a photo
00:16:26.509 --> 00:16:29.690
of that post when each day arrives. And then
00:16:29.690 --> 00:16:31.350
you could just search for the photo that you
00:16:31.350 --> 00:16:33.750
want it to use for that post and give it to it
00:16:33.750 --> 00:16:35.730
and have it take care of the rest. Now I have
00:16:35.730 --> 00:16:37.850
so many more use cases that I could list off,
00:16:37.929 --> 00:16:39.669
but we don't have enough time. So you may be
00:16:39.669 --> 00:16:42.669
thinking, man, I don't want to try to learn another
00:16:42.669 --> 00:16:45.809
AI tool. And I'll say, I get it, man. It makes
00:16:45.809 --> 00:16:48.409
total sense. But I would say here, this one is
00:16:48.409 --> 00:16:51.549
so ridiculously easy to use. And as a result,
00:16:51.570 --> 00:16:54.269
doesn't require a huge learning curve. And all
00:16:54.269 --> 00:16:57.570
AI services now have an import export function
00:16:57.570 --> 00:17:00.570
where it has a prompt that you can put in another
00:17:00.570 --> 00:17:03.789
AI chatbot or AI agent that you've been using
00:17:03.789 --> 00:17:06.289
that is more familiar with you and has some context
00:17:06.289 --> 00:17:09.089
built up. And you can export your information
00:17:09.089 --> 00:17:11.910
out of it just with that prompt in a normal chat
00:17:11.910 --> 00:17:15.009
window, copy and paste that into your Muse. And
00:17:15.009 --> 00:17:18.549
now Muse has some starting context that it can
00:17:18.549 --> 00:17:21.750
use to really jumpstart its familiarity with
00:17:21.750 --> 00:17:23.950
you so you don't have to build that over time.
00:17:24.009 --> 00:17:26.710
So it really takes away the friction of getting
00:17:26.710 --> 00:17:29.089
hooked up with a new tool. And my challenge is...
00:17:29.289 --> 00:17:32.349
Just start with one chat, one thing that you
00:17:32.349 --> 00:17:35.750
want it to try to do and see how it works. That's
00:17:35.750 --> 00:17:38.009
what I did because I wasn't really quite sure
00:17:38.009 --> 00:17:39.769
what I wanted it to do. So I was like, yeah,
00:17:39.789 --> 00:17:41.630
sure. This is kind of annoying and I want to
00:17:41.630 --> 00:17:43.769
get it off my plate and I don't feel bad for
00:17:43.769 --> 00:17:45.769
asking it to do it. And if it doesn't do it well,
00:17:45.869 --> 00:17:47.869
then it doesn't cost me anything except maybe
00:17:47.869 --> 00:17:50.329
a few minutes prompting it. So I tried it a little
00:17:50.329 --> 00:17:53.589
back and forth and it had a ridiculously intuitive
00:17:53.589 --> 00:17:56.450
good idea about what I was trying to get it to
00:17:56.450 --> 00:17:58.880
do. And so then I was like, well, what else could
00:17:58.880 --> 00:18:00.940
I have it do? And that snowball just started
00:18:00.940 --> 00:18:02.980
rolling. And one of the interesting things about
00:18:02.980 --> 00:18:06.299
Muse is that it has a couple different selections
00:18:06.299 --> 00:18:09.660
on the left -hand side. And one of them is ideas.
00:18:09.960 --> 00:18:12.940
And as you connect more services and start to
00:18:12.940 --> 00:18:16.259
use it more, it starts to have very relevant
00:18:16.259 --> 00:18:19.400
ideas of what it can help you with. So if you're
00:18:19.400 --> 00:18:21.900
challenged in what you should have it do, that
00:18:21.900 --> 00:18:24.519
ideas section starts to be super handy where
00:18:24.519 --> 00:18:26.339
you're looking through it and you're like, yes,
00:18:26.420 --> 00:18:29.200
absolutely, let's do it. Now I get it. Some people
00:18:29.200 --> 00:18:31.660
might have security concerns. Meta certainly
00:18:31.660 --> 00:18:34.680
has gotten in trouble for that in the past. And
00:18:34.680 --> 00:18:36.380
there have even been some class action lawsuits
00:18:36.380 --> 00:18:40.140
around security and its data usage in the past.
00:18:40.440 --> 00:18:43.539
Zuckerberg gives some discussion around this
00:18:43.539 --> 00:18:46.519
since it's obviously a hot topic and every journalist
00:18:46.519 --> 00:18:48.839
seems to be asking him about this. And he talks
00:18:48.839 --> 00:18:52.220
about how Facebook is inherently a social sharing
00:18:52.220 --> 00:18:56.809
service. information tends to be more free -flowing
00:18:56.809 --> 00:18:59.990
in that service than in something, which he gives
00:18:59.990 --> 00:19:02.930
the example of WhatsApp, for example, a secure
00:19:02.930 --> 00:19:05.950
communication platform that not even Meta can
00:19:05.950 --> 00:19:09.069
see your communications on. So he's saying they
00:19:09.069 --> 00:19:12.069
learned a thing or two about that platform, and
00:19:12.069 --> 00:19:14.349
so they've brought some of those things into
00:19:14.349 --> 00:19:17.529
Muse, loosely speaking, is the general idea.
00:19:17.789 --> 00:19:19.809
One of the first things that I thought was very
00:19:19.809 --> 00:19:23.710
cool was this credential management. vault situation
00:19:23.710 --> 00:19:26.589
that they have going on where you get to input
00:19:26.589 --> 00:19:30.009
your credentials and your agent and Meta can't
00:19:30.009 --> 00:19:33.630
see your login information. That is pretty amazing.
00:19:33.789 --> 00:19:36.869
As well as payment options as well. Those two
00:19:36.869 --> 00:19:39.190
things got my attention because they're definitely
00:19:39.190 --> 00:19:42.349
unique and much easier to use than other services
00:19:42.349 --> 00:19:44.589
that I was familiar with. Now, there are currently
00:19:44.589 --> 00:19:48.140
some challenges there too in that a lot of services
00:19:48.140 --> 00:19:51.240
that you log into these days are protected by
00:19:51.240 --> 00:19:54.329
multi -factor authentication They can allow you
00:19:54.329 --> 00:19:56.390
to use pass keys, but that's not something your
00:19:56.390 --> 00:19:59.410
AI agent has access to. And so at least at its
00:19:59.410 --> 00:20:03.009
current iteration, there isn't a easy multi -factor
00:20:03.009 --> 00:20:05.990
authentication solution. So every time that your
00:20:05.990 --> 00:20:08.730
agent tries to log in to any of these services,
00:20:09.029 --> 00:20:10.990
it's going to ping you for the code, similar
00:20:10.990 --> 00:20:13.190
to what your spouse probably has to do 10 times
00:20:13.190 --> 00:20:15.509
a day, as my wife and I joke about all the time.
00:20:15.630 --> 00:20:17.849
But I like to say, if you have an executive assistant
00:20:17.849 --> 00:20:21.509
that has access to a lot of your services, then
00:20:21.509 --> 00:20:23.410
you're kind of used to doing that because there
00:20:23.410 --> 00:20:25.789
are certain things that you can't create additional
00:20:25.789 --> 00:20:28.910
users in those platforms. And so you're giving
00:20:28.910 --> 00:20:31.549
that person access. if you trust them to that
00:20:31.549 --> 00:20:34.230
area of your life. So similar way to function
00:20:34.230 --> 00:20:37.230
in that route. So by that very logic, you do
00:20:37.230 --> 00:20:39.730
want to be conscious in what you're giving the
00:20:39.730 --> 00:20:43.009
agent access to. Meta itself talks about this,
00:20:43.049 --> 00:20:45.849
as do other AI services. Like, hey, please be
00:20:45.849 --> 00:20:48.730
careful what you give the agent access to. Don't
00:20:48.730 --> 00:20:51.670
give it these things. And if you're in a industry
00:20:51.670 --> 00:20:55.430
that is regulated for compliance, security, and
00:20:55.430 --> 00:20:57.170
those kinds of things, you're going to want to
00:20:57.170 --> 00:21:00.069
be very conscious in what you share with it.
00:21:00.319 --> 00:21:02.400
not just to protect yourself, but to protect
00:21:02.400 --> 00:21:04.680
the business and protect the information that
00:21:04.680 --> 00:21:06.880
you've been entrusted by your customers or your
00:21:06.880 --> 00:21:08.900
patrons. And another thing that got my attention
00:21:08.900 --> 00:21:12.500
concerning privacy and security was that it is
00:21:12.500 --> 00:21:15.980
always defaulting towards the ask permission
00:21:15.980 --> 00:21:19.579
first model. So it never assumes permission and
00:21:19.579 --> 00:21:22.680
it always assumes it needs to ask. Now you can
00:21:22.680 --> 00:21:25.900
certainly ramp that up by giving it more control
00:21:25.900 --> 00:21:28.740
by selecting things like always allow in this
00:21:28.740 --> 00:21:32.140
conversation or always allow this type of action,
00:21:32.279 --> 00:21:34.799
which can of course save you time, but you do
00:21:34.799 --> 00:21:37.220
want to be selective in when you allow it to
00:21:37.220 --> 00:21:40.119
do those kinds of things. So for example, purchasing
00:21:40.119 --> 00:21:43.200
and login ability is always ask first. It will
00:21:43.200 --> 00:21:45.980
never log in without your knowledge, even if
00:21:45.980 --> 00:21:48.460
you've already put your credentials in the credential
00:21:48.460 --> 00:21:51.039
vault, which I've left on just to make sure that
00:21:51.039 --> 00:21:54.359
I'm aware every time it's in one of my services
00:21:54.359 --> 00:21:56.579
that are protected with a login. So there's so
00:21:56.579 --> 00:21:59.880
many things that you can use this tool for. So
00:21:59.880 --> 00:22:01.640
let's run through some practical things that
00:22:01.640 --> 00:22:03.710
you can just kind of brainstorm. Now, if you
00:22:03.710 --> 00:22:06.150
have an AI chatbot now, you can even start by
00:22:06.150 --> 00:22:08.829
asking it, hey, what are some things that you
00:22:08.829 --> 00:22:12.069
can help me do? maybe connect some services to
00:22:12.069 --> 00:22:13.990
it, like your email or some things like that,
00:22:14.009 --> 00:22:16.089
so we can gain some additional understanding.
00:22:16.309 --> 00:22:18.930
But even just asking a flat -out question without
00:22:18.930 --> 00:22:21.890
it being attached to anything can typically allow
00:22:21.890 --> 00:22:24.269
it to ask a couple questions on what are some
00:22:24.269 --> 00:22:26.250
things that you've been wanting to do but have
00:22:26.250 --> 00:22:28.509
been putting off, what are some things you've
00:22:28.509 --> 00:22:31.130
not been able to get past the finish line, and
00:22:31.130 --> 00:22:33.549
then you can collaborate on some ideas. And I'm
00:22:33.549 --> 00:22:35.609
telling you, it will fish some things out that
00:22:35.609 --> 00:22:38.059
might surprise you. Now, if you end up connecting
00:22:38.059 --> 00:22:41.339
a bunch of things, also getting another AI agent's
00:22:41.339 --> 00:22:43.559
export, popping those in there for some easy
00:22:43.559 --> 00:22:46.700
memory, connecting your to -do app or your Apple
00:22:46.700 --> 00:22:48.819
reminders and some things like that can give
00:22:48.819 --> 00:22:51.319
it some easy ways to know how to help you really,
00:22:51.359 --> 00:22:54.230
really quickly. thereby sparking the ideas tab
00:22:54.230 --> 00:22:57.069
to life, which is pretty impressive. So those
00:22:57.069 --> 00:22:59.710
are some easy things that you can do to get the
00:22:59.710 --> 00:23:01.849
ball rolling. But let's say you're a business
00:23:01.849 --> 00:23:04.190
owner and you're like, man, I really want to
00:23:04.190 --> 00:23:06.950
stay on top of reviews, but sometimes they can
00:23:06.950 --> 00:23:09.730
be really time consuming. You can prompt your
00:23:09.730 --> 00:23:12.630
Muse agent by saying, hey, browse my company
00:23:12.630 --> 00:23:15.950
reviews, get familiar with how I respond to positive
00:23:15.950 --> 00:23:19.630
and negative reviews. Then scan my page weekly
00:23:19.630 --> 00:23:22.210
for new reviews that I've not yet responded to
00:23:22.210 --> 00:23:25.009
and draft me replies to all of them and ping
00:23:25.009 --> 00:23:27.670
me when they're ready for my review. Bam. Once
00:23:27.670 --> 00:23:29.769
they pass your review, you could copy and paste
00:23:29.769 --> 00:23:31.789
them yourself. Or if you don't want to log in
00:23:31.789 --> 00:23:33.769
or open that, you can say, perfect, these all
00:23:33.769 --> 00:23:36.029
look great. Go ahead and post them. Another simple
00:23:36.029 --> 00:23:38.549
prompt might be after you plug in a lot of the
00:23:38.549 --> 00:23:41.519
integrations, you could simply ask it, hey. From
00:23:41.519 --> 00:23:44.819
all my integrations, give me a short five -point
00:23:44.819 --> 00:23:47.220
executive morning brief of things that need my
00:23:47.220 --> 00:23:50.059
attention, maybe things waiting on me, or maybe
00:23:50.059 --> 00:23:52.799
areas that I've dropped the ball. Those are all
00:23:52.799 --> 00:23:56.299
really cool prompts to kind of send it on a scavenger
00:23:56.299 --> 00:23:58.579
hunt to identify the top five things that need
00:23:58.579 --> 00:24:00.940
your attention that morning. And if you ask it
00:24:00.940 --> 00:24:03.240
to do that on a daily basis, it'll be there for
00:24:03.240 --> 00:24:05.579
you every single day. We've already talked about
00:24:05.579 --> 00:24:08.359
a social media strategy. I don't know what social
00:24:08.359 --> 00:24:11.019
media fulfills for you, but if you are a content
00:24:11.019 --> 00:24:14.279
creator in any way, this is a huge asset for
00:24:14.279 --> 00:24:17.420
you in just growing your ability to create content.
00:24:17.640 --> 00:24:20.140
And then a bonus one for me that I didn't expect,
00:24:20.200 --> 00:24:22.130
to be honest. I don't know about you, but if
00:24:22.130 --> 00:24:23.789
you've got a lot of things going on, a lot of
00:24:23.789 --> 00:24:26.190
things that you're working on, sometimes there
00:24:26.190 --> 00:24:28.990
are personal things that are on your to -do list
00:24:28.990 --> 00:24:32.289
that just end up shuffling to the back for months.
00:24:32.859 --> 00:24:35.279
maybe even years. And so there were some things
00:24:35.279 --> 00:24:38.359
that I was putting off and not executing on.
00:24:38.480 --> 00:24:40.720
And finally, I was like, well, shoot, I lose
00:24:40.720 --> 00:24:43.359
nothing by asking to see what it could bring
00:24:43.359 --> 00:24:45.740
to the table concerning this issue. I took a
00:24:45.740 --> 00:24:48.160
couple emails that had some context information
00:24:48.160 --> 00:24:51.599
about it, so I didn't have to try to build the
00:24:51.599 --> 00:24:53.799
understanding from scratch. And it picked it
00:24:53.799 --> 00:24:56.180
up pretty quickly and started moving things across
00:24:56.180 --> 00:24:59.109
the goal line where... maybe it was stagnant
00:24:59.109 --> 00:25:01.670
for a ridiculous amount of time. And I'll be
00:25:01.670 --> 00:25:03.809
honest with you, that is not something that I
00:25:03.809 --> 00:25:06.410
expected. So some of those hours that I saved
00:25:06.410 --> 00:25:09.769
weren't hours I would have spent if I didn't
00:25:09.769 --> 00:25:11.829
have this tool. It was like a combination of
00:25:11.829 --> 00:25:14.910
things that were going to take my time anyway,
00:25:15.029 --> 00:25:18.450
and then things that I wouldn't have spent time
00:25:18.450 --> 00:25:21.549
on and would have continued to be left undone
00:25:21.549 --> 00:25:24.740
like they had been for months. maybe even years.
00:25:24.980 --> 00:25:27.259
So it's like a win -win for me in multiple areas,
00:25:27.519 --> 00:25:30.480
all contributing to that five to 10 hour window
00:25:30.480 --> 00:25:33.619
each week. And it doesn't show any evidence of
00:25:33.619 --> 00:25:36.400
slowing down yet. Every time I open up my iPhone
00:25:36.400 --> 00:25:39.059
and swipe up to see what the recommended apps
00:25:39.059 --> 00:25:42.660
are, it is now the top left app, no matter what.
00:25:42.680 --> 00:25:45.339
No matter what time of the day, Siri knows, yeah,
00:25:45.500 --> 00:25:48.099
you probably are wanting Muse to help you with
00:25:48.099 --> 00:25:51.170
something. Facts. Thanks, Siri. So if this is
00:25:51.170 --> 00:25:53.190
your first time hearing about Muse, I'm going
00:25:53.190 --> 00:25:55.829
to go ahead and leave my referral code in the
00:25:55.829 --> 00:25:57.769
description below. Like I said earlier, that
00:25:57.769 --> 00:26:00.950
gives both of us 1 billion usage tokens. Now,
00:26:01.009 --> 00:26:03.650
my referral code will eventually run out. So
00:26:03.650 --> 00:26:06.549
if it no longer works, other people can comment
00:26:06.549 --> 00:26:09.470
in the comments below on what your referral code
00:26:09.470 --> 00:26:12.690
is and you can get additional tokens that way.
00:26:12.750 --> 00:26:14.789
And that way we can keep the referral tokens
00:26:14.789 --> 00:26:17.470
going. in that regard. And remember what I said
00:26:17.470 --> 00:26:20.170
earlier, you want to start shifting your mind
00:26:20.170 --> 00:26:24.190
to not just how can Muse help me with this, but
00:26:24.190 --> 00:26:28.150
how can Muse do this for me? It's a super powerful
00:26:28.150 --> 00:26:30.829
shift in your brain that can help you delegate
00:26:30.829 --> 00:26:34.430
even more. And for my fellow entrepreneurs, business
00:26:34.430 --> 00:26:36.930
leaders out there, delegation is one of those
00:26:36.930 --> 00:26:39.650
things that you probably wrestle with and find
00:26:39.650 --> 00:26:41.750
challenging. Because when it involves another
00:26:41.750 --> 00:26:45.009
human being, you can sometimes feel like a burden.
00:26:45.130 --> 00:26:48.009
Whereas with something like this, an AI agent
00:26:48.009 --> 00:26:50.289
does not have a family where you might be interrupting
00:26:50.289 --> 00:26:53.109
family time. It won't make you feel guilty for
00:26:53.109 --> 00:26:57.210
asking it to do a 17th thing in the day. And
00:26:57.210 --> 00:27:00.150
it will work round the clock if you ask it to.
00:27:00.289 --> 00:27:03.009
And that is just absolutely amazing. I'm not
00:27:03.009 --> 00:27:05.890
going to lie. Sometimes I wake up and I go, I
00:27:06.269 --> 00:27:08.470
mean, this is exciting. what else could I have
00:27:08.470 --> 00:27:11.730
Muse do? I can't remember a time in history where
00:27:11.730 --> 00:27:14.829
I woke up with that kind of wonder. It's kind
00:27:14.829 --> 00:27:17.410
of fun. And I hope it can be fun for you too.
00:27:17.630 --> 00:27:20.049
As always, thanks for listening to the Optimizing
00:27:20.049 --> 00:27:22.630
Beyond podcast. Remember, growth happens when
00:27:22.630 --> 00:27:25.230
you take action. So subscribe, share this with
00:27:25.230 --> 00:27:27.890
a friend, and most importantly, download Muse
00:27:27.890 --> 00:27:30.769
and put what you learned into practice. Because
00:27:30.769 --> 00:27:34.089
as we know, daily anything changes everything.
