How to Create Marketing Images With AI: Prompts and Edits
A repeatable three-step routine for turning a plain idea into a usable marketing image, then keeping every image after it consistent with the first.
The useful question is not what AI can do at work. It is which parts of your week it can take, and what you must never hand it.
Most advice about AI at work is written at the altitude of “transforming industries,” which is unhelpful when what you have is a Tuesday, a full calendar, and a report due Thursday.
Here is the ground-level version: four categories of work where it reliably helps, and the boundaries that keep it from becoming a problem.
The recurring, low-judgment writing that eats an hour a day in ten-minute pieces.
Turn these notes into a project update for a client who is not technical and is slightly anxious about the timeline: [notes]. Lead with status, be specific about what's done and what's next, name the one risk without alarming them, and end with what I need from them. Under 200 words, plain language.
I need to tell a colleague their section of the deck isn't good enough and has to be redone by Friday. We work together often and I don't want this to be weird. Write three versions at different levels of directness, and tell me which you'd send and why.
Three versions is the move for anything socially awkward. Seeing the range makes the right register obvious in a way that describing it does not.
Here's my rough thinking on why we should change our onboarding process: [brain dump]. Don't write it up yet. First tell me: what's the strongest version of this argument, what's the obvious objection, and what evidence would I need to make it land with a finance-minded director? Then give me a structure.
Structure before prose, every time. A well-argued memo with mediocre sentences beats a beautifully written one with a hole in the middle.
Here's the quarterly data. Tell me the three things that actually changed, what's within normal variance, and what a skeptical director would ask about these numbers. Then give me a slide outline — one message per slide, stated as a sentence, not a topic. Flag anything where the data doesn't support a strong claim.
“One message per slide, stated as a sentence” is the single most reliable improvement to any deck.
Check every number it repeats back. Arithmetic on pasted tables is a known weak point, and a wrong figure in a board deck is the kind of error that gets remembered.
I've been moved onto a project involving [unfamiliar area] and I have two days. Explain it as if I'm competent but new: what it is, how it works, the vocabulary I need to not sound lost, the three things practitioners argue about, and the five questions I should ask in my first meeting that would reveal whether the project is in good shape.
The questions are the valuable output. Being able to ask a good question on day one is worth more than being able to summarize the field.
Here's a 60-page vendor report I need to have an opinion on by tomorrow. Give me: what they're claiming, what evidence they provide, where the evidence is weaker than the claim, and what a careful reader would push back on. Quote the specific passages.
Confidentiality. Do not paste client data, personal data about colleagues or customers, credentials, unreleased financials, or anything under NDA into a tool your employer has not approved. This is the most common way people create a real problem, and it happens casually — usually in a hurry, on a Thursday.
Check your organization’s policy. If it does not have one, ask. “I asked and was told it was fine” is a considerably better position than the alternative.
Accuracy. Anything with a number, a date, a citation, a name, or a legal consequence gets verified. Your name is on the output regardless of how it was produced.
Judgment. Performance reviews, hiring decisions, disciplinary matters, and anything affecting a specific person’s livelihood. Use it to think and to phrase; do not use it to decide.
Attribution. Norms vary widely by workplace and role. Find out what yours are before you need to explain yourself.
Meetings that should have been emails, unclear priorities, a manager who changes their mind weekly, and too much work for the hours available. AI raises throughput. If the problem is direction rather than volume, more throughput makes it worse.
File Assistant for supported reports, contracts, and vendor documents. AI Research for current questions where model recall may be stale. The Business Planner and Interview Coach assistants provide starting points for structured work conversations. Voice Chat offers another way to think through a problem. Keep role and project context in the current conversation, subject to your employer’s data rules.
Check your policy first — many organizations now have one, and several require disclosure. Confidential data is the harder line: that one is not a matter of etiquette.
Pasting confidential information into an unapproved tool. Second is publishing an unverified factual claim under your own name.
Producing better work faster does not look lazy. Producing obviously generated work that you did not check looks exactly like what it is.
Routine writing, document comprehension, structuring an argument, and getting oriented in an unfamiliar area. In most jobs that is a meaningful share of the week.
The work worth handing over is the work your employer is not actually paying you for — the drafting, the formatting, the reading, the reorienting. What is left is judgment, relationships, and decisions, which is the part that was always the job.
Try it in ChatUp
Run the prompts above against the model that suits the task, keep the useful context across chats, and pick it back up on any device.
Try for Free