The five pillars of a prompt that actually works

If your AI keeps giving you generic, slightly-off answers, the problem is almost never the AI. It is that it was asked a vague question and did its best.

This is usually called prompt engineering, which makes it sound like a technical discipline. It is not. It is five things, and once you know them you use them without thinking.

The five pillars

Every prompt worth writing has these:

1. Expert. Who should it be while it answers. A copywriter, a bookkeeper, a client relationship manager.
2. Task. The specific thing to do. One thing, stated plainly.
3. Context. What it needs to know that it cannot see. The situation, the history, the constraints, your tone.
4. Output. What you want back, and in what shape. Length, format, how many options.
5. Goal. What this is for. What has to be true after someone reads it.

Most people write only the task. That is why the results feel like they could have been written for anyone, because they were.

What weak looks like

Write an email to my clients about the price increase.

There is nothing wrong with this except that it is missing four of the five. No role, no context, no shape, no purpose.

The AI does not know who the clients are, how long they have been with you, whether this is your first increase or your fourth, whether you want warm or formal, how long it should be, or what a good outcome looks like. So it invents all of it, plausibly and blandly, and you get something you have to rewrite.

What strong looks like

You are a client relationship manager for a small service business.

Draft an email telling my existing clients that the monthly retainer rises from $1,500 to $1,750 from 1 November.

These are eleven long-standing clients, most with me two years or more. It is the first increase in three years and it covers the added reporting they have been asking for. My tone is warm and direct, and I do not over-apologise.

One email, under 200 words, plain text, no subject line options, ready to send.

Nobody should feel blindsided, and nobody should need to reply to understand it. They read it once, understand why, and carry on.

Same request. Five pillars instead of one. The result comes back close to sendable, because everything it needed to know was on the page.

Note that none of that is technical. It is the briefing you would give a good assistant, written down.

Speak literally

The one habit that separates people who get good results from people who do not: an AI will do exactly what you say.

It does not read between the lines, it does not know what you obviously meant, and it will not quietly correct your instruction to the thing you actually wanted. If you say “make it shorter” it will make it shorter, possibly by cutting the part that mattered. If you say “under 200 words” it will hold that line.

Being specific is not being bossy. It is the whole skill.

Where this gets more powerful

The five pillars matter most when the AI can actually see your work.

Asked cold, the Context pillar is you typing out the background every time. Connected to your inbox, your calendar and your files, most of the context is already there, and it stops being something you supply and starts being something it already knows.

That is the point at which prompting gets shorter rather than longer, because the AI holds a memory of your business and you only have to say the new part.

Keep them where you can see them

Expert. Task. Context. Output. Goal.

Put them somewhere you will see them for the first couple of weeks. After that you will do it automatically, and going back to one-line prompts will feel like briefing someone with your eyes closed.

This is Step 8 of Saviwith Foundations. The five pillars are most of the value on their own, and they get considerably more useful once your AI is connected to the tools your work actually lives in.

Thirteen steps, at your own pace, lifetime access.

Start your course now · $497