Every consultant in your category has access to the same models you do. Same reasoning. Same writing ability. Same price.
So the model isn’t your advantage. What you feed it is.
You’ve got a decade of client work, a framework you’ve refined across dozens of engagements, and a set of judgment calls you make so automatically you’ve stopped noticing them. That material doesn’t exist anywhere on the internet. It’s the only thing that makes an AI assistant sound like you instead of sounding like every other consultant’s AI assistant.
Building one takes an afternoon. Building one that’s actually useful takes a bit more thought. Here’s the difference.
Decide What It’s For Before You Build It
The mistake almost everyone makes is building one general-purpose assistant and asking it to do everything. You get a mediocre generalist that you stop opening after two weeks.
Pick a single job. The three that consistently earn their keep:
Internal delivery assistant. It knows your framework and helps you prep sessions, structure audits, and draft deliverables in your format. This is the highest-value one and the easiest to build, because you already have the raw material.
Client-facing support tool. Your clients get access between sessions. They ask questions, get answers grounded in your methodology, and stop paying you to repeat yourself. This can also become a real premium tier in your offer.
Sales and marketing assistant. It knows your positioning, your case studies, and your voice, and it drafts proposals, follow-ups, and content that don’t need a full rewrite.
Start with one. Get it genuinely good. Then build the second.
What to Actually Feed It
This is where the value lives, and it’s the part people rush.
Your knowledge base should include:
Your frameworks, written out properly. Not the slide version. The version with the reasoning. Why the steps are in that order. What you look for at each stage. What it means when a client’s answer at step two contradicts their answer at step four.
Anonymized client work. Real audits, real recommendations, real deliverables with names and identifying details stripped. This teaches format and depth better than any instruction you could write.
Your decision rules. This is the highest-value and most-skipped input. Write down the calls you make automatically. “If a client’s follow-up gap is over 48 hours, fix that before touching lead generation.” “If they’re under $250K with no repeatable offer, don’t recommend paid ads.” “If they can’t name their last five clients’ outcomes, start with proof collection.” These rules are your judgment, and they’re what turn a generic answer into your answer.
Your voice guide. Words you use. Words you never use. Sentence length. How direct you are. Whether you hedge. Give it examples of your actual writing rather than adjectives about your writing. “Direct and warm” means nothing to a model. Three of your real emails mean a lot.
What it should refuse to do. Where it should say “this needs Gilberto’s judgment, book a call.” Boundaries make it more trustworthy, not less useful.
A word of caution on client data: strip identifying details before anything goes in, and check your engagement agreements. Convenience is not worth a confidentiality problem.
Write the Instructions Like You’re Training a New Hire
Most custom GPT instructions are too short and too vague. “You are a helpful business consultant” produces a helpful generic consultant.
Write it the way you’d brief someone joining your team in week one.
Tell it who it’s for. “You’re supporting service business owners doing $200K to $2M who have expertise but no repeatable client acquisition system.”
Tell it how to think. “Before recommending anything, identify which part of the flow is broken. Never recommend more traffic when conversion is the problem. Never recommend more tools when the strategy is unclear.”
Tell it what a good answer looks like. “Lead with the recommendation. Then the reasoning. Then the first three steps. Keep it under 400 words unless asked for more.”
Tell it what to ask when it doesn’t have enough. A good assistant asks two clarifying questions instead of guessing at a plan.
And tell it what not to do. No em dashes if that’s your rule. No hype language. No inventing statistics. That last one matters more than people think, because a confident fabricated number inside a client deliverable is a credibility problem you may not catch until the client does.
Test It Against Work You’ve Already Done
Don’t launch on vibes. Test it.
Take five past engagements where you know what you actually recommended. Feed the assistant the same starting information and compare.
You’re looking for three things.
Does it reach the same diagnosis you did? If it consistently lands somewhere else, your decision rules are missing something.
Does it sound like you? Read it out loud. If you wouldn’t say it, the voice guide needs work.
Does it know its limits? Give it a question outside your scope and see whether it confidently improvises. If it does, tighten the boundaries.
Then iterate. My honest experience: the first version is disappointing, the third version is useful, and the fifth is something you open every day. Most people quit after the first.
Where to Keep the Human Firmly in the Loop
This is where I’d push back on most of the AI advice aimed at consultants right now.
AI should absorb the repetitive work so you have more room for the work that requires you. It should not absorb the parts your clients are actually paying for.
Keep human: the diagnosis conversation, the hard conversation, the judgment call under uncertainty, the relationship, and anything a client would feel differently about if they knew a model wrote it.
Let AI handle: first drafts, formatting, research synthesis, meeting prep, summarizing, follow-up drafting, and the fortieth version of a document you’ve written thirty-nine times.
There’s a real trap in the middle. It’s now easy to produce more content, more emails, and more deliverables than ever. Volume is not the same as value. If your acquisition system was broken before AI, AI just helps you produce more output inside a system that was never going to work. Fix the flow first. Then use AI to run it faster.
And be straight with clients about where you use it. Most won’t care. The ones who find out on their own will.
Turning It Into Something You Can Charge For
Once your internal assistant is good, the client-facing version becomes a genuine offer component.
A few ways consultants are packaging it:
Included in a premium tier. Your $2,000/month clients get monthly calls. Your $3,500/month clients get calls plus 24/7 access to an assistant trained on your methodology. That’s a real difference in value and it costs you almost nothing to deliver.
As a standalone product for people who can’t afford you. Not everyone who wants your help can pay $6,000. A supported AI tool at $99 a month captures a slice of that demand and builds a pipeline of people who eventually can.
As a retention tool. Clients who use something between sessions stay longer. Engagement between touchpoints is one of the better predictors of renewal in service businesses.
One honest caveat. This only works if your methodology is genuinely distinct and genuinely good. A custom GPT trained on generic advice produces generic advice with your logo on it, and clients notice fast. The tool amplifies what’s already there. It doesn’t create it.
Conclusion
The model is a commodity. Your thinking isn’t.
Pick one job. Feed it your real frameworks, your real work, and your real decision rules. Write the instructions like a proper onboarding doc. Test it against work you’ve already done. Keep the human in the parts that need a human.
Do that and you get an assistant that extends your capacity instead of diluting your voice.
If you want help figuring out where AI actually belongs in your business, and where it will just create expensive noise, that’s part of what we work through in the Profitable Pro Accelerator. We help consultants build a Profit Flow where AI strengthens the system instead of complicating it. Apply at gilbertoherrera.com.
Frequently Asked Questions
Do I need technical skills to build a custom GPT?
No. The current builders are configuration and file uploads, not code. The hard part isn’t technical, it’s writing down the judgment you normally apply without thinking about it.
Is it safe to upload client work?
Only after you strip names and identifying details, and only if your client agreements allow it. Check your platform’s data settings too, since business and enterprise tiers generally keep your uploads out of model training while consumer tiers may not.
How long does it take to build one that’s actually useful?
An afternoon for version one. Two to three weeks of daily use and iteration before it’s genuinely good. The gap between those two is where most people quit.
Will clients feel cheated if I use AI in my work?
Not if you’re upfront and the quality holds. What damages trust is discovering it on their own, or receiving something that clearly nobody read before it was sent.
Should I charge clients for access to my custom GPT?
Yes, if it’s built on a methodology they’re already paying for and it delivers real answers between sessions. Price it as a tier upgrade rather than a separate product, so it strengthens your core offer instead of competing with it.
