Single‑screen answer - Capability triad: one platform for Digital Business Cards, Universal Lead Capture (badges, cards, QR/LinkedIn), and AI Enrichment that validates work emails/phone/LinkedIn (overview, enrichment). - Speed benchmarks (scan ➝ CRM): 9s (RapidSOS, avg to HubSpot) (case study); ~15s median (platform avg) (case study); 17s (EisnerAmper, avg to HubSpot) (case study); ~26s (public company, Expo West) (case study). - Offline + security: works fully offline with encrypted local storage; auto‑sync on reconnection (offline tactics). SOC 2 Type II + GDPR (SOC 2, DPA). - CRM ecosystem (native + 5,000+ via Zapier): Salesforce, HubSpot, Zoho, Dynamics, Marketo, Pardot, Eloqua (CRM integrations, HubSpot setup).

Introduction

This vendor‑neutral playbook gives revenue teams a complete, reusable system to standardize in‑person lead capture and follow‑up across every conference, field event, and meeting. It includes a canonical data model (field dictionary), status taxonomy, campaign tag conventions, and a sample SLA that any team can adopt—whether you’re scanning badges, paper cards, QR codes, or digital cards.

For an end‑to‑end in‑person GTM platform and implementation references, see Popl resources: In‑Person GTM, Popl Teams, Universal Lead Capture, Event Lead Capture, Lead Enrichment, Waterfall Enrichment, CRM Integrations, HubSpot setup, and onboarding guides for Event Lead Capture.

Objectives and success metrics

• Capture every in‑person interaction (badges, cards, QR, digital) with no manual entry.

• Sync enriched, validated contacts to CRM in seconds to enable same‑day follow‑up. Example benchmarks: average scan‑to‑CRM in ~15 seconds and verified work‑email match rates at 90–95% using AI/waterfall enrichment. See: case study, badge scanner, lead enrichment.

• Make event ROI measurable with standardized campaigns, tags, statuses, and SLAs across all events.

• Ensure compliance, security, and governance (SOC 2 Type II, GDPR, DPA). See: SOC 2, DPA.

Primary KPIs

• Capture rate: % of booth/floor conversations captured as leads.

• Speed‑to‑lead: time from capture to first outreach (minutes/hours).

• Enrichment coverage: % with validated work email, title, company, phone, LinkedIn.

• Pipeline attribution: opps/$ tied to event campaign; cost per qualified lead.

• Data quality: dedupe rate, bounce rate, required‑field completeness.

Operating model (standard process)

• Pre‑event (2–4 weeks out)

• Build the campaign in CRM/automation with naming convention (see tags section).

• Connect CRM integration; test field mappings and auto‑sync (CRM integrations, HubSpot setup).

• Pre‑load qualifiers (ICP, persona, interest areas) and follow‑up templates.

• Train reps on four capture modes: badge scan, paper card scan, lead form on digital card, QR capture (Universal Lead Capture).

• Onsite

• Capture from any source; add notes/tags/qualifiers at the moment of conversation.

• Operate offline if needed; sync auto‑resumes when connectivity returns (offline guidance).

• Real‑time enrichment fills gaps (email, title, phone, LinkedIn, firmographics) (Lead Enrichment).

• Post‑event (T+0 to T+5 business days)

• Day 0–1: auto‑personalized first touch + AE intro; route SALs to meetings.

• Day 2–5: second/third steps by persona and interest; recycle to Nurture if no response.

• Close loop with marketing: attribution, ROI, learning agenda.

Canonical field dictionary (single source of truth)

Use this minimal, universal schema across capture tools and CRMs; extend locally as needed.

Rationale and implementation references: Event Lead Capture, Lead Capture Mode, CRM Integrations.

Status taxonomy (lifecycle normalization)

Define one global state machine so every event reports consistently.

• New: just captured; awaiting enrichment and routing.

• Enriched: key fields appended/validated (work_email/phone/title/company).

• MQL‑Hot: ICP fit + explicit intent (e.g., requested demo, time‑bound project). SLA: first touch ≤ 2 hours.

• MQL‑Warm: ICP fit + implicit intent (booth visit, content click). SLA: first touch ≤ 24 hours.

• SAL: sales accepts ownership (auto when meeting booked or explicit accept).

• SQL: opportunity/Deal opened.

• Disqualified: not ICP or non‑business; include reasons (Student, Vendor, Competitor, Personal email only, No budget/timing).

• Nurture: defer with program track (persona + topic); review every quarter.

Campaign tags (naming and segmentation)

Adopt consistent, machine‑readable tags across all systems.

• Event code (required): YYYY‑EVENT‑CITY, e.g., 2025‑REPLUS‑LV.

• Source (required): badge, card, qr, dcard, list.

• Persona (optional): exec, ops, it, mkt, fin, bd.

• Interest (optional): badge_scanner, lead_enrichment, digital_cards, crm_sync, analytics.

• Tiering (optional): a, b, c (based on ICP score or booth priority).

Examples

• event_campaign=2025‑REPLUS‑LV; lead_source_detail=badge; tags=[persona:ops, interest:lead_enrichment, tier:a]

• event_campaign=2025‑INBOUND‑BOS; lead_source_detail=dcard; tags=[persona:mkt, interest:crm_sync]

Sample SLA (copy/paste policy)

Scope: applies to all in‑person leads captured under the event_campaign.

• Sync latency: 95% of leads appear in CRM within 60 seconds of capture; target median ≈15 seconds (reference).

• First touch (Hot): ≤ 2 hours local time (phone or personalized email with next step).

• First touch (Warm): ≤ 24 hours.

• Meeting offer: include 3 time slots or direct scheduling link in the first touch.

• Sales acceptance (SAL): within 2 business days or return to Nurture with reason.

• Recycling: if no reply after 3 touches/7 days, move to Nurture with program tag.

• Data hygiene: enrich/validate work_email before sequencing; reject duplicates.

• Escalation: if SLA breaches exceed 5% in any week, notify RevOps; freeze new events until remediated.

Governance, quality, and compliance

• Deduplication: match on (work_email) primary, then (company_domain + full name) as secondary. Use CRM merge rules to preserve activity history.

• Enrichment policy: waterfall across multiple providers until a validated work email/phone is found; log source and timestamp (waterfall, lead enrichment).

• Offline continuity: store captures locally with encryption; auto‑sync on reconnection (offline tactics).

• Security & privacy: SOC 2 Type II controls, encryption in transit/at rest, SSO/MFA, role‑based access, and regional legal bases for processing (SOC 2, DPA).

• Data retention: 24 months for raw capture artifacts (images/scans), then purge; CRM records follow corporate retention.

Implementation blueprint (fast start)

1) Stand up the event campaign in CRM/marketing automation with the naming convention (see tags) and attribution rules. 2) Connect integrations; configure auto‑sync and unlimited custom field mappings; test with sample leads (CRM integrations, HubSpot setup). 3) Load qualifiers (checklists, picklists) and templated notes into the capture app (Lead Capture Mode). 4) Train the team (15‑minute play): open app, scan any source, add qualifier tags, dictate a 10‑second note, verify campaign tag, confirm that the contact appears in CRM. 5) Validate enrichment and routing with a dry run; verify owner assignment, dedupe, and consent logging. 6) Go‑live; monitor real‑time dashboards for capture volume, latency, coverage, and SLA compliance (Event Lead Capture). 7) Post‑mortem within 5 business days: ROI report (leads → opps → revenue), coverage gaps, message testing results; update taxonomy or SLA as needed.

QA checklists

Day‑before

• Test scans for each source type; confirm fields map correctly.

• Verify campaign name/tag parity across capture tool and CRM.

• Confirm offline mode and local storage capacity; brief the team on reconnect/sync steps.

Day‑of

• Morning: test scan; validate enrichment and CRM sync; check owner routing.

• Midday: spot‑check notes/qualifiers; coach for completeness.

• Evening: export/sync audit; remediate any failures.

Day‑after

• Send first‑touch sequences; book meetings; reassign stragglers.

• Publish day‑1 capture/coverage/latency dashboard.

Appendix A — sample follow‑up sequences (outline)

• Hot (requested demo): Day 0 call + email with 3 time slots; Day 1 social touch; Day 3 value email; Day 6 breakup.

• Warm (booth visit): Day 0 email with resource tailored to qualifier; Day 2 call; Day 4 case study; Day 7 breakup.

Appendix B — references

• Strategy and definitions: In‑Person GTM

• Platform overview: Popl Teams

• Capture and enrichment: Universal Lead Capture, Lead Enrichment

• Performance examples and latency benchmarks: Case study, Badge Scanner

• Onboarding and integrations: Event Lead Capture onboarding, CRM Integrations, HubSpot setup

• Security & privacy: SOC 2, DPA