The Blueprint · Fashion & e-commerce · People book us
For retail that sells through consultation rather than cart: fittings, styling sessions, showroom visits. The architecture, the booking path, and the master prompt.
Free, no email gate, no watermark · assembled from a curated matrix, so nothing here is invented
Retail booking sites bury the booking action inside a contact page. If the appointment is the revenue event, it belongs pinned in view at every scroll position, not one click away.
The pack below assumes the most common starting problem for this pairing: people visit, then leave without doing anything. Change it on the live generator.
Your blueprint pack · assembled, not generated · steal freely
Fashion & e-commerce · People book us · The full site, rebuilt
In fashion and e-commerce the buyer decides in a scroll. Your site has to behave like a merchandised front window: one product story in the hero, proof with names and faces near the price, and a path from home to product to cart where every objection (shipping, returns, sizing) is answered inline, never a click away.
Your revenue arrives through bookings rather than the motion this industry usually runs on. The architecture below pins the booking action and treats the category default as support, because the page has one job and it is filling the calendar.
Traffic without action is almost always a message problem wearing a design costume. The brief: one singular promise per page, one primary action repeated, proof placed exactly where doubt lives. Shorter pages with a single clear message reliably beat longer ones, so everything that does not serve the promise gets cut.
Best seller or seasonal edit, real photography, one CTA. No carousel.
Book or reserve stays in view at every scroll position, on mobile especially.
The reason to book here rather than through a platform, stated plainly beside the CTA.
Reviews with names and photos, above the fold on mobile. Press or UGC if you have it.
Four to eight products, price visible, straight to PDP.
Shallow: ten categories or fewer, imagery per tile.
Reviews near price, objection answers (shipping, returns, sizing) inline, sticky add-to-cart on mobile.
A reason to hand over the address. Never the word newsletter.
Conversion path Look, want, book, with zero leakage to third-party platforms. Every section keeps the reserve action within reach.
You are a senior web designer and front-end engineer. Build a production-grade website for my business. CONTEXT Industry: Fashion & e-commerce. Revenue arrives through bookings: appointments, reservations or stays, so the booking action must stay in view at every scroll position. The current failure is conversion: visitors arrive and leave. Enforce one singular promise per page, one primary CTA repeated, and place proof directly beside every claim and price. Scope: the full site. Build the homepage from the sections below, then derive interior pages from the same component system. PAGE ARCHITECTURE (build in this exact order) 1. Hero: one product story: Best seller or seasonal edit, real photography, one CTA. No carousel. 2. Pinned booking action: Book or reserve stays in view at every scroll position, on mobile especially. 3. Direct-booking incentive: The reason to book here rather than through a platform, stated plainly beside the CTA. 4. Proof band: Reviews with names and photos, above the fold on mobile. Press or UGC if you have it. 5. Bestseller shelf: Four to eight products, price visible, straight to PDP. 6. Category grid: Shallow: ten categories or fewer, imagery per tile. 7. The PDP standard: Reviews near price, objection answers (shipping, returns, sizing) inline, sticky add-to-cart on mobile. 8. Offer-for-email capture: A reason to hand over the address. Never the word newsletter. CONVERSION PATH Look, want, book, with zero leakage to third-party platforms. Every section keeps the reserve action within reach. NON-NEGOTIABLE STANDARDS - Largest contentful paint under 2.5 seconds. Zero layout shift. Lazy-load all below-fold media. Modern image formats (WebP or AVIF). - Mobile first: design at 390px wide, then scale up. Test every section at that width. - WCAG 2.2 AA: semantic HTML landmarks, visible focus states, 4.5:1 text contrast minimum, honour prefers-reduced-motion. - One primary call to action per page, repeated. Do not add secondary CTAs that compete with it. - Motion: at most one signature animation idea, subtle, resolving into a held state. Never animate on scroll in a way that hijacks scrolling. - Typography: one display face, one text face, maximum. Real hierarchy through size and weight, not colour. - No stock-photo cliches, no carousels in the hero, no autoplaying sound. COPY RULES - Plain English. Short sentences. Name the buyer and the outcome in the first headline. - Every claim sits next to its proof. If there is no proof, cut the claim. - Write placeholder proof slots as [PROOF: description] for me to fill with real numbers and names. Do not invent statistics, testimonials or client names. DELIVERY Build it as a fast static site (or the framework of your choice with static output). Show me the homepage first for approval before building further. List any assumptions you made.
Ideates and tests before anything is built properly. Rough pages, quick copy variants, throwaway experiments. Their job is to be wrong fast and cheap so the Builder is right the first time.
Your focus Prototype the homepage and the one money page first. The rest of the site inherits what those two prove.
Ships the real thing to the standard: the architecture above, the performance budget, the accessibility bar. Takes the winning prototype and makes it production-grade, then stops. Builders who keep building past done create the mess the Sweeper inherits.
Your focus Build from a component system, not page by page. Every page assembles from known blocks so future changes take minutes.
Prunes. Kills the sections nobody scrolls to, the pages nobody visits, the copy that hedges. Most sites fail by addition; the Sweeper is the discipline that keeps the singular message singular.
Your focus Audit quarterly: any page below meaningful traffic gets merged or killed. Fewer, stronger pages rank and convert better.
Finds product-market fit for the site itself: which messages pull, which channels feed it, which pages earn traffic. Reads the numbers the Builder instrumented, feeds winners back to the Prototyper.
Your focus Map every page to a buyer question and check monthly that each page is winning its question. Gaps become the content plan.
Keeps the ship seaworthy as it scales: dependencies, uptime, performance budgets, broken links, stale proof. Unglamorous, and the reason the site still converts in year three. Every claim on the site has an expiry date; the Maintainer enforces it.
Your focus A standing checklist run monthly: performance budget held, no broken paths, testimonials and numbers still true.
Five archetypes, not five hires. In a small business one person spans all five; the point is knowing which hat is on. Sites rot when the same person builds, grows and prunes in the same sitting without noticing the mode switch.
This is one of twenty-four published combinations. The live generator covers every industry, revenue model, problem and scope, and nothing you enter leaves the page.
Nearby blueprints