Question 1

Is charging on?

Accepted Answer

Yes. Free stays free. Pro, Team, and the $29 lifetime export check out through pay.yito.ai.

Question 2

Are end users counted as seats?

Accepted Answer

No. Seats are teammates in the dashboard. People who answer the widget are unlimited.

Question 3

What does BYOK mean?

Accepted Answer

Bring Your Own Key for later AI upgrades. Available on every plan, including Free.

Question 4

How will annual billing work?

Accepted Answer

Annual is 20% off the monthly seat price, billed once a year. Same seats. Same features.

Question 5

Is there a limit on signals?

Accepted Answer

No. Signals from people who answer the widget are unlimited on every plan.

Question 6

Will you email my users?

Accepted Answer

No. Email surveys die. The product is one in-app question at the paywall.

Question 7

Is the sentence enough?

Accepted Answer

No. Cancel and pricing reasons are hypotheses. Compare usage, leftover credits, and Stripe before you ship a change.

Question 8

When does more paid start?

Accepted Answer

If you had no paying customers yet, the period starts on the first paid customer. If you already had a Stripe book, the first customer-id sync locks those ids as baseline. More paid is a score, not a fee.

Question 9

How do you know a new conversion order?

Accepted Answer

A new conversion is the first successful pay by a Stripe customer id or user id that was not in the baseline set. They stay new this period. The same id paying again is a renewal. The same id paying more is an upgrade. Totals alone cannot tell them apart.

Decision	DataFast	MakeThisBetter	PostHog	MorePaying
Core question	Which channel creates revenue?	What should we improve?	What happened in the product?	Why did a ready-to-buy user stop or pay?
Native capture moment	Visit → signup → payment attribution	In-product feedback anywhere	Events, funnels, surveys, experiments	Pricing, checkout, paid, and cancel moments
Default evidence	UTM, referrer, journey, revenue	Screenshot, DOM, console, recording	Events, properties, replay, cohorts	Reason, plan, usage, channel, money, Stripe status
Agent workflow	MCP, API, and CLI for analytics	Skill, MCP, and CLI turn feedback into code	Analytics and experimentation workflows	Pick the highest-value blocker, ready it, release through a SHA
Proof after shipping	Channel and campaign revenue	Feedback moved to shipped and reporter notified	Funnel and experiment metrics	Blocked revenue plus 7/14/30-day paid lift for the release
Best fit	Marketing allocation	Broad product feedback	Product analytics platform	Paywall conversion work for SaaS and AI products

The missing layer after analytics and feedback

Stop collecting reasons that never become revenue work.