Turn every prompt in the Advisor OS library into a standalone Custom GPT that your entire practice can use — no technical skills required.
A Custom GPT is a purpose-built version of ChatGPT that has been pre-configured with specific instructions, knowledge files, and conversation starters. Instead of pasting the same prompt every time you start a new chat, a Custom GPT remembers everything permanently.
Think of it this way: the Prompt Library gives you the blueprints. A Custom GPT is the finished machine — built once, used forever. Your team opens it, clicks a conversation starter, pastes their input, and gets a structured, compliant, on-brand output every time.
Below you will find a step-by-step guide for building any Custom GPT, followed by a complete blueprint for every prompt in the Advisor OS library. Each blueprint tells you exactly what to name it, what to paste, what files to upload, and what conversation starters to add.
Go to chat.openai.com → click your profile icon (bottom-left) → select 'My GPTs' → click '+ Create a GPT'. You need a ChatGPT Plus or Team subscription to create Custom GPTs.
Give it a clear, functional name that your team will recognise instantly. Use the naming convention: [Practice Name] + [Function]. For example: 'attooh! Pre-Meeting Prep Engine' or 'attooh! Compliance Scanner'.
In the Description field, write one sentence explaining what this GPT does. This appears in the GPT gallery and helps your team understand its purpose at a glance.
This is where the magic happens. In the 'Instructions' field, paste the full prompt from the Buy Back Friday™ Prompt Library. This becomes the GPT's permanent system prompt — it governs every response the GPT produces.
These are pre-written prompts that appear as clickable buttons when someone opens the GPT. Add 3–4 starters that reflect the most common use cases. For example, a Pre-Meeting Prep GPT might have: 'Prepare a brief for a retirement review meeting' or 'Generate a pre-meeting brief for a new client onboarding'.
You can upload reference documents that the GPT can search when generating responses. Upload your Tone Blueprint, practice SOPs, product comparison sheets, fee schedules, or compliance checklists. The GPT will use these as context without you needing to paste them every time.
Toggle on/off: Web Browsing (for market research GPTs), Code Interpreter (for data analysis), and DALL·E (usually off for advisory GPTs). For most advisory prompts, you only need the default text generation capability.
Use the Preview panel on the right to test your GPT with real scenarios. Run 3–5 test cases before sharing. Check that the tone matches your blueprint, the output structure is correct, and compliance flags are working. When satisfied, click 'Save' and choose your sharing setting.
14 ready-to-build Custom GPTs. Click any card to see the full build specification.
Do not build all 14 at once. Start with the Master Prompt, Pre-Meeting Prep, and Post-Meeting Multi-Deliverable. These three cover 80% of daily advisory work.
Prefix every GPT with your practice name. This makes them instantly recognisable in the GPT sidebar and prevents confusion if team members have personal GPTs too.
Set a calendar reminder to refresh your Tone Blueprint, fee schedules, and compliance checklists. Outdated knowledge files produce outdated outputs.
In ChatGPT, you can pin GPTs to the top of your sidebar. Pin your top 3 so they are always one click away.
Run at least 3 real scenarios through each GPT before sharing with your team. Check tone, structure, and compliance flags. A poorly configured GPT erodes trust faster than no GPT at all.
Your admin team has different needs. Build a dedicated 'Admin Task Engine' that combines the Task Delegation Engine and SOP Generator. This gives them a single entry point for all operational work.