01 Start with the task
Before writing a headline, finish this sentence: “This helps [person] complete [task].” A category such as productivity or automation is too broad to tell someone whether to keep reading. Name an observable activity, such as turning approved meeting notes into a draft follow-up.
The narrower sentence also gives you something to demonstrate.
02 Separate availability from ambition
Say what a reader can access today. A private beta, a recorded demonstration and a generally available product are different offers.
Explain required accounts, supported inputs and important limitations near the invitation to try it. If a feature is planned, label it as planned instead of placing it in the current workflow.
03 Show one representative example
Describe the starting input, the action and the resulting output. Use information you have permission to share.
If the output needs human review, include that review in the example. Avoid choosing a polished result that conceals a limitation a new user is likely to encounter.
04 Give the reader one next step
Choose the action that fits availability: try the product, request access or watch the demonstration. Test the link as a new visitor.
Ask one specific feedback question, such as where the workflow became unclear. Review those responses after launch and update the announcement if the same confusion recurs.