with the skill
**A: Clear differentiator, no existing draft.** I’d use two audience-specific heroes: lead with the social awkwardness for founders and the scheduling workflow for enterprise ops. Keep the calendar overlay central in both.
## Indie founder version
### Send a scheduling link that feels fair to both of you.
Your invitee can overlay their own calendar on your invite and compare it with your availability. They can pick a time with both schedules in view.
**CTA:** Create a scheduling link
*Supporting line:* Your availability. Their calendar. A time that works for both.
## Enterprise ops version
### Let invitees compare calendars before they choose a time.
Recipients can overlay their own calendar on your scheduling invite to see where your availability fits into their day. Give them the context to choose a time that works for both sides.
**CTA:** Create a scheduling link
Show the rest (13 more lines)
*Supporting line:* Recipients choose with their own calendar in view.
## Why these differ
- **Founders:** The headline addresses the hesitation around sending someone a link and asking them to accommodate you.
- **Enterprise ops:** The headline explains the workflow directly, without implying unverified security, scale, or compliance capabilities.
### Alternative headlines
- **Founders:** “Make your scheduling link feel more considerate.” Softer and more understated than “fair.”
- **Enterprise ops:** “Put both schedules in view when recipients book.” More compact, with the mechanism front and center.
**Alternative CTA:** “See how calendar overlay works” if the next step is a product walkthrough rather than link creation.