Your press release failed because of timezones.
Founder in Singapore sends to TechCrunch at 9am.
His time.
It's 6pm in San Francisco. Everyone's gone home.
His email sits overnight. By their morning it's buried under 150 newer emails.
Zero response.
Here's what nobody gets:
Your press release doesn't exist in "internet time."
It exists in someone's workday. Their office hours. Their timezone.
You're not sending to "the internet."
You're sending to Dave in London who starts at 9am GMT.
Or Sarah in NYC who's slammed until 11am EST.
Real example:
Austin startup sends to UK outlets at 10am Central.
That's 4pm London. Brits are wrapping up for the day.
Release sits overnight. By their 9am, it's 12 hours old. Buried.
Same release. Sent at 2am Central (8am London time).
3 pickups by lunch.
What actually works:
TechCrunch in SF? Send 9-11am Pacific. Forbes in NYC? Send 9-11am Eastern. Guardian in London? Send 9-11am GMT.
Send in THEIR morning. Not yours.
Multi-timezone targets?
Don't send once. Send three times.
- 9am EST for NYC
- 9am GMT for London (schedule for 4am EST)
- 9am SGT for Singapore (schedule for 9pm EST previous day)
One release. Three send times.
Today's challenge:
Pull up your last press release.
What cities were your target outlets in?
What time was it THERE when you hit send?
Post it below. Let's see how many of us accidentally emailed journalists at 3am.
Posted Feb 26, 2026, 7:44 AM UTC