Imagine having a private army of workers.
Each specialised at doing one task that you hate doing.
All humming along working together.
That’s the goal today.
We’re moving up the levels of AI again. This next level is Custom GPTs.
Are you ready to build an army of agents working for you?
We’re moving to the 3rd level of AI today: Custom GPTs.
Custom GPTs are like mini-AIs built for specific tasks.
ChatGPT has a GPT Store where you can find what others have built:
There are lots of fun tools here but what we need are GPTs built specifically for our business.
Anything another person builds won’t match our exact needs. Thankfully we can easily deploy a Custom GPT ourselves.
Do not build Custom GPTs just for the sake of it. Even if they are cool.
Getting one optimised takes time.
Remember this chart?
We started with tasks like writing blog articles, drafting press releases or answering customer service inquiries.
We initially used ChatGPT in an ad hoc way to deal with these tasks. And as time passed we realised that the same handful of ad hoc prompts had to be used again and again.
These most used prompts we added to our Library. We polished them to make them as efficient as possible and then stored them in an easy to use system like an Excel sheet or Notion document.
Now that we are building Custom GPTs we will follow the same basic pattern.
If there are library prompts that we use again and again and again let’s convert them into Custom GPTs.
We’ll use the blog writing example from before.
First up is finding the interface. It’s a little hidden.
When in ChatGPT Plus go to Explore GPTs and then Create (in the top right). Alternatively go directly to this link.
This’ll bring you to this interface:
The main thing to note here is that you basically have two standard ChatGPT interfaces: one on the left, one on the right.
The one on the left is for creating your Custom GPT.
The one on the right is for testing your Custom GPT.
You’ll move between the two. Adding instructions on the left and testing the final product on the right. And then looping back to the left to add corrections and additional information.
It’s a lot like the prompt engineering we’ve already been doing. We are still talking to an AI. Now we are just doing so to make another AI!
ChatGPT will want to know the name and basic usage of your Custom GPT. It will also want to generate a picture for you.
Just follow the questions and let it get all this done. Otherwise it’ll keep bothering you!
Keep answering the questions with as detailed answers as possible until you get to a question like “How else can I improve results?”
At this point grab your library prompt from the last Part and bring it to the create screen. Type this:
Here is a prompt that captures what I wish this Custom GPT to do.
[copy/paste prompt]
This will feed all the work you’ve previously done using and polishing this prompt into the Custom GPT.
Once it’s ingested this information go ahead and test it using the panel on the right hand side.
For this particular blog-writing Custom GPT for example I’d type “please write a blog article on the topic of” whatever topic I wanted an article on.
The Custom GPT is primed to use the information I’ve fed into it already and will complete the task following those instructions.
Solid work - the Custom GPT is ready.
OK great you might be thinking. That’s kinda cool.
But…why don’t I just copy in my library prompt each time I need a blog article like this?
Why do I need to make a Custom GPT for this?
The answer: workflows.
We can chain Custom GPTs together and “call” on them within ChatGPT.
Let’s say I have a task that looks like this:
This process has 3 discrete tasks.
I can make one Custom GPT for each task.
I’d have a SummaryGPT, BlogWriterGPT and ToneOfVoiceGPT for example.
I can then “call” on these GPTs one at a time within ChatGPT .
I do this by typing @ and then selecting the GPT I want to use.
It looks like this:
This let’s me flow information all the way through, from one step to the next.
Instead of me juggling multiple prompts I can quickly call on these separate Custom GPTs and quickly chain together workflows.
First things first, as a Premium member here’s a link to a full Playbook on CustomGPTs. It’s more than we can cover in one Part so here’s a full guide.
Second, some best practices for chaining workflows.
The most important single lesson here is to make your Custom GPTs hyper-specific.
As soon as you try to take the scope of a GPT too wide it’s usefulness will fall off a cliff.
For example don’t try to create a GPT that can write any blog. Instead, for example, create one that is very good at creating List-style blogs in a certain style.
The more specific the task the more focused your prompts can be and the higher the quality of the output.
From this fact comes the next tip - take your complex tasks and break them down into small individual steps. Then make Custom GPTs for each of those small steps.
How best to break tasks down? Let’s use ChatGPT!
Act as a productivity engineer
Break this task down into its constituent steps.
The task is [wide description]
A successful outcome looks like [success]
Unsuccessful outcome looks like [failure]
Giving ChatGPT ideas of i) the rough task and ii) what success and failure look like will allow it to break up most tasks into small constituent elements.
Each of those elements can be a Custom GPT.
My advice here is to build each step one at a time, testing it out as you go. Don’t try to build it ALL and then test.
If your first step’s Custom GPT produces a good result - move to step two.
If it doesn’t then chances are the step is too complex and needs to be broken down again.
If that’s the case feed that single step into the prompt above to split it.
This can be time consuming but i) you’ll get faster as you practice the skill and ii) the CustomGPT workflow you create off the back of this will be very accurate and very valuable.
Custom GPTs put us firmly in the intermediate level of AI usage.
In the next Part we’ll go to Advanced - building our own AI apps.
Getting here will give your business an absolutely unfair advantage.
Here’s a reminder of the week: