Jan Six

Executive Summary

As a Marketing Strategist, I have analyzed your landing page at jansix.at. My review focuses on how effectively you convert cold traffic into engaged prospects, clients, or users.

While the minimalist aesthetic is visually pleasing, the page currently functions more as a digital business card than a high-converting landing page. It relies heavily on your existing industry reputation rather than actively selling your expertise.

Below is a brutally honest, actionable breakdown of your hero section, value proposition, and overall conversion strategy.

1. Hero Text Effectiveness & Value Proposition

The hero section is the most critical real estate on your website. Currently, it leans too far into minimalist design at the expense of clear, compelling copywriting.

The 5-Second Test Failure

Problem: A cold visitor cannot immediately determine the specific business value you provide within the first 5 seconds. Stating your name and title (e.g., "Design Systems Engineer") tells them what you are, but not why they should care.

Why it matters: Users leave web pages in 10-20 seconds unless a clear value proposition captures their attention. If you don't instantly communicate the problem you solve, potential high-ticket clients will bounce.

Recommended fix: Transition your copy from "identity-driven" to "benefit-driven."

• State exactly who you help (e.g., SaaS teams, enterprise design teams).
• Highlight the core outcome of your work (e.g., scaling design, reducing engineering handoff time).
• Keep the subheadline focused on the tangible tools or methods you use (like Tokens Studio/Figma).

Resources to help:

• CXL: How to Write a Great Value Proposition
• Nielsen Norman Group: How Long Do Users Stay on Web Pages?

2. Above the Fold First Impression

The visual hierarchy above the fold dictates where the user's eye travels. Currently, the lack of directional cues creates a passive browsing experience.

Missing the "Hook"

Problem: The first impression is clean but sterile. It doesn't hook the visitor or guide them toward a specific action, causing unnecessary friction and cognitive load.

Why it matters: Cognitive fluency dictates that users prefer websites that are easy to understand and navigate. A lack of clear direction causes confusion, which kills conversion rates.

Recommended fix: Restructure the above-the-fold layout to guide the user's eye directly to your value and CTA.

• Add a small "social proof" element above the headline (e.g., "Creator of Tokens Studio, used by 100k+ designers").
• Ensure high contrast between the background and your primary headline.
• Use an F-pattern layout to naturally guide the eye from the logo to the headline, and down to the CTA.

Resources to help:

• CrazyEgg: Understanding the F-Pattern Layout
• Copyhackers: How to Write a Homepage Headline

3. Target Audience Alignment

Your messaging currently assumes the visitor already knows who you are and what you do. This alienates potential enterprise clients or founders who need your specific design system expertise but aren't deep in the Figma community.

Speaking to Pain Points

Problem: The copy lacks empathy for the visitor's pain points. Enterprise clients don't just want a "Design System"; they want to stop wasting developer hours and fix inconsistent UI.

Why it matters: People buy solutions to their problems, not titles. Tailoring your messaging to specific pain points increases resonance and conversion likelihood.

Recommended fix: Explicitly address the friction your target audience faces.

• Identify your ideal client (e.g., VP of Product, Lead Designer).
• Mention the pain point in the subheadline (e.g., "Stop wasting time on manual UI handoffs").
• Showcase a brief case study or metric of how you solved this for a past client.

Resources to help:

• HubSpot: How to Find Your Target Audience
• Unbounce: Pain Point Copywriting

4. Call to Action (CTA) Optimization

A beautiful portfolio is useless if it doesn't clearly tell the user what to do next. Your CTA strategy is currently too passive.

Weak Primary Actions

Problem: Standard portfolio CTAs like "Contact Me" or a simple email link are low-intent and uninspiring. They require the user to do the heavy lifting of figuring out what to say.

Why it matters: A strong, action-oriented CTA reduces friction and explicitly tells the user what happens when they click. Friction at the CTA stage leads to massive drop-offs.

Recommended fix: Upgrade your CTA to be high-contrast, prominent, and benefit-driven.

• Make the CTA a distinct, high-contrast button, not just a text link.
• Change the copy from a generic action to a value-driven action.
• Add a secondary, lower-commitment CTA (like "View my recent case studies").

Resources to help:

• VWO: Call to Action Best Practices
• Optimizely: What is a Call to Action?

5. Concrete "Before → After" Suggestions

To instantly improve your conversion rate, implement these specific copywriting upgrades to your hero section.

Suggestion 1: The Main Headline

Before: "Jan Six - Design Systems Engineer" (Critique: This is a job title, not a value proposition. It offers no distinct benefit.)

After: "I build scalable Design Systems that save engineering teams hundreds of hours." (Why this matters: It immediately identifies the deliverable (Design Systems) and the hard business value (saving time/money) for the target audience.)

Suggestion 2: The Subheadline

Before: "Creator of Tokens Studio. Working at the intersection of design and code." (Critique: Good credibility, but "intersection of design and code" is an overused, vague cliché.)

After: "Creator of Tokens Studio. I help enterprise teams bridge the gap between Figma and code, creating flawless, automated UI workflows." (Why this matters: It maintains the powerful social proof of Tokens Studio while explicitly stating the exact workflow problem you solve.)

Suggestion 3: The Primary Call to Action

Before: "Get in touch" or "Email me" (Critique: High friction. The user has to figure out what to write in the email.)

After: "Book a Design System Audit" (Linked to a Calendly or structured Typeform). (Why this matters: It offers a specific, tangible service. The user knows exactly what they are clicking for, which significantly lowers the barrier to entry.)

Suggestion 4: Adding Social Proof Above the Fold

Before: Empty space or abstract graphics. (Critique: Missed opportunity to establish immediate trust with a cold audience.)

After: "Trusted by teams at [Company Logo 1], [Company Logo 2], and 100k+ Figma users." (Why this matters: B2B buyers look for safety. Showing recognizable logos or impressive user metrics immediately de-risks the decision to hire you.)

Product Positioning Score: 8/10

Here is a strategic analysis of the product positioning for Jan Six’s core offering (Tokens Studio / Figma Tokens), based on the messaging across his web properties.

1. Problem-Solution Fit

Is the problem clear? Solution compelling? The problem-solution fit is exceptionally strong for a specific niche. The implicit problem—Figma and codebases easily fall out of sync, creating massive manual handoff work—is a massive pain point for scaled teams. The solution of creating a "single source of truth" for design tokens that bridges design and development is highly compelling. However, the landing page assumes the visitor already fundamentally understands why design tokens matter, relying heavily on the user experiencing the pain beforehand rather than agitating the problem directly.

2. Feature Communication

Are features benefits-focused? Currently, feature communication leans heavily toward the technical execution rather than the strategic benefit. Phrases focusing on "JSON sync," "GitHub/GitLab integration," and "W3C token format" appeal to developers but are purely feature-driven. Shift required: Translate these into benefits. Instead of just saying "GitHub integration," frame it as: "Change a core brand color in Figma, and automatically trigger a pull request in your codebase. Zero manual handoff."

3. Market Positioning

Who is this for? Is it clear? The positioning speaks directly to Design Systems Engineers, Design Ops, and highly technical Product Designers. This is a brilliant wedge strategy. However, the highly technical language (referencing JSON, aliases, and CI/CD pipelines) creates a steep learning curve that might alienate mid-level designers who want to adopt tokens but are intimidated by code. The "who" is clear, but the funnel could be widened by softening the top-of-page messaging.

4. Competitive Angle

What makes this unique? The competitive angle is the product's greatest strength. While Figma has introduced native variables, Jan Six’s tooling positions itself as the "headless" token engine that truly connects to external code repositories. The uniqueness lies in being an agnostic bridge rather than a walled garden. This needs to be highlighted louder: you aren't just styling in Figma; you are managing a global product architecture.

---

Strategic Recommendations

• Agitate the Pain Above the Fold: Before introducing the mechanics of token management, explicitly state the problem. Add a subheadline like: Stop manually updating hex codes across Figma and your codebase.
• Elevate the "Aha!" Benefit: Move away from leading with "manage your design tokens" to leading with the ultimate value proposition: "The single source of truth for your design system—from Figma to code."
• Segment the Messaging (Designers vs. Devs): Create two distinct narrative pathways on the page. Show designers how it makes them faster (multi-theme management without duplicating files) and show developers how it makes them safer (automated PRs, strict JSON structures).
• Clarify the "Figma Native" Differentiator: Address the elephant in the room directly. Briefly explain why scaling teams need this in addition to Figma's native variables (e.g., deeper code sync, W3C standard compliance).

Bottom Line

You have built a technically superior, deeply sticky product with undeniable product-market fit among technical designers; to capture the broader market, you must shift your messaging from how the tool works (features) to the time and friction it saves (benefits).