“It's 9am.. Something that used to take 30 minutes took 30 seconds. They looked at the old way and couldn't believe they'd tolerated it. That was the aha.”
When I'm before they've opened a browser tab, they've done the following in raycast: chec, I want to execute the most frequent 20% of their computer interactions without touching the mouse, so I can surface information from connected tools (GitHub, Linear, Notion, Calendar) without switching apps.
A developer, designer, or technical knowledge worker on Mac who replaced Spotlight with Raycast and then spent three weekends making it the center of their computing workflow. They open Raycast more than any other application. They open it for things they didn't know a launcher could do. They've written or installed extensions for their most repetitive tasks. They mention Raycast in the same breath as mechanical keyboards and monitor setups — tools that are invisible when they work and felt intensely when they don't.
To execute the most frequent 20% of their computer interactions without touching the mouse — reliably, without workarounds, and without becoming the team's single point of failure for raycast.
A developer, designer, or technical knowledge worker on mac who trusts their setup. Execute the most frequent 20% of their computer interactions without touching the mouse is reliable enough that they've stopped checking. Extension quality signals (last updated, maintainer activity, install count) surfaced. They've moved from configuring raycast to using it.
It's 9am. Before they've opened a browser tab, they've done the following in Raycast: checked their calendar for the day, pulled up yesterday's Linear issues that are still open, searched their clipboard history for a URL they copied on their phone, converted a hex code to RGB for a quick Slack answer, and started a timer for their first focus block. None of these required opening an application. This is now so normal they don't think of it as productivity — they think of it as computing.
Uses Raycast as their default launcher on Mac. Has 20–40 extensions installed. Uses Raycast Snippets for recurring text (email templates, code blocks, addresses). Uses Raycast Clipboard History as a replacement for a dedicated clipboard manager. Has configured Window Management as a replacement for another app. Uses the Calendar extension more than the native Calendar app for quick event lookup. Has a Raycast AI subscription they use occasionally but aren't sure it's essential. Would notice Raycast disappearing within 4 minutes of starting their computer.
Two things you'd notice: they reference raycast in conversation without being asked, and they've built workflows on top of it that weren't in the original plan. Execute the most frequent 20% of their computer interactions without touching the mouse is consistent and expanding. They're now focused on surface information from connected tools (GitHub, Linear, Notion, Calendar) without switching apps — a sign the basics are solved.
It's not one thing — it's the accumulation. Extensions that require API configuration they don't want to look up on a Saturday that they've reported, worked around, and accepted. Then a competitor demo shows the same workflow without the friction, and the sunk cost argument collapses. Their worldview — the mouse is the enemy of flow state — every task the keyboard can do is time recovered — makes them unwilling to compromise once a better option is visible.
Pairs with `vscode-primary-user` for the keyboard-native developer workflow end-to-end. Contrast with `mouse-first-user` archetype to map the cognitive and ergonomic divide in developer tooling. Use with `cursor-primary-user` for the full AI-assisted, keyboard-driven development environment picture.