with the skill
**Diagnosis:** A. You gave me a differentiator and an audience split, with no existing draft or voice to preserve. I'm building from the overlay mechanic only and inventing no proof.
## Hero (shared version)
**Headline**
Pick a time with both calendars in view.
**Subhead**
Send a booking link. The person you're meeting layers their own calendar over your open slots and picks a time that fits both of you.
**Primary CTA**
Create your scheduling link
**Proof line (under CTA)**
[NEED: real customer count, logos, or a named quote. Ideally one indie and one enterprise name.]
## Alternative headlines
- **A:** Pick a time with both calendars in view. *Rationale: it describes the mechanic as a picture. It passes "Now you can…" and makes no claim either audience would read as a red flag.*
- **B:** Book meetings where the other person can check their calendar too. *Rationale: it puts the invitee's experience first, which is the fairness angle. It's longer and slightly less visual.*
Show the rest (23 more lines)
- **C:** The scheduling link your invitee can check against their own calendar. *Rationale: it fits the "{category} for {audience}" formula and is the most literal, but the least emotional.*
## The indie/enterprise problem
One page can serve both, but only if the hero avoids words that split them. "Move fast" reads as immature to enterprise buyers, and "enterprise-grade" reads as bloated to founders. The shared hero above talks only about the mechanic, which both groups value. Fairness works for a founder booking a customer call and for an ops team booking external vendors or candidates.
If you can split traffic (separate URLs, ad groups, or a persona toggle), swap only the subhead and secondary CTA:
**Indie founders**
- Subhead: Send a link, and your invitee sees their own calendar next to your open slots. You skip the "does Thursday work?" thread and look organized doing it.
- CTA: Create your scheduling link
- [NEED: free plan or trial terms, so the CTA can say it]
**Enterprise ops teams**
- Subhead: Every external invitee sees their own calendar beside yours when they book, so conflicts are visible before they pick a time.
- CTA: Book a demo
- [NEED: confirm you have a sales-led path. If not, keep the self-serve CTA.]
## Open items before this ships
1. **Privacy of the overlay.** Enterprise buyers will ask first whether the host can see the invitee's event details. If the answer is no, that's a strong line for the subhead, but I can't write it until you confirm.
2. **Enterprise credibility.** I left out security and compliance claims. Send me certifications, SLAs, or admin controls you actually have and I'll add a proof line for that variant.
3. **Outcome claims.** I avoided "fewer reschedules" and "faster booking" because nothing here supports them. Any usage data, even from a pilot, would let me write a stronger subhead.