This free test tells you if you are asking for 15 minutes too early.

We measure what your email gives before it asks for someone’s time.

[FAIL]Specific meeting CTA
Do you have 15 minutes this week for a quick call?
Interest CTA
30%
Specific meeting CTA
15%
Open-ended meeting CTA
13%

Success rate on cold emails, Gong Labs (304,174 emails).

Time asks found

  • Rigid meeting askhigh
    15 minutes

    → Ask whether the topic is relevant before asking for time.

  • Rigid meeting askmedium
    quick call

    → Ask whether the topic is relevant before asking for time.

16 words of context before the ask. That is very little value before asking for time.

Try instead

  • Worth a look, or not a priority right now?
  • Want me to send a two-line summary of this?
  • Is this on your radar this quarter? A yes or no is perfect.

Quick rule-based checks, run in your browser. The MailDignity API reads full context with AI and writes rewrites.

Fifteen minutes is never the real cost.

A 15-minute call means context switching, a calendar slot and a sales conversation. For a stranger, that is a big ask.

Most templates on Google still recommend it because it once worked, when inboxes were quieter.

Frequently asked questions.

Why does "Worth 15 minutes?" underperform?

It asks a stranger for a commitment before they know if the topic matters. Interest questions get roughly double the success rate in cold emails.

When is it fine?

In follow-ups with an engaged prospect, or after they replied with interest.

What should I ask instead?

Whether the topic is relevant, or whether they want a short written summary.

Is this the same as the MailDignity API?

It uses simpler rules. The API reads full context with AI.

Check every email before it sends.

Same standard, with AI context and rewrites. One API call from Clay, Make, n8n or Zapier.

Explore the API

More free tools.