Solutions Pages
Three page types that help visitors find Visualist through the lens of their profession, their job, or their studio stage. All are always-on, on-nav, and built for depth.
Solutions pages live under the Solutions nav and help visitors understand whether Visualist is right for their specific situation: by professional field, by the job they need to do, or by the size and stage of their studio. All three are always-on, on-nav, and built for depth.
A By field page speaks to a specific professional field: interior designers, personal stylists, or wedding and event planners. It is the full vertical narrative, accessible via the Solutions nav. Its job is identity recognition: making the visitor feel seen as a professional before introducing the product.
Build one per live vertical at launch. Update when a significant product change affects how Visualist serves a specific field. Review annually at minimum.
Curious and identity-matching. Asking: is Visualist for someone like me? Arrived from organic search, a referral, or the nav. Has not yet decided Visualist is relevant.
Identity headline naming the visitor by profession. The structural trap named precisely for this vertical (source from ICP definition). How Visualist solves it (feature to workflow moment translation). Social proof from this vertical. Links to Field x Use case pages. Soft CTA.
"Try it free" or "See how it works for [profession]." Soft pressure. One at the end. Never use internal persona names (Peyton, Indigo, Emery) in the CTA.
Never use internal persona names in page copy. Each vertical page must be specific. If copy could be swapped between two verticals without editing, rewrite it. Frustration language must be sourced from the ICP definition. Do not mention proposals as a strength.
Not a Field campaign page (E2): this is nav-accessible and built for depth. Not a Field x Use case page (E1). Not a homepage.
| Slug | Page title |
|---|---|
| /for/interior-designers | Visualist for interior designers |
| /for/personal-stylists | Visualist for personal stylists |
| /for/wedding-planners | Visualist for wedding and event planners |
A By use case page addresses a specific job to be done: moodboarding, client communication, project management, wardrobe management. Accessible via the nav, built for visitors who know what they need to do but may not identify with a specific profession.
Build for the use cases most central to the product at launch. Add pages as the product expands. Update when the product's handling of a use case changes significantly.
Job-aware and evaluating fit. Knows what they need to do. May or may not have identified as a specific professional type.
Use case headline (functional and searchable). How Visualist handles this use case (answer first). ICP specificity earned through the three verticals naturally. Feature breakdown for this use case (2-4 features, each with name, description, and connection to workflow). Field x Use case links per relevant vertical. Soft CTA at the end.
"Try it free." One CTA placed after the ICP specificity section, not before.
High brand drift risk. Every sentence must pass the tone test. Do not let the page read as if Visualist is for any small business. Do not list features not live for this use case.
Not a Field x Use case page. Not a Category page.
| Slug | Page title |
|---|---|
| /solutions/client-management | Client management for creative studios · Visualist |
| /solutions/moodboarding | Moodboarding with Visualist · Visualist |
| /solutions/project-delivery | Project delivery for boutique creatives · Visualist |
A By stage page speaks to a visitor based on the size and structure of their studio, not their profession. Two pages: Solo Operator (one person running everything) and Small Studio (two to five people). A visitor arrives because they recognize their studio structure and want to know whether Visualist is designed for it.
Build two Stage pages: one for Solo Operators and one for Small Studios. Update when the product's value proposition for a specific studio size changes. Review annually.
Studio-size aware and evaluating. Knows they run a solo studio or a small team. Must confirm within the first scroll that the page understands their structural reality.
Stage identity headline (name the studio type directly). The structural trap for this stage (Solo: capacity ceiling; Small Studio: coordination problem). How Visualist helps at this stage (feature-to-problem translation specific to studio structure). The path forward (concrete, not vision). Social proof from this stage. Soft CTA.
"Try it free." Soft pressure. One at the end.
Structural trap narrative must be specific to the stage. Do not conflate Solo Operator and Small Studio pain. Source stage-specific language from the ICP definition.
Not a Field page. Not a pricing page.
| Slug | Page title |
|---|---|
| /solutions/solo-studio | Visualist for solo operators |
| /solutions/growing-studio | Visualist for growing studios |