System Prompts for Small Business: A Reusable 10-Part Template

What should system prompts for small business actually contain?

Not a slogan or a clever command that happened to work once. A useful system prompt is a reusable operating brief, not a magic sentence.

It tells the AI which business it is helping and defines the work in enough detail to repeat it. It also sets a boundary for anything that needs a person. The aim is not to remove judgement. It is to stop rebuilding the same context every time you open a new chat.

Put the instructions where the work lives

The label changes between tools, but the practical idea is consistent.

OpenAI describes ChatGPT Projects as a place to keep instructions and reference material with related chats for recurring work. Its project instructions apply inside that project. Anthropic says Claude project instructions can hold context and requirements for a particular workflow.

That gives you a simple placement rule. Put account-wide preferences in global instructions. Keep workflow-specific rules with the relevant project. A quote follow-up process should not quietly control how the AI handles an unrelated supplier comparison.

Keep the reusable brief somewhere your team can review it as well. Do not let the only copy live inside one person’s old chat history.

The ten parts of a small-business system prompt

Lumomatics uses a ten-part formula. Each part answers a different operating question.

Part	What to write	Practical check
1. Role	The narrow job the AI is performing.	Make the responsibility clear to a new staff member.
2. Business context	Services offered, location, hours and relevant terms.	Include enough context to avoid generic advice.
3. Goals	The result this task should produce.	Define an observable finish.
4. Audience	Who will read or use the output.	State what the reader already understands.
5. Standards	What acceptable work looks like, supported by a good example where possible.	Give the reviewer a stated standard.
6. Constraints	Prohibited actions, privacy limits, facts not to infer and decisions reserved for a person.	Name what the AI must not guess.
7. Workflow	Required inputs, the order of work, the review point and the handoff.	Define the missing-input path.
8. Tone	The business voice in plain terms.	Check that it sounds natural when read aloud.
9. Output format	The exact shape, length and fields required.	Make the result usable without reformatting.
10. Escalation rules	Conditions that stop the task and send it to a named human role.	Give each exception a clear destination.

The order is less important than completeness. A beautifully written role cannot rescue missing source information. A perfect tone guide cannot decide whether the AI is allowed to offer a discount.

A hypothetical quote follow-up prompt

Hypothetical example, not a client result: say a home-maintenance business wants help drafting quote follow-up emails. Its reusable brief could look like this.

Role: You are a drafting assistant for the office manager. You prepare quote follow-up emails for review. You do not send them.

Business context: The business handles residential maintenance work. Use only the customer details, quoted scope and timing supplied with the task.

Goal: Draft a useful follow-up after a quote has been issued, so the customer can reply with a decision or a clear request for more information.

Audience: The recipient is a homeowner who has already received the quote.

Standards: Keep the message specific to the supplied scope. State the next step plainly. Do not add pressure or claim that availability is running out.

Constraints: Never invent a price, date, inclusion, warranty or discount. Do not add personal information that is absent from the source notes.

Workflow: Check that the customer name and quoted work are present. If required information is missing, return a short missing-information note instead of drafting the email. Otherwise prepare the draft for human review.

Tone: Plain Australian English. Warm and direct. Avoid sales jargon.

Output format: Return a subject line followed by an email of no more than 120 words. End with one clear reply option.

Escalation rules: Stop and flag the task if the notes mention a complaint, a safety issue, a scope dispute or a requested contract change. The office manager owns the next action.

Notice what is absent. There is no request to “make it amazing”. The brief describes the work and protects the boundary around it.

You can adapt the same structure to internal meeting summaries or enquiry triage. The task changes. The operating questions do not.

Test the brief before the team reuses it

A system prompt becomes useful when it survives ordinary exceptions, not when its first example looks polished.

Prepare a small test set using made-up or safely redacted information. For the hypothetical follow-up prompt, include:

• a complete quote record
• a missing customer name
• an unclear quoted scope
• a request for an unapproved discount
• a note containing a complaint

Read each result against the prompt. When a test fails, update the responsible section. Then rerun the same cases before replacing the old version.

Put a version identifier at the top of the reusable brief and name the person who approves changes. This turns quiet prompt edits into a simple business procedure rather than personal trial and error.

Know where the prompt ends

A system prompt does not connect tools or perform a workflow by itself. Nor does it guarantee every answer is correct.

If the result will reach a customer or change a business record, keep the review step explicit. If you later automate part of the process, the prompt becomes one controlled component inside that larger workflow.

The small-business AI readiness checklist can help you decide whether the underlying task is stable enough to document. If the process itself changes every week, write the process down before polishing its AI instructions.

Start with the reusable brief

The free AI Prompt Starter Guide includes the ten-part formula and a master business-assistant prompt you can adapt. Start there and build one prompt around a real recurring task.

If you want the fuller library, the AI Prompt Operating Kit is AUD $49. It adds the 59-page guide, three worked industry examples, five specialist prompt chapters and a separate copy-paste prompt file.

Build one reusable brief. Test it on the awkward cases. Keep a person responsible for the boundary.