A free trial should show the core promise once

A trial design prompt about activation events, usage caps, and feature gates.

A free trial that hides the core promise may protect revenue on paper but fails to teach the product. I would let the user complete the main workflow once, then charge for scale, repetition, team use, or reliability. Where do you draw the line between useful trial and giving away too much?