Chidinma runs a boutique event planning business in Chicago: corporate parties, milestone celebrations, nonprofit galas. She is the sole planner with two part-time assistants. When she started using an AI writing tool for client proposals, she had the same experience every time. She would ask for a proposal draft, get something technically adequate but completely generic, spend twenty minutes rewriting it to sound like her, and wonder what the tool was actually saving her. One day, frustrated, she spent thirty minutes doing something she had been putting off: writing out who her business was, what made her different, what tone she used with clients, and what she never said. She pasted that description into the tool's "Custom Instructions" field. Her next proposal draft came back sounding almost exactly like her. She sent it with one small edit. The thirty-minute investment eliminated the twenty-minute rewrite she had been doing every single time.

That thirty-minute investment was the creation of a system prompt, a set of instructions that shapes every AI response before you even ask your first question. It is one of the highest-leverage things you can do with an AI tool. Most small business owners never do it.

What a System Prompt Is

A system prompt (also called custom instructions or context settings, depending on the tool) is a block of text that tells the AI how to behave across all your conversations. It is the difference between working with a blank-slate assistant who knows nothing about you, and working with one who has been thoroughly briefed on your business.

Without a system prompt, the AI defaults to generic professional tone, no knowledge of your industry or clients, no awareness of your preferences, and no memory of what you have told it in the past. You end up providing context from scratch every time you ask for something. Worse, you tend to provide slightly different context each time, which is why output quality feels random rather than consistent.

With a system prompt, that context is always present. The AI knows you are a Chicago event planner who works with corporate clients, uses warm but professional language, never uses exclamation points, and always includes a timeline section in proposals. Every output reflects that from the first sentence.

Think of it as the briefing document you would give a new assistant before their first day. Except you only write it once, and unlike a new assistant, the AI never partially remembers it, never applies it on Monday and forgets it on Thursday, and never needs the awkward second conversation about tone. Whatever is in the field is applied in full, every time.

What to Include in a Business System Prompt

A good system prompt covers six things. Each one answers a question you would otherwise be answering repeatedly inside individual prompts, which is the test for whether something belongs here at all. Work through them in order the first time. They build on each other, and the later sections are much easier to write once you have committed the earlier ones to text.

1. Who you are

Your name, business name, what you sell or do, and who your clients are. One to three sentences. Keep it factual and specific. Specificity is what makes this section useful: "event planner" produces generic output, while the industries and job titles of your actual buyers change how the AI pitches and what it assumes the reader already knows. Example: "I'm Chidinma Obi, owner of Obi Events in Chicago. I plan corporate events, milestone celebrations, and nonprofit galas for mid-to-large Chicago organizations. My clients are typically event coordinators, executives, and development directors at companies and nonprofits."

2. Your voice and tone

How do you communicate with clients? Formal or conversational? Warm or direct? What words do you use often? What words or phrases do you never use? The banned list is the part most owners skip and the part that saves the most editing, because the phrases you always delete are the ones the AI will always reach for. Example: "Write in a warm but professional tone. Use clear, direct language. Never use exclamation points. Avoid corporate jargon like 'synergy' or 'leverage.' Do not use phrases like 'of course' or 'certainly.'"

3. What you're typically asking for

Tell the AI your most common use cases so it defaults to appropriate output structures without you having to specify them every time. If a document type of yours always contains the same sections, name those sections here rather than in every request. Example: "I frequently ask for proposal drafts, follow-up emails, vendor inquiry letters, event timeline templates, and social media captions. For proposals, always include sections for: Event Overview, Our Approach, Timeline, and Investment."

4. What you never want

Explicitly prohibiting things you consistently have to remove from AI output saves time and frustration. Build this section by watching your own edits for a week. Anything you delete more than twice belongs on the list. Example: "Do not include pricing placeholders, I'll add those manually. Do not mention competitors. Never suggest the client check with their 'team', I deal directly with decision-makers."

5. Your business context

Any standing facts the AI should know: your service area, your typical event size, your signature style, relevant constraints. These are the facts that quietly prevent wrong output, since an AI that does not know your service area will happily draft a proposal for a job you cannot take. Example: "We work exclusively in the Chicago metropolitan area. Events typically range from 50 to 500 guests. We are known for incorporating local vendors and cultural elements specific to Chicago neighborhoods."

6. Output format preferences

How do you want information structured? Bullet points or prose? Short paragraphs or detailed sections? Specific length guidance? Setting these once means every draft arrives at roughly the right length and shape, which is most of what separates a draft you edit from a draft you rewrite. Example: "Proposal sections should be 2 to 4 paragraphs each. Use bullet points only in the Timeline section. Keep emails under 200 words."

The Six Elements at a Glance

Read down the third column and the pattern is clear. Every element exists to retire a specific piece of repeated work. If a section of your system prompt is not retiring anything, it is decoration, and it can come out.

That test also tells you how to write the first draft without staring at a blank field. Do not try to describe your business in the abstract. Instead, go back through the last handful of AI drafts you edited and look at what you actually changed. The tone you kept restoring is your voice section. The phrases you kept deleting are your prohibitions. The context you kept retyping is your business section. The structure you kept imposing is your format section. Chidinma's thirty minutes were not thirty minutes of invention; they were thirty minutes of writing down what she already knew from twenty-minute rewrites.

Where to Set It Up

Different AI tools handle system prompts in different ways, and the field is usually tucked somewhere in settings rather than presented as a feature, which is a large part of why so few owners ever find it. Here is where to look in the most common tools:

• ChatGPT: Go to your profile icon, select "Customize ChatGPT," and fill in the "What would you like ChatGPT to know about you?" and "How would you like ChatGPT to respond?" fields. These apply to all new conversations.
• Claude: In the Claude web app, access "Profile" settings and look for "Custom instructions." In Claude Projects, you can set project-specific instructions that apply to all conversations within that project.
• Other tools: Look for "Custom instructions," "Context," "Persona," or "System settings" in the tool's settings or profile menu. Most modern AI writing tools have some version of this feature.

Notice the two-level structure in that second entry, because it is the more useful pattern once you are past the first week. A profile-level instruction describes your business and applies everywhere. A project-level instruction describes one body of work and applies only inside it. If you handle several distinct client types or service lines, the standing facts about your company go in the profile and the specifics go in the project.

If you use multiple AI tools for different purposes, maintain a master version of your system prompt in a document you can copy from. Update it when your business or preferences change, at minimum once a year. Without a master copy, the versions in each tool drift apart, and you end up with a good briefing in one tool and a stale one in another with no way to tell which is which.

Task-Specific Prompts vs. System Prompts

A system prompt sets up the AI's general behavior. For specific tasks, you still write a task prompt, but it can be much shorter because the system prompt has handled the context.

Without a system prompt, a task prompt might be: "Write a proposal for a 200-person corporate holiday party at the Palmer House. My company is Obi Events and we specialize in Chicago-themed events. Please keep it professional but warm. Include sections for event overview, our approach, timeline, and investment. Don't include pricing, I'll add that. Use direct language, no exclamation points."

With a good system prompt already in place, the same task prompt becomes: "Write a proposal for a 200-person corporate holiday party at the Palmer House Hilton, December 14th."

Same quality output. A fraction of the prompting work. Look at what survived into the short version: the guest count, the venue, and the date. Everything that disappeared was context about Chidinma's business rather than about this particular job. That is the dividing line. Facts about the job go in the task prompt; facts about the business go in the system prompt.

That dividing line is worth applying deliberately rather than by feel, because the failure it prevents is not obvious when it happens. Put a specific venue or guest count in the system prompt and it will not announce itself; it will quietly colour an unrelated vendor letter three weeks later, and you will read that letter wondering why it mentions a holiday party. The test is a simple one. Ask whether the fact will still be true of everything else you are likely to request. If it will, it belongs in the settings. If it belongs to one job, type it into that job.

Anti-Patterns to Avoid

• Writing only the positive half. Most owners describe their business and their tone and stop there. The "what you never want" section is where the repeated editing actually lives, and leaving it out means you keep deleting the same phrases forever.
• Keeping job details in the system prompt. A specific venue, guest count, or date belongs in the task prompt. Put them in the system prompt and they leak into every unrelated draft you request afterwards.
• Setting it once and never revisiting it. A system prompt written around the clients you had two years ago produces output aimed at a business you no longer run. Review it at least once a year, and whenever your services or voice change.
• Configuring one tool and forgetting the others. The briefing only applies where you pasted it. If you use several tools, keep the master document and update all of them together.
• Describing your voice in abstractions. "Professional but approachable" tells the AI almost nothing. Named prohibitions such as no exclamation points and no "synergy" change output immediately.
• Forgetting the scope of the setting. Custom instructions apply to all new conversations, not just work ones. Anything you would not want shaping an unrelated request does not belong at the profile level.

Practice Prompts

The first two are the ones to run today, and they work in either order. The rest refine what those two produce, which means they are worth returning to a week later rather than attempting all at once in a single sitting.

• Draft it by interview. "I am going to describe my business. Interview me until you can write a system prompt covering six things: who I am, my voice and tone, what I typically ask for, what I never want, my business context, and my output format preferences. Ask one question at a time."
• Harvest your own edits. "Here are several AI drafts and my edited versions of each: [paste]. Identify the changes I made every time, and write them as instructions for a system prompt."
• Make the voice section concrete. "Rewrite this description of my tone so that every line is a specific, checkable instruction rather than an adjective. Here is what I have: [paste your tone section]."
• Test the before and after. Run one long task prompt containing all your context, then set the system prompt and run the short version. Compare the two drafts and count the edits each one needs.
• Annual review. "Here is my current system prompt: [paste]. Here is what changed in my business this year: [describe]. Tell me which lines are now out of date and what is missing."

Reflection Questions

• What context do you retype into almost every prompt? Why is it not in your system prompt yet?
• Which words or phrases do you delete from AI drafts every single time?
• If a new assistant read your system prompt, could they write in your voice without asking you anything?
• Do the AI tools you use regularly all have the same briefing, or has one of them drifted?
• When did your business last change in a way your system prompt does not yet reflect?

Glossary

• System prompt: A block of text that tells the AI how to behave across all your conversations, applied before any individual request.
• Custom instructions: The name most consumer AI tools give to the system prompt field in their settings. Also appears as "Context," "Persona," or "System settings."
• Task prompt: The individual request you type for one specific job, containing the details unique to that job.
• Project-level instructions: A system prompt scoped to one body of work rather than to your whole account, applying to every conversation inside that project.
• Master version: The single document where you keep your system prompt, copied out to each tool so the versions do not drift apart.
• Prohibition list: The "what you never want" portion of a system prompt, built from the edits you find yourself making repeatedly.

Related Lessons

• System Prompts vs User Prompts draws the same dividing line from the other direction, starting with the individual request.
• The Anatomy of an Effective Prompt covers what remains in a task prompt once the standing context has moved into your settings.
• Brand Voice Consistency Across AI-Generated Content extends the voice and tone section across every channel your business writes for.
• Setting Up AI Tools for Your Team matters once more than one person is generating output that should sound like the same company.
• Building Your Personal Prompt Library is where the master version of your system prompt should live alongside your tested task prompts.

Closing

Chidinma's tool did not improve. Her briefing did. The proposals had always been generic because nothing in the request ever said who she was, how she wrote, or what she refused to say, and no amount of rephrasing a task prompt fixes an absent briefing. Thirty minutes of writing replaced a rewrite she had been performing on every draft.

Open the settings of the AI tool you use most and fill in the field. Six sections, specific instead of abstract, with the prohibitions written down. Then keep the master copy somewhere you will find it next year.

Key Takeaways

• A system prompt is a one-time briefing document that shapes all your AI interactions. Write it once, and every output from that tool reflects your voice, context, and preferences automatically.
• Without a system prompt, you're re-explaining yourself every time. Context you provide repeatedly in individual prompts belongs in your system prompt instead.
• Include six elements: who you are, your voice and tone, typical use cases, what you never want, your business context, and output format preferences. Thirty minutes to write a thorough system prompt eliminates hours of editing over the following months.
• Task prompts become dramatically shorter once a system prompt is in place. You provide the specific details of the task; the AI already has everything else it needs.
• Set up system prompts in every AI tool you use regularly. Most tools have a custom instructions or context field in their settings. Use it.
• Update your system prompt when your business changes. New clients, new services, new voice guidelines, keep the prompt current so the AI reflects where your business is today, not where it was when you first wrote it.

Frequently Asked Questions

• How long should a system prompt be? Long enough to cover the six elements and no longer. Each section exists to retire a piece of repeated work, so if a line is not preventing an edit you keep making, it is padding.
• What is the difference between a system prompt and a task prompt? The system prompt holds facts about your business that are true for every request. The task prompt holds facts about one job, such as the guest count, the venue, and the date.
• Where do I find the setting? It varies by tool. Look for "Custom instructions," "Context," "Persona," or "System settings" in the settings or profile menu. Most modern AI writing tools have some version of the feature.
• Do I need a separate system prompt for each tool? You need the same briefing in each tool you use regularly. Keep one master version in a document and copy it out, so the tools do not drift apart as you make changes.
• How often should I update it? Whenever your business or preferences change, and at minimum once a year. New services, new client types, and new voice guidelines all make a stale prompt produce output aimed at the business you used to run.