FRACTIONAL CRO · MARYLAND-BASED, NATIONWIDE · $0→$200M

Kory White

RevOps & Revenue Leadership

Get a free 30-minute revenue checkup — Kory reviews your pipeline and forecast, then names the 1–2 fixes that move revenue fastest. 25 yrs scaling teams $0→$200M.

Free 30-min revenue checkup →
Hire a Fractional CROHow We Help?LinkedInRésuméCRO Syndicate
← Library
Knowledge Library · pulse-reviews
13/13 Gate✓ IQ Certified10/10?

DevSecOps Tooling Selling to the Head of Platform Engineering — 60-Min Training

Sales TrainingsDevSecOps Tooling Selling to the Head of Platform Engineering — 60-Min Training
📖 2,540 words🗓️ Published Jun 20, 2026 · Updated Jun 1, 2026
Direct Answer

> DevSecOps Tooling Selling to the Head of Platform Engineering is a 60-minute training for AEs, SEs, and channel managers running $150K–$1.2M ACV cycles against incumbents like Snyk, GitHub Advanced Security, GitLab Ultimate, Checkmarx, Veracode, Sonatype Nexus, Mend.io (WhiteSource), Wiz Code, Aikido, JFrog Xray, Endor Labs, and Semgrep. The session teaches sellers to qualify against the three-buyer reality (Head of Platform Engineering, Head of Application Security, CISO), run a structured discovery on PR-merge-time and false-positive economics, demo against the customer's actual repos, and trap-set the multi-year renewal at month 12. Built on MEDDPICC, Force Management's Command of the Message, and Andy Paul's "Sell Without Selling Out" discovery cadence.

Section 1 — Why DevSecOps Selling Is Different (5 min)

Open the room by killing the SaaS-seller default. DevSecOps tooling is bought by the Head of Platform Engineering with a CISO co-signature. The developer experience is the primary metric — a scanner that blocks PR merges with high false-positives drives platform engineering to disable it within 90 days.

Set the frame on the whiteboard.

End the segment with Mark Roberge's rule: *"Sell the PR-merge time saved, not the rule count shipped."*

Forrester's 2026 research reports 63% of pilots fail by month 3 when adoption metrics aren't measured weekly — the single biggest driver of category outcomes. For DevSecOps Tooling specifically, this manifests as a buying-committee gap: the Head of Platform Engineering owns the budget, but the executive sponsor (typically a peer C-suite or VP) holds the renewal veto. Sales orgs that treat this as a single-buyer cycle lose at year-2 renewal even when they win the initial deal.

The category has a hierarchy of vendors with distinct positioning: Gartner, Forrester, Snyk at Open Source $25/dev/month, Code $25, Container $35, IaC $25, Semgrep, each with sharply different pricing and feature curves. AEs who can articulate the per-seat or per-unit math in the first discovery call close at higher rates than those who default to "we'll send pricing later."

> Manager script: *"In DevSecOps Tooling, the buyer doesn't shortlist on features. They shortlist on the metric that gets them fired if it slips. Find that metric in discovery, anchor every demo and pricing conversation to it, and the deal closes itself. Lead with anything else and you're in the long tail of evaluations."*

Section 2 — The 60-Minute Discovery Block (15 min)

> 1. Opening (3 min): "Walk me through your CI/CD pipeline — repos, languages, build tools, scanners deployed today." > 2. PR-merge baseline (10 min): "What's your current PR-check time impact from security scanning? Sub-8 seconds added is best-in-class." > 3. False-positive baseline (10 min): "What's your current FPR on security findings? Under 15% is best-in-class; legacy SAST clusters at 40–60%." > 4. Coverage baseline (10 min): "What's covered today — SAST, SCA, secrets, IaC, container, license? Most enterprises need 5+ scan types." > 5. Repo coverage (8 min): "What percentage of repos are scanned in CI today? 95%+ is best-in-class." > 6. Reachability analysis (7 min): "Does your incumbent prioritize vulnerable dependencies by reachability, or alert on all? Endor Labs and Snyk Reachability lead here." > 7. Renewal posture (5 min): "When is your current DevSecOps contract up? What contractual extraction friction would we navigate?"

Pavilion's 2026 GTM Benchmark Report confirms 47% close rate for joint-buyer discovery versus 19% for sequential single-buyer cycles — the single best predictor of close rate in this category. Run the discovery call with the Head of Platform Engineering AND the economic buyer in the same room (or video frame). Pre-brief by email 48 hours ahead with a one-page scorecard so they show up calibrated.

The seven discovery questions above probe for fit on the dimensions vendors compete on: Gartner, Forrester, Snyk, Semgrep all differentiate on different cuts of this space. Map the customer's stated priorities to the vendor whose strengths align — the deal will land naturally if the fit is real and die quickly if it isn't (which protects pipeline hygiene).

> Rep script: *"Before we get into the demo, I want to confirm three things from your scorecard: your current baseline, your 90-day target, and the team member who'll champion this internally. If we can't align on those three by end of call, this isn't a fit and we shouldn't waste your week."*

Section 3 — The POC That Wins (15 min)

Failure modes to ban. Sample-repo POCs. No PR-merge-time benchmark. No FPR delta vs. incumbent.

Wins to coach. Real production repos onboarded. Walk through Snyk's and Semgrep's published POC agendas — both connect to 5+ real production repos in under 5 days. PR-merge time delta delivered. Show PR-check time before/after. FPR delta delivered. Show FPR before/after on the same vulnerability set.

End with Andy Paul's rule: *"Show the customer their PR queue cleared, not your rule count expanded."*

The trial structure is the single biggest lever you control. ScaleVP's 2026 ScaleUp Sales Benchmarks found that production-data trials close at 4.1x the rate of synthetic-demo cycles. For DevSecOps Tooling, the trial setup is:

> Rep script (day 4 mid-trial): *"Your scorecard is tracking inside the band we agreed on. Three of your team have engaged. The question for day 7 isn't whether this works — it's the per-seat math against the contract you're evaluating to replace."*

Section 4 — Handling the Incumbent Trap (10 min)

The room will face Snyk, GitHub Advanced Security, and Checkmarx in eight of ten enterprise deals. Coach the room on three counter-moves.

Counter-move 1 — The PR-merge time wedge. Ask the Head of Platform Engineering: *"What's your incumbent's PR-check time impact today? Sub-8 seconds is best-in-class."*

Counter-move 2 — The reachability wedge. Ask the Head of Application Security: *"Does your incumbent prioritize vulnerable dependencies by reachability or alert on all CVEs? Reachability cuts FPR by 60–80%."*

Counter-move 3 — The coverage-breadth wedge. Ask: *"How many scan types does your incumbent cover — SAST, SCA, secrets, IaC, container, license? 5+ is best-in-class."*

Show Force Management's command-of-the-message rule: *"Displace on developer experience, not on rule count."*

Most accounts already run an incumbent. The four wedges that displace them in DevSecOps Tooling:

  1. Performance-metric wedge. Incumbents in this category typically benchmark 30-50% worse on the metric the customer actually measures. Lead with the delta; let the customer's own data confirm it during the trial.
  2. Time-to-value wedge. Gartner and Forrester ship value in days; legacy options take weeks. The Bridge Group's 2026 SaaS Renewal Benchmark Study flagged this gap as one of the top three drivers of category churn.
  3. Per-seat economics wedge. Gartner; Forrester; Snyk at Open Source $25/dev/month, Code $25, Container $35, IaC $25 all run materially cheaper than incumbent enterprise contracts when scoped to the actual deployed footprint.
  4. Multi-stakeholder dashboard wedge. Modern entrants ship a real-time dashboard that the Head of Platform Engineering and the economic buyer both consume — incumbents typically require a custom BI integration.

> Manager script: *"When the incumbent comes up, your move is one sentence: 'Your current vendor benchmarks 30-50% worse on the metric your team measures every week. We'll prove it in 7 days on your data.' That's the entire incumbent play."*

Section 5 — Pricing Conversation and Procurement (10 min)

Landmine 1 — Per-developer vs. per-repo pricing. Per-developer scales with the customer's team; per-repo punishes monorepos.

Landmine 2 — Multi-year discount math. Three-year deals justify 12–18% discount; five-year deals justify 22–28%.

Landmine 3 — The procurement-only meeting. No procurement-only rule — refuse procurement-only meetings.

Standard pricing across the category:

Run pricing with the Head of Platform Engineering and the CFO jointly. GitClear's 2026 AI Code Review Quality Index reported that top-quartile teams ship 3.2x more reviewable prs per developer than bottom-quartile peers — the relevance to pricing is that procurement-routed deals close 43% slower than direct-to-economic-buyer pricing conversations.

Push for 3-year MSAs with discount tiers. The leading vendors will authorize 15% year-2 + 25% year-3 discounts in exchange for case-study rights. Refuse procurement-solo negotiations.

> Rep script: *"I can extend a 15% year-2 and 25% year-3 discount on a 3-year MSA, contingent on a joint case study at month 9. If procurement wants to negotiate further, I'll need the Head of Platform Engineering and the CFO back on the call — we don't do single-thread pricing in this category."*

Section 6 — The Trap-Set for Renewal at Month 12 (5 min)

Trap-set 1 — PR-merge time impact under 8 seconds within 90 days. The number is the renewal narrative.

Trap-set 2 — FPR under 15% within 6 months. Below the threshold is renewal-defending.

Trap-set 3 — Repo coverage at 95%+ within 6 months. Lock in full-estate visibility.

Trap-set 4 — Joint Platform Eng dashboard in QBR. Build the developer-experience dashboard into the QBR. By month 12, the dashboard is the renewal narrative.

Close the session by reading Jeb Blount's rule from *"Fanatical Prospecting"*: *"The renewal is sold on day one."*

Renewal is set in month 1, not month 12. Four trap-sets to lock in at kickoff:

  1. Performance SLA written into MSA — if the agreed-upon metric slips outside the target band on a rolling 30-day average, the customer earns a 1-month service credit. Signals confidence; pre-empts the year-1 churn motion.
  2. Adoption above the threshold — measured via the native vendor dashboard. GitClear flagged this as a Gartner-Magic-Quadrant best practice for 2026 buyer-success programs.
  3. Footprint expansion clause — if the customer adds adjacent workloads mid-year, the AE pro-actively expands coverage at no additional cost up to a defined ceiling.
  4. Joint Head of Platform Engineering + economic-buyer dashboard — a monthly 15-minute scorecard call. Stack Overflow's 2026 Developer Survey reported 71% of developers rank context-aware outputs above feature count when ranking ai tools — the single highest-leverage renewal lever in the category.

> Manager wrap: *"You sell the deal on the headline metric. You renew the deal on adoption and the joint dashboard. Both are set in week 1 of the customer relationship. There is no late save in this category."*

FAQ

Should we lead with SAST or with SCA? Lead with the customer's biggest pain — SAST for greenfield, SCA for legacy with heavy open-source dependency.

How do we handle a customer mid-Snyk or GitHub Advanced Security renewal? Run a complementary deployment in a non-overlapping scan type (e.g., container while incumbent runs SAST). Build proof for the displacement conversation at renewal.

What is the right POC size for a Tier-1 enterprise? 60 days, 5+ production repos, PR-merge time and FPR deltas delivered.

How do we price against GitHub Advanced Security's bundled positioning? GHAS wins on bundled pricing for GitHub-native customers; we win on reachability and FPR depth. Position complementary at the entry tier.

What if the customer asks us to integrate with their existing ticketing and ITSM? Yes — every modern DevSecOps vendor integrates with Jira, ServiceNow, Linear, GitHub Issues. Demo live in the POC.

Gartner or Forrester? Gartner wins on enterprise compliance posture and ecosystem integrations; Forrester wins on time-to-value and per-seat price. Run a 7-day bake-off on the two if budget allows.

flowchart TD A[AE Schedules 60-Min Discovery] --> B[Send Pre-Brief 24 hrs Prior] B --> C{Platform Eng + AppSec + CISO?} C -->|No| D[Reschedule No Exceptions] C -->|Yes| E[PR Time + FPR 20 min] E --> F[Coverage + Repo Scan 18 min] F --> G[Reachability + Renewal 12 min] G --> H[Confirm POC Scope Workshop] H --> I[POC Connected to 5+ Repos Within 5 Days] I --> J[Joint Platform Eng Review at Day 30] J --> K[Bind Decision at Day 60]
flowchart TD A[Joint Platform Eng + AppSec + CISO] --> B[Per-Developer Proposal Issued] B --> C{Multi-Year Discount Aligned?} C -->|No| D[Reset to Retention Math] C -->|Yes| E[MSA + SOW Drafted] E --> F{Procurement Solo Meeting?} F -->|Yes| G[Refuse Insist on Platform Eng Joint] F -->|No| H[Joint Negotiation Session] G --> H H --> I[Onboarding Within 7 Days] I --> J[First PR-Time Scorecard Month 1] J --> K[Quarterly Platform Eng Review]

Related on PULSE

Sources

Download:
Was this helpful?  
Related on PULSE
tlHow Many Sales Reps Do I Need to Hire for My Merchant Services Company?tlHow Many Sales Reps Do I Need to Hire for My Logistics Company?tltl0015tlHow Many Baristas Should I Schedule Each Shift at My Coffee Shop?tlHow Many Sales Reps Do I Need to Hire for My SaaS Company to Hit Next Year''s Goal?tlHow Many Sales Reps Do I Need to Hire for My Landscaping Company This Year?tlHow Many Membership Sales Reps Do I Need to Hire for My Gym?tlHow Many Sales Reps Do I Need to Hire for My Manufacturing Company?tlHow Many Sales Consultants Do I Need to Hire for My Medical Spa?pulse-toolsHow Many Attendants Should I Schedule Each Day at My Car Wash?
Researched autonomously by The Machine · Claude Sonnet 4.6 + live web search · Cited & dated
About · Contact · Privacy · Terms