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

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 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 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 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 Hex Collaborative Data Analyst

A data analyst or analytics engineer who uses Hex because it combines everything they used to do across 3–4 separate tools into one collaborative environment. They write SQL to pull data, Python to transform it, and build visualizations and dashboards — all in the same notebook. They share their work as interactive apps that stakeholders can explore without learning SQL. They've replaced Jupyter notebooks, Mode, and Google Sheets with Hex. They are the data person who makes data accessible to people who aren't data people.

“The marketing team asks: "Which campaigns drove the most pipeline last quarter?" The data analyst opens Hex, writes a SQL query to pull campaign data, joins it with pipeline data, and adds a Python cell to calculate attribution.”