Build sites that feel designed, not generated.
brief/ studies real category leaders, then turns their anatomy into page strategy, visual direction, proof requirements, and launch-ready build prompts.
Sites studied
830+
Categories
15
Viewports
3
live category scan
SaaS homepage blueprint
section plan
ready to buildHero
show product outcome
01
Proof
add dashboard evidence
02
Workflow
map the process
03
CTA
choose one next action
04
taste score
92
specific visual proof
prompt pack
generated visual brief
Product proof first.
Replace abstract hero art with a workflow screenshot, outcome metric, and proof card the buyer can understand immediately.
Captured sites
830+
Industry maps
15
Viewports
3
Product
brief/ turns research into instructions a website can actually use.
Category read
What strong pages in the buyer's market consistently show, avoid, and prove.
Page anatomy
The section sequence, message priority, proof burden, and conversion path.
Visual requirements
The screenshots, diagrams, charts, images, and crops the site needs to feel real.
Builder handoff
Specific prompts and page instructions a designer or AI builder can execute.
Client paths
One simple front door. Three valuable outcomes.
01
Start a new website
Turn business context into page strategy, copy hierarchy, visual requirements, proof objects, and builder prompts.
Open workflow
02
Audit an existing site
Submit a URL and get a category-aware critique of what feels generic, under-proven, confusing, or visually weak.
Open workflow
03
Judge the finished build
Run the launched or staged site back through brief/ to see whether it honored the original blueprint.
Open workflow
Visual direction
Every section gets a visual job before anything gets built.
That is the difference between "AI made a page" and "a designer knew what this section had to prove."
before
after
Hero visual proves the workflow and shows a measurable outcome.
Visual asset
workflow screenshot
Proof object
metric + customer receipt
The output
A blueprint a builder can execute.
Page blueprint
Section order, message hierarchy, CTA path, and proof burden.
Visual brief
The images, screenshots, diagrams, charts, and crops each section needs.
Taste read
Spacing, density, contrast, type rhythm, polish, and category fit.
Build prompts
Specific instructions a human or AI builder can execute without guessing.
Taste becomes visible when the page proves something.
brief/ looks for the things humans notice before they can name them: spacing, density, polish, useful visuals, proof, and the absence of generic filler.
Hero
Product outcome
Show the result the buyer gets in the first viewport.
Proof
Evidence stack
Pair claims with dashboards, quotes, metrics, logos, or workflow receipts.
Workflow
Process map
Make the buyer understand the sequence without reading a wall of text.
Pricing
Decision path
Expose the offer clearly enough that the next click feels obvious.
Pricing