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

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 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 Zapier Non-Technical Automator

An operations coordinator, marketing manager, or executive assistant who discovered Zapier and spent an afternoon automating a task that had been eating 45 minutes of their week. That experience was formative. They now have 12 Zaps running, three of which they fully understand, one of which they're afraid to touch, and one that they know has been broken for two weeks but the fix intimidates them. They are not a developer. They are the closest thing to one in their department.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about error messages that tell them a Zap failed but not what to do about it in two weeks.”

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

A full-stack or backend developer at a startup or scale-up who has been asked — once too many times — to pull data from the database for a non-technical teammate. They discovered Retool as a way to give those teammates self-service access without giving them direct database access. They've built 3–8 internal tools: an admin panel, an operations dashboard, a customer lookup tool, and at least one thing they built in a weekend that the whole company now depends on.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about retool queries that are fast in development and slow in production on real data volumes 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 PostHog Growth Engineer

A growth engineer, product engineer, or technical PM who uses PostHog as their all-in-one growth stack — analytics, feature flags, A/B tests, session replay. They chose PostHog because they didn't want to stitch together Amplitude, LaunchDarkly, and Hotjar. They think in funnels, retention curves, and statistical significance. They are technical enough to self-serve but product-minded enough to care about the "so what" behind the data.

“It happened mid-workflow — the growth engineer is running an A/B test on the onboarding flow.”

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 Clay Growth Operator

A growth lead, revenue ops manager, or technical sales operator who found Clay and spent two weeks rebuilding their entire outbound motion around it. They were already combining data from LinkedIn, Apollo, Clearbit, and spreadsheets manually — a process that was slow, inconsistent, and unscalable. Clay collapsed that into one workflow. They now build outbound lists in hours that previously took weeks. They are evangelical about it. They're also aware that most people at their company don't understand what they've built.

“The head of sales wants a list of 500 Series B SaaS companies that have posted a VP of Sales job in .”

The Height Engineering Team Lead

An engineering team lead or technical PM at a company of 20–150 people who evaluated Linear and wanted more — more project hierarchy, more cross-functional visibility, more flexibility for non-engineering teams to work alongside engineering in the same tool. They chose Height. They're building their system in it. They like that it feels like a tool built by people who understand engineering workflows, not a project management tool that engineering is expected to tolerate. They're still learning the edges of it.

“It happened mid-workflow — sprint planning is Monday.”

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

The Make Integration Architect

An automation specialist, operations engineer, or technical ops manager who builds complex workflows in Make because Zapier wasn't enough. They connect 10–30 tools with branching logic, iterators, aggregators, error handlers, and data transformations. They build automations that look like flowcharts, not if-then rules. They've learned Make's visual interface deeply — routers, filters, webhooks, custom HTTP modules. They are the person who automates what everyone else does manually, and they take quiet pride in systems that run for months without intervention.

“A teammate asked how they managed build multi-step automations with branching logic that handles different cases (approval/rejection, success/failure).”

The Arc Browser Power User

A developer, designer, or technical knowledge worker who switched to Arc and reorganized their browser-based work around Spaces and Folders instead of horizontal tab strips. They had 40 tabs open in Chrome on a normal day. They were managing them by scrolling and guilt. Arc replaced the tab strip with something structural. They have opinions about it that they've refined over 8 months of use. The opinion is: it's better. The caveat is: it requires learning a new mental model that takes 3 weeks to stop fighting.

“The shift was quiet.”

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 Raycast Workflow Automator

A developer or technical power user on macOS who has made Raycast the nerve center of their computing workflow. They don't just launch apps — they manage clipboard history, control Spotify, search GitHub issues, translate text, convert currencies, and run custom scripts — all from a single keyboard shortcut. They've installed 15–30 extensions and written a few of their own. They are the person whose colleagues watch them work and ask "what is that tool and how do I get it." They measure productivity in keystrokes saved.

“It happened mid-workflow — the developer starts their day.”

The Mintlify Developer Advocate

A developer advocate, DX engineer, or technical founder at a developer-facing company who chose Mintlify because they believed documentation was a product, not a document. They write docs in MDX. Their docs live in a git repository alongside their code. They ship documentation the same way they ship features: PR, review, merge, deploy. They care about the visual quality of their docs because they know developers judge a product by how it feels to learn it — and bad docs signal a bad API. They've recommended Mintlify to three other devrel teams. All three use it now.

“The shift was quiet.”