New Special, Same Look: Stop Rewriting Your Restaurant Promo Brief

Last Thursday's post already had a look. Cool light, a tight crop on the plate, the special named in the first line. This Thursday the fish changes. The look does not. The slow part is opening a blank chat and typing the light, the crop, and the rules again, then moving the result into another tool to see if it matches.

A shop, a studio, and a listing desk run into the same restart. The special, the class, or the property is new. The way the posts should look was settled last time.

1. What the first try is actually asking for

The hope is one sentence and a finished promo. Type "Thursday fish special" and receive a clip that already knows the room. The start does not work that way.

A Topview Bot keeps a creative brief you have already settled, and it can bring that brief in from ChatGPT, from Claude, or from a Board you already use. You still say what this week is. "Fish" is not enough. The plate, the light, and whether anyone is in the frame have to be in the note, or the result is a generic dish on a generic table.

The other hope is that you will download the clip, upload it somewhere else, and ask a chat whether it matches. On the Board, the conversation and the generation stay in one place. A result the product supports can go into the next task without that download and upload. You still watch it. A connected page does not approve the shot for you.

2. Where the first session slows down

The first slowdown is the sentence. Last week's post lived in your head as "our usual." The Bot does not inherit "our usual" until you have told it, or until you have pointed it at work you already did. Low, cool light and a tight plate is a preference it can remember. It is not a preference it can guess from the word special.

The second slowdown is the reference. You can picture the shot, a wet street outside the door, a hand setting the plate down, and still not have a frame for it. You describe that picture in ordinary language. The Bot searches the film references it can reach, and it can also look through image results and Pinterest. Which of those come back depends on the task and on how the product is set. A frame you find is a reference for the look. It is not a clip from someone else's film that you can post as the special.

The third slowdown is the pile. References, storyboards, and finished shots land on the Board. You can ask the Bot to group them. You still check that the Thursday fish did not get filed with last month's dessert.

A generated dining room is not tonight's service. It is not a photograph of the plate you will serve, and it is not a guest who agreed to appear. If the post needs the real dish, use the real dish. Use the generated shot when you need a planned picture, and say so if a viewer could mistake it for the service.

3. What you stop retyping on the second post

Once the look is in the Bot, the next special starts from that memory. Lighting, color, and pacing do not have to be briefed again unless this week is supposed to look different. You change the dish. You leave the house style.

If that style already lives in ChatGPT or Claude, or on a Board from an earlier project, the Bot can start from those preferences instead of from a blank description. You still read what it kept. A note saved for a dark dinner can be wrong for a bright lunch special.

When the same steps keep coming back, find references, plan the shots, make the assets, the Bot can store that sequence as a Skill and run it again. The page does not ship a finished skill called "restaurant special." You save the steps you actually repeat. A Skill is the sequence. Memory is the look. They answer different questions.

4. The three starts on the page

The page does not publish a diary of someone else's first month. It publishes three starts.

You open the Bot from the homepage, from a Bot conversation on the Board, or from the floating assistant while you are already creating.

You make it yours. You say what you are making, you give the visual preferences, or you bring preferences in from a workflow you already use.

You put it to work. You ask for references, a storyboard, the assets, or a Board that has been grouped. More than one Bot can take separate jobs at the same time, and supported shots can generate together, when the model and the account allow it. The first special needs one look and one clear dish. A queue of Bots can wait.

5. When the saved look is worth keeping

Keep it if the same look returns every week. A restaurant special, a class timetable, a listing, a product post: the item changes, and the style should stay the one you already set. The time you get back is the retype. You still watch the shot.

If you will make one post and never match it again, there is little for the memory to do next time.

If a second person publishes the specials, the page says you will be able to share a Bot that already has the preferences and the methods. That share is marked as a preview. What travels with the Bot, who can open it, and when it is finished can still change. Until then, the saved look lives in the Bot you set, and the other person still needs the brief.

The page does not print a price for this start. Whether it belongs in the week depends on how often you would otherwise retype the look.

6. The dish in the post still has to be yours

Name the special you actually sell. Keep the light and the crop you already use. Ask for a reference when you can picture the shot and cannot find it. Group the pile when the Board is the thing slowing you down. Watch the result before it goes on the shop's page.

The clip can plan the promo. It does not take the place of the plate, the room, or a guest. Last week's look can stay. This week's fish has to be the fish you have.