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

The 1Password Security-Conscious Admin

An IT manager, security engineer, or technically-minded operations lead at a company of 20–500 people who adopted 1Password for Teams and now manages credential hygiene across an organization. They have strong feelings about credential sharing via Slack. They have seen what happens when a shared account has no owner and the person who knew the password leaves. They've spent time cleaning up credential sprawl left by a company that grew faster than its security practices. They run 1Password now. It is imperfect but it is dramatically better than what came before.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about vaults that grow without structure until nobody knows what's in them or who owns it in two weeks.”

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 Drata Compliance Manager

A security manager, compliance lead, or IT director at a SaaS company of 50–500 people who is responsible for achieving and maintaining SOC 2 Type II certification. Before Drata, this was a spreadsheet, a shared drive, and a six-month audit season that consumed 30% of their capacity. Drata made it something they can manage in the background with periodic attention spikes. They're not relaxed about compliance — that would be naive — but they're less reactive. That's the win.

“A teammate asked how they managed maintain continuous compliance evidence without a manual collection sprint before every audit.”

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 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 Supabase Indie Hacker

A solo developer or indie hacker building a SaaS product where Supabase is the entire backend. They chose Supabase because it gives them Postgres, auth, storage, and real-time out of the box — and they can ship their MVP in a weekend instead of a month. They write SQL directly, use Row Level Security because they have to, and treat the Supabase dashboard as their admin panel. They are building a business alone and Supabase is the co-founder that handles the backend.

“The shift was quiet.”

The Supabase Full-Stack Developer

A full-stack developer or indie hacker who uses Supabase as their backend and thinks of it as their database, their auth layer, their file storage, and their API layer at once. They came from Firebase and wanted Postgres. Or they came from setting up their own Postgres and wanted the tooling. Either way they arrived at Supabase and found a backend they could move on from thinking about. They write SQL fluently. They use Row Level Security. They are deeply comfortable in the Supabase dashboard. They have strong feelings about their Supabase tables.

“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.”