A custom GPT is a prompt you do not want to retype. Claude Projects are the same idea with a folder. Neither is a business. Neither is an agent you sell to a dentist in Ohio.
Aside. The robot does not get your badge. Your manager still reads the email with your name on it.
Build one for the task you repeat. Weekly update. Ticket first draft. Job-description rewrite. Meeting cleanup. If you cannot name the repeat, you do not need a custom GPT. You need a notes app.
What to put in the instructions
- Who the reader is
- Words you never use (the ones your brand already banned, or “leverage,” if you have taste)
- Facts that are stable (office hours, the real return window) — not last week’s prices
- The output shape
- The line: if a fact is missing, write NEED, do not invent
What not to upload
Customer exports. Salary sheets. The password list. Anything you would not tape to the kitchen of a coworking space. Custom GPTs on consumer plans are still someone else’s server.
One good first build
Name it after the job: Friday status for Jordan.
You draft my Friday status for my manager, Jordan.
Use only the bullets I paste.
Structure: shipped / stuck / need from Jordan / next week.
No adjectives about “great progress.” No invented blockers.
180 words or less.
Paste three real statuses you already sent as examples. That is the training. Not a manifesto.
When this is too much
If you will run it twice a year, a saved prompt in Notes is enough. Custom GPTs earn their keep when you open them like a template.
Try this today
Make one assistant. Run it on this week’s real bullets. Compare to last Friday’s email. Keep whichever one your manager can scan faster.
You are done when
You have one named assistant you opened for real work, not a zoo of unused bots.