FIRST-PARTY DATA
The State of Intake
GateCurate scores every inbound submission for fit before an operator ever sees it. These are the aggregate numbers from the founding cohort's actual intake data — not a survey, not an estimate.
n = 47 submissions · 2026-06-26 – 2026-09-16 · pulled from production 2026-09-26 · full methodology below.
87%
Scored automatically, before a human looked
What this means for operators: the fit-scoring step is already doing most of the triage. Only the remainder needs a manual look just to get categorized.
Priority tier, of the 41 scored submissions
24%
Hot (Red) — n=10
34%
Warm (Yellow) — n=14
41%
Cool (Blue) — n=17
What this means for operators: a bit under a quarter of everything that clears scoring comes in hot enough to warrant a same-day call. The rest can wait for a batch.
Vertical mix, of 47 submissions
Real Estate & Property Management
28% (n=13)
No vertical specified
26% (n=12)
Other named verticals (Construction, Home Services, Creators & Coaches, Media/Entertainment/PR)
26% (n=12)
Across Verticals (legal, healthcare, professional services, tech)
21% (n=10)
What this means for operators: real estate & property management is the single largest identified vertical in the founding cohort — but "no vertical specified" is nearly as large, which says as much about how early intake happens as it does about who's sending it.
Methodology
Every figure above comes directly from GateCurate's production intake database
(Cloudflare D1), pulled 2026-09-26. The base population is 47 rows in the leads table: submissions to the operator-intake fit-scoring pipeline
between 2026-06-26 and 2026-09-16, with the site's newsletter sign-ups and
vendor-form submissions excluded (they aren't scored for fit), and 4 internal
QA/smoke-test runs removed.
"Priority tier" is the fit-scorer's own color grade — Hot (Red), Warm (Yellow), or Cool (Blue) — shown as a share of the submissions that were actually scored. A fourth grade, "Not-a-fit / Evergreen," exists in the product but isn't shown here: too few submissions carry it, and the underlying field also defaults unscoreable submissions into that same bucket, so it doesn't cleanly measure "wrong-fit" the way a public number should.
Minimum cell size: every slice published on this page represents at least 10 submissions. Where a real category (an individual vertical, for instance) fell below that floor, it's grouped into a combined "other" bucket rather than shown on its own.
Not shown: median time-to-first-response isn't published because GateCurate's schema doesn't yet capture an operator's first response as a timestamp — only when a lead record was last edited, which isn't the same thing. We'd rather show nothing than a number that doesn't mean what it claims.
This is a snapshot, refreshed by hand as the founding cohort grows — not a live query against the database. Press & data requests: support@gatecurate.com .