Bind standing instructions to one job

A new chat is open. You provide half the rate sheet, forget the cancel rule, and the draft offers a discount you do not run. Next quote, same hole. The tool did not forget on purpose. Nothing was saved.

The short answer

The sequence below is the control path: same vendor pages, same prompts, product names kept exact.

One saved workspace per recurring job, with the rules and the files already in it. ChatGPT calls that a Project, and a custom GPT when you need a reusable helper. Claude calls it a Project. Gemini calls it a Gem. Today's customer facts stay in the message. The standing rules do not.

Why every chat starts empty

A blank chat has no rate sheet and no voice. The model fills the gap with something that sounds helpful. Saving the instructions once, next to the approved files, is the fix. A mega-prompt that tries to cover the whole company collides with itself. One job per workspace.

ChatGPT Projects and custom GPTs

Projects in ChatGPT keep related chats, uploaded files, and custom instructions together. OpenAI's help says Projects are available on free and paid plans. Business, Enterprise, and Edu can share a project with teammates. Limits change. Confirm them in the account and on openai.com/pricing.

Custom GPTs are a saved helper with instructions and optional knowledge files. OpenAI's current help gates creating and publishing a GPT to Business, Enterprise, and Edu. Other plans can still use a GPT that was shared with them.

Start with three projects, not twelve:

1. Quotes. Upload the rate sheet you stand behind, scope boundaries, one anonymized winning proposal, and the deposit and cancel rules that already exist. Instruction: "Draft from these files only. Do not invent line items."
2. SOPs. Upload the messy current steps and the stop-points you already enforce. Instruction: "Organize and tighten. Do not invent steps. Mark gaps [NEED]."
3. Customer email. Upload three emails you actually sent that worked, plus a one-page voice note. Instruction: "Match the length and directness of the examples. Facts come from the user message."

Claude Projects

Projects are workspaces with their own chats, files, and project instructions. Free accounts can create a limited number. Paid plans expand that. Confirm the cap on Anthropic's pricing page.

On Team and Enterprise, projects can be shared with view or edit permissions. Owners control org-wide sharing. Confirm the current options in Anthropic's Projects article before you roll it out.

Standing instructions worth writing once: who you are in one sentence, a calm local voice, never invent price or policy, and a person still sends customer-facing copy.

Gemini Gems

Use Gems in Gemini Apps: on gemini.google.com open Gems, choose New Gem, enter a name and instructions, optionally add files under Knowledge, preview, then Save. Previewing does not save the Gem. Tips for creating custom Gems say custom Gems are created in the Gemini web app.

Build the same three jobs: quotes, SOPs, customer email. The Gemini Apps Privacy Notice treats Gem instructions as information you provide. Do not put secrets in the instruction box.

Which to pick when

• You already live in ChatGPT and you want chats, files, and instructions in one folder → a ChatGPT Project
• You want a helper other people can open by name, and you are on a Business, Enterprise, or Edu workspace → a custom GPT
• The long document has to stay careful for months → a Claude Project
• The team already works in Gemini Apps and you want a saved instruction plus Knowledge files → a Gem
• Two or more people must share the same files → the team plan that actually shares (ChatGPT Business or Claude Team). Confirm sharing on the live help page.

Try this: the quotes workspace in one sitting

1. Name it Quotes — [your shop].
2. Provide standing instructions: voice, and never invent a price or a policy.
3. Upload the smallest set of approved files that define scope and price.
4. Start a chat: "Draft a proposal section from these files for [job type]. Mark [NEED]."
5. Fill every [NEED], then ask for a tighten pass.
6. Save the final in the proposal folder you already use, with a date. The chat is not the filing cabinet.

Files to put in, and leave out

Put in approved policies, templates, anonymized examples, and a glossary. Leave out card numbers, full charts, passwords, and a whole unrestricted staff folder. The workspace is still the vendor's product. Read what not to provide before you upload a customer file.

Example (illustrative): a plumbing shop with two estimators

Problem: each estimator retypes the trip charge. What was built: one quotes Project with the rate sheet and the cancel rule, and the same three instructions copied into a Gem for the owner who lives in Drive. Tools it lives in: ChatGPT Project, and a Gem. Owner still does: fills [NEED] and sends the quote. Payoff: not measured.

Mistakes and limits

• One giant project for the whole company.
• Uploading a customer list "just in case."
• Assuming a free plan shares with the crew. Read the sharing line on the current help page.
• Editing only inside the chat and never saving the sent quote in your own folder.
• Treating a polished Gem preview as saved. Google's help says the preview does not persist until you click Save.

Doing this inside the tools you already use

If you would rather have this exact job drafted from the software you already use, with you still approving every send, see how a custom build works.

FAQ

Do I need a custom GPT and a Project?

No. A Project is the folder for a job. A custom GPT is a named helper with those instructions baked in. Start with the Project. Add a GPT when someone who will not open the right folder keeps starting a blank chat.

Can free accounts do this?

ChatGPT help says Projects exist on free and paid plans, with sharing on Business, Enterprise, and Edu. Claude free accounts get a limited Project count. Gems are created in the Gemini web app. Confirm the cap you actually have before you promise the crew a shared workspace.

What goes in the chat versus the saved instructions?

Frozen rules and approved files go in the workspace. Today's customer, today's scope, and today's [NEED] items go in the message.

Where do Claude Artifacts and Gemini Canvas fit?

They build a checklist you can click. That is a different job: a quote checklist without a developer.

Keep these

• One workspace per job. Start with quotes, SOPs, and customer email.
• Standing rules in the workspace. Today's facts in the message.
• No secrets in the instruction box.
• The sent quote lives in your own folder, dated.

Sources

• Projects in ChatGPT
• Custom GPTs
• Claude Projects
• Use Gems in Gemini Apps

Related reading

• Build a quote checklist without a developer
• What not to provide
• Draft a quote without inventing the price