Field Reports

The work, documented

Real outbound engagements broken down by baseline, diagnosis, system installed, observed change and what remained unresolved. No victory-lap case studies. No mystery math.

Evidence over attribution

Published field reports

Title slide of a workshop deck reading 'Outbound That Actually Works' with SD Lab and FusionAuth branding.
Report / 001FusionAuth logoFusionAuthSDR Summit → Revenue Rebuild → Advisory

From SDR training to an embedded outbound operating system

An SDR training engagement earned deeper operational trust and expanded into outbound strategy, SDR development, hiring, org design and leadership alignment — ending as an embedded operating cadence rather than a workshop.

  • Outbound System
  • SDR Leadership
  • Coaching
  • Pipeline
  • ~4% → 7.73% connect rate· Nooks · Jul 2026 window
  • 1,411 dials · 3 meetings set· Nooks export
Read Field Report
First page of the Outbound System Build document for Visual Identity Group, listing the overview and opportunity summary.
Report / 004Visual Identity Group logoVisual Identity GroupFounder-led outbound system build

From Outlook to a founder-led outbound OS

A founder moved from scattered relationship-and-referral selling to operating a documented outbound workflow himself, built around how he actually works rather than around an outsourced team.

  • Founder-Led Sales
  • Outbound System
  • Messaging
  • ~7 weeks to founder-operated handoff· Engagement timeline · Dec 2025–Feb 2026
  • Founder running the weekly workflow independently· Handoff review
Read Field Report
Engagement overview document listing the project goal, timeline, deliverables and who does what.
Report / 003Queryon logoQueryonFounder-led sales system build

Turning founder-led sales into an installable system

The founder needed founder-led sales to become repeatable, measurable and eventually transferable to an SDR/AE team. The system installed; outbound messaging signal still needed iteration at the end of the build.

  • Founder-Led Sales
  • Outbound System
  • Enablement
  • Founder-led sales system documented and installed· Engagement deliverables
  • Custom SOWs → four repeatable proposal types· Proposal framework
Read Field Report
Historical outcome receiptFR/006
S44
27 enterprise meetings$100K+ qualified pipeline
Report / 006S44Outbound engine build from scratch

Building an outbound engine from scratch

A lean early-stage automotive SaaS team had no outbound function at all. The work was to define the target, build the message and install a calling motion the team could run itself.

  • Build From Scratch
  • Outbound System
  • Pipeline
  • 27 enterprise meetings· Client engagement record
  • $100K+ pipeline· Client engagement record
Read Field Report
Scope of work page from the SD Lab proposal for ServiceChannel listing sales messaging, tech stack and process development gaps.
Report / 005ServiceChannel logoServiceChannelSDR Enablement Accelerator → Cadence & Sequence Build

Stabilizing an inherited SDR team

An enablement leader inherited a seven-person SDR team while still carrying Sales Enablement. The work was to stabilize the team with playbooks and cadence rather than turn that leader into a full-time SDR manager.

  • SDR Leadership
  • Enablement
  • Messaging
  • Coaching
  • Behavior and process change in under one month· Client testimonial · Jul 2023
  • Playbook, vertical campaigns and a written SDR→seller handoff· Engagement deliverables
Read Field Report
Opening slide of the Kustomer Sales Accelerator kickoff workshop deck.
Report / 002Kustomer logoKustomer14-week Revenue Accelerator

From one-off training to a 14-week SDR performance system

Two SDR managers, a VP of Sales and a 15-person SDR team moved from one-off training to a weekly performance operating cadence with coaching, inspection and shared standards.

  • SDR Leadership
  • Coaching
  • Enablement
  • Pipeline
  • 50% Q2 → 81% Q3 → low-90s Q4· Ryan O'Donnell · client testimonial
  • 3 SDRs promoted to Commercial AE· Client testimonial
Read Field Report

The evidence standard

Every report follows the same shape: the baseline before the work, the constraint we diagnosed, the system installed with the team, the change we can actually verify: labeled as measured or client-reported — and the questions that stayed open. Where causality can't be claimed, it isn't.

Earlier engagement write-ups predate this standard and are kept for continuity in the pre-standard archive.