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

The Resend Transactional Email Developer

A full-stack or backend developer who needs to send transactional emails — password resets, welcome emails, order confirmations, notifications — from their application. They chose Resend because the developer experience felt like it was designed for someone who writes code, not someone who uses a drag-and-drop email builder. They write their email templates in React. The API is simple enough that they memorized it. They are not thinking about email infrastructure. They are thinking about their product.

“The shift was quiet.”

The Superhuman Executive

A founder, executive, investor, or senior individual contributor for whom email is a primary work surface and inbox zero is not aspirational — it is the operating condition required to function. They use Superhuman because they did the math: the time saved per email multiplied by 200 emails per day is real money. They have strong keyboard habits. They were already fast at email. Superhuman made them faster. They will tell you about it if you ask, and sometimes if you don't.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about mobile experience that can't fully replicate the keyboard-driven speed of desktop in two weeks.”

The ConvertKit Creator Monetizer

An online creator — YouTuber, course seller, coach, author, or educator — who has built an email list and uses ConvertKit to turn that audience into revenue. They chose ConvertKit because it was built for creators: the tagging system makes sense for how creators think about audience segments, the Creator Pro features align with their actual business model, and the community of ConvertKit users is full of people doing exactly what they're doing. They are building a creator business, not just an email list. They see their subscribers as an audience, not a database.

“They've just launched a new course.”

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 Mailchimp Small Business Owner

A small business owner, solopreneur, or creator who sends a regular email to their list — weekly newsletter, promotional email, customer announcement. They are not a marketer by training. They set up Mailchimp because it was recommended and free. They've been using it for 1–4 years. They care about their list and think of it as their most direct connection to their customers. They are not fully sure what open rates mean in a post-Apple-MPP world but they still check them because it's the only signal they have.

“A teammate asked how they managed send emails their list looks forward to, not emails that get unsubscribed from.”

The HubSpot Marketing Manager

A marketing manager at a company with 20–150 employees who is responsible for the entire marketing function — content, email, social, paid, and now increasingly the CRM data that sales keeps asking about. They chose HubSpot or inherited it. They use more of it than anyone else at the company. They still feel like they're not using it right, even after two years.

“It's Monday morning.”

The Dovetail UX Researcher

A UX researcher or research ops manager at a company with a growing research practice. They've conducted enough studies that the insights are now a problem: they exist in documents, recordings, sticky notes, and people's memories. Dovetail is where they're consolidating that. They tag, they theme, they surface insights in a way that teams can find without having to ask a researcher. They believe the research repository is the infrastructure of a research-driven company. They're building it while also running new studies. It is a lot.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about research that gets done, presented, and forgotten — the insight graveyard problem in two weeks.”

The Dovetail Research Operations Manager

A UX research lead or research operations manager at a product company who uses Dovetail to turn the chaos of qualitative research — interview transcripts, survey responses, usability test recordings — into a structured, searchable insights repository. They tag, code, and synthesize findings so that when a PM asks "what do we know about onboarding friction?" the answer is a link, not a 3-week research project. They are the librarian of user insights, and they've learned that research nobody can find is research that didn't happen.

“A teammate asked how they managed tag and code qualitative data (transcripts, notes, videos) with consistent taxonomy.”

The Calendly High-Volume Scheduler

A consultant, account executive, advisor, or service professional for whom scheduling external meetings is a daily operational task. They use Calendly because they calculated — consciously or not — that 20 minutes per meeting of back-and-forth email was adding up to hours per week. They now send a link. They feel slightly awkward about it the first time with each new contact. The other person always thanks them for it.

“The shift was quiet.”

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 Clay GTM Engineer

A GTM engineer, growth operations lead, or RevOps professional who uses Clay as their data enrichment and workflow engine. They build spreadsheet-like tables that pull from 50+ data providers — enriching companies with technographic data, finding decision-makers' emails, scoring leads based on signals, and triggering personalized outreach. They think in data transformations and API calls. They've replaced hours of manual prospect research with Clay workflows that run in minutes. They are the engineer of the sales pipeline's data layer.

“The shift was quiet.”

The Apollo Sales Development Rep

A sales development representative or outbound sales rep at a B2B company who uses Apollo as their prospecting command center. They build prospect lists from Apollo's database, enroll them in email sequences, track opens and replies, and try to book meetings. They send 50–200 outreach emails per day and know that personalization is the difference between a reply and the spam folder. They are a relationship builder working at volume, and they've developed an intuition for which prospects will respond and which won't.

“The shift was quiet.”

The Clerk Authentication Developer

A full-stack developer at a startup who chose Clerk because building authentication from scratch — login, signup, email verification, OAuth, MFA, session management — is 2 months of work that adds zero product differentiation. They integrate Clerk's pre-built components, customize the flows, and manage users through the dashboard. They appreciate that auth "just works" but they've also hit moments where Clerk's opinionated approach conflicts with their product's specific needs. They are a developer who decided that auth is infrastructure, not a feature worth building themselves.

“The developer is building a new SaaS product.”

The Kajabi Course Creator

A course creator, coach, consultant, or subject matter expert who chose Kajabi because they wanted one platform instead of five. They have a course, probably a coaching program, possibly a membership community, and they wanted all of it to live together with one checkout, one email system, one analytics dashboard. They pay more for this than they would if they stitched together cheaper tools. They've decided that simplicity and integration are worth the difference. The Kajabi community is genuinely part of their decision — knowing that tens of thousands of other creators are building on the same infrastructure.

“A teammate asked how they managed run a profitable online education business without managing multiple platforms.”

The Kajabi Course Creator

A consultant, coach, or subject-matter expert who has turned their expertise into an online course business on Kajabi. They teach everything from business strategy to photography to fitness. They chose Kajabi because they didn't want to connect Teachable + ConvertKit + Stripe + WordPress + Zapier just to sell a course. They build landing pages, host video lessons, manage email sequences, process payments, and track student progress — all in one platform. They are a teacher who became a business owner, and the business runs on Kajabi.

“A teammate asked how they managed create and deliver online courses with video, text, quizzes, and downloadable resources.”

The Pitch Deck Builder

A startup founder, sales director, or brand marketer who builds presentation decks that matter — investor pitches, sales proposals, quarterly business reviews. They chose Pitch because PowerPoint felt like 2005 and Google Slides felt like giving up on design. Pitch gives them templates that look professional and a collaborative workflow that doesn't require sending a file over email. They spend more time on decks than they'd like to admit. They care more about how those decks look than they'd admit in a meeting.

“An investor meeting is in 48 hours.”

The Grammarly Professional Writer

A content writer, communications manager, or marketing professional who writes 3,000–10,000 words per week — blog posts, emails, reports, social copy. They don't need Grammarly to tell them "their vs. there." They use it for the subtle stuff: passive voice creep, sentences that technically make sense but are hard to read, tone shifts that happen when they're tired, and the comma they always second-guess. They've learned to accept some Grammarly suggestions automatically and reject others consistently. They have a relationship with the tool.

“It happened mid-workflow — the writer is finishing a 2,500-word blog post.”

The Stripe Integration Developer

A full-stack or backend developer at a startup or mid-size company who built and maintains the Stripe integration for their product. They integrated Stripe once — it took a week in dev, two days in staging, and then went live and mostly just worked. Now they're the person who gets the Slack message when a payment fails. They know the Stripe docs well enough to find what they need. They have a complicated relationship with webhooks.

“A teammate asked how they managed understand what happened when a payment fails before the customer reaches support.”

The Photoshop Production Designer

A graphic designer — in-house or agency — who uses Photoshop as their primary production tool for image work. They've been in Photoshop for 5–15 years and work with the efficiency of someone who knows exactly where everything is and what everything does. They don't explore menus. They use shortcuts. Their workspace is a system they've tuned. Photoshop is slow sometimes and they've learned to work around it the way you work around a colleague's habits — with patience and workarounds they've stopped noticing.

“The shift was quiet.”

The Apollo SDR

A sales development rep or account executive at a B2B company of 20–300 people who runs outbound prospecting as a core job function. Apollo is their prospecting database, their sequencing engine, and their activity tracker. They use it every day. They've built sequences that work and sequences that don't, and they've learned the difference by watching reply rates. They're not sentimental about approaches that aren't working. They test, they iterate, they move on.

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

The Tally Non-Technical Form Builder

A startup founder, indie maker, or operations person who creates forms for surveys, lead capture, applications, and feedback — and who bounced off Typeform's pricing, Google Forms' aesthetic, and Airtable Forms' rigidity. They found Tally and built their first form in 4 minutes. They converted immediately. They use Tally for things that other tools make too complicated or too expensive for what's essentially a box to collect information.

“A teammate asked how they managed create a well-designed form fast without a mental model of how the tool works.”

The Typeform Research and Marketing User

A UX researcher, marketer, or operations person who uses Typeform because they've seen what happens to completion rates when you use Google Forms. They care about the quality of the responses they collect — which means they care about the experience of filling in the form. They design forms deliberately: question order, logic branches, conversational tone. They know their completion rate. They have an opinion about it.

“The shift was quiet.”

The Stripe Platform Builder

A technical founder or senior developer building a platform where money flows between multiple parties — a marketplace, a SaaS with payouts, or a platform that onboards sellers. They chose Stripe because the API is good, but they've discovered that Stripe Connect is a different animal entirely. They understand payment intents but still get confused by the relationship between accounts, charges, and transfers. They are building financial infrastructure and it keeps them up at night.

“The first time a seller on their platform got paid automatically — money flowed from buyer to platform to seller with the correct fee split, no manual step, no CSV export.”

The Ghost Independent Publisher

An independent journalist, researcher, media entrepreneur, or content organization that chose Ghost because platform ownership matters to them. They're running a publication with a membership model — free and paid tiers, regular editorial content, and a direct relationship with readers they're not willing to cede to Substack's network effects or Beehiiv's operator framing. They are technically capable enough to run Ghost on managed hosting or self-host it. This was a deliberate choice. The people who choose Ghost have thought about the alternatives more carefully than most tool decisions require.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about theme customization that requires Handlebars knowledge most writers don't have in two weeks.”

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 Basecamp Small Agency Owner

A small agency owner, studio founder, or remote team lead with 3–20 people who chose Basecamp because they were tired of configuring project management tools. Basecamp's opinionated structure — message boards, to-dos, schedules, docs, campfire — is not a limitation to them. It's the point. They didn't want to design a system. They wanted to use one. They've been on Basecamp for 2–6 years. They've recommended it to other agency owners who are drowning in Notion setups and Jira configurations. Some of them listened.

“A client project kicks off Monday.”

The Canva Marketing Manager

A marketing manager or content lead at a 10–100 person company who produces 20–50 pieces of visual content per week. They're not a designer and they know it — but Canva makes them good enough. They've built a template library that keeps everything on-brand, and they resize for every platform in one click. They're proud of the speed but occasionally embarrassed when a real designer sees their work. They are the reason the brand looks consistent, even if the brand guidelines live in a Google Doc nobody reads.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about brand Kit limitations — fonts upload fine but brand colors sometimes don't apply consistently in two weeks.”

The Squarespace Small Business Owner

A small business owner — a bakery, a yoga studio, a photography business, a consulting firm — who built their website on Squarespace because they needed something that looked professional without hiring a designer or developer. They chose a template, swapped in their photos, wrote their copy, and launched. They're not technical, but they figured out the editor. They update the site monthly — new photos, seasonal hours, blog posts when they have time. The website is their digital storefront, and they treat it with the same pride they treat their physical one.

“A potential customer finds the small business owner's Squarespace site through Google.”

The Vercel Agency Deployer

A developer at a web agency or a freelancer who deploys and manages 20–100 client projects on Vercel. They chose Vercel because the developer experience is excellent and Next.js deploys are zero-config. But managing 50 projects across 15 clients has turned deployment into project management. They spend as much time in the Vercel dashboard organizing teams and domains as they do writing code. They know every deployment preview URL is a demo link, and they've sent the wrong preview to the wrong client exactly once.

“A client emails asking why their site is showing an old version.”

The Greenhouse Recruiting Coordinator

A recruiting coordinator or in-house recruiter at a growing company who manages 15–40 open roles simultaneously. Greenhouse is their command center — every candidate, every interview, every offer lives there. They are the logistics engine of hiring: scheduling interviews across time zones, nudging hiring managers for feedback, and keeping candidates warm through what feels like an increasingly long process. They measure their success not in hires made but in process efficiency — time-to-fill, interview-to-offer ratio, candidate experience scores.

“A teammate asked how they managed keep candidate response times under 24 hours across all active roles.”

The Segment Data Architect

A data engineer or analytics engineer who manages Segment as the central event routing layer. Every product event — page views, clicks, purchases, signups — flows through their Segment workspace before reaching the data warehouse, analytics tools, and marketing platforms. They are the plumber of the data stack. Nobody thanks them when data flows correctly, but everyone notices when it doesn't. They think in events, properties, and destinations. They've learned that the hardest part of data infrastructure isn't moving data — it's keeping it clean.

“The shift was quiet.”

The Pitch Startup Storyteller

A startup founder, head of product, or strategy lead who creates presentations that need to look beautiful and tell a compelling story — investor decks, product roadmaps, board updates, customer pitches. They chose Pitch because it produces better-looking slides with less effort than PowerPoint or Google Slides. They value design defaults that make everything look good automatically. They collaborate in real time with co-founders and design team members. They are visual communicators who believe that how a story is presented is as important as the story itself.

“It happened mid-workflow — the founder is preparing for a Series A fundraising round.”

The Intercom Support Lead

A customer support lead or manager who runs their team's entire operation through Intercom. They built the macro library, set up the routing rules, and configured the chatbot — all while also jumping into the inbox during peak hours. They measure first response time, resolution time, and CSAT obsessively. They believe in automation but hate when it makes customers feel like nobody's listening. They are the bridge between what the product team ships and what customers actually experience.

“A teammate asked how they managed keep first response time under 5 minutes during business hours.”

The Rippling HR Administrator

An HR administrator, people ops manager, or office manager at a 50–500 person company who manages Rippling as their all-in-one HR platform. They handle onboarding (IT provisioning, payroll setup, benefits enrollment), offboarding (access revocation, final paycheck, COBRA), and everything in between. They chose Rippling because the alternative was stitching together 5 separate tools. They appreciate the unified system but have learned that "all-in-one" means "all the complexity in one place." They are the person who makes sure new hires have a laptop, a paycheck, and health insurance on day one.

“It happened mid-workflow — a new engineer starts Monday.”

The QuickBooks Small Business Owner

A small business owner — a contractor, consultant, retailer, or service business — doing their own bookkeeping in QuickBooks because they can't yet justify what an accountant costs. They are not a numbers person by nature. They are running QuickBooks because they were told they had to, not because they wanted to. They feel mild anxiety every time they open it and have not reconciled their accounts in two months.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about transactions that categorize wrong and silently corrupt their books in two weeks.”

The Contentful Content Manager

A content manager, digital editor, or marketing manager at a company with a developer-built Contentful implementation. They publish product pages, blog posts, campaign content, and documentation through Contentful's web interface. They did not design the content model — a developer did. They live inside that model every day and have a detailed understanding of which fields do what and which ones are a mystery. They are not a developer but they've learned to think in content types.

“A teammate asked how they managed publish and update content quickly without waiting on a developer for every change.”

The Squarespace Small Business Owner

A photographer, therapist, consultant, restaurant owner, or small retailer who built their own website on Squarespace because it was the best option they could manage independently. They are not a developer. They do not want to be. They want a website that looks professional, is easy to update, and doesn't require a support ticket to change the menu. They've succeeded at this mostly. There are two things on their site that have been wrong for three months because fixing them would require understanding something they don't want to learn.

“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 Ramp Finance Manager

A finance manager, controller, or CFO at a company of 20–300 people who adopted Ramp to eliminate the expense report process that everyone hated and nobody trusted. They issue cards. They set limits. They receive receipts automatically from employees who forward a text message or take a photo. They close the books faster. They've calculated how many hours per month expense reports used to consume and they don't miss a single one of them. They are the person at the company who is most enthusiastic about Ramp.

“A teammate asked how they managed close the books faster by eliminating the expense report chase.”

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 Retool Internal Tools Developer

A full-stack developer or engineering lead tasked with building internal tools — admin dashboards, customer support panels, operations consoles. They chose Retool because writing React apps for internal use felt wasteful, but they still need to write SQL, connect APIs, and handle auth. They are a developer using a low-code tool, which means they appreciate the speed but feel the constraints more acutely than a no-code user would.

“The support team needs a tool to look up customer accounts, view their subscription history, and issue refunds.”

The Craft Personal Document Creator

A professional in the Apple ecosystem — Mac, iPad, iPhone — who uses Craft for everything from meeting notes to project proposals to personal journals. They chose Craft because it feels native to macOS and iOS in a way that Notion and Google Docs don't. They value beautiful typography, smooth block-based editing, and the ability to work offline on an airplane and sync when they land. They are a writer who cares about the writing environment, not just the output.

“The shift was quiet.”

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 Ramp Finance Controller

A finance controller, VP of Finance, or head of accounting at a 50–500 person company who chose Ramp because they were tired of chasing receipts, manually categorizing expenses, and closing the books a week after month-end. They manage corporate cards, set spend policies, and review transactions. They appreciate Ramp's automation but know that "automated" still means they're the one who catches the exceptions. They are the financial guardrail of the company.

“It happened mid-workflow — month-end arrives.”

The Typeform Survey Designer

A UX researcher, product manager, or marketer who chooses Typeform over Google Forms because the survey experience matters. They've learned that completion rate is the most important metric for a survey, and completion rate is a design problem. They craft surveys that feel like conversations: one question at a time, conditional logic, thoughtful copy. They spend as much time on the question experience as they do on the question content. They are the person who says "we can't just send a Google Form — that sends a message about how much we value their feedback."

“The shift was quiet.”

The Deel Global Team Manager

An operations lead, HR manager, or founder at a remote-first company who has team members across 5–20 countries. They use Deel because hiring internationally is legally complex and paying people across borders is operationally painful. They manage contracts, process payments, and handle compliance for contractors and full-time employees in countries they've never visited. They've learned that "hiring remotely" really means "learning employment law for every country you hire in." Deel handles the parts they can't.

“The shift was quiet.”

The Perplexity Research Analyst

A research analyst, journalist, consultant, or knowledge worker who has replaced their Google-and-10-tabs workflow with Perplexity. They don't search for links — they ask questions and expect synthesized answers with citations. They use it for competitive analysis, market research, fact-checking, and deep dives into topics where they need to learn fast. They've learned which types of questions Perplexity handles well (factual synthesis) and which it doesn't (opinion-based, very recent events). They trust it more than ChatGPT because of the citations, but they still verify.

“A teammate asked how they managed get comprehensive, cited answers to complex research questions in minutes instead of hours.”