Library / Tool / Speed-to-lead score: ingest lag and first-touch lag

ToolHow to wire it

Speed-to-lead score: ingest lag and first-touch lagIf GHL sees the lead at 9:12 and they submitted at 9:03, you already lost a share.

Speed-to-lead is two clocks: ingest (source → GHL) and first outbound (GHL → SMS/call). This scorecard is how an intern measures both in coverage hours and after hours. Vendor dashboards and 'we try to call same day' are not scores. Each yes is a point; the number is how many clocks you can defend.

00

The short version

Intern through CEO

Speed-to-lead is two clocks: ingest (source → GHL) and first outbound (GHL → SMS/call). This scorecard is how an intern measures both in coverage hours and after hours. Vendor dashboards and 'we try to call same day' are not scores. Each yes is a point; the number is how many clocks you can defend.

  1. 01

    Measure ingest separately from human speed. A fast human on a 12-hour ingest is still slow.

  2. 02

    Coverage-hours filter. Overnight leads should not ruin an in-hours median without being labeled.

  3. 03

    CSV as the process scores zero on ingest, even if someone is 'fast' on Monday.

  4. 04

    After-hours silence until morning scores zero on the after-hours row.

  5. 05

    Use this score before you buy more ads into that source.

Who

Same system. Three jobs.

Read your row

Intern

What you actually do

You own the stopwatch and the two timestamps. CSV is not a workaround you get to keep.

Operator

What you protect

Two clocks. Coverage filter. After-hours designed. Token health. One source at a time.

CEO

What you refuse to fund

Speed-to-lead is a score, not a vibe. Ingest lag is an outage. Until the score is defensible, more media is more cooling.

Wire

How to connect it

Objects, then edges

Source timestamp, GHL create timestamp, first outbound timestamp, coverage hours, after-hours path, owner, CSV ritual (should be zero).

  1. 01

    Instant Form / Google lead / portal / web form → GHL in minutes

  2. 02

    In-hours → SMS or call under the SLA (often five minutes)

  3. 03

    After hours → honest SMS now; queue ordered by wait

  4. 04

    Token/webhook failure → P1, not a marketing story

Steps

Do this in order

Why, then done when
  1. 01

    Pick one source

    Meta, Google lead form, web, portal, phone. One this week.

    Why: Blended speed hides the dead door.

    Done when: Source named.

  2. 02

    Time ingest

    Submit test. Source timestamp vs GHL created.

    Why: This is clock one.

    Done when: Minutes written.

  3. 03

    Time first outbound

    SMS/call timestamp on the contact.

    Why: Clock two.

    Done when: Minutes written.

  4. 04

    After-hours test

    If you claim 24h demand.

    Why: Honesty.

    Done when: Contact created now + honest SMS or fail.

  5. 05

    Score and ticket

    Sum the rows. Gaps are tickets, not ad copy.

    Why: Optimizing ads on a dead webhook is the usual waste.

    Done when: Score posted.

Intern

Stopwatch. Two timestamps. After-hours if relevant. You are not writing ad copy.

CEO

Refuse spend increases on a source that scores poorly on ingest. You are buying cooling leads.

Failure

CSV Monday. Token dead. After-hours voicemail. 'Same day' as a slogan. Blended minutes.

Test

One live submit. Two timestamps. Score the rows. File P1 if ingest is hours.

Why

Questions people actually ask

Pushback is normal

Isn’t first-call-win a sales thing?

Ingest is ops. If the CRM is hours late, sales never got a fair clock.

We don’t SMS.

Then first outbound is a call or email — still timestamp it. SMS is often faster; it is not the only legal clock.

Agency owns the lead inbox.

Then you score zero on system-of-record until ingest is your GHL. Agency speed you cannot see is folklore.

Sheet

Score it this week

0% · 0/10

Each row is a pass/fail. 0% is not a grade for the brand — it is whether the objects exist. Under 50% means do not add traffic. 50–80% means finish write-in. Above 80% means review Monday, then the next leak.

  1. Source timestamp available (not only 'today')

    Ads Manager / form / call vendor. 1 if yes.

  2. Ingest to GHL ≤ 5 minutes on a test

    1 if yes. Hours = 0.

  3. CSV is not the operating process

    1 if no weekly import ritual.

  4. First outbound ≤ 5 minutes in coverage hours

    SMS or call logged on the contact.

  5. Owner on create (not Slack claim)

    1 if GHL assignment exists without a channel.

  6. After-hours creates the contact immediately

    1 if yes. Holding until morning = 0.

  7. After-hours SMS tells the truth about hours

    1 if honest. 'We’ll call now' when closed = 0.

  8. Morning queue ordered by wait time

    1 if yes. Random inbox = 0.

  9. Webhook/token health checked this week

    1 if someone looked. Silent death = 0.

  10. Median minutes reported with coverage filter

    1 if the number is defined. Blended vibe = 0.

This week

This week: score one source, after-hours if you take those leads, ticket ingest if > minutes, no extra spend on that source until ingest passes.

Working notes

GHL Engine Checklist

The minimum CRM, pipeline, and nurture spec before you add more pages. Request the file. It arrives by email — not a public dump, not a drip of slogans.

Request the notes ↗
Next

If the leak is expensive, talk.

Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.