raycast.com landing page review

Your hero sells a feeling before explaining the product. “Your shortcut to everything” could describe almost any productivity app; visitors need to understand that Raycast is a keyboard-first launcher before the broader promise becomes persuasive.

1. 1High impactHeadline

   “Everything” is ambitious but does not explain what Raycast actually helps visitors do.

   Headline clarity scores 6.0/10 and carries the most weight in this review. People unfamiliar with Raycast must read further before they can decide whether it belongs in their workflow.

   Now

   Your shortcut to everything.

   Change to

   Apps, files, and tasks. One shortcut.

2. 2High impactSocial proof

   “Built for professionals like you” asserts audience fit without giving visitors a concrete customer story or endorsement.

   Social proof scores 2.4/10, your weakest conversion area. A long list of capabilities establishes breadth, but does not show that working professionals actually rely on Raycast.

   Now

   Built for professionals like you.

   Change to

   Keep this heading, but add two static customer quotes directly beneath it. Each must be a real, approved quote describing a specific workflow, with the customer's name, role, and company when permitted. Use one developer workflow and one other professional workflow. Place the stronger quote immediately below the hero as well; do not hide both inside a carousel.

3. 3High impactHero subheadline

   The subheadline explains the category, but “a collection of powerful productivity tools” is generic and “extendable” makes visitors translate a product attribute into a benefit.

   You have concrete outcomes elsewhere on the page—searching files, controlling apps, and using AI—but the opening copy does not lead with them.

   Now

   A collection of powerful productivity tools all within an extendable launcher. Fast, ergonomic and reliable.

   Change to

   Raycast is a keyboard-first launcher for your desktop. Search files, control your apps, and get help from AI without breaking your flow.

4. 4Medium impactInteractive CTA

   The prompt field offers an immediate start, but its placeholder combines the first action with syntax instructions. “Send” does not reinforce what visitors are trying.

   Your CTA already scores a strong 8.9/10, so replacing it with a signup gate would be a step backward. The opportunity is to make the existing interaction easier to understand on first use.

   Now

   Ask anything, @ tools, or / for commands…

   Change to

   Keep the prompt field and its working interaction. Change the placeholder to “Ask Raycast AI a question…” and the “Send” button label to “Ask Raycast AI”. Move “Use @ for tools and / for commands” into helper text beneath the field. Add a clickable example, “How do I create a Raycast extension?”, that fills the field without submitting it.

5. 5Medium impactExtensions section

   The section quickly expands into many different tools and tasks, from Linear and JIRA to Spotify and Google Translate.

   The page is already highly scannable at 9.3/10. The remaining issue is prioritization: a technical visitor should see a recognizable workday before browsing the full catalog.

   Now

   There’s an extension for that.

   Change to

   Change the heading to “Your work tools. One shortcut.” Keep “Use your favorite tools without even opening them.” Show Linear, GitHub only if available, Slack, and Notion in the initial work-focused view; if GitHub is not available, use the existing JIRA card instead. Keep the other extensions accessible through the existing category controls.

6. 6Medium impactReliability claim

   The precise crash-free claim has no accompanying explanation of its scope or measurement period.

   “99.8%” can be persuasive to technical buyers, but precision without context can raise questions instead of resolving them. This is especially important while customer proof is weak.

   Now

   Reliable. 99.8% crash-free rate.

   Change to

   Keep the claim only if you can substantiate it. Add a visible “How we measure reliability” link beside it, leading to the measured platform, reporting period, and definition of crash-free rate. If that documentation is unavailable, replace the line with “Reliable. Built for your daily workflow.”

• Replace the hero headline with “Apps, files, and tasks. One shortcut.”
• Replace the hero paragraph with the rewritten keyboard-first launcher description.
• Change “Send” to “Ask Raycast AI” and move the @ and / instructions below the prompt field.
• Change “There’s an extension for that.” to “Your work tools. One shortcut.”
• Add a measurement link beside the 99.8% reliability claim, or remove the unsupported precision.

• Keep the modern foundation: design modernity scores 9.4/10. Consistency is the weaker area at 5.4/10; consolidate the four main font families and 35 font sizes into one body/UI family, one display family, and a defined heading scale. Reserve the keyboard-style type for the keyboard demonstration.
• Standardize corners by component role. With 65 distinct radius values, use one radius each for buttons, inputs, and cards rather than allowing every section to introduce another treatment.
• Visual hierarchy scores 7.5/10. Keep the rewritten headline, supporting sentence, and interactive prompt together as the first decision-making block; place the keyboard showcase after that block rather than letting it compete with the product explanation.
• Responsiveness scores 7.6/10 despite extensive responsive styling. At 375px and 390px widths, make the prompt and submit button a single-column stack, collapse the extension cards to one column, and contain the keyboard illustration so it cannot create page-level horizontal scrolling.

• The prompt field lets visitors begin immediately. Preserve that product-led interaction rather than forcing signup before they can engage.
• Concrete extension descriptions such as “Create, search and modify your issues without leaving your keyboard” connect features to recognizable tasks. Keep that specificity.
• The short headings, category controls, and task examples make a broad product easy to scan. Preserve that structure rather than adding long explanatory paragraphs.