TRANSCRIPT 🔗
WEBVTT
00:00:14.026 --> 00:00:16.437
Today we've got, uh, Ryan Castillo back with us.
00:00:16.486 --> 00:00:22.716
We, we were just talking pre-show, it's been 30-plus episodes since we recorded for us, so, uh, glad to have you back, Ryan
00:00:23.574 --> 00:00:24.484
Yeah, thanks.
00:00:24.574 --> 00:00:26.245
Yeah, again, congrats to you guys.
00:00:26.245 --> 00:00:28.545
I mean, 30 episodes is a lot, you know?
00:00:28.664 --> 00:00:29.875
So it's,
00:00:30.071 --> 00:00:30.521
Yeah
00:00:30.655 --> 00:00:33.064
cool to see how the show has progressed since we first talked
00:00:34.127 --> 00:00:39.996
Yeah, definitely, 'cause I, I think, I didn't look back before the, the call, but I think you might have been our second guest, second or third, somewhere around there.
00:00:39.996 --> 00:00:47.267
You, it w- you were definitely one of the first guests we had, so it is pretty cool to, to have you back and kind of check in, and we can just jump off from there.
00:00:47.267 --> 00:00:54.216
So, you know, last time I think Noatoa was fairly new, but, you know, sounds like things are going pretty well.
00:00:54.216 --> 00:00:59.777
If you wanna just kind of talk about kind of where things are with Noatoa and, um, you know, how you guys are doing, that'd be great
00:01:00.182 --> 00:01:00.633
Yeah.
00:01:00.713 --> 00:01:05.412
Um, so back then, I think we were running two products.
00:01:05.442 --> 00:01:08.632
We were-- We had Wafris, which was like a web application firewall.
00:01:08.933 --> 00:01:12.683
We had gone to a, a number of, of Rails conferences and promoted that.
00:01:13.072 --> 00:01:19.072
Um, but in the midst of all that and trying to promote it, AI started becoming a thing.
00:01:19.492 --> 00:01:28.582
And I think when we first asked ChatGPT about Wafris, it started sp-spurting out a lot of things about like Waffle House and like waffles.
00:01:28.593 --> 00:01:30.893
It was, it was basically hallucinating about the brand.
00:01:31.343 --> 00:01:44.513
And we were like, "Huh, that's, that's interesting." And, um, a lot of founder friends, we were like, "Okay, what happens if we start running a bunch of people's businesses through this?" You know, and then we started kinda building some scripts and stuff like that.
00:01:44.992 --> 00:02:05.522
And, um, that actually started rolling, and so we decided, "Hey, w-why don't we try and build an AI visibility product?" Um, and that's how Noatoa was born, and it kept on getting more and more traction, and kinda took the eye or the eye off the ball with Waf-Wafris.
00:02:05.543 --> 00:02:08.793
So I think sometime last year, we decided to kinda sunset it.
00:02:09.223 --> 00:02:13.342
Um, and, you know, there, there have been some pivots around Noatoa.
00:02:13.802 --> 00:02:26.883
Um, there's a lot of people who have thought that, okay, um, we're losing organic search, we're losing traffic and all that stuff, and, you know, AI is somehow gonna-- AI visibility is somehow gonna replace
Load full transcript
that.
00:02:26.883 --> 00:02:29.082
A-and that's just not true.
00:02:29.383 --> 00:02:34.703
Um, and some of the metrics around AI search aren't great either.
00:02:34.893 --> 00:02:41.242
Like, uh, I think the main ones are sentiment, visibility or mentions, and citations.
00:02:41.932 --> 00:02:49.872
Those are decent metrics, but at the same time, it's all dependent on you're tracking, the data that's coming in.
00:02:49.953 --> 00:02:54.973
So as we've always known, you know, garbage data in, garbage out, insights out.
00:02:55.002 --> 00:02:59.483
So, you know, that's, that's something that we've, we've been working against as well.
00:03:00.640 --> 00:03:01.100
Got it.
00:03:01.950 --> 00:03:03.010
Yeah, that, that's interesting.
00:03:03.010 --> 00:03:17.161
I, I think about it sometimes even, you know, like I don't have a specific product that I'm promoting, but obviously my company, we use SEO and that's kind of been one of our biggest things is always getting SEO, free SEO traffic essentially, right?
00:03:17.161 --> 00:03:25.080
And like we are still trying to navigate now when is ChatGPT or Claude bringing up our name.
00:03:25.621 --> 00:03:30.360
Like Ryan, Ryan, my co-host here, I'm not sure how his company handles it.
00:03:31.371 --> 00:03:39.961
Um, but it, it definitely hasn't seemed to be like a huge breakthrough or, or like it hasn't overtaken our SEO traffic or anything like that.
00:03:40.401 --> 00:03:55.540
Um, so I- I've actually thrown Noatoa in front of my boss to say, "Hey, this is a tool we might wanna look into." We haven't pulled the trigger on it yet, but like what, what kind of clients are you seeing, I guess is maybe my, where my question's going here is like, are you, you getting like various clients?
00:03:55.540 --> 00:03:57.170
Are you getting more tech-oriented people?
00:03:57.170 --> 00:03:58.610
Like what, what are you seeing?
00:03:59.191 --> 00:03:59.681
Yeah.
00:03:59.730 --> 00:04:02.281
We're actually getting people all over the map.
00:04:02.381 --> 00:04:15.330
You know, um, in our industry, everyone is targeting the agencies because the agencies are the one that are, that are most ready to buy, um, primarily because they're suffering loss of their client base, right?
00:04:15.425 --> 00:04:15.745
Sure
00:04:16.040 --> 00:04:40.680
they're seeing their metrics fall through the floor, and they're trying to justify to their clients, like, "What is our next step?" Um, but we're also seeing people come in that-- Another, like, primary client cu- customer base is people that are coming in and, um, we actually look at their keywords, and we see that, like, over half of their keywords are vulnerable to, to losing traffic to AI search.
00:04:41.000 --> 00:04:43.370
Um, so those are a big, you know, user base.
00:04:43.721 --> 00:04:50.790
Um, the third bucket are people that have zero search volume traffic at all, and they're just AI curious.
00:04:51.110 --> 00:04:55.911
They're just kind of like window
shoppers, or they've started up a new brand and they don't really know how to market that brand.
00:04:56.281 --> 00:05:00.031
Um, the first two are the ones that we can help the most with.
00:05:00.071 --> 00:05:08.750
We're, we're trying to do some things to help with that third bucket, but, um, there's a lot of education, you know, across all three that has to happen.
00:05:09.430 --> 00:05:09.821
Yeah.
00:05:10.891 --> 00:05:14.440
Are you guys putting out a lot of, like, educational content then?
00:05:14.610 --> 00:05:18.021
Just, you know, typical content marketing types of things to help with that
00:05:18.423 --> 00:05:28.312
Yeah, so this, this is where things, um, of come, come into play as far as like, hey, how, how do we show up in, like, AI conversations?
00:05:28.312 --> 00:05:31.033
Like you said, you guys are trying to have that happen for your brand.
00:05:31.452 --> 00:05:35.413
Um, it is a mixed bag.
00:05:35.622 --> 00:05:58.293
Like, it's been hard for us to put out educational content because, you know, on some levels the thought is, is like, "Hey, we are not gonna actually see any search traffic for that." So in the past six months to a year, we've been really hesitant to do that, mainly because our thought is like, "Hey, this isn't gonna actually bring any traffic to the site.
00:05:58.612 --> 00:06:11.783
What this is actually gonna do is it's just gonna feed ChatGPT and people are just gonna stay and live in ChatGPT." Um, we've kind of turned around on that and said, "No, we're not gonna work ab- worry about the metrics anymore at all.
00:06:12.052 --> 00:06:31.083
You know, we're just gonna worry about our branding, and we're gonna worry about helping as many people as possible." And so within the last month or so, we've kind of pivoted towards like, hey, now we're gonna start going about, like, releasing more videos, releasing educational content, participating in more Slacks in different communities, and talks and podcasts and, and all of that.
00:06:32.127 --> 00:06:32.567
Got it.
00:06:32.766 --> 00:06:33.156
Okay
00:06:33.295 --> 00:06:39.646
interesting things there that I wanna dive into, but first, for, uh, I wasn't on the first call with you, right?
00:06:39.665 --> 00:06:44.146
And I'm guessing a bunch of our audience, uh, maybe didn't see that or know of Knowatoa.
00:06:44.156 --> 00:06:46.536
Can you just give us like a high-level view?
00:06:46.536 --> 00:06:52.185
I mean, I, I get AI search, but what exactly are you doing to help with AI search?
00:06:52.185 --> 00:06:54.156
So that's question number one that I'll kick back to you.
00:06:54.656 --> 00:06:55.357
Sure, sure.
00:06:55.607 --> 00:06:59.057
So, uh, and the product has shifted, right?
00:06:59.146 --> 00:07:11.817
Um, originally what we used to do is someone would come in and they would submit their brand and, um, we would take those keywords from that brand and look at intent behind those keywords and generate questions.
00:07:12.586 --> 00:07:24.107
we take those questions and we ask it against all the AI models like AI Overviews, AI Mode, Gemini, Claude, Perplexity, ChatGPT, and just to see what answers come back.
00:07:24.377 --> 00:07:27.497
And then from those answers, we would kind of look at these metrics.
00:07:27.497 --> 00:07:36.666
We would see like, "Hey, are all these like positive answers about the b- brand or are all these negative?" Um, how many times is this brand mentioned in these answers?
00:07:36.677 --> 00:07:38.567
How many time are their competitors mentioned?
00:07:38.987 --> 00:07:43.737
Um, what kind of citations and referrals to other sites are being mentioned in these answers?
00:07:43.997 --> 00:07:46.166
And so the product today shows all that.
00:07:46.516 --> 00:08:02.516
Um, and so originally we were like a visibility platform, but now what we're trying to do is we're trying to pivot that more around, hey, everything that's coming back in this is actually just a small sample size of what the internet thinks about your brand.
00:08:02.877 --> 00:08:12.716
And so as a user, what you need to do is you need to figure out when looking at this data, um, where do your prospects and customers actually live?
00:08:12.906 --> 00:08:16.937
Do they live in the sites that are being returned from the data that we're pulling?
00:08:17.257 --> 00:08:22.047
And what gaps are there in the answers that are being returned?
00:08:22.276 --> 00:08:30.026
You know, is this brand-- some- is there a feature about your brand that, that's being misrep- represented or is not being covered in these answers?
00:08:30.326 --> 00:08:38.496
And if so, we help you plan out where you need to show up and what you need to say so that you can attract your customers about
00:08:38.518 --> 00:08:38.967
Okay.
00:08:39.118 --> 00:08:44.427
So that's a, that's a good segue into my second question is, you know, putting your education hat on, right?
00:08:44.427 --> 00:08:48.488
Like, what are examples of what you might recommend, right?
00:08:48.498 --> 00:08:51.447
How do you show up in AI, right?
00:08:51.447 --> 00:08:55.868
'Cause y- it, uh, you, you said you were sort of hesitant to do content, right?
00:08:55.868 --> 00:08:59.957
So, like, what else is there, right, for us that are,
00:09:00.273 --> 00:09:00.793
Yeah.
00:09:00.957 --> 00:09:01.817
AI illiterate?
00:09:02.783 --> 00:09:08.393
and the, the clarifying point on there, it was the, the, the kind of content that we were willing to do.
00:09:08.753 --> 00:09:15.263
Um, right now, if you look at like keywords, let's just talk about keywords, and I'm gonna interchange keywords and questions a lot here.
00:09:15.562 --> 00:09:23.572
Um, with keywords, what everyone used to do in the old organic way, days is like they, they try to rank for everything.
00:09:23.653 --> 00:09:31.302
You know, they try to find long-tail keywords somewhat related to their brand, not related to their brand, whatever they could do to bring in traffic.
00:09:31.692 --> 00:09:34.082
Um, like HubSpot is a great example.
00:09:34.092 --> 00:09:35.533
HubSpot's a CMS.
00:09:35.533 --> 00:09:40.562
They had, they had pages that were optimized for like how to write a cover letter.
00:09:40.932 --> 00:09:51.893
There is nothing in like HubSpot's like product that helps people with cover letters or getting jobs, and so they were just trying to get that free traffic to see if they can convert that into an actual sale.
00:09:52.423 --> 00:10:02.263
And so in today's world, you don't really want to optimize for like informational keywords unless it's a new topic.
00:10:02.312 --> 00:10:03.982
Like, you know, Fable is a new topic.
00:10:03.993 --> 00:10:09.793
That's something that you might optimize for, but you won't… That content won't be greenfield anymore.
00:10:09.873 --> 00:10:16.923
You know, in a couple months, ChatGPT or all these other AI models will eventually be able to answer all the questions around that.
00:10:17.722 --> 00:10:29.123
So that's something a lot of like marketing departments that are focused on SEO are trying to kind of resolve theirselves against is like, "Hey, what keywords are we actually still trying to go for?
00:10:29.442 --> 00:10:43.273
Like what should we optimize for?" So, so in our recommendations it's like, hey, throw out all the informational keywords or at least change your expectations as far as what you're gonna get out of them, um, as far as traffic and how long that traffic is gonna come to your site.
00:10:43.643 --> 00:10:52.322
But instead, you know, look for all the gaps, again, in the keywords, in the questions that, you know, your content may not be answering.
00:10:52.673 --> 00:10:57.712
And furthermore, like think about where are the places that your audience lives.
00:10:57.712 --> 00:10:59.342
They don't just live on your site anymore.
00:10:59.482 --> 00:11:04.192
Like another thing some people have said is, know, everywhere is a homepage now.
00:11:04.192 --> 00:11:09.832
ChatGPT is your homepage now, so, uh, LinkedIn is your homepage now, YouTube is your homepage now.
00:11:09.832 --> 00:11:13.253
So are you putting content in all those different areas?
00:11:13.332 --> 00:11:19.732
You know, this is something that we always used to, to preach as marketers, but it was just always hard to do.
00:11:19.732 --> 00:11:22.423
It's like how can we be in so many channels at the same time?
00:11:22.883 --> 00:11:30.972
Um, now that's kinda more important than ever because by repeating that message, you're increasing the likelihood that you show up in these AI conversations.
00:11:31.408 --> 00:11:39.798
So it's, it's less that content doesn't work, it's that content has to be more, both more targeted and more broad, if that even makes sense.
00:11:40.238 --> 00:11:48.168
Targeted in terms of the questions or keywords you're, you're answering, uh, in broad and, you know, the chan- distribution.
00:11:48.207 --> 00:11:50.298
Um, okay.
00:11:51.076 --> 00:11:51.366
Yep
00:11:51.648 --> 00:12:06.687
All right, so Noatoa then helps find those gaps and gives you sort of a, a, a guide to where you're either falling short or missing, uh, the message in the case of sentiment analysis, it sounds like, uh, if, if I got that right.
00:12:06.697 --> 00:12:06.717
Yeah.
00:12:07.102 --> 00:12:07.613
Yep, that's
00:12:07.788 --> 00:12:08.067
Okay.
00:12:08.717 --> 00:12:17.778
right, so the third question that I have for you is, uh, I wanted you to go a little bit deeper on a comment you made, which is you, you kind of threw the analytics out, right?
00:12:17.957 --> 00:12:28.347
Um, you know, m- maybe that was said, uh, uh, you know, with a, a grain of salt, but I'd like to hear more about that.
00:12:28.347 --> 00:12:33.567
'Cause as you were talking, I was thinking like, I don't actually care about the analytics that much.
00:12:33.587 --> 00:12:43.248
Um, you know, I think, uh, Brendan, earlier on you said, "I don't know what you do at Locable." Well, I can tell you, we create content around the stuff that we care about.
00:12:43.398 --> 00:12:47.618
Um, we don't have a specific SEO strategy.
00:12:47.618 --> 00:12:52.467
We just put out things that we think will be helpful for our customer base, and we try to reference it as much as possible.
00:12:52.587 --> 00:12:55.077
But I'm not looking at like, did this keyword rank?
00:12:55.107 --> 00:12:56.888
And frankly, I don't care.
00:12:57.077 --> 00:12:57.697
Um,
00:12:58.144 --> 00:12:58.504
Sure
00:12:59.677 --> 00:13:07.927
you maybe elaborate a little bit more on, you know, why you don't look at the analytics or perhaps clarify what you do care about.
00:13:08.599 --> 00:13:09.068
Yeah.
00:13:09.078 --> 00:13:11.788
So give more into my background.
00:13:11.788 --> 00:13:15.479
So before all this, you know, we all had different stops in our career.
00:13:15.548 --> 00:13:19.099
I, I was working at a, um, you know, like a Fortune 500 company.
00:13:19.099 --> 00:13:24.808
You know, they're trying to get to a billion dollars, and I worked on, in marketing and attribution there.
00:13:25.198 --> 00:13:43.489
And, um, you know, everyone, just to kind of illuminate attribution for the audience, is that attribution is kind of the study of trying to figure out, okay, hey, we spent this mon- this money on X, you know, and it resulted in Y sales, or Y leads, or Y conversions.
00:13:43.869 --> 00:13:53.269
Um, and can we track every single marketing action or marketing touch to this spend or action on our side?
00:13:53.678 --> 00:14:04.769
Um, and that was very challenging at that job because we were having sales cycles that lasted, like, as long as two years or a year plus, you know.
00:14:04.769 --> 00:14:08.749
And these were, these were deals that were, you know, six-figure deals.
00:14:09.068 --> 00:14:23.399
And so in all of that, you know, I would say like, "Oh, you know, the first touch for this user might have been this Google thing." And then the
sales side will be like,"Well, we've been, we've been prospecting this deal for six months, you know.
00:14:23.399 --> 00:14:37.188
Why should Google get any kind of credit?" Or, "Why should the, like, PR side get any kind of credit in this kind of stuff?" And it, and it, it all kind of at some level becomes, comes kind of hand-wavy, like, you know, just made-up
00:14:37.296 --> 00:14:37.655
Yeah
00:14:37.808 --> 00:14:44.089
to kind of paint the picture that you, you want to see because of course departments have to justify budgets and that kind of thing.
00:14:44.528 --> 00:14:50.729
Um, but the end of the day, um, it's just like what you said, Ryan.
00:14:51.149 --> 00:14:56.808
What's most important is, like, being useful and helpful to your prospects and your audience.
00:14:57.208 --> 00:15:07.948
And now with the privacy stuff, the privacy stuff in email, the, you know, it, it's getting harder and harder to track, like, how many times you touch a user.
00:15:08.019 --> 00:15:10.609
There, there's no way of doing that in ChatGPT.
00:15:10.609 --> 00:15:22.259
There's no way of doing that in Claude, like, of knowing, like, all the answers that I ask on a given day so that, you know, something that I've bought after I've researched Claude, there's no way they're gonna be able to tie that back to me.
00:15:22.807 --> 00:15:22.966
Yeah.
00:15:23.037 --> 00:15:32.677
I, I'd even add just like the iOS has gotten so much stricter and like Private Relay and even just Safari in general, like just strips a lot of that attribution stuff out.
00:15:32.706 --> 00:15:35.456
Yeah, we, we've dealt with some of that in our industry as well.
00:15:35.626 --> 00:15:36.636
It, it is a challenge
00:15:37.089 --> 00:15:42.158
And so analytics is important, attribution is important.
00:15:42.168 --> 00:15:50.609
Like when you're running ads, you know, it, it, it is smart to say like, "Hey, you know, we spent $1,000 on these keywords.
00:15:50.639 --> 00:15:55.188
We got, you know, 100 leads from that." That, that's important and that's interesting.
00:15:55.589 --> 00:15:59.458
But you also have to realize the flaws in that approach as well.
00:15:59.469 --> 00:16:06.278
It's like now you can't just say like, "Hey, we're optimizing for all these keywords and now we're getting all this traffic," because that's kind of broken on some level.
00:16:06.408 --> 00:16:17.019
You know, you don't see… More things are showing up under direct and like plausible than, um, than organic or social or those o- other- all those other kind of things.
00:16:17.308 --> 00:16:28.629
And so when you kind of try to look at your efforts for your business or for your marketing and stuff like that, what you have to really ask is like, what are we really trying to accomplish here?
00:16:29.119 --> 00:16:31.729
You know, are we trying to increase leads with this campaign?
00:16:31.778 --> 00:16:33.168
Are we trying to educate?
00:16:33.458 --> 00:16:34.528
Are we trying to do these things?
00:16:34.538 --> 00:16:36.418
Is it really important to look at these metrics?
00:16:36.469 --> 00:16:37.339
Do these matter?
00:16:37.458 --> 00:16:46.528
You know, your, your gut comes into play, your experience comes into play, the, the numbers come into play, and you need to kind of be able to, you know, figure out like what works best for you.
00:16:46.808 --> 00:16:47.989
I know that's kind of like a,
00:16:48.035 --> 00:16:48.336
Well,
00:16:48.489 --> 00:16:49.918
it depends answer, but
00:16:50.176 --> 00:16:50.785
I, I wanna
00:16:50.828 --> 00:16:51.139
is
00:16:51.306 --> 00:16:59.686
dive, dive into that a little bit more if, if you're, if you're okay with it 'cause… All right, so, um, I have a publication business that I, I run.
00:16:59.725 --> 00:17:01.285
It's magazines, all right?
00:17:01.365 --> 00:17:11.905
Uh, they're quarterly publications, um, high-end sort of coffee table style, glossy, thick paper, will sit on a table for, you know, years sometimes.
00:17:14.715 --> 00:17:18.976
you know, I lose sales because people are like, "I, I don't know if it's working.
00:17:19.276 --> 00:17:23.605
I haven't gotten any leads from it." And I'm like, "Well, how are you tracking that?" Right?
00:17:23.605 --> 00:17:27.076
There's no actual… And, and, you know, you can ask.
00:17:27.336 --> 00:17:33.125
That doesn't mean they're gonna respond with, "Oh, I saw your ad." Like, most people wouldn't say that.
00:17:33.865 --> 00:17:44.605
Um, and even if they say, "Oh, I came to your website," that doesn't mean they didn't see the ad six, seven, eight times consciously or subconsciously the way, right?
00:17:44.605 --> 00:17:46.355
There's no way to track that.
00:17:46.355 --> 00:17:58.226
And I think that's-- there are very few mediums, including, like, the digital stuff, where you can actually get from the beginning end in right?
00:17:58.306 --> 00:18:05.395
And, like, the closest I think we get is with, like, perhaps social media attribution channels, right?
00:18:05.395 --> 00:18:06.566
But even that is flawed.
00:18:07.935 --> 00:18:14.375
yeah, so what, you know, what do you, you know, g- given your background, what would you people, right?
00:18:14.375 --> 00:18:32.036
'Cause I, I'm, I'm curious from a business perspective, but, like, know, the other side of that is simply just like, all right, uh, the way I would look at it is like, all right, I'm, I'm spending X amount of dollars, right, in all my advertising, it is leading to some, you know, revenue that comes in at the end of the day.
00:18:32.036 --> 00:18:34.445
And those are really the two numbers I care about, right?
00:18:34.445 --> 00:18:36.016
Spend and dollars.
00:18:36.026 --> 00:18:45.145
And if that is in the right direction, right, like spend is going down, revenue going up, or at least staying equal to where it was, then I'm happy.
00:18:45.415 --> 00:18:51.855
If it start, you know, if costs are going up and revenue stays flat or it goes down, then I'm unhappy and I want to adjust, right?
00:18:51.855 --> 00:18:56.336
But that's, that's about the level that I'm willing to go in terms of, like, analytics.
00:18:57.145 --> 00:19:00.756
I'm curious your viewpoint given, you know, where you came from and what you're working on.
00:19:01.398 --> 00:19:06.939
Yeah, and, and this came down to the conversations that we would have with the CEO at the company.
00:19:06.939 --> 00:19:13.229
It's like, "Well, we can't attribute all this stuff to all our other efforts, you know, of our inbound marketing.
00:19:13.528 --> 00:19:19.568
You know, it's very easy to attribute all this stuff to our sales efforts, like our in-person events and conferences and all that other stuff.
00:19:20.219 --> 00:19:22.729
you want us to just give up on all these other things?
00:19:22.739 --> 00:19:32.479
Should we just, like, fire everybody and, you know, kill these departments?" And, you know, the response was always no, because a lot of those efforts are branding and are not trackable.
00:19:32.769 --> 00:19:42.919
And so, you know, usually the people that are wanting to cut are the people that, you know, don't understand the value of that effort.
00:19:43.239 --> 00:19:48.278
You know, like you said, that magazine is gonna sit there on that table for years and decades.
00:19:48.669 --> 00:19:52.999
You know, like, in some industries, that's super important, you know?
00:19:52.999 --> 00:19:56.568
Maybe, like, there's a jet ski magazine that's been sitting on that table, and
00:19:56.672 --> 00:19:57.001
Right, right
00:19:57.199 --> 00:20:00.019
that goes into that barber shop, they're like,"Oh, man, this jet ski is awesome.
00:20:00.358 --> 00:20:09.848
Let me see if I can go find it on Craigslist or something like that." Or, you know, even those m- those, those magazines like 10 years old, you know, "That's the jet ski I want," or whatever, you know?
00:20:10.127 --> 00:20:10.498
Yeah
00:20:12.798 --> 00:20:14.358
but I get it, you know?
00:20:14.358 --> 00:20:20.528
And this kinda goes back to another one of you guys' previous episodes where, where someone was talking about, like, how SaaS is dead.
00:20:20.979 --> 00:20:31.509
Um, the reason why they're talking about SaaS being dead is because the way in which they've marketed their SaaS and, like, how they've tracked that has changed drastically.
00:20:31.848 --> 00:20:43.519
Everyone was dependent on organic as this free marketing channel that, you know, Google would just bless you with traffic, and then if you cracked that formula, you would somehow… Your business would grow.
00:20:43.538 --> 00:20:49.798
And now that that's been taken away seemingly overnight, people are trying to, wrestle with that.
00:20:50.179 --> 00:20:59.269
And I think more and more people are kinda gonna kinda have to come to terms with, like, how you've been looking at the business, Ryan, is that, hey, all of this stuff is not trackable.
00:20:59.729 --> 00:21:17.209
So all we can do is try to
really think about where our audience is, where they're experiencing the pain that they're experiencing or where they're trying to find information about the job that they want to do, and make sure that we're in those channels with the stuff that they need.
00:21:17.655 --> 00:21:18.036
Right
00:21:18.709 --> 00:21:24.669
the more we think about that as an industry, you know, that's, that's kind of the human, human advantage in all of this.
00:21:26.448 --> 00:21:29.327
Yeah, I, I, I think that's a, a good point.
00:21:29.567 --> 00:21:41.597
Um, you know, I would even go so far as, you know, I'm gonna transition the conversation here a little bit, um, and, you know, maybe we can dive into some AI stuff, uh, despite my best efforts to stay away from it.
00:21:42.048 --> 00:21:54.097
Um, but the… You know, from a business perspective, I'm most interested these days about, all right, how do I take and use AI to make it repeatable, right?
00:21:54.097 --> 00:22:04.847
A- and in the case of, um, know, what we were just talking about, you know, the, the first step would be, all right, like, what metrics do I care about, right?
00:22:04.847 --> 00:22:10.837
Can I get those metrics and then feed that back into the AI to like, all right, you know, what's the next step?
00:22:11.978 --> 00:22:20.718
Um, you know, so the example here would be, all right, we know revenue and we know cost of, of customer acquisition or CAC or whatever you wanna call it.
00:22:20.867 --> 00:22:25.548
Um, you know, give me a report, you know, each week.
00:22:25.647 --> 00:22:28.678
Are tho- are those numbers going up or down, right?
00:22:29.428 --> 00:22:35.417
then I'd like to trigger off of that and say, "All right, uh, costs are going up and revenue is going down.
00:22:35.428 --> 00:22:36.268
What do we do about it?
00:22:36.278 --> 00:22:37.327
Give me an analysis.
00:22:37.327 --> 00:22:38.827
Where are the gaps," right?
00:22:38.837 --> 00:22:39.718
"Fill in the holes.
00:22:39.718 --> 00:22:50.907
Give me a list of things that I can try this week to try to move the needle." And I think it's easy to talk about that, And it makes sense.
00:22:50.928 --> 00:22:54.577
It's very hard to implement that, um, at least with AI, right?
00:22:54.577 --> 00:23:04.928
You can do it manually the way we've always done it, and I think that's a skill that a lot of us, uh, including myself, fail to, uh, hone on a day-to-day basis.
00:23:05.127 --> 00:23:11.557
Um, curious, are-- what are you seeing… Uh, uh, we talked pre-show a little bit about your AI stack.
00:23:12.948 --> 00:23:18.288
You know, so maybe this is just a good segue into how you're feeling about AI and what you're using it for.
00:23:18.298 --> 00:23:22.887
You know, is that, uh, something that you would consider, um, or are you in a completely different mindset?
00:23:23.894 --> 00:23:32.404
Yeah, I, I think pretty deeply about… And, uh, I think there are a number of like, uh, talk submissions I've done.
00:23:32.404
--> 00:23:54.484
I'm actually gonna do one locally about everyone, not only, you know, SaaS owners or founders, but everyone in- with a technical background that is working with AI, they have to understand where the human perspective and the human experience is most important and where the AI can help and not to blur that boundary, you know?
00:23:54.617 --> 00:23:54.897
Sure
00:23:55.815 --> 00:24:09.694
one, one great example that I'll give as far as like, you know, using AI is, um I think one thing that we kind of talked about is like, hey, one of the moats is your customers, your prospects.
00:24:09.775 --> 00:24:17.755
You know, as long as you're serving them, as long as you're helping them, you know, your business will or, or be around for a long time.
00:24:18.194 --> 00:24:25.345
Um, so I try to get as, on as many customer calls as possible.
00:24:25.365 --> 00:24:34.015
I try to do all the support tickets, I try to do all the emails, because I, as the founder, have to understand where our prospects and customers are coming from.
00:24:34.055 --> 00:24:35.585
I have to understand that deeply.
00:24:35.934 --> 00:24:42.924
So, um, I will jump on call with anyone just to understand, like, where they're coming from.
00:24:44.234 --> 00:24:49.815
where the AI can start to take over is like, okay, I've, I've had, like, 20 Zoom conversations this week.
00:24:50.285 --> 00:24:53.765
Okay, now let me submit those 20 Zoom conversations to Claude.
00:24:53.825 --> 00:25:03.545
Let me put them in various projects of the three different buckets that I mentioned before, the agency bucket, the losing, like, click traffic bucket, and then the zero traffic bucket.
00:25:03.634 --> 00:25:04.105
Okay.
00:25:04.295 --> 00:25:11.674
Well, now that they've been put into this, these buckets, all right, now I can start having some conversations about, like,"Hey, what are the patterns that you see?
00:25:12.085 --> 00:25:23.884
What are, what are the things that we talked about in all of these, um, that are in these conversations?" Okay, well now, like, I have those conversations, and now I have another Claude window opened against our code base.
00:25:24.095 --> 00:25:25.785
Okay, what things are actually doing?
00:25:25.984 --> 00:25:28.424
Like, how are we serving these, these needs?
00:25:28.684 --> 00:25:34.765
And what, what pieces of content do we have published to actually answer these questions?
00:25:35.214 --> 00:25:46.934
And so at some point, you know, the AI starts to co- to take over, but then I come back into the place, and then I'm like, "Okay, well, well, I think that this feature is best for this user or for this use case.
00:25:46.964 --> 00:25:54.595
I think this article needs to exist for this user and needs to be explained in this way." I don't wanna just rely on it generating AI slop.
00:25:54.674 --> 00:26:01.865
I know intuitively human to human what is the best for you because I've listened to you and I've empathized with you.
00:26:02.325 --> 00:26:08.164
Um, and so that's kind of, you know, that's one example of, of how we use AI in our process.
00:26:09.039 --> 00:26:11.180
Yeah, I, I think I agree with you, right?
00:26:11.230 --> 00:26:13.400
There, there's gotta be sort of guardrails, right?
00:26:13.400 --> 00:26:14.700
So you avoid the slop.
00:26:14.930 --> 00:26:23.150
Um, but I think a lot about, you know, so that, that process that you described, right, totally makes sense all the way through.
00:26:25.009 --> 00:26:26.130
Is any of it automated?
00:26:27.549 --> 00:26:38.859
Right, so that, so that you don't have to, like, do the prompt to, like, aggregate the data, know, uh, y- y- you described three or four steps there, and I, I, I won't do it justice to try to repeat them back to you.
00:26:38.859 --> 00:26:40.819
People can rewind 30 seconds.
00:26:40.859 --> 00:26:44.519
But that's great, but it takes time, right?
00:26:44.519 --> 00:26:52.049
How much of that could you on autopilot to get you to the point where you need to, you know, then have your human, uh, intervention?
00:26:53.078 --> 00:26:53.509
Yeah.
00:26:53.509 --> 00:26:56.699
So, um, a number of things are automated in that.
00:26:56.699 --> 00:27:01.278
So I have skills for extra-extracting insights into those conversations.
00:27:01.568 --> 00:27:04.699
Those skills map the data into other files.
00:27:04.739 --> 00:27:08.078
Like, I think Brendan had mentioned like,"Hey, everything should be in Markdown." It…
00:27:08.281 --> 00:27:08.612
Sure
00:27:09.335 --> 00:27:09.674
Yep.
00:27:10.209 --> 00:27:13.088
and then, so that's capturing all the data there.
00:27:13.328 --> 00:27:34.128
Um, when I go to, like, building out the feature or writing the blog posts, um, I used to be very big into Claude and, like, living in Claude, but then I, I found that, you know, I would just kind of argue back and forth with Claude all day, and then I'd have to, like, open all these work trees, and it, it just didn't seem like an efficient process.
00:27:34.509 --> 00:27:41.818
Um, so, uh, I'm good friends with Jesse at Bento, and I've essentially copied his process.
00:27:41.848 --> 00:27:45.229
And what he does is he uses Cursor and cloud agents.
00:27:45.519 --> 00:28:01.088
So once he kind of figures out, like, you know, from the conversations or from the insights like, "Hey, this, this post needs to exist," or, "This, um, this feature needs to exist," then I go to Claude, or not Claude, I'm sorry.
00:28:01.098 --> 00:28:05.538
I go to Cursor and I say, even with this mic, I use Super Whisper and I talk into the conversation.
00:28:05.538 --> 00:28:07.909
I was like, "Hey, this thing needs to exist.
00:28:07.979 --> 00:28:09.388
It doesn't exist right now.
00:28:09.969 --> 00:28:17.239
Go spin it up in the cloud and then open up a PR for it." And then once the PR is open, that's when the human intervenes again
00:28:17.506 --> 00:28:17.855
Right
00:28:17.969 --> 00:28:20.679
out like,"Hey, is this
built in the way that I want it to be built?"
00:28:21.596 --> 00:28:23.276
A- and is that true for content too?
00:28:23.286 --> 00:28:27.855
Like you have it open a PR, or is there a different workflow for content creation?
00:28:27.915 --> 00:28:29.576
And, you know, I'm leading
00:28:30.871 --> 00:28:37.901
That, that's still-- I'm still honestly, you know, I've mentioned that we kind of are pivoting on, on content right now.
00:28:38.211 --> 00:28:48.701
Um, so lot of me is trying to kind of like find my voice as far as like how I want us to be represented and to be useful.
00:28:49.000 --> 00:28:53.141
Right now, the flow is, um, I'll just record a video.
00:28:53.221 --> 00:28:56.911
Like someone will ask a question, I'll record a Loom, I'll record a video.
00:28:57.441 --> 00:29:01.141
That video goes to Descript, that transcript goes to Claude.
00:29:02.101 --> 00:29:08.050
like says like, "Okay, do we need to add more point of views that you're trying to express to your point of views file?
00:29:08.381 --> 00:29:12.560
Um, okay, how do we refine this down to like a tweet?
00:29:12.871 --> 00:29:23.691
How do we refine this down to a LinkedIn post, to a newsletter, and to an article?" Um, we have some stuff in place that automates all that, um, but I think it could do a better job.
00:29:23.990 --> 00:29:33.871
And especially, uh, as far as like the handoff to the human side, because I think what we were doing is, we were pushing it a lot to buffer and publishing it in all those places.
00:29:34.171 --> 00:29:38.000
But what that really loses is the channel rules.
00:29:38.381 --> 00:29:38.810
Like,
00:29:39.061 --> 00:29:39.291
Hmm.
00:29:39.340 --> 00:29:49.570
we would just be pushing stuff to LinkedIn, and when we pushed to, to LinkedIn, we weren't considering LinkedIn's algorithm or like their standards as far as like how people should interact with a platform.
00:29:49.851 --> 00:29:56.201
I think LinkedIn has like a rule of, um, four posts max a week, and then we'll, we'll promote those posts.
00:29:56.201 --> 00:30:00.780
But those have to be well thought out, deep, you know, useful to the community posts.
00:30:01.111 --> 00:30:11.270
Or, you know, if you want to show up on Twitter, you know, you should actually participate and have conversations with people, and then as they respond to you, they, they need to… you need to be ready to respond.
00:30:11.540 --> 00:30:16.490
So, um, as far as publishing, you know, we're still, we're still trying to figure
00:30:16.519 --> 00:30:16.670
Yeah.
00:30:18.109 --> 00:30:21.480
All right, one, one last question then I'll cede the floor back to, to Brendan.
00:30:21.559 --> 00:30:28.839
Um, You, you talk about, you know, uh, you, you mentioned point of view file and other markdown files.
00:30:29.809 --> 00:30:33.369
How are you organizing that stuff right now, right?
00:30:33.369 --> 00:30:38.759
Is it, uh, do you have like a, a, a repo that is separate that you put all that stuff in?
00:30:38.759 --> 00:30:41.470
Are you putting it in your, your code base?
00:30:41.750 --> 00:30:43.700
Do you have some other system, right?
00:30:43.700 --> 00:30:50.230
Like, you, you're sort… Brendan and I talk a lot about building a second brain or a command center for the business, right?
00:30:50.240 --> 00:31:01.130
And you see people talking about like, "Oh, I put everything on Google Drive in this folder." Um, or, you know, a lot of people are like, "Oh, I have a, a skills repo, uh, on GitHub." How do you think about that?
00:31:01.160 --> 00:31:07.329
'Cause it's something that we're, I'm trying to figure out and I'm just collecting, you know, more and more insights of people who have tried things
00:31:08.146 --> 00:31:10.116
Uh, we put it all in our code base.
00:31:10.166 --> 00:31:26.126
And, and the reason why is because when we wanna publish a post, you know, we do have Claude skills and other skills that are just like, "Hey, know, I forgot to create updates for the last, you know, 10 or 15 features we released over the last couple weeks.
00:31:26.517 --> 00:31:37.997
Can you, can you just generate posts for this?" And Claude will look through the, the Git logs and everything like that, look through the code, and it'll, it'll come pretty close to, to releasing, like, a feature update for that.
00:31:38.446 --> 00:32:01.076
Um, the other reason is, uh, by doing that, it allows us to interact with, like, various MCPs, even our own MCP, and use the content of, um… Like for instance, with Noatoa, we, we, we, we give you the ability to choose, pick and choose the questions you wanna track, um, and we give you suggestions and build content for you.
00:32:01.426 --> 00:32:07.906
Um, if we want to weigh that against our code base, it's-- I'm getting very meta here.
00:32:08.237 --> 00:32:11.406
Um, "Hey, here's the suggested post.
00:32:12.326 --> 00:32:21.426
How does this stack against what exists inside the code base?" And so-- Or the content, like what content ex- already exists for this topic that's been suggested by Noatoa.
00:32:21.751 --> 00:32:22.122
Right
00:32:22.396 --> 00:32:29.737
we use that M-MCP in the same Claude session that has access to our code, and then it makes the, you know, it makes the post itself that much stronger
00:32:30.799 --> 00:32:33.859
That's a, a very interesting insight that I'm gonna write down.
00:32:33.869 --> 00:32:39.329
Th- this idea of weighing, you know, the suggestions against the code base or existing content.
00:32:39.829 --> 00:32:44.539
Th- that sort of feels like it needs to be in the list of things that you do regularly.
00:32:44.539 --> 00:32:46.240
So you for that one.
00:32:47.710 --> 00:32:48.660
all right, what else you got, Brendan?
00:32:48.660 --> 00:32:49.680
I've been talking long enough.
00:32:50.442 --> 00:32:50.972
No, it's all good.
00:32:50.982 --> 00:32:51.742
This has been great.
00:32:51.742 --> 00:33:03.032
I, I've actually really enjoyed having this tangent off
onto the, like, marketing and SEO and all these things that are very much related to what we're doing all the time, but not, you know, the AI coding of what, of it all.
00:33:03.462 --> 00:33:07.042
So now I'm gonna take a, a hard left turn and go right into AI coding of it all.
00:33:07.457 --> 00:33:08.416
Sure, sure, sure
00:33:08.873 --> 00:33:17.813
Uh, I, the biggest thing that, that jumped out from what you were just talking about, you know, you touched on using… g- getting out of Claude and getting into, uh, Cursor.
00:33:18.472 --> 00:33:26.363
And, and I think I understand what you were saying with, like, using the, the cloud agents and stuff, but I'd like you to just elaborate for my own benefit and, you know, the audience.
00:33:26.363 --> 00:33:33.093
Like, uh, what, what does that workflow look like in whether it's the marketing stuff or even just coding?
00:33:33.143 --> 00:33:35.063
Um, 'cause you guys are still using Rails, correct?
00:33:36.452 --> 00:33:43.063
Yeah, so, so what's… L- maybe let's just start with, let's go into the code side now and just talk about, like, a, a new feature.
00:33:43.063 --> 00:33:44.212
Like, what, what does it look like?
00:33:44.212 --> 00:33:48.752
What's your workflow look like using Cursor and Claud- eight- or, uh, cloud agents and stuff like that?
00:33:49.270 --> 00:33:49.820
Yeah.
00:33:50.161 --> 00:33:57.320
Okay, so, you know, a- as a founder of a small team, there's only so many hours that we have in a day.
00:33:57.480 --> 00:33:57.740
You know?
00:33:57.740 --> 00:34:00.310
And there are a thousand things that come up all the time.
00:34:00.421 --> 00:34:00.721
You know?
00:34:00.750 --> 00:34:05.730
And again, going back to the whole SaaS is dead thing, uh, that's why I'm a firm believer against that.
00:34:05.730 --> 00:34:10.521
There's just so much that we have to do in a given day to, like, keep this thing going.
00:34:10.920 --> 00:34:24.070
Um, so what that looks like now is whenever I get an email, whenever I get a, a support ticket, whenever I get an idea, what I do is I go open up Cursor.
00:34:24.150 --> 00:34:28.351
I literally go and I open up a new, um, cloud agent.
00:34:28.701 --> 00:34:40.920
I pull the microphone to me or I, I'm ready to type it, and I'm just like, "Hey, see if you can make this feature exist." And, and Cursor comes… There are a couple of plugins I think I use.
00:34:40.940 --> 00:34:43.340
I think I use something… What is this thing called?
00:34:43.340 --> 00:34:46.400
I'm a… I think it's called Thermos.
00:34:47.010 --> 00:34:47.300
Oh, wait.
00:34:48.331 --> 00:35:04.335
Uh, Ther- Uh, there, there's basically this thing that I use after I give it the description, what it does is it spins up multiple, um, agents, and they kinda can argue with each other about the code.
00:35:04.894 --> 00:35:05.315
Okay
00:35:05.695 --> 00:35:09.175
and I let that happen in the background.
00:35:09.275 --> 00:35:15.135
After I've done my dictation and submitted it, Cursor is, does no longer exist in my brain.
00:35:15.135 --> 00:35:17.235
I go back to doing all the other founder things.
00:35:17.590 --> 00:35:17.891
Yep
00:35:17.985 --> 00:35:32.574
then at some point, if it's the same day or if it's a couple days later just because we're so busy, um, what I'll do is I'll say like, "Okay, now it's time for me to do a PR review." And I go back in Cursor, I have skills for this.
00:35:32.614 --> 00:35:39.385
I say, "Okay," like, "look at all the open PRs." And that feature will be one of those open PRs.
00:35:39.695 --> 00:35:43.014
And at that point, it's time to start interrogating the feature.
00:35:43.135 --> 00:35:50.355
Tryin'- time to start kind of figuring out like, "Hey, does this actually work the way that I want?" Like, "Is this actually popping up in the place I want it to pop up?
00:35:50.355 --> 00:36:09.494
Is this actually the user experience so that I want the user to have?" Um, or like, "How does this code look?" Or, "What, what decisions did it make that, that I like or don't like?" Um, and then still within Cursor, you know, I'll do a number of like security checks or like, you know, code quality checks and stuff like that.
00:36:09.905 --> 00:36:16.795
And then I issue another skill that just, uh, merges it and then ships it to production.
00:36:17.195 --> 00:36:29.885
And then, at that point, if it was something that, um, a user requested or a support ticket came in for, then you know, I, I send off like the,"Hey, we, we built this thing for you.
00:36:30.235 --> 00:36:33.275
Thanks for, you know, rec- recommending it," or, "Thanks for reporting it."
00:36:33.847 --> 00:36:34.237
Yeah
00:36:34.565 --> 00:36:35.704
so that's the typical workflow.
00:36:36.135 --> 00:36:36.655
Some of them
00:36:36.670 --> 00:36:37.061
Got it.
00:36:37.125 --> 00:36:38.445
like pretty complicated.
00:36:38.465 --> 00:36:41.184
You know, I've kind of been pushing the envelope with it.
00:36:41.605 --> 00:36:42.045
You know, I
00:36:42.047 --> 00:36:42.456
Okay
00:36:42.764 --> 00:36:43.454
pushed the envelope.
00:36:43.474 --> 00:36:46.215
Like there's a pretty big architecture change that I want to do.
00:36:46.614 --> 00:36:50.994
Um, and I know everyone's been talking about Fable and throwing like huge things at Fable.
00:36:51.375 --> 00:36:54.204
Um, this has just worked for me.
00:36:54.344 --> 00:36:59.335
Like I don't want to live in the conversation, you know, for my entire day.
00:36:59.385 --> 00:37:01.144
I got other things to do, you know?
00:37:01.144 --> 00:37:05.155
So I just want to live in these conversations needed.
00:37:06.070 --> 00:37:06.481
Yeah.
00:37:06.670 --> 00:37:22.371
I mean, that's definitely interesting to me because, I mean, my role is not a founder, but, you know, as a manager and having all the different things coming at me, whether it's s- people on the support team, people on my team wanting code review, you know, my CEO looking for things.
00:37:22.641 -->
00:37:26.130
Like, I've- can never really just focus down on code.
00:37:26.141 --> 00:37:29.780
Now, I, I will write code similarly to what you just talked about.
00:37:30.271 --> 00:37:34.411
Now, Ryan and I, we had John Nunemaker on earlier this year.
00:37:34.411 --> 00:37:41.951
He put us… Well, I've been using Conductor less and less, but the workflow you just described is sort of like what Conductor does.
00:37:41.951 --> 00:37:50.561
It's like you get your own little work tree, and you kinda, I kinda kick it off and let it kinda run, and then I'll come back, and it, it does reviews, all those kinds of things.
00:37:50.721 --> 00:37:57.510
And they're basically all skills, but of course, because Conductor's its own harness, you just like click a button rather than using a skill.
00:37:57.900 --> 00:37:59.990
But that, that does sound pretty similar.
00:38:00.880 --> 00:38:03.331
Um, but yeah, I, I think… Go ahead
00:38:03.541 --> 00:38:08.822
I was gonna say, I mean, uh, to, to me, Conductor is slightly different, right?
00:38:08.831 --> 00:38:21.382
That the problem it solves is that, you h- you know, how many of those concurrent conversations can I have in my local development environment without clobbering, you know, the
00:38:21.527 --> 00:38:21.927
Yeah
00:38:22.061 --> 00:38:23.032
in process, right?
00:38:24.231 --> 00:38:27.481
You know, you solve that, it sounds like, by just doing everything in the cloud, right?
00:38:27.481 --> 00:38:34.422
Cloud spins up its own, you know, environment, everything is isolated, at least to the point where it goes to a PR, right?
00:38:34.431 --> 00:38:36.882
And then you have to merge it back in, right?
00:38:36.882 --> 00:38:49.811
Conductor, which I, I just came back to this week, Brendan, because I'm hitting this problem again, is like, all right, now that I've got a workflow for me that is working with, all right, ask a question, build the architecture.
00:38:49.811 --> 00:38:53.931
I have it save it as a MD file, uh, in the code base, right?
00:38:53.931 --> 00:39:04.902
'Cause sometimes I'm just planning, and sometimes I, I just need to remember for later, but I'm not actually gonna do anything with it, and sometimes I'm like, all right, I just need the plan for AI to follow, um, that, you know, that I've approved.
00:39:05.592 --> 00:39:12.342
What happens is I, I… once I start going through that implementation plan, right, I want it to verify, right?
00:39:12.342 --> 00:39:19.862
So I want it to run the test suite, and I want it to, you know, open up, you know, Playwright or Selenium or, you know, whatever, and actually click through the UI.
00:39:20.481 --> 00:39:24.882
And I quickly realize all of a sudden that I can only do one conversation at a time that way, right?
00:39:24.882 --> 00:39:30.282
Because otherwise the second one says, oh, the test, you know, the d- the test database is already in use.
00:39:30.311 --> 00:39:34.061
Like, and then it, it goes down this tangent of like, oh, let me try to spin up Docker.
00:39:34.061 --> 00:39:38.481
I'm like, no, no, no, no, no, just wait until the, the port is open or use a different port, right?
00:39:38.481 --> 00:39:40.842
Like, it's not that hard, right?
00:39:40.842 --> 00:39:49.581
But Conductor solves those problems in my mind, uh, uh, you know, for anyone… That's more for anyone listening than it was a question, but if… Go ahead.
00:39:49.592 --> 00:39:51.371
It sounds like you got something you wanna say
00:39:51.512 --> 00:39:58.632
I, I, we never used Conductor, but I think we built something similar and, and it was this whole idea behind work trees
00:39:58.903 --> 00:39:59.193
Right
00:39:59.342 --> 00:39:59.713
like that.
00:39:59.853 --> 00:40:02.862
You know, prior to this, I had never, ever used a Git work tree, you know?
00:40:02.862 --> 00:40:03.032
The--
00:40:03.382 --> 00:40:03.882
Same here.
00:40:03.952 --> 00:40:04.143
Yeah.
00:40:04.784 --> 00:40:04.914
Yeah.
00:40:04.914 --> 00:40:06.773
I, I had no idea what it was until a couple months ago
00:40:06.842 --> 00:40:28.492
e- even when my co-founder had like brought it up, I was like, "I don't, I don't ever wanna use that." And, um, we went down the rabbit hole of like pushing the envelope with it to the point where I think we were like generating screenshots and, and using those screenshots to test, um, like click, doing like click tests
00:40:28.592 --> 00:40:28.601
Mm-hmm.
00:40:28.813 --> 00:40:32.032
the screenshots, and it just got too cumbersome.
00:40:32.822 --> 00:40:42.152
then even, even with that, the pattern that I was noticing is that like a small feature would become an, an, an epic.
00:40:42.512 --> 00:40:42.932
You know?
00:40:42.932 --> 00:40:47.503
Like if you're living in the conversation and you're just having the conversation, then you're just like,"Oh, I need to add this other thing.
00:40:47.543 --> 00:40:48.552
I need to add this other thing.
00:40:48.592 --> 00:40:51.632
I need to add this other thing." And then nothing ever ships.
00:40:52.083 --> 00:40:55.992
And so, or it just becomes too big to ship.
00:40:56.302 --> 00:41:03.023
And so, we still use those same principles with this Cursor workflow that I'm describing.
00:41:03.313 --> 00:41:07.612
You know, now I'm not living in that conversation anymore.
00:41:07.702 --> 00:41:15.172
Now I, I'm, I'm living in, know, a proposal mode, or I'm living in review mode.
00:41:15.422 --> 00:41:29.083
And then when I'm in review mode, you know, then it says like, "Okay, I wanna test this out," and it says, "Okay, well, we'll use the work tree, work tree stuff that you had set up and all that stuff." So I think Conductor kind of fits into this workflow that I'm describing.
00:41:29.382 --> 00:41:31.003
I've just never personally used it.
00:41:31.072 --> 00:41:31.922
But, um,
00:41:31.974 --> 00:41:51.884
Yeah, I guess… Yeah, I think my point was more like I, I look at Conductor as a harness more so than, you know… And, and that
harness is exactly what you just described, which is, you know, use work trees and then has some setup scripts to get around, you know, the, the shared database problem, right?
00:41:51.914 --> 00:41:56.273
But it just, it abstracts all that away and gives you a nice UI to try to track the conversation.
00:41:56.273 --> 00:42:00.103
But if you're not in the conversation, to your point, less value.
00:42:00.114 --> 00:42:07.353
You don't need, necessarily need Conductor, unless I'm missing something, uh, to do the, the end-to-end workflow.
00:42:07.403 --> 00:42:08.213
It just does give
00:42:08.413 --> 00:42:08.822
No
00:42:08.923 --> 00:42:10.634
UI to see where you're at.
00:42:10.697 --> 00:42:11.097
Hmm
00:42:12.023 --> 00:42:14.204
but yeah, interesting.
00:42:14.224 --> 00:42:17.893
Like I, I don't necessarily want to be in the conversation.
00:42:18.813 --> 00:42:31.224
You know, once I have a plan that I've sort of stamped, um, I find that it, it, Claude still gets caught asking questions even though I'd say, "Go build the thing," right?
00:42:31.224 --> 00:42:39.373
So it's like I'll say go, and I'll come back, you know, two hours later and it hasn't even started 'cause it was like, "What do you want me to do here?" I'm like, "You have the plan, just do it.
00:42:39.403 --> 00:42:40.543
Like we've already done this.
00:42:40.574 --> 00:42:41.344
Why are you asking?
00:42:41.353 --> 00:42:45.873
Like continue, please." And I've wasted, you know, two hours of wall time
00:42:46.920 --> 00:43:01.391
and, and that's, you know, a lot of people are big about, like, living in the conversations and using these tools to ship content for people and stuff like that.
00:43:01.791 --> 00:43:05.681
But a lot of these conversations just, like, really frustrate me.
00:43:05.760 --> 00:43:06.121
You know?
00:43:06.121 --> 00:43:06.411
Like,
00:43:07.030 --> 00:43:07.460
Yeah
00:43:07.590 --> 00:43:14.231
uh, I'll, I'll, I'll be talking to Claude about, like, a, um, "Hey," you know,"we just ran this service contract.
00:43:14.291 --> 00:43:16.041
I need to send, send the invoice.
00:43:16.351 --> 00:43:20.610
You know, I just want you to, like, double-check, like, what I wrote here.
00:43:20.630 --> 00:43:30.940
You know, just give me a, a thing." And then Claude will say stuff like, "Oh, this is where people always get it wrong." Or they'll, like, they'll introduce all these, like, random quips, and I'm like: Wait, do people really get this wrong?
00:43:31.251 --> 00:43:32.851
Do… Are people actually doing this?
00:43:32.851 --> 00:43:33.811
Like, how do you know this?
00:43:33.840 --> 00:43:36.760
And it's just like, Why are you just making up all this other fluff for me?
00:43:36.760 --> 00:43:37.771
I don't wanna see all that.
00:43:37.791 --> 00:43:42.371
I just wanna get the job done, ship the thing, and move on to the next thing.
00:43:42.721 --> 00:43:47.201
Um, so, um, just my personal philosophy.
00:43:47.201 --> 00:43:52.311
I mean, the AIs, like, help enhance the stuff that I'm trying to do, but I'm not trying to live in them all the time.
00:43:52.311 --> 00:43:56.380
I got, I got li- a lot more interesting things that I wanna do outside of all this
00:43:56.592 --> 00:44:03.692
To, to clarify, just'cause you just gave an example of using it to like, you know, spot check copy for an invoice it sounded like, right?
00:44:03.692 --> 00:44:04.512
Which I totally get.
00:44:04.512 --> 00:44:06.132
I wouldn't wanna live in that conversation either.
00:44:06.132 --> 00:44:08.052
I'm just looking for a quick gut check, right?
00:44:08.052 --> 00:44:14.952
But that is a very different, um, sort of use case than building a big feature, right?
00:44:14.981 --> 00:44:22.681
Um, so I'm cur- like do you, you don't like to live in either conversation or just like the conversations where you don't feel like you have anything to add?
00:44:23.487 --> 00:44:27.547
No, uh, I, just want to get them done as quickly as
00:44:27.905 --> 00:44:28.215
Right.
00:44:28.365 --> 00:44:29.306
Yeah, I mean, that makes sense
00:44:29.467 --> 00:44:30.067
yes.
00:44:30.077 --> 00:44:39.327
You know, um, it-- The, the living in the conversation and, and, and adding more and more features, that was me, like, maybe four or five months ago.
00:44:39.577 --> 00:44:41.907
Like, uh, you know, I just kept on getting stuck.
00:44:41.907 --> 00:44:45.896
I kept on just adding more stuff, and that's just, that's not useful.
00:44:46.384 --> 00:44:50.094
So what you're telling me is, you know, basic engineering principles still apply.
00:44:50.304 --> 00:44:50.704
You know, small
00:44:50.722 --> 00:44:51.422
100%.
00:44:51.434 --> 00:44:52.074
often, right?
00:44:52.074 --> 00:44:52.534
Okay, cool.
00:44:52.623 --> 00:44:53.793
100%, yeah.
00:44:53.842 --> 00:44:54.693
100%,
00:44:54.833 --> 00:44:55.173
Yeah.
00:44:55.554 --> 00:44:59.103
No, I, I mean, I, I find myself in that trap often.
00:44:59.284 --> 00:45:07.744
Um, you know, both, you know, feature bloat, right, and getting too big to ship, uh, which is something I'm personally, you know, cognizant of and trying to work on.
00:45:08.724 --> 00:45:24.213
You know, at the same time, there's this… I think this is a human problem, not a, a machine problem, that it's like you want to-- You have this reaction where you, i- if the AI is gonna go off the rails, uh, no pun intended, um, you wanna catch it early and correct it early.
00:45:24.364 --> 00:45:31.023
But the truth is, I think that, you know, or at least I'm finding, is that throwing away the code is easier right at the end.
00:45:31.023 --> 00:45:32.094
It takes a lot less time.
00:45:32.094 --> 00:45:34.943
So just let it do what it's gonna do, and then correct it at the end.
00:45:34.943 --> 00:45:37.853
And if that means you throw away half the code, so be it, right?
00:45:37.873 --> 00:45:39.213
'Cause, like, you didn't write it.
00:45:39.623 --> 00:45:41.434
No blood, sweat, and tears there, right?
00:45:41.434 --> 00:45:49.114
Like, but that is just so anti how we think, I think, as people, it's hard to let go.
00:45:49.114 --> 00:45:50.034
So, you
00:45:50.231 --> 00:45:59.380
Yeah, and it's funny you say that though because just yesterday I was working on like a little side project that I started, I don't know, s- three, four months ago, something like that.
00:45:59.920 --> 00:46:03.181
And I actually decided to take Fable and say, "Hey, take a look at this.
00:46:03.181 --> 00:46:05.150
This feels like it's going on way too long.
00:46:05.210 --> 00:46:13.190
It should be done." And it looked at like, "Hey, you've already invested this much time in coding." And I went back to it, I'm like, "No, you did this.
00:46:14.481 --> 00:46:15.440
I, I don't really care.
00:46:15.440 --> 00:46:17.371
Let's just throw it away." And it's like, "Oh yeah, good point."
00:46:17.371 --> 00:46:17.748
just had this conversation with, with my business partner earlier
00:46:17.760 --> 00:46:19.251
So it even thinks that way.
00:46:21.675 --> 00:46:25.726
estimates and I'm like, half the time it says, "Oh, this is like a three to four-day feature." I'm
00:46:25.943 --> 00:46:26.362
Yes.
00:46:26.443 --> 00:46:26.943
Yeah.
00:46:27.306 --> 00:46:29.056
10 minutes, so I
00:46:29.072 --> 00:46:29.132
Right
00:46:29.195 --> 00:46:35.286
know where you got that." And then on the, on the flip side, it comes back and says, "Oh, this can be done in seven to eight days." I'm like, "You're full of crap," right?
00:46:35.286 --> 00:46:35.646
Like,
00:46:36.150 --> 00:46:36.501
Yeah
00:46:36.695 --> 00:46:39.536
you know, normally this would be a six-month to a year feature.
00:46:39.536 --> 00:46:40.735
You're not doing it in three days.
00:46:40.735 --> 00:46:44.235
Like I, AI is good, but you're not like that good, right?
00:46:44.295 --> 00:46:44.755
Um,
00:46:44.777 --> 00:46:45.217
Mm-hmm.
00:46:45.577 --> 00:46:45.976
Yeah
00:46:46.210 --> 00:46:48.650
and those kind of things are infuriating to me.
00:46:48.688 --> 00:46:49.068
Yeah.
00:46:49.380 --> 00:47:06.521
uh, we, we know like one of the… I know one of the CTOs that just started working with Amazon and, know, in the last six months and, and one of the things that she was doing is like she was looking at big and seeing like how AI has actually really impacted their productivity.
00:47:06.831 --> 00:47:09.891
You know, like what, what it has, has it actually done?
00:47:09.951 --> 00:47:12.920
You know, have people been able to ship more PRs and stuff like that?
00:47:13.331 --> 00:47:23.231
And, and the truth is yes, on some levels, like yes, more PRs are getting out there, but now it creates this, this other bottleneck where someone has to approve all these PRs and stuff like that.
00:47:23.731 --> 00:47:32.460
It… Yes, it's increased or it's decreased the time to PR, which is like a, a success metric for, for engineers at a lot of, at a lot of cor- corporations.
00:47:32.923 --> 00:47:34.324
Speaking of metrics you wanna throw away
00:47:34.630 --> 00:47:34.851
yeah.
00:47:35.800 --> 00:47:42.233
but, um A lot of these problems are still human problems,
00:47:42.775 --> 00:47:43.324
Yes
00:47:43.353 --> 00:47:50.083
And a lot of us are, have become like overly reliant on the AI to argue back with it.
00:47:50.152 --> 00:47:56.072
And so you have to really like be super critical of the things that are coming back, you know?
00:47:56.072 --> 00:48:04.693
Like you have to be ready to argue with it about the stuff like, "Hey, why'd you tell me that this is gonna take like 10 days when you can do it in five minutes?" And stuff like that, you know?
00:48:05.092 --> 00:48:05.402
Like,
00:48:05.648 --> 00:48:07.657
I don't even bother arguing with that.
00:48:07.657 --> 00:48:08.038
I just, "Just go.
00:48:08.197 --> 00:48:09.418
It'll be done." Right?
00:48:09.443 --> 00:48:09.722
go.
00:48:09.753 --> 00:48:09.992
Like,
00:48:10.088 --> 00:48:23.757
I think you gotta, you gotta pick your battles of, like, where y- you mentioned earlier, like, where can a human provide, like, the intuitive value that an AI is gonna miss, And that, that's where I'll focus my argument time, right?
00:48:23.757 --> 00:48:30.568
And that's usually at the bigger… Not always, but usually at the bigger architectural level of des- system design, right?
00:48:30.568 --> 00:48:35.648
'Cause, like, it-- AI is very good at building a feature in isolation, especially if it's greenfield.
00:48:36.427 --> 00:48:44.128
But if it's part of an existing application that needs to interact with the other parts of the app, it tends to miss those, at least in my experience.
00:48:44.157 --> 00:48:52.608
And that could just be a prompt problem, but, um, I feel like that's where I can add value, you know, in the conversation or at least in the planning phase.
00:48:52.668 --> 00:48:54.538
Um, yeah.
00:48:54.547 --> 00:48:55.967
You know, statement, not a question.
00:48:56.369 --> 00:49:02.498
No, and you know, it-- This comes in, back into the marketing side.
00:49:03.318 --> 00:49:09.898
By design, the future of all these AIs is they want to keep you in the conversation as long as possible.
00:49:10.039 --> 00:49:11.938
They do not want you to leave the platform.
00:49:12.309 --> 00:49:22.278
They-- Google wants you in AI mode, ChatGPT wants you in, in that chat, Claude wants you in its chat, and it, it just wants to continue to provide you value and provide you with that loop.
00:49:22.728 --> 00:49:29.739
And what is, like a lot of people are starting to notice is this is just exhausting.
00:49:29.958 --> 00:49:30.329
You know?
00:49:30.358 --> 00:49:30.778
Yeah
00:49:31.148 --> 00:49:37.679
back in the day when we were, when we were pairing all the time or pairing was a, a big thing in the, the, the software development side.
00:49:37.679 --> 00:49:47.079
Like, yeah, it's cool to have two people on a project and pair and, like, you have a second pair of eyes, but that is just an
exhausting endeavor to, like, pair and look at code all the time.
00:49:47.079 --> 00:49:59.268
And now, now we are in, like, five pairing sessions at the same time while trying to juggle our other work and then, like, you know, trying to just push it more and more and more and like, "Hey, how can we make this thing do stuff overnight?
00:49:59.289 --> 00:50:00.748
How can I just burn more tokens?
00:50:00.748 --> 00:50:03.378
Oh, I need to get to my Fable limit," or whatever else.
00:50:03.778 --> 00:50:06.338
And what's the point of that?
00:50:06.548 --> 00:50:06.989
You know?
00:50:06.989 --> 00:50:07.289
Like, the
00:50:07.574 --> 00:50:07.835
Yeah
00:50:07.969 --> 00:50:23.668
the, the, the point should be in all of this is like,"Hey, how can I make the most use of this, this tool so I can go out and live my life the way I wanna live my life?" And, um, I think that's kind of lost on a lot of people right now.
00:50:24.403 --> 00:50:32.164
ironic that the companies, the AI companies actually wanna keep you in the loop considering how much it costs for them to keep you in the loop.
00:50:32.224 --> 00:50:36.043
You think they'd optimize for, you know, outcome and efficiency.
00:50:36.994 --> 00:50:40.864
Um, but not my problem to solve.
00:50:43.722 --> 00:50:44.132
Yeah.
00:50:44.413 --> 00:50:46.003
I mean, this has definitely been interesting.
00:50:46.032 --> 00:50:51.813
Um, I know we're getting close to time where we might wanna wrap up just, uh, to respect your time here, Ryan.
00:50:51.813 --> 00:51:01.302
But, um, is there anything else, like, around the, the coding side of things or even just, you know, Noatoa business stuff that you wanna talk about before we do start wrapping up?
00:51:01.793 --> 00:51:02.143
Hmm.
00:51:02.833 --> 00:51:03.782
trying to think.
00:51:03.992 --> 00:51:17.213
Uh, no, uh, you know, I think, um, I guess one thing I think, and I've already touched this, is there's gonna be, there's gonna be a bounce back from all this, right?
00:51:17.242 --> 00:51:37.063
You know, a lot of agencies, uh, especially, uh, in the marketing side, and this is just gonna come back just to like all of our working experiences side, is like everyone has become over-reliant and like so AI, know, optimize that I think the counter is gonna happen.
00:51:37.253 --> 00:51:41.043
You know, everyone's saying like,"Oh, SaaS is dead," that everyone's relaun- launching products.
00:51:41.043 --> 00:52:04.353
But now you're gonna see like a lot of these product, products that exist and they're like, "Hey, we actually need an experience engineer scale things, who can figure out like what platforms we need to push our data to, how to take, you know, some of this data that we're just pushing to SQLite or SQL or whatever else and push it to Redis and like that." You know, the, the human experience still matters in all this.
00:52:04.393 --> 00:52:26.742
And, you know, that's what I would encourage everyone to think about instead of like, "Hey, doom and gloom, AI's gonna take my job or AI's gonna kill my SaaS," is to think about like,"Hey, what have we actually done on the human side that the AIs can't do?" Like, let's give ourselves some credit and, you know, let's like double down on that and, um, you know, be hopeful.
00:52:27.762 --> 00:52:28.072
So
00:52:29.452 --> 00:52:30.233
That's a good message.
00:52:30.242 --> 00:52:30.552
Yeah.
00:52:30.592 --> 00:52:32.722
That's a good place to, to wrap up too.
00:52:32.853 --> 00:52:36.333
Um, where do you wanna point people to before we sign off?
00:52:36.833 --> 00:52:37.193
Sure.
00:52:37.262 --> 00:52:40.972
Uh, people can find us at knowatoa.com.
00:52:40.972 --> 00:52:45.512
That's know, K-N-O-W-A-T-O-A.com.
00:52:45.922 --> 00:52:50.112
Um, the, the landing page is still being updated, you know.
00:52:50.143 --> 00:52:52.742
Um, some of our tooling is still being updated.
00:52:52.983 --> 00:52:57.663
Uh, I'm start- gonna start, uh, being more and more present on Twitter.
00:52:57.932 --> 00:52:59.143
I know people call it X now.
00:52:59.143 --> 00:53:00.842
I still call it Twitter because I was
00:53:01.208 --> 00:53:01.699
Same here
00:53:01.742 --> 00:53:04.333
the, the, the fail cl- the fail whale and all that stuff.
00:53:04.762 --> 00:53:08.242
Um, but yeah, you know, I'm gonna start posting videos.
00:53:08.242 --> 00:53:21.262
I think I'm about to do like a, a 30-day, like, publishing content challenge, you know, just to kind of share like what we're doing the AI visibility company to kind of like promote our brand and stuff like that.
00:53:21.362 --> 00:53:21.753
So
00:53:22.132 --> 00:53:22.532
Awesome.
00:53:23.032 --> 00:53:23.282
there.
00:53:24.063 --> 00:53:24.432
Cool.
00:53:24.943 --> 00:53:25.833
Well, thanks for joining us.
00:53:25.853 --> 00:53:26.693
It's been great having you again
00:53:27.172 --> 00:53:27.422
Yeah.
00:53:27.963 --> 00:53:28.523
Thanks, guys.