The Blueprint · Professional services · People sign themselves up
Monthly seats, retainers and subscription advisory need a signup path, not a sales process. The architecture that supports it.
Free, no email gate, no watermark · assembled from a curated matrix, so nothing here is invented
Retained services describe the relationship and never state what arrives each month. A named cadence and a named artefact convert far better than the promise of access.
The pack below assumes the most common starting problem for this pairing: the site is a bottleneck: every change takes weeks. Change it on the live generator.
Your blueprint pack · assembled, not generated · steal freely
Professional services · People sign themselves up · A site that runs as a growth engine
Professional services sell on specificity. Name exactly who the work is for and who it is not for, show the method as named steps, and put numbers and names behind every claim. Qualified buyers convert because they feel understood; unqualified ones filter themselves out, which is a feature.
Your revenue arrives through self-serve signups rather than the motion this industry usually runs on. The architecture below puts the product itself in the first viewport, because nobody signs themselves up for something they have not seen working.
A site the team cannot change is a liability compounding weekly. The brief includes the operating layer: a component system where pages assemble from known blocks, content editable without a developer, and a publishing path measured in minutes. The redesign matters less than the rebuild of how changes ship.
Who you serve, what changes, why you. If it could hang on a competitor site, rewrite it.
Real interface, moving if possible. A 60 to 90 second product film beats any feature grid.
Tiers on the page and a single conversion verb used site-wide. Hidden pricing filters out the buyers you want.
Name the ideal client and the wrong fit. Specificity converts and filters at once.
Your process as named steps. A named method reads as owned IP.
Results, clients, tenure. One strong case beats six vague logos.
Packages or entry points with from-pricing. Vague scope reads as vague thinking.
An audit, a consult, a scored review. A specific first step, never a bare contact form.
Conversion path Hero promise, see the product, believe the proof, check the price, sign up. Every section moves that sequence forward or gets cut.
You are a senior web designer and front-end engineer. Build a production-grade website for my business. CONTEXT Industry: Professional services. Revenue arrives through self-serve signups: trials and demos, so the product itself must be visible in the first viewport. The current failure is changeability: build everything from a reusable component system with content editable in one place, so a non-developer can ship a page change in minutes. Scope: the full site plus the growth layer: analytics events on every conversion action, an email capture with a real incentive, and a content section structured one buyer question per URL. PAGE ARCHITECTURE (build in this exact order) 1. Hero: the position, one sentence: Who you serve, what changes, why you. If it could hang on a competitor site, rewrite it. 2. Product in the first viewport: Real interface, moving if possible. A 60 to 90 second product film beats any feature grid. 3. Pricing, transparent, and one signup verb: Tiers on the page and a single conversion verb used site-wide. Hidden pricing filters out the buyers you want. 4. For and not-for: Name the ideal client and the wrong fit. Specificity converts and filters at once. 5. The method, named: Your process as named steps. A named method reads as owned IP. 6. Proof with numbers and names: Results, clients, tenure. One strong case beats six vague logos. 7. Engagement tiers: Packages or entry points with from-pricing. Vague scope reads as vague thinking. 8. Diagnostic CTA: An audit, a consult, a scored review. A specific first step, never a bare contact form. CONVERSION PATH Hero promise, see the product, believe the proof, check the price, sign up. Every section moves that sequence forward or gets cut. 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 Run a standing experiment queue: one landing page or message test in flight at all times, findings fed to the Grower.
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 the measurement in from day one: events on every conversion action, so the Grower argues from numbers.
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 Sweep the experiment backlog too. Losing tests get documented and closed, never left half-running.
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 Own the loop: lifecycle flows, content cadence, channel spend, all reviewed against one page of numbers each month.
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 Formal SLOs: speed, uptime and data accuracy tracked like revenue, because at this scale they are revenue.
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