From Zero to Draft: My Real AI Content Creation Process

Hey everyone, my name's Jason. Today

we're going to do something different.

We're going to build some stuff in public. Usually for stuff we do for

public. Usually for stuff we do for clients, it's all super engineered. It's

like, you know, stuff we've prototyped and then thought through extensively.

Um, but today all I want to do is show kind of the things we do at the very beginning when we're not fully sure what to even do. We're just exploring what's possible to give you, I guess, a little

sneak peek into how we work, maybe a little bit of how we use off-the-shelf AI tools. I think one thing you'll

AI tools. I think one thing you'll probably be surprised by is like we're not using anything fancy, especially um at the very beginning. To go from zero

to 70%, really, you can get there using, you know, tools you're paying like 10 bucks a month for. um to go from 70 to 100 and then to do that repeatedly at

high scale, that's when you start needing, you know, the more fancy workflows and some of the engineering um that we have kind of a a big team here at Growth X for. So, I was trying to

look for a topic that was like kind of easy to understand, but then uh there's there's a big gap from doing it at a really surface level to doing it really

really well. There's a Marcel looks like

really well. There's a Marcel looks like you want to come in.

>> Oh, okay.

>> We'll leave this in there.

>> Yeah. So, something where like you know the difference between like really really kind of bare bones and really really great is like wide and we can show you know exactly why like the the

purpose of using AI like how uh it can help kind of improve the quality of content and it's not just something where you tell it to write something.

Um, and it and it writes it. I'm doing

this for more of like a kind of audience of builders. You know, I'm assuming

of builders. You know, I'm assuming you're working somewhere or building something where, you know, you have users and most likely it's software, though it doesn't have to be. And in

that realm, I think one of the things we're all aware of whether we're doing it for ourselves or like for our product is kind of connecting things together.

And in this case, I've taken the example of two tools I think like plenty of people use of Calendarly and Slack. Um,

and writing a guide uh from the shoes of, you know, I'm pretending I'm I'm Calendarly uh to help my users. A lot of them use my product. They want to connect it to Slack for a variety of

reasons. Um, I want to write something

reasons. Um, I want to write something to help them. And this is like, you know, something that could be like we could publish like hundreds of these, right? There's a million things Cali can

right? There's a million things Cali can connect to. That's what we're going to

connect to. That's what we're going to try to do. So, um, you know, rough goals of today, kind of show how to use AI to create something like this. Um, I've

never done a guide like this before. So,

I'm literally just going to kind of work here and see what we can, uh, get done.

And then, um, as I'm building it, um, you know, I'm going to hopefully get into some of the nuances that we kind of are aware of for the other content that we produce. Um, to, uh, just show you,

we produce. Um, to, uh, just show you, you know, what to watch out for and how to like think about using these tools.

You know, the first thing I did was just like poke around a little bit to see what's out there. Um, again, if you've been in the software space, you've looked at these integration uh guides.

Probably companies like Zapier have uh, you know, really really kind of saturated the space of that sort of content with um, honestly, you know, pages that are are very informative and

very useful, but um, for the most part very formulaic. Let's just look at a few

very formulaic. Let's just look at a few of these here, right? Like I think ju just to showcase like you know there is a difference between kind of kind of thin to like really detailed and

inherently useful. Um I guess that's

inherently useful. Um I guess that's kind of my my uh goal here. So like on the you know more thin side and this isn't meant to be a critique you know like a lot of these products like make for example have thousands of these

pages and it's like reasonable. Not

everyone is uh written kind of in a lot of detail you know for the most part like when you read this it's it's useful. Um, but it's like very

useful. Um, but it's like very formulaic, right? Like I'm looking at

formulaic, right? Like I'm looking at kind of a bucket of triggers and actions I can use. Um, you know, I I can see how

this is kind of assembled um with uh, you know, their databases of all these like actions to be uh, programmatically generated. When I look at the FAQ,

generated. When I look at the FAQ, there's nothing really special about like Countly or Slack. It kind of just I imagine they have these on every single

page they have. Uh same with this stuff, right? Like it's, you know, again, it's

right? Like it's, you know, again, it's it's not a bad kind of front door, but doesn't really say a ton stuff with like a little bit of detail. Um you know,

this one there's not a ton, but you can see at least they've created this is actually kind of interesting. They've

created a kind of onboarding slideshow almost um interactive demo. I guess that's what story link does actually maybe. Anyway,

but they have some detail, right? Like

at least, you know, this is specifically about Calendarly and Slack, so that one's interesting. You get even better.

one's interesting. You get even better.

I mean, this is written by Calendarly already. I imagine if I followed this, I

already. I imagine if I followed this, I would actually accomplish what I'm trying to do. Um, there's like specific knowledge about the product. There's

links to things that are useful if I want to go deeper. Um, yeah. So, this is getting like really useful, right? like

where I imagine if I can write this for you know hundreds of products I'm really helping out um my users but you know some of the things I think could be

better here is like um you know maybe I can get a little bit into the background knowledge maybe for an audience that's a little bit not technical. Um, I guess if I'm Cali, this help center article

really is meant to just install the Slack app. But, you know, if I'm trying

Slack app. But, you know, if I'm trying to think about how it helps somebody in general, I would think about like what could I do on adding Slack, like what problems am I solving? What use cases

can you share with me to like make my life better, you know, depending on who I am. This is good. And then create. Um,

I am. This is good. And then create. Um,

honestly I couldn't find too many for Calendarly, but uh, you know, I have an example here from Web Flow where this is a Web Flow uh, Stripe integration

article, and you can see how um, you know, it goes a lot more in depth. It

kind of talks about why you would want to do something. There's a lot of options here from kind of more for non-technical people to, you know, stuff where you got to use a little bit of

code, but they're kind of linking and bringing some relevant context to kind of where you can go to learn more. Um,

you know, it's telling you ways you can build and some of the things you can build like subscription billing, uh, you know, syncing payment data, even talking

about different kind of use cases like membership sites.

The FAQ here, you know, you can contrast this to um, the initial one with uh, Calendarly and Slack from Make this is actually about, you know, Stripe and Web

Flow. So, I think this one's pretty

Flow. So, I think this one's pretty good. Yeah. So, I mean, there's a wide

good. Yeah. So, I mean, there's a wide range here. I think what I'm going to

range here. I think what I'm going to try to do is aim for, you know, grape. I

don't know if I can do that in a short period of time, but um I will try. And

uh so, you know, I'm going to think a little bit about how to do that. A lot

of times what I see is, you know, somebody might just kind of prompt something one shot. So like let's say I was trying to do that maybe just to learn about the topic like how can I integrate

Calendarly with Slack.

Uh I'm a marketer so not that technical but want to know

what's possible. So,

what's possible. So, uh yeah in case I can pull in my company's engineers.

So, we can let that run. And honestly,

let's let's try this with a multiple.

This one, we can do research with the big boy model.

We can even do perplexity and let's just see what it comes up with because I mean going back to what we're trying to do here, we're trying to write a um piece of content from the

perspective of Calendarly to help their users, right? So um a lot of what we

users, right? So um a lot of what we need to assemble here at the beginning is the raw materials to write something.

A lot of times depending on what is being used for the raw materials I think the output you know won't be as nice. Like if you're using kind of really thin pages from

some of the integration companies that we saw you know to write a comprehensive guide you can imagine how there's just not enough there to come up with something useful. Whereas you know if

something useful. Whereas you know if you dug deep um that's when you can actually make uh something helpful. So

just looking at this perplexity answer um we can see there's different options there's like a slack app there's let's see shortcuts I guess when you integrate

Slack app um they have step-by-step instructions again this is all to kind of just like install the Slack app and and you can

see kind of you know if you're writing purely um without steering the AI like most of what it's going to pull in is

the stuff that historically is like ranked really well on Google. Um like in this case I don't just want instructions for installing the Slack app. Like I

want to understand, you know, like what I can do here. I want to understand what the other options are. You know, if uh maybe I'm a bit technical or if I want to kind of go a little deeper and build

something a little bit more complicated.

But you can see how kind of the the entire answer here is being driven by I mean what I assume is you know ranked very high when you search for hey how do

I integrate Slack here. Um yeah and then it's like hey install the app or use zap your make. I think for the most part

your make. I think for the most part that's like kind of useful but a little bit surface level.

Um okay so this one is like eh it's okay. Um, let's look at the clawed one.

okay. Um, let's look at the clawed one.

We have this one's surprisingly short. Let's see

what is it saying. Natives me slack.

So, it's talking about the integration again. Um, this is interesting. So, now

again. Um, this is interesting. So, now

this is going a little bit deeper where it's giving you some options for other things you could do. So, Slack

uh bots more workflow automation to do things.

you know, they're multi-step or a little bit more complicated.

Um, and even analytics, which is pretty cool. Um, and this is like anchoring how

cool. Um, and this is like anchoring how I asked it. Uh, maybe I would ask my engineers. So, to even kind of prep me

engineers. So, to even kind of prep me to do that. So, this one's a little bit better, but I think, you know, one of the immediate things I realiz is I mean, I thought I clicked research. I don't

know why there's like no links here. Um,

so again, you know, if I'm thinking about the raw materials to write, this is like this could be better. Um, look

look at chat GPT, install the app, of course, uh, workflow builder or relay tool. This

is kind of helpful. So, it's like, you know, use the app kind of here, your low code solutions. I guess it's in the

code solutions. I guess it's in the order of complexity a little bit, right?

Citing some, you know, additional apps.

So, like how it's not just Zapier. Um, I

think Chachi PT honestly sometimes is pretty good at taking search results and filtering for the stuff that's a little

bit higher quality and useful. Yeah,

this one's pretty good. Honestly,

um, it might go a little bit too in depth for a marketer. Like I feel like if I was um that the raw information here is useful, but if I was writing this for that sort of audience, I would

more so just communicate the possibility and maybe a little bit of the architecture for how to do it, but not show them the code because, you know, again, as a marketer,

I feel like most of them would not know how to use this information. We have

some potential uh kind of use cases.

Okay, so this is really good. So, like

even right off the bat, I'm like leaning towards, hey, I'm going to use chat GPT to kind of source the information to write. Um, I'm just going to make a note

write. Um, I'm just going to make a note of that. So, I'm going to store the

of that. So, I'm going to store the research that this pulled because it's not half bad, honestly.

Um, one of the annoying things of these apps is I think in the desktop app when you copy this, it doesn't take any of the links.

And it looks like that is the case here as well. And I I want the links because,

as well. And I I want the links because, you know, if I'm writing a piece of content, I want to link to things that are helpful. Um,

are helpful. Um, if I can't grab that, I can't make a helpful article that's linked to the right places.

So, that also did not work. Let's see.

Okay. If I copy the element, this is going to be too much.

Oh man.

So the problem I'm running into is I want the text. If I was using the API, it would give it to me. But you know, for example, I want this specific link so that when I'm writing my article, I

can link directly to it. So let's say I'll do strip HTML uh lead text.

Let's see if this all these numbers. I

guess it's a is it giving me the link? It is not.

Uh let's see. Okay. Well,

what if uh extract text and links for citations?

Let's hope this doesn't blow up the context.

This link work. It does. Great. Okay.

Okay. So, we'll let that run. But

basically what I'm trying to do here is I'm trying to assemble research that I'm going to use when I'm going to start writing. Right? So, um so that's you

writing. Right? So, um so that's you know what I'm doing here is kind of breaking down the act of writing into its individual pieces and then I guess grabbing the context that I'll know I'll

need. And I know I don't have it here

need. And I know I don't have it here but I mean if we think about it like you know how do we want to write? So

what have we been doing so far? my plan

for writing. So the first step is planning the article. Um we haven't fully done that but we should do that.

Um next step is uh research the topic.

Um you know we want to prepare actually before all of this we want to prepare the artifacts and I'll get into that our

search topic and then we want to then we want to write. So, um, we've done some research. Uh, you know, we should do

research. Uh, you know, we should do some planning. I know I'm kind of like

some planning. I know I'm kind of like moving backwards. So, what am I actually

moving backwards. So, what am I actually trying to write here in the article? Um,

and honestly, I'm going to use chat GPT again because it's been behaving well today. Um, trying to write a integration

today. Um, trying to write a integration guide for um a marketing

audience on how to integrate Calendarly with Slack. What is a useful format to

with Slack. What is a useful format to structure the article benefits setup?

This is not bad. I you know I I think one thing I generally don't like about a lot of the SEO content is like there's just so much boilerplate. So shorter

bullets uh um focus on the main section giving

on integrating uh cally lesson on benefits some stuff use cases.

Cool. This one's not bad. I liked in the research how it got more complicated as it went. um for integration

it went. um for integration uh methods. um start of easy uh and you

uh methods. um start of easy uh and you know turnkey and get into low code and eventually um

and now that I think about it one thing that would be helpful is if we fed it the research here is some research on the topic see so you can start seeing it's already

kind of starting to take shape shape.

There's like different options.

Um, this isn't half bad. So, I'm going to copy this out. So, I mean, like one kind of learning, you know, from writing a

bunch of uh content in general is like breaking things up helps a lot. You

never want to kind of mash all these steps into one. Um because that's a recipe to have something that's one not

very good and two hard to kind of fix because you don't know where it's going wrong. Okay, so now we have the we have

wrong. Okay, so now we have the we have the writing plan. Um we're kind of working backwards here a little bit. But

one of the things that you'll most likely need, especially if you're writing for a company, is uh you're going to need some artifacts that help

shape the tone, kind of how you talk about your own product, and also um just the audience you're writing for. And to

be honest, you know, I I probably should have done these first to use it for research and also uh to shape the writing plan, but we can do that later.

So, um let's do the company brief. So

the actually earlier today we did a workshop where we went through um a lot of this. So I'll link that. But uh one

of this. So I'll link that. But uh one of the things in the workshop is we made a lot of nice prompt templates that you

can use to generate these artifacts. Um

so let's just use those. So company

context is a good one. Um, I mean, we can go through this a little bit, but basically what I want the output to be is

something that captures what my company does, what my product does, you know, what pains does it solve, kind of what the main hooks are and differentiators are. basically just a useful context

are. basically just a useful context where you know imagine if I'm writing this article here um maybe one of the readers is somebody who's like uh trying

to pick between Cali Cal you know some like HubSpot calendar um by seeing what the integrations are um so they're really like assessing you know how rich

maybe the ecosystem is of tools you can uh combine together and context about you know what makes Calendarly who Calendarly is for will help shape

the article that comes out. Depending on

uh how your company structured, a lot of this is things that the uh product marketing team might think about when creating this stuff. It's actually a great way to collaborate with different

teams at your company. So again, I'm going I'm just going to stick to chat GPT. Um

GPT. Um let's see, where do I change the company name?

Uh, okay. I don't need I don't need that.

okay. I don't need I don't need that.

Uh, okay. Write me a company profile for only.

Here are your instructions.

I like how narrative it's getting.

Um, another thing I guess that comes from experience like using a lot of these artifacts is you don't want them to be too long. This one actually I personally

too long. This one actually I personally don't like how it did not go out and research. So, it's probably using

research. So, it's probably using trained in uh knowledge. So, I'm going to change that.

Run it again. create a research report on Cali structure and we'll see I don't want to use deep research

because that'll take 10 minutes. I'll

just use search.

Um okay. So we'll let that run. It'll do

its thing. Um and we also want tone and style. Um, this one is a little bit

style. Um, this one is a little bit different where we're trying to match an existing piece of content. Um, so in

this case, you know, I don't know if I've never read a bunch of Cali stuff. I

don't know if I like it, but uh, we can just base it on that and see what it comes up with. But something you can do here and that we do all the time is like

we find content that we do like. It

doesn't even have to be a B2B software company's blog. It can be um your

company's blog. It can be um your favorite writer if that's how you want to write. It could be uh you know a

to write. It could be uh you know a blogger newsletter or whatever it is. Um

in this case we'll be a little boring and just use Calendarly.

And I'm going to try to find I mean as you can tell writes a lot of SEO stuff which doesn't have the best

tone. Let's see. How do I find something

tone. Let's see. How do I find something written by their founder?

All right, that's not bad. This is uh this is decent.

Feel like a lot of these would be better assistant prompts, but I know can't really do that in the app. So, uh do you understand?

Cool. And then to that for this style of your writing. Um, le a guide to match

your writing. Um, le a guide to match this.

And we'll just let that run. All right.

And then the last artifact is about the audience.

You know, when you're writing, you got to keep in your head who you're writing for and what their problems are. So, a

little bit self-explanatory. So for

context, it's really helpful to have that when you're writing uh content. So

let's see, what do we have here? Using

the format above now that I understand how to use these.

So here's the prompt. Um and I'll share all this. You know, I'm not spending a ton

this. You know, I'm not spending a ton of time reading these, but it's essentially just giving a framework for how you want the artifact to be.

Great. Um, the company is Cal Lake.

Here's some information about them.

And I'm going to feed it the company context, uh, which is company profile.

Should probably read it, but I'm going to assume it's half decent. Um,

and I'm going to allow it to search the internet. Honestly, some of these I

internet. Honestly, some of these I would use deep research, but for the sake of time on this already lengthy video, I'm going to keep it short. I

understand. Please confirm.

Yes please.

Great. So, now we have our artifacts. I

would say again some of these come out a little bit long where uh make this shorter.

Don't give any guidelines on length or structure. Um and I'm saying that

structure. Um and I'm saying that because I want to shape that myself instead of having the writing guidelines kind of enforce something that might not

apply to every article.

Let's see what do we have on this one.

Great. So, we'll take this, load it into the writing guide.

We'll have the company profile loaded into the company brief.

O, that one's a little bit long, but we'll keep it. Um, and then audience and personas.

We will also a bit long please summarize the above.

Great. So while that's running now we have all the pieces we need. Um we have all the artifacts. We have the research

which uh is right here.

Um, we have audience persona.

And now we're finally ready to write.

So, um, again, one of the things you'll probably run into is when you write, oneshotting is always kind of a little bit worse. So, I'm just going to write

bit worse. So, I'm just going to write in the most ideal kind of way, but um maybe as a followup, I can show some of the pitfalls, but um

so now that we're when you're starting to write um I'm still going to use the most basic model, but I think for most of this, if you're willing to wait, use

a better model. Create me a prompt for a writer that can create amazing

integration guide for Slack and Calendarly.

Want the article to be informative, the right level of detail for a marketing audience.

uh and prefer pointing to helpful resources instead of being too

comprehensive um in the melody.

Let's see what that comes up with.

Okay, you know what? I'm going to uh just take this part because I actually have my own style guide that I'll use.

Um and I'll go from there. So,

the article I'm writing has the following outline.

Let's see. So, I'm going to paste in the writing plan. Here

writing plan. Here is the research on the topic. Compile

research.

So like this is where like long um artifacts start being a little bit cumbersome.

Company context.

Um, one thing you'll run into a lot is just like you need to keep this prompt very clean. So, you need like, you know,

very clean. So, you need like, you know, whether I'm using like these little commas or these little chevrons, just a way to like create separation so the AI

doesn't get very confused. Um,

they are writing style.

And then we have what do we call this audience plus problems.

Great. So I know I said not to try

Great. So I know I said not to try everything in one go, but um I think because I've done a lot of work on the uh actual artifacts, this might not be half bad. I'm just going to look at the

half bad. I'm just going to look at the goals one more time. Um, explain what the integration does.

I want my outline to do that. So, I'm

going to try to remove like too many prescriptive things. Um,

prescriptive things. Um, this one's fine. Highlight use cases is fine. Um,

fine. Um, this is actually great. So, I'm glad it said that. Um, clear.

said that. Um, clear.

Yeah. So, let's run it and let's see.

I pick a model.

I'm just going to do let's do thinking.

Let's just do slightly longer.

We'll let that run.

So, this is doing it kind of in one shot. I think you know what I would

shot. I think you know what I would recommend is shaping it section by section. And so while it's doing that,

section. And so while it's doing that, let's do a uh separate chat where we use the quickest model

uh to do it section by section. Write

the intro and first H2.

Um a bit under I think I have a system instruction output and markdown. Let's see output

and text.

Great. So I mean let's just read how this is. Um,

this is. Um, so you know, one thing that's immediately kind of nice is it talks about problems. Um, I didn't really tell it, you know,

what the use cases are, but kind of surfacing client meeting notifications, you know, that get lost in inboxes where Slack is a little bit easier to see.

That's cool. Um, sales opportunities, you know, it's writing to my audience, right? Like marketers, top off ofunnel

right? Like marketers, top off ofunnel people. Um, so that's great. Um, I like

people. Um, so that's great. Um, I like how it's not too long. You know, we're not doing a recipe guide where there's kind of a novel before you get to the

meat of it. Um, so honestly, this is not bad. Um, I would definitely just keep

bad. Um, I would definitely just keep shaping chunks of this, but um, I like the intro. Uh, integration options.

the intro. Uh, integration options.

It's kind of getting started, uh, with the most simple. Um, you can see how it's pointing to the app directory. So, honestly, I like this.

directory. So, honestly, I like this.

So, when I'm writing stuff like this, I kind of still copy it out, you know, to something like notion or a Google doc.

Um, because I just don't want it to get lost.

And in this case, you know, I don't I don't like having intro.

So, this is great. So, let's let's continue here. So write the next section

continue here. So write the next section on uh low code methods plus um more

technical solutions.

Uh and I know it has it in the context, but I'm just going to go back to my writing guide

to pull that out. Um,

yeah. So, looking at the next sections.

Okay. Low code automation. Again, I like how it's linking to really helpful resources.

I like how it's staying within Slack and Countly and not going out to some third party that's, you know, writing a kind of SEO type blog post. And again, a lot

of this, you know, is shaped because we did research and we made sure the raw materials kind of had everything um that we're looking for. Uh the developer solution, you know, we have some stuff

here. I feel like this is one where we

here. I feel like this is one where we can beef up a little bit. But um why don't we complete the writing first and then

uh write write the rest. I'm getting

lazy here, but again it has my writing guidelines and uh my outline.

Oh, all right.

So, this is I mean, for me, you know, as a first draft, this honestly seems not bad at all. Um, some immediate

improvements I can see is, you know, if this is written for uh somebody to be able to like forward to their engineer or to be a little bit more technical, it

could use a little bit more detail. Um,

this section could probably use a little bit more detail. Um, I think the titles are not great, you know, like generally for H2 titles, you want to uh kind of

give a little bit more detail. Um, but

overall it's not bad. We can check how the let's see output and rich text.

Check how the one shot but using a uh deep thinking model does. All right.

Well, while that runs, you know, I I think again this is the first draft. You can kind of see how

first draft. You can kind of see how these steps improve writing quite a bit.

Um the artifacts kind of shape the at a meta level, the tone. um you know how it kind of ties the content back to what the company does and what problems it's

trying to solve. um you can see how research really you know you can think of it like you know it's like the building blocks of your article and um for me honestly if I were to go back and

improve this I mean let's we can spend some time doing that but like research would be um probably the first place for me you know I uh when I look at these sections it's like there could be more

helpful links here more helpful context but how's the model supposed to know unless I've done the research right so some things I would do here is like

maybe I would run, you know, multiple like deep research runs um where I collect all the information I want.

Maybe I would restrict, you know, the research to places I know are reputable.

Like maybe I should pull in a couple Reddit threads. Um maybe I should, you

Reddit threads. Um maybe I should, you know, restrict a research run just to the API docs of each of the uh integrations. Um, you can see like postw

integrations. Um, you can see like postw writing, you know, draft one, like there's a lot we would do here. So, you

know, there's like polish and some of the things that I would want to polish is like H2 titles being more descriptive. You know, um, we're still

descriptive. You know, um, we're still in a world of SEO and uh, how you shape your titles still matters a little bit for whether um, things rank up uh, in

search. Um, you know, other things I

search. Um, you know, other things I might do is, uh, maybe I'm not totally happy with the tone. Um, so maybe I'll do, uh, another run, you know, strictly

just to enforce a certain, uh, tone or a certain way of talking about my product if I found that, you know, it wasn't abiding by the artifacts as much. Um, if

you're writing this for SEO or uh AI mentions, like some of the things that you know you still want to do is uh let's see for SEO maybe I want to do

internal linking um maybe I want to do kind of references to you know the latest stats research

um for uh AI kind of attention like go AO um maybe I want to kind I mean, this article actually does it well already,

but I want my sections to be very succinct so that when it's chunked up, you know, and referenced, um, it'll carry all the information that you'd

want. Um, you know, maybe we want like a

want. Um, you know, maybe we want like a TLDDR section, uh, at the top or an FAQ section at the bottom. Um, you know,

table of contents. Um, maybe we want a factchecking step. Um, you know, for the

factchecking step. Um, you know, for the most part, I haven't run this integration. I've never really spent a

integration. I've never really spent a bunch of time looking at the API. Um,

and you know, like there's honestly a ton you can do here from just uh, you know, running some research on the API docs and then using that to verifying

um, uh, to I I mean, we've tried things like running cloud code or uh, codeex to actually literally try to integrate

these things together. Um, especially

when you're writing, you know, more than one article. you know, this is like

one article. you know, this is like hard. Um, yeah, but you can see how

hard. Um, yeah, but you can see how like, you know, this could go on and on here, right? Like you can kind of uh

here, right? Like you can kind of uh let's see. I mean, even write additional

let's see. I mean, even write additional drafts. You can kind of repurpose like

drafts. You can kind of repurpose like you can create, you know, uh I'll do this maybe in a future video. You can

make this a LinkedIn post, you know, um a Reddit thread. Um, so you know, I feel like what I'm showing is like the

proof of concept for, hey, if I'm Calendarly and I want to create like a really rich ecosystem of integrations and I want to give my users docs to kind

of, you know, enable them to use all these tools, maybe I I want to write a few hundred of these, you know, and maybe um uh I want to make sure that

every time my product updates, my API updates, every one of these articles updates with that instantly. Um, I want to make sure it ranks for SEO, for GEO,

and you know, again, you know, the reason we exist is if you're trying to do that, uh, and you know, you're trying to do that fully with humans, you you

can see how, you know, even with AI, this takes quite a long time to write.

like what you want instead is a machine that does that, right? The things that I've done, you know, use whatever tool you want, use our tool. Um, you can

encode that into a workflow. And when

you do that, it compounds a lot easier.

Like, you know, when you're training a human, you have to make sure they get this checklist and they're making sure all the H2 titles are great every time.

They have an FAQ. when you have a workflow, you know, generally it doesn't uh degrade or take a step back, you know, if you're um building it properly.

And over time, you can layer on all these pieces um and you can run it as many times as you want. So

uh you know, I hope this has been helpful. I think for many this probably

helpful. I think for many this probably brought up more questions than it answered uh more. But you know we have more videos, we have courses, we have

workshops. Um take a look, join the next

workshops. Um take a look, join the next one. I think we're always trying to

one. I think we're always trying to share what we're building. And uh thank you for listening.