Architecture
Prompt for an architect website
A Claude or ChatGPT prompt to build the website of an architecture practice: the work before the words, a sheet per project that carries the whole site, and the way a project actually begins.
In short
For an architecture practice whose built work is the argument. Gets your assistant to build a project index with images first and one sheet per project (programme, place, year, surface, role, credited photographs), the practice, and how a project starts. Published with SayLive.
What this prompt asks your assistant to build
Written as you would say it. Paste it as is, then answer what your assistant asks.
I want a website for my architecture practice, built in this conversation and published with SayLive. Our built projects are the argument: the people who hire us look at the work first and read about us second. The site must show the work in a way that holds, and say how a project starts with us. Before writing. Look us up (our registration, the professional body, the press, the competitions), tell me what you found, and ask me one question at a time for the rest: which projects can be shown and which are under a confidentiality clause, the facts of each project (programme, place, year, surface, our role), who holds the rights to each photograph, and the exact registration wording required where we practise. Never present a render as a photograph and never invent an award. Then propose the site plan, page by page, with what each page says and where it links. I validate, then you write. The pages. A project index with images first and the least possible text: the projects, not a brochure. One sheet per project, which is the template that carries the whole site: programme, location, year, surface, client type, our mission (full or partial), the photographs with their credits, two paragraphs on what the project solved. The practice: the people, the approach, what we refuse to do, our registrations. Contact: how a project actually begins, what to send us for a first conversation, with a form. And a short FAQ: do you take small projects, how are fees structured, how long does it take. The tone. Sober and factual. The buildings speak; the text names, dates and measures. No "passion for spaces". So people find us. Write what people type: architect and the city, house renovation architect, extension, the kinds of programme we take. One title and description per page, one H1, each project sheet titled with the programme and the place, and the registration in the footer of every page. Technically. A static site where images are the point and still load fast: WebP, resized to the display size, lazy-loaded below the first screen, each sheet under 400 KB on first view. Every photograph with its alt text and its credit. No third-party script, no cookie banner. With SayLive. I give you the photographs through the media library, in the order I want them shown. When I say publish, publish and give me the address. I reread on a laptop and a phone, you fix and republish; if a version is worse, we go back to the previous one. When I am happy, I connect our domain.
What to have at hand before you paste it
- Your business name, address, opening hours, phone and email.
- Five to ten photographs you own the rights to.
- Three concrete proofs: years in business, a certification, a number that means something.
- For each project: programme, place, year, surface, your role, and who took the photographs.
With SayLive, even better
What you get with SayLive on top
This prompt is enough: pasted into any assistant, it gets you a good site. Connected to SayLive, the same assistant works with what is held back here, with nothing to install:
- The SayLive skills, loaded by themselves: the research on your business before a line is written, the floor a page has to reach, the SEO plan with its queries and internal links, the structured data, and the critical review the assistant gives its own work before publishing. Included with every site.
- The Blueprint "Architect": what a specialist of your trade knows and this prompt does not say. The questions to ask before the first line, the pages a site of this kind needs, what goes wrong in this trade, and the claims never to make unchecked. Bought once, for the site, 29.
- Alma, our designer agent: an art direction that holds from one conversation to the next, rather than your assistant's default style. Recruited once, 99.
- A human, if you want one: the Boost, 499 per expert day, when you would rather have a person take the site in hand.
And with every published site: 150 publications, 50 MB of media, 50 form messages, 50 review tickets, your own domain connected, and the previous version back in one sentence.
Frequently asked questions
How many projects should the site show?
Fewer, better documented. Six complete project sheets beat thirty thumbnails; the prompt asks your assistant to build the sheet as the template that carries the site.
What about photo credits?
They are compulsory in practice and a real claim from a photographer when missing. The prompt tells your assistant to ask who shot each project and what the licence allows online.
Renders or photographs?
Both, clearly told apart. A render presented as a photograph is the one thing a client remembers against you.