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

The HubSpot Sales Rep

A B2B sales rep or account executive who opens HubSpot 30+ times a day. They manage a pipeline of 20–80 active deals and are measured on close rate and revenue. They didn't pick HubSpot — their sales leader did — but they've gotten good at working within it. They know which shortcuts save time and which required fields are slowing them down. They log activities because they have to, not because they want to. They care about closing deals, not about CRM hygiene.

“The shift was quiet.”

The Drata Compliance Automation Lead

A security engineer, compliance lead, or CTO at a startup who needs SOC 2, ISO 27001, or HIPAA compliance to close enterprise deals. They chose Drata because the alternative was spreadsheets, manual evidence collection, and $50K in consultant fees. They've connected their cloud infrastructure, HR tools, and code repositories to Drata for automated evidence collection. They understand that compliance is a business requirement, not a security one — the real security work is separate. They are simultaneously grateful for automation and frustrated by how much manual work remains.

“A teammate asked how they managed automate evidence collection across cloud infrastructure, identity providers, and HR systems.”

The Excel Financial Modeler

A financial analyst, FP&A professional, or investment banker who builds financial models in Excel the way architects build buildings — with structure, precision, and the knowledge that if one formula is wrong, everything above it falls. They've been using Excel for 5–15 years. They think in cell references, not coordinates. They know keyboard shortcuts that most people don't know exist. They've built models that a CEO used to make a $50M decision, and they've spent weekends debugging a circular reference that shouldn't have been circular.

“The CFO asks for a scenario analysis by tomorrow morning: what happens to cash flow if revenue grows 10% slower than projected and two enterprise deals slip to next quarter.”

The DocuSign Contracts Sender

A sales rep, account executive, or operations manager who sends 5–30 contracts per month for electronic signature. DocuSign is not their job — it's the thing they do at the end of their job. They want contracts signed as fast as possible because a signed contract is a closed deal or a cleared obligation. They did not design the templates they use. They sometimes modify them in ways that create problems they don't discover until someone calls.

“The shift was quiet.”

The Attio Revenue Operations Lead

A revenue operations lead or head of sales operations at a Series A–C startup who chose Attio because legacy CRMs either cost too much (Salesforce) or think too rigidly (HubSpot). They build custom objects, design pipeline views, and create automations that match how their team actually sells — not how a CRM template assumes they sell. They think in data models, not contact records. They've realized that a CRM is only as good as the data in it, and their primary job is making sure the data stays clean and the team actually uses the tool.

“It happened mid-workflow — the company is expanding from SMB to mid-market sales.”

The Excel Financial Analyst

A financial analyst at a corporation, investment firm, or consultancy for whom Excel is not software — it is the medium of thought. They spend 5–7 hours a day inside spreadsheets. They build models that other people are afraid to open. They have keyboard shortcuts memorized that the rest of the company doesn't know exist. They've rescued a broken model the night before a board presentation. They have opinions about Excel that they share without being asked.

“It happened mid-workflow — they're building a 3-year P&L model for a new product line.”

The Liveblocks Real-Time Developer

A frontend developer who needs to add real-time collaboration to an existing app — live cursors, presence indicators, shared document editing, or collaborative whiteboards. They chose Liveblocks because building WebSocket infrastructure from scratch is a project in itself, and they need to ship the feature, not the infrastructure. They understand React, they understand state management, and Liveblocks extends those mental models to multiplayer. They are building the "Google Docs" experience for their product.

“It happened mid-workflow — the developer is adding collaborative editing to a project management tool.”

The Contentful Headless CMS Developer

A frontend or full-stack developer who integrates Contentful as the content backend for a website, app, or digital experience. They set up the content models, build the delivery layer, and create the bridge between what content editors want to publish and what the frontend can render. They appreciate the API-first approach but have learned that "headless" means they're responsible for everything the CMS traditionally handled — routing, preview, caching, image optimization. They build the head.

“A marketing team wants to launch a new campaign page type.”

The Sanity Content Architect

A developer or content architect who uses Sanity because they think about content as structured data, not pages. They design content models that serve web, mobile, email, and API consumers from a single source. They've built custom studios, created real-time collaborative editing environments, and used GROQ to query content in ways traditional CMS query languages can't express. They are the architect of the content layer, and they treat content modeling with the same rigor as database schema design.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about customizing the Studio deeply requires significant React knowledge, raising the bar for non-senior developers in two weeks.”

The Roam Research Networked Thinker

A writer, researcher, or knowledge worker who uses Roam Research as an extension of their thinking. They don't organize notes into folders — they write, link, and let the graph reveal connections. They use daily notes as their entry point, double-bracket references to build a web of ideas, and block references to connect thoughts across pages. They've read about Zettelkasten, spaced repetition, and evergreen notes. They've adopted some of these ideas and adapted others. They are building a thinking system, not a filing system.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about performance degrades with large graphs — search and page loads slow down over time 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 Roam Research Networked Thinker

A researcher, academic, writer, or knowledge-intensive professional who uses Roam because it is the only tool that treats the connection between ideas as a first-class object. They write in Daily Notes. They [[bracket]] everything. They have a graph with 3,000–15,000 nodes that they've been building for 2–4 years. They know their graph is their most valuable intellectual asset. They also know that Roam's development has slowed, that the tool has rough edges, and that they've considered migrating to Obsidian or Logseq at least twice. They haven't migrated. The switching cost is partly the data — mostly the habit.

“They're writing an essay about institutional memory.”

The Reluctant Salesforce User

An enterprise sales rep at a company with 200+ employees who did not choose Salesforce. It was there when they arrived. They've been trained on it twice. They use about 20% of its features and have found workarounds for everything else. They log activity because their manager checks. They update opportunities because forecasting requires it. They do not believe Salesforce makes them better at sales. They believe it makes their manager better at measuring sales.

“The shift was quiet.”

The Attio Revenue Operator

A revenue ops manager, head of sales, or technical founder at a startup of 10–100 people who evaluated the legacy CRMs and decided not to inherit their constraints. They chose Attio because it's data-model-first — they can define what a record means in their business rather than forcing their process into Salesforce's assumptions. They are building their CRM from scratch. This is a significant investment. They are aware of that and have decided it's worth it.

“A teammate asked how they managed build a CRM that reflects their actual sales process rather than a generic framework.”

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 Wix First-Time Website Owner

A small business owner, freelancer, event organizer, or individual who needed a website and chose Wix because they wanted to design it themselves. They are not technical. They have no interest in becoming technical. They evaluated Squarespace and liked Wix's drag-and-drop freedom more — the ability to place anything anywhere without template constraints. They've built a website they're proud of. It has some inconsistencies that they can't see but a designer would notice immediately. This is fine. The website does what they need it to do.

“The shift was quiet.”

The DocuSign Legal Operations Manager

A legal operations manager, contracts administrator, or legal team member responsible for the organization's DocuSign implementation. They manage templates, set up signing workflows, and make sure contracts go through the right approval chains. They're the person who built the NDA template, the SOW template, and the vendor agreement template. They field requests like "I need this signed by Friday" and translate them into proper DocuSign envelopes with the right fields, routing, and compliance settings. They are the API between the legal team and everyone else who needs something signed.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about template management becomes unwieldy as the library grows — versioning and deprecation are manual processes in two weeks.”

The Readwise Knowledge Synthesizer

A voracious reader — books, articles, newsletters, podcasts, Twitter threads — who realized that reading without capturing is forgetting. They use Readwise to collect highlights from Kindle, Instapaper, podcasts, and the web, then Readwise Reader for their daily reading queue. They've built a workflow where everything they consume flows through one system, highlights are tagged and resurfaced, and insights compound over time. They are the person who can always find "that article I read about X" because they highlighted the key passage six months ago.

“It happened mid-workflow — the knowledge worker is writing a strategy memo about pricing models.”

The GitLab DevOps Engineer

A DevOps engineer or platform engineer who chose GitLab because the promise of "one tool for the entire DevOps lifecycle" was too compelling to ignore. They manage the CI/CD pipelines, configure the runners, set up the security scanning, and maintain the deployment workflows. They appreciate that everything lives in one place — no integrating GitHub with CircleCI with Snyk with ArgoCD. But they've also learned that "one tool that does everything" sometimes means "one tool that does everything at 80%."

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about cI pipeline configuration in YAML becomes deeply nested and hard to maintain as complexity grows in two weeks.”

The Framer Motion Designer

A product designer or motion designer who gravitates toward Framer because it treats animation and interaction as first-class design elements. They don't just design screens — they design how screens transition, how elements respond to hover, how content enters and exits. They've used Figma for static design but find it limiting when the design's value is in how it moves. They are the person who insists that the ease curve matters and that a 200ms delay feels different from a 300ms delay.

“A teammate asked how they managed design and prototype complex animations and transitions that developers would struggle to implement from specs.”