A custom assistant is just a saved set of instructions plus some files you have uploaded. That is the whole concept.
Which is why it is worth doing, and why the elaborate versions people attempt usually fail. The value is in not re-explaining your business every time you open a chat, not in building something clever.
I have built perhaps fifteen and use three. The three I use are the boring ones.
Here is how to build one properly in about an hour, what to put in it, and which three I would build first.
Quick Info
What a Custom Assistant Actually Is
Three parts, and none of them are technical.
That is it. If you have written a good briefing document for a new freelancer, you have already done the hard part of this.
A custom assistant is an induction pack that answers questions.
Writing the Instructions
This is where the quality comes from, so spend the time here rather than on the files.
The structure I use, in this order.
Be specific and be negative where it matters. The prohibition list is what stops it doing the two or three things that would actually embarrass you.
Choosing the Knowledge Files
Fewer, better files. This is the most common mistake and it is easy to fix.
Uploading forty documents makes retrieval worse, not better, because the assistant has more places to look and more chance of quoting something out of date.
What I actually upload for a business assistant:
And a maintenance rule: date every file, and replace rather than add when something changes. An assistant quoting last year's prices is worse than no assistant.
The Three Worth Building First
One. The content assistant
Knows your style guide, your services and your audience. Used for drafting, editing and structural feedback. The one I use most by a wide margin.
Two. The enquiry responder
Knows your services, prices, availability and the answers to your ten most common questions. Drafts replies to incoming enquiries, which you then send. Saves more time per week than anything else on this list.
Three. The internal knowledge assistant
Knows your processes, your templates and how you do things. Answers questions from you or your team about your own business. Its real value shows up when someone new joins.
That is the set. Build those three, use them for a month, and only then consider whether a fourth is solving a real problem or just interesting.
Testing It Before You Rely on It
Twenty minutes that prevents most of the disappointment.
Fix the instructions based on what fails. Two or three rounds of this gets it to a state you can trust, which is the point.
Sharing It, and the Bit to Be Careful About
You can share a custom assistant with your team or publish it, and both have implications worth thinking about for a minute.
Uploaded knowledge files can generally be extracted by a determined user through the conversation. So do not upload anything you would mind a competitor or a customer reading. No client lists, no contracts, no personal data, no internal financials.
For anything genuinely confidential, keep it out of the files and reference it manually when needed.
For team use, also decide who maintains it. An assistant with year-old knowledge that people still trust is a slow-acting problem.
When a Custom Assistant Is the Wrong Answer
Worth saying, since it gets recommended for everything.
If the task needs to run without you, on a schedule or triggered by an event, you want an automation with an AI step in it, not a chat assistant. My automation article covers those.
If the task needs live data from your systems, a chat assistant reading static files is the wrong shape.
And if you only do the task monthly, a saved prompt is sufficient. Not everything needs to be built.
Frequently Asked Questions
No. It is a page of written instructions plus a few uploaded files. If you can brief a freelancer in writing, you can build one.
Few and current. Three to five well-chosen documents work better than forty, which makes retrieval worse and risks quoting outdated information.
Assume determined users can extract content from knowledge files through conversation. Do not upload anything confidential, including client data or contracts.
An enquiry responder that knows your services, prices and common questions. It usually saves the most time per week.
Include an explicit prohibition in the instructions telling it to say when something is not covered by its files, then test that behaviour deliberately.
When the task must run without you, on a schedule or triggered by an event, or when it needs live data from your systems.
Before You Go
An hour on the instructions, three current files, twenty minutes of testing. That is a custom assistant worth using.
The instruction template I use and the style guide format are in the resources section.
If you want a set built and tested for your business, get in touch.
Three files, one page of rules, Tariq
I'm a marketing consultant, entrepreneur and content creator. I help businesses grow through practical marketing, websites, SEO, content and AI.
More About Tariq →