Who actually uses these products,
and what made them stay.

The Spline Web 3D Designer

A product designer, visual designer, or creative developer who started using Spline because they wanted 3D on their website or product and Blender was too much. They have a 2D design background — Figma is their native language. Spline felt like Figma with a Z-axis. They've built at least one thing they're proud of: a 3D hero section, an interactive product visualization, a floating element that reacts to cursor position. They use it for client work and personal projects. They consider themselves an early adopter of the idea that 3D should be accessible to product designers, not just motion designers.

“They're redesigning a SaaS product's marketing homepage.”

The Spline 3D Web Designer

A web designer or creative developer who uses Spline to add 3D to their web projects without the learning curve of Blender or Cinema 4D. They create 3D hero sections, interactive product visualizations, animated icons, and immersive landing pages. They are a designer who crossed into the third dimension. They appreciate that Spline runs in the browser, exports to the web natively, and feels like a design tool rather than a 3D modeling application. They are the person making websites feel like they have depth.

“A SaaS company wants a landing page that stands out.”

The Linear Engineering Manager

An engineering manager or head of engineering at a startup of 20–150 engineers who uses Linear at the issue level to track work and at the Projects level to communicate progress. The ICs live in issues and cycles. The EM lives in projects and the roadmap view. They're the translation layer between "what the team is building" and "what the company thinks we're building" — and Linear Projects is the interface they use to close that gap.

“It happened mid-workflow — it's Thursday.”

The Make Power Automator

An operations lead, automation specialist, or technical non-developer who moved to Make (formerly Integromat) after hitting the ceiling on Zapier. They know what they wanted to build and Zapier's linear trigger-action model couldn't do it: conditional branches, iterators, error handlers, multi-route flows. Make could. They learned Make. They have built things in Make that non-technical people would describe as software and technical people would describe as creative. They exist in the middle of the developer-to-non-developer spectrum and they've built a practice there.

“A client needs a system: when a new deal is created in HubSpot above a certain value, create a proje.”

The Harvest Freelancer and Agency Owner

A freelancer, consultant, or small agency owner (2–15 people) for whom time is the product. They track hours against client projects and invoice from those hours. Harvest is where the financial reality of their business lives. They've learned that unbilled hours are lost revenue, that clients will dispute invoices without time entries to back them up, and that the difference between a profitable month and a break-even month is often the accuracy of their time tracking. They are disciplined about logging time — or they are trying to become disciplined about it.

“A teammate asked how they managed track time accurately enough that invoices are defensible and projects are profitable.”

The Superhuman Inbox Zero Executive

A startup CEO, VP, or senior director who receives 150–300 emails per day and treats email like a production system. They chose Superhuman because Gmail was too slow and too noisy. They've memorized the keyboard shortcuts, configured their split inbox, and use the AI triage to surface what matters. They process email like a speed reader processes text — scanning, deciding, acting — in bursts of 15–20 minutes, 3–4 times per day. They are allergic to unread counts and consider inbox zero a professional discipline, not a personality quirk.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about the AI triage sometimes miscategorizes important messages from new contacts in two weeks.”

The Logseq Academic Researcher

An academic researcher, PhD student, or independent scholar who uses Logseq as their research knowledge base. They take notes on papers, link concepts across disciplines, and use the graph view to see how ideas connect in ways linear note-taking never revealed. They chose Logseq because it's local-first (their research data stays on their machine), uses an outliner format that matches how they think, and builds a knowledge graph without forcing a predetermined structure. They are building a second brain for their research, and they expect it to outlast their current institution.

“The shift was quiet.”

The Linear Product Manager

A product manager at a 20–200 person startup who moved to Linear because Jira was too heavy and Notion boards weren't structured enough. They work at the initiative and project level while their engineers work at the issue level. They need to see the forest while the team sees the trees. They love Linear's speed and keyboard shortcuts but struggle to get the strategic views they need without building custom views for every stakeholder meeting.

“It happened mid-workflow — the CEO asks "are we on track for the Q2 launch?" The PM opens Linear, checks 4 projects across 2 teams, counts completed vs.”

The Raycast Power User

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.

“It's 9am.”