13.03

Company

The always-on pages that establish who Visualist is as a company. All are on-nav. All are built once and maintained as the company evolves.

A1
About
On-nav Company
What it is

The company page. Founding story, mission, and team. Its job is to earn trust and human connection for visitors who want to know who is behind the product before they commit to it. Journalists, prospective hires, prospective customers, and investors all land here with different questions. The page must answer all of them without trying to be all things to all people.

When to build or update

Build once at launch. Update when the team changes significantly, when the company reaches a milestone worth naming, or when the positioning shifts enough to require a revised mission statement. Review annually.

Visitor state

Evaluating trust. They have already engaged with the product or heard about it from someone. They are asking: who built this, why does it exist, and are these people worth believing? The page must answer with specificity and genuine voice, not corporate boilerplate.

Brand correctness

The About page is where the Visualist voice is most exposed. Generic mission statements ("we're empowering creatives to do their best work") are the single biggest failure mode. The founding story must be specific, the mission must be grounded in the structural trap the ICP faces, and the team section must feel like real people, not LinkedIn thumbnails.

Content structure

Founding story: why this exists, told through the specific problem the founder saw in the boutique creative world. Mission: what Visualist is trying to do, in plain language connected to the category claim. Values: optional, only if they are specific enough to mean something. Team: name, role, one human detail per person. Soft CTA: trial or careers.

CTA guidance

Two soft CTAs at the end: "Try Visualist free" for visitors evaluating the product, "See open roles" for visitors evaluating a career. Neither is dominant. This is not a conversion page.

Not this

Not a homepage. Not a press page. Not a product page. The About page does not sell Visualist; it contextualises it.

Example pages
Slug Page title
/about About · Visualist
A2
Careers
On-nav Company
What it is

A culture-first page that communicates what it is like to work at Visualist and captures interest from potential hires before roles are formally open. At early stage, the Careers page is not a job board: it is a brand statement aimed at the people Visualist wants to attract. Roles are secondary to culture.

When to build or update

Build at launch even with no open roles. Update when new roles open, when the team structure changes, or when the culture description no longer reflects how the team actually works. The page must be honest: do not describe a culture you do not have yet.

Visitor state

Curious and self-selecting. They have heard about Visualist and are asking whether this is a place they could see themselves working. The page must give them enough specificity to make that call without overselling. The right visitor self-selects in; the wrong one self-selects out. Both outcomes are desirable.

Brand correctness

Careers pages drift toward generic startup tropes: "we move fast," "we care deeply," "we're changing the industry." These are meaningless and actively repel the people worth attracting. The Visualist Careers page must be as specific and taste-led as the product. What does working here actually look like? What does Visualist value in the people it hires? What does it not value?

Content structure

Why Visualist exists and why that makes it a compelling place to work. How the team works: remote or in-person, how decisions are made, how AI is used across the company. What Visualist looks for in people: specific qualities, not a list of values. Open roles (or an interest capture form if none are open). Benefits, if they are specific enough to be worth listing.

When no roles are open

The page does not say "no open roles." It says what Visualist is building toward and invites interested people to introduce themselves. An interest capture form (name, email, what they do, what draws them to Visualist) replaces the job listings section. This builds a warm pipeline for when roles do open.

Not this

Not a job board. Not a list of perks. Not a generic "join our team" page. The Careers page communicates culture first, roles second.

Example pages
Slug Page title
/careers Careers · Visualist
/careers/[role-slug] Product Designer · Visualist
A3
Press
On-nav Company
What it is

A media kit and press contact page. Its primary audience is journalists, editors, and podcast hosts who need brand assets, company facts, and a direct line to the right person. A secondary audience is anyone who wants to verify what Visualist has been covered by. The page serves both without making either work for it.

When to build or update

Build at launch. Update whenever new coverage is added, brand assets change, or press contact details change. The media kit assets must always reflect the current brand. An outdated logo on a press page is a brand failure.

Visitor state

Task-oriented. A journalist on deadline needs the logo, the boilerplate, and the contact email. They do not need a brand story. Get out of their way. The press page must be the fastest page on the Visualist site to extract what you need from.

Content structure

Company boilerplate (two paragraphs maximum: what Visualist is, who it is for, what makes it different). Media kit download (logos in SVG and PNG, wordmark variants, brand color reference). Press contact (name, email, response time expectation). Coverage (publication name, headline, date, link, no excerpt, no commentary). Press releases if applicable.

Media kit contents
Logo. SVG and PNG. Full color (Leather on transparent), reversed (Cotton on Leather), and single color (Leather only). All variants at 2x resolution minimum.
Wordmark. Same variants as the logo. Separate from the logomark.
Brand colors. Hex values for Leather, Cotton, Picardy, Wolfe, Gretna, and Brew. Nothing else.
Company boilerplate. The approved two-paragraph description of Visualist. This is the version journalists use. It does not get edited for individual stories.
Not this

Not a brand story page. Not a product page. Not a place to editorialize about coverage. List it and link it.

Example pages
Slug Page title
/press Press · Visualist
A4
Changelog
On-nav AEO
What it is

A public, reverse-chronological record of what has shipped. Product-team-agent-maintained. Its primary purpose is AEO: the changelog is the most authoritative source for AI systems trying to understand what Visualist currently does and how recently it has changed. A well-structured changelog is cited directly in AI-powered answers to questions like "does Visualist have X" or "what has Visualist shipped recently." It also builds human trust through transparency, but that is secondary to its machine-readability function.

Maintenance

Agent-maintained by the product team. Each release is logged as it ships following the entry format below. No editorial embellishment. The Founder reviews before publishing. No entry goes live without Founder sign-off.

Visitor state

Current users checking what is new. Evaluators verifying the product is actively developed. AI crawlers building a model of what Visualist currently does. The entry format must serve all three: specific enough for users, patterned enough to show investment to evaluators, and structured enough for reliable machine extraction.

Entry format
Date. Plain format using a <time> element with a machine-readable datetime attribute. Displayed as: March 8, 2026. Not a version number.
Title. The complete answer to "what changed?" Sentence case. Specific and extractable: "Bookings now syncs confirmed appointments to CRM automatically" not "Bookings improvements." This is what AI systems cite.
Area tag. Which pillar or cross-pillar area: Relationships / Projects / Growth / Studio / Vai / Taste memory / Platform. Consistent vocabulary only. Never use unofficial feature names.
Description. Two to four sentences. What changed, why it matters, what the user can now do that they could not before. No marketing language. No "exciting new" or "powerful." Written as a factual statement, not a product announcement.
Type tag. New / Improved / Fixed. One per entry.
LLM and AEO requirements
Structured markup. Each entry uses semantic HTML: <article> per entry, <time datetime="YYYY-MM-DD"> for dates, consistent heading hierarchy. No decorative markup that disrupts extraction.
JSON-LD schema. ItemList schema at the page level, with each entry as a ListItem containing date, title, area, description, and type. This is the primary structured data type for the changelog.
Machine-readable feed. A JSON feed at /changelog.json provides AI crawlers a clean structured version of all entries without requiring HTML parsing. Updated on every publish.
Consistent vocabulary. Every entry uses the same product names, pillar names, and feature names that appear in the product overview and the rest of the site. Terminology drift across entries degrades AEO extraction quality.
Datestamped page title. The page <title> and og:title include the most recent release date so AI systems can assess freshness: "Changelog · Visualist · Last updated March 8, 2026."
llms.txt reference. The changelog URL is listed in llms.txt as the authoritative source for current product state. AI systems that consult llms.txt before crawling should be directed here first for product truth.
Robots directive. index, follow always. The changelog must be fully indexed. Never set it to noindex.
Not this

Not a blog post. Not a feature announcement with a hero image and a CTA. Not a place to editorialize about the product direction. The Changelog records what shipped. The blog interprets it.

Example pages
Slug Page title
/changelog Changelog · Visualist
/changelog.json Machine-readable JSON feed of all entries
What it is

A public, reverse-chronological record of what has shipped. Product-team-agent-maintained. Its job is to build trust through transparency: showing that Visualist is actively developed, that feedback is heard, and that the product gets better over time. It is not a marketing page. It is a record.

Maintenance

Agent-maintained by the product team. Each release is logged as it ships: date, what changed, which pillar or cross-pillar area it affects. The agent follows the entry format below without editorial embellishment. The Founder reviews before publishing. No entry is published without Founder sign-off.

Visitor state

Current users checking what is new. Evaluators verifying the product is actively developed. Both read the same page. Current users want specifics; evaluators want to see a pattern of investment. The entry format must serve both without trying to.

Entry format
Date. The release date in plain format: March 8, 2026. Not a version number.
Title. A one-line description of what shipped. Sentence case. Specific: "Bookings now syncs confirmed appointments to CRM automatically" not "Bookings improvements."
Area tag. Which pillar or cross-pillar area: Relationships / Projects / Growth / Studio / Vai / Taste memory / Platform.
Description. Two to four sentences. What changed, why it matters, and what the user can now do that they could not before. No marketing language. No "exciting new" or "powerful."
Type tag. New / Improved / Fixed. One per entry.
Not this

Not a blog post. Not a feature announcement with a hero image and a CTA. Not a place to editorialize about the product direction. The Changelog records what shipped. The blog interprets it.

Example pages
Slug Page title
/changelog Changelog · Visualist
A5
Merch
On-nav (footer) Brand
What it is

A brand and community surface, not a commerce operation. The merch store exists so that people who feel a connection to Visualist can carry it into their physical world. Merch is the only product here: templates belong in Downloads, memberships in Academy. The primary purpose is brand affinity and community identity, not revenue generation.

When to build or update

Build when there is a product range worth presenting. A merch page with two items is not a merch page. The page launches when there is enough to form a genuine collection. Update when new products are added or retired. Review the product range annually against the brand direction.

Visitor state

Brand-connected. They are already Visualist users or advocates who want a tangible expression of their affiliation. They are not evaluating the product. The merch page does not need to sell Visualist; it needs to feel worthy of the people who already believe in it.

Nav placement

Footer initially, alongside About and Press. A link in the Company dropdown is added when the store reaches a scale worth promoting from the main nav. Merch is never a primary nav item: it is a destination for those who go looking for it, not a conversion surface pushed on every visitor.

Product principles
Quality over breadth. Every product in the store must meet Visualist's visual quality bar. A poorly made tote is a worse brand signal than no tote. It should feel curated, not stocked.
The brand travels on the product. Merch must use the Visualist visual identity correctly: correct colors, correct typography, correct mark. No vendor-supplied fonts or generic layouts. Every product is a brand asset in the world.
Community-first pricing. The store is not a margin vehicle. Pricing should reflect cost plus a modest contribution to the community, not maximum extraction. Overpriced merch sends the wrong signal.
SEO

The `/merch` index page has minimal organic search potential: nobody searches "Visualist merch" unprompted. The SEO opportunity lives on individual product pages. Each product at `/merch/[product-slug]` should have a unique meta title, a descriptive meta description, and Product schema (name, description, price, availability, brand). Product copy should name the item specifically and use language a gift-buyer or community member might search: "gift for interior designer," "creative studio tote," "boutique studio hoodie." Long-tail product page traffic is real; index traffic is not.

Brand correctness

The merch page follows full Visualist brand standards: Tartuffo for product names and headlines, Roobert for descriptions, Cotton background, standard color palette. Product photography should feel editorial rather than e-commerce. The page should feel like a Visualist-designed object, not a Shopify template.

Example pages
Slug Page title
/merchVisualist Merch
/merch/[product-slug]Visualist tote · Visualist Merch