Better prompts, fewer revisions: a faster way to build your website
A reusable brief for getting a more useful first draft and making precise design changes.
Raccog TeamWriter at Raccog5 min readUpdated 23 September 2026
The quickest path to a useful website draft starts before generation: make the important decisions explicit. Raccog can work from a short description, but a focused brief helps it avoid guessing about your audience, content and layout.
Most wasted revisions come from the same place. The builder had to guess something, guessed reasonably, and guessed differently from what you pictured. A brief is how you stop paying for that.
Give your brief five ingredients
Include the business, audience, pages, visual direction and primary action. These are practical constraints the builder can use throughout the site.
Build a website for a freelance product photographer. The audience is small ecommerce brands. Include Home, Portfolio, Packages and Contact. Use a restrained white background, charcoal text and a teal accent. Make requesting a quote the main action. Use placeholder images and leave package prices for me to fill in.
You can keep the structure and replace the details for a restaurant, agency or local service business.
Each ingredient decides something specific:
| Ingredient | What it settles |
|---|---|
| Business | The vocabulary, and which pages are conventional for the trade |
| Audience | Reading level, tone, and which objections the copy answers |
| Pages | Scope — and, just as importantly, what is not built |
| Visual direction | Palette, contrast and how loud the design gets |
| Primary action | Where every page points and what the buttons say |
Leave one out and the builder fills it in. That is not a failure — it is what a brief with a hole in it asks for.
Be specific where it matters, loose where it does not
A brief is not a specification. Over-constraining it costs you the useful part: the draft that shows you an option you had not considered.
Worth pinning down: page list, audience, primary action, anything factual (hours, service names, locations), anything you are legally careful about.
Worth leaving open: section order within a page, exact headline wording, illustration choices, how many columns a grid uses. Let the first draft propose, then correct.
Tell the builder what content is real
If you have approved copy, business hours or service descriptions, include them. If information is missing, ask for a visible placeholder. This makes it easier to distinguish content ready to publish from content that still needs your attention.
A sentence that saves a lot of cleanup later:
Use clearly marked placeholders for anything I have not given you, and do not invent testimonials, client names, awards or statistics.
Avoid asking the builder to invent reviews, awards or customer results. A convincing layout does not need unsupported claims, and a claim you cannot support is the one thing on the page that can cost you.
Group related feedback
Review the first draft in passes. First check the page structure and content. Next look at typography, spacing and color. Finally test mobile navigation and the main action.
A focused revision might be:
On the Packages page, show three comparable options with the same information order: who it is for, deliverables and turnaround. Keep prices as placeholders. Use the existing typography and accent color.
This is easier to assess than a long list of unrelated edits across every page. Three short prompts that each change one thing will usually land faster than one long prompt that changes twelve.
Say what to keep, not only what to change
The most common surprise in a revision is collateral damage: you asked for a new hero and the navigation changed too. Naming what stays fixed prevents it.
Replace the hero image with a wide photo placeholder and keep the headline, the navigation and the section order exactly as they are.
"Keep the existing typography and accent color" is worth adding to almost every design revision.
Reuse the brief for new pages
When adding an FAQ or a new service page, repeat the relevant audience and style constraints. Ask the builder to reuse the existing navigation and link the new page from the appropriate section.
Add an FAQ page for the same ecommerce audience. Answer six questions about turnaround, licensing, reshoots, file formats, travel and payment. Match the existing type and spacing, add it to the main navigation, and link it from the Packages page.
A brief you can copy
Keep this as a starting template and fill in the brackets.
Build a website for [business] serving [audience]. Include [page list]. Use [colors and visual direction]. Make [primary action] the main action on every page. Use this copy where I have given it: [facts, hours, services, prices]. Use clearly marked placeholders for anything else, and do not invent testimonials or results.
Good prompts do not remove the need for judgment. They reduce avoidable revisions by making your intentions clearer from the start.
Common questions
Is a longer prompt always better? No. Length helps only where it removes a guess. A 400-word brief full of adjectives is weaker than an 80-word one that names the audience, the pages and the action.
Should I write the copy myself? Write the parts that are claims — prices, guarantees, credentials, availability. Let the draft propose the connective writing, then edit it in your own voice.
What do I do when a revision makes something else worse? Say what you want restored and what you want kept, in the same prompt as the next change. Correcting forward is usually faster than undoing.
Try it on your own brief.
One sentence about the business, and Raccog drafts the whole site.
Read next