Field Report / 001How FusionAuth turned SDR training into an outbound operating system
SD Lab embedded a progressive coaching and execution system across targeting, messaging, cold calling, campaign construction, call review and pipeline inspection — then helped FusionAuth turn it into a durable operating cadence.
Workshop → embedded operating system
Proof point 01
Engagement record
Weekly coaching and inspection cadence established
Proof point 02
Engagement record
Improved connect performance during execution
Proof point 03
Calling data · engagement record
Report thesisTraining only pays when it becomes operating behavior — FusionAuth is the engagement where a workshop earned enough trust to become the outbound operating system, and then the leadership cadence around it.
- Outbound System
- SDR Leadership
- Coaching
- Pipeline
- Industry
- B2B SaaS | Identity & Access Management
- Engagement
- Workshop → Revenue Rebuild → Embedded Outbound Advisory
- Dates
- 2026
Began as a workshop, expanded into a Revenue Rebuild, and continued as embedded advisory.
Artifacts from the work
A compact view of the work. Open any item to inspect it.
What was actually happening
FusionAuth had SDR talent and outbound activity, but the motion lacked consistency, structure, inspection and a unified operating rhythm. Manual dialing, inconsistent call volume, limited visibility and underdeveloped messaging made it difficult to know whether the team needed more effort or a better system.
What we found
The issue was not simply hustle. Targeting, messaging, live-call behavior, tooling, feedback loops and leadership cadence all needed to work together. SD Lab reframed the engagement from isolated sales training into a working Revenue Rebuild.
Outreach was aimed broadly rather than at a defined buying context.
Relevance could not be proven on a call, so connect quality stayed low regardless of dial volume.
Dialing was manual and volume swung week to week with no floor.
There was no stable denominator, which made every performance conversation anecdotal.
Calls were happening but not being reviewed against a shared standard.
Coaching stayed general. Nothing compounded from one week into the next.
Leadership had no recurring inspection point between the rep's activity and the pipeline.
Problems surfaced at the end of the month instead of during the week they were created.
What we built
- Account and persona prioritization
- A research and relevance standard behind outreach
- Rep-owned weekly outbound plays
- Cold-calling and discovery coaching using live execution
- A competitor-displacement play
- A multichannel outbound campaign built from target accounts through sequence and calling
- Call review, ride-along and weekly commitment feedback loops
- Rep scoreboards and pipeline operating reviews
- Dialer-supported calling and performance visibility
How the work ran
The engagement progressed from workshop → assignment → live execution → inspection → refinement. The SDRs submitted plays and calls, worked from real accounts and campaigns, and received coaching against what was happening in the field rather than hypothetical scripts.
- 01WorkshopThe mechanic gets taught in the room, not mailed as a deck.
- 02AssignmentEach rep leaves with a play they own and submit.
- 03Live executionThe play runs against real accounts that week.
- 04InspectionCalls, plays and activity are reviewed against what actually happened.
- 05RefinementThe system changes based on the field, then repeats.
Receipts from the engagement
How teaching became behavior: each skill moved from workshop to assignment, live execution, inspection and refinement.
The operating structure the engagement strengthened, from account focus through inspection, coaching and iteration.
How the team operates now
FusionAuth moved from fragmented outbound activity toward an inspectable operating system. Targeting became more intentional, execution became measurable, calls became inspectable, coaching became evidence-based and leadership gained a weekly operating rhythm the team increasingly owns.
Broad outreach with no proven relevance
Prioritized accounts and personas with a research standard behind every touch
Manual dialing with volume that swung week to week
Dialer-supported calling with visible performance reporting
General feedback disconnected from live calls
Weekly review of submitted plays and recorded calls against a shared standard
Performance discussed at month end
Weekly inspection of activity, plays and pipeline in a recurring operating review
What we can verify
- Connect performance improved during the execution period, per calling data reviewed with the team
- Outbound meetings were set from the rebuilt motion
- Weekly leadership and rep coaching cadence became established
- Reps submitted weekly outbound plays and worked from real accounts under review
- The team can run the workshop → assignment → execution → inspection loop without SD Lab in the room
- Reps build a multichannel campaign from target accounts through sequence and call track
- A competitor-displacement play exists and can be re-pointed at other migration events
- Leadership inspects calls and weekly commitments against a documented standard
Performance observations come from calling data reviewed during the engagement. Specific client metrics are not published. Workshop goals, meeting targets and modeled pipeline values are not presented as achieved results.
What stayed behind
- Progressive workshop curriculum
- Targeting and persona worksheets
- Weekly outbound play submissions
- Cold-call and discovery field guides
- Competitor-displacement play
- Multichannel campaign build
- SDR coaching playbook
- Revenue Rebuild plan
- Execution reviews
- Performance reporting
What remained unproven
Every engagement leaves something unresolved. These are the limits of what this report can claim.
- The improvement was observed over a limited reporting period — durability across quarters is not yet proven
- Hiring, org design and the next phase of the revenue engine were in progress at the time of publication
Sales training becomes valuable when it turns into operating behavior. FusionAuth is the flagship example of SD Lab teaching the system, building it with the reps, inspecting live execution and helping leadership turn it into an ongoing cadence.
The thinking behind this work
- FrameworksMost SDR Coaching Is ReactiveReactive coaching starts after the miss. This is the inspection cadence: daily, weekly, monthly, quarterly. That surfaces the problem while there is still time to change it.Read
- FrameworksThe Constraint Nobody Is Looking AtApparent rep-performance problems are often system constraints. How to tell the difference before you coach, PIP or replace.Read
- FrameworksYou Don't Have an Activity Problem. You Have an Aim ProblemWhy teams can hit activity KPIs while missing pipeline because targeting and prioritization are wrong.Read
More in the Resource Library and on Media.
Build Your Outbound Operating System
If you want this kind of operating-partnership work in your own org, see how the Revenue Rebuild works today. Read the evidence first, then we can talk about your system.
Published from the engagement record. Client metrics, commercial terms and internal documents are intentionally not published. Diagrams are conceptual summaries, not client files.