Pre-standard archive. This write-up predates the Field Report evidence standard and its claims are not source-verified. Verified engagements are published as Field Reports.
Building the operating system behind a growing SDR organization.
A documented rebuild of the outbound infrastructure, leadership cadence, messaging system, and SDR operating rhythm installed inside a growing developer observability company.
An executive summary of the rebuild.
Outcome figures are approximate and reflect the engagement window. Business results are the client's to report.
Every Rebuild Report documents the operating system behind a real client engagement. Names, metrics and proprietary details may be generalized to protect confidentiality, but the methodology reflects the actual work completed.
Six phases. One operating system.
Every Revenue Rebuild moves through the same six phases in the same order. Kentik, FusionAuth and every future engagement map to this backbone.
The order is deliberate. Observation before diagnosis. Diagnosis before wedge. Wedge before installation. Installation before adoption. Adoption before compounding. Skipping a phase produces the failure mode of the phase before it.
- Phase / 0101 / 06ObservationWatch before you write.
Sit with the team as it currently runs. Live calls, pipeline reviews, manager 1:1s, existing documentation. No recommendation written until the operating system has been observed in motion.
- Phase / 0202 / 06DiagnosisName what is actually breaking.
Document, in shared language, the specific places the operating system is failing to compound. Ambiguity is the diagnosis before activity is.
- Phase / 0303 / 06WedgeNarrow before you sharpen.
Narrow the ICP and name the buyer conversation with the sharpest signal. Messaging cannot be fixed on top of a diffuse target. The wedge is usually already inside the product story.
- Phase / 0404 / 06InstallationRebuild the calendar, not the deck.
Install the operating system — messaging spine, qualification standard, coaching rubric, pipeline review shape, manager operating rhythm, inside the client's own tools, alongside the existing business.
- Phase / 0505 / 06AdoptionAdoption is behavior, not announcement.
The signal is unprompted use — reps and managers referencing the frameworks in their own words, in their own week, without being asked. Language shifts precede metric shifts.
- Phase / 0606 / 06CompoundingThe system runs after the consultant leaves.
Weekly rhythm holds without the consultant in the room. Frameworks are updated in place, owned by named people, reviewed on a cadence. The operating system becomes internal infrastructure.
Situation
Kentik had strong executive backing, capable managers, and a full SDR bench selling network observability into platform, SRE, cloud ops, DevOps and security teams.
What it did not have was a shared operating system underneath them. Messaging drifted from rep to rep. ICP definitions were interpreted differently across managers. Account prioritization relied on individual instinct rather than a documented framework.
Pipeline reviews happened, but qualification standards were not consistent across the team. Coaching quality depended on which manager a rep reported into. Documentation existed in scattered docs and Slack threads, but it was not operationalized into the rhythm of the week.
The team had support and talent. It did not yet have a repeatable system.
- Industry
- Developer Observability
- Buying Committee
- Platform Engineering · SRE · Cloud Ops · DevOps · Security
- Technical Buyer
- Platform / SRE lead evaluating network observability at cloud scale
- Organization
- Multi-manager SDR org, ~15 reps, aligned to enterprise AE segments
- Sales Motion
- Outbound-led enterprise, multi-thread, multi-quarter cycles
- Enterprise Complexity
- Technical evaluation, security review, multi-stakeholder sign-off
Initial Diagnosis
A documented assessment before any recommendation was written.
- Messaging changed noticeably from rep to rep, even inside the same vertical.
- ICP definitions were interpreted differently by each manager.
- Account prioritization depended on rep instinct rather than documented criteria.
- Pipeline reviews lacked shared qualification standards.
- Coaching quality varied with individual manager style.
- Documentation existed, but was not operationalized into the weekly rhythm.
Install a repeatable outbound operating system rather than improve isolated activities.
What We Rebuilt
Account Qualification Framework
01A written framework SDRs use to separate buying signals from company fit. Reps can articulate why an account is being worked, not just that it is.
Buying Committee Personas
02Personas documented for platform, SRE, cloud ops, DevOps and security — what each owns, how they get evaluated, and what a useful conversation with them sounds like.
Account Prioritization System
03A tiered account model reps consult on Monday morning. Fit, intent, and access are graded consistently instead of assessed one rep at a time.
Persona Prioritization Matrix
04Personas ranked by influence, urgency, and reachability so reps stop opening the wrong title inside the right committee.
Outbound Messaging System
05One messaging spine spanning vertical narratives, persona angles, and objection-ready proof points. Reps compose from it instead of writing from scratch.
Cold Call Frameworks
06Conversational scaffolding built from live-call review — openers, transitions, discovery, and next steps that hold up with technical buyers.
Email Frameworks
07Modular email components reps assemble from. Personal and on-brand without templating every rep into the same voice.
LinkedIn Cadences
08Native LinkedIn sequences written the way technical buyers actually read — short, specific, low theatre.
SDR Coaching Rhythm
09A weekly coaching cadence tied to real calls and real pipeline, using a shared rubric and documented follow-through instead of ad-hoc feedback.
Manager Operating Rhythm
10The manager's week rebuilt from the calendar down — 1:1s, deal reviews, coaching blocks, and forecast checkpoints in fixed slots.
Pipeline Review Template
11A single-page pipeline template used identically across the team. Same shape, same language, same standards for what counts as qualified.
Sales Playbooks
12Written playbooks covering ICP, personas, messaging, cadence, discovery, and handoff — the reference reps and managers open instead of relying on tribal memory.
Fit signals, disqualifiers, and the questions used to grade a new account.
Tiered account model reps consult before Monday planning.
Operating System Timeline
Twelve weeks, six phases.
- Week 1 – 2DiagnoseSat with leadership and reps. Reviewed live calls, current messaging, existing playbooks, and pipeline data.Sat with leadership and reps. Reviewed live calls, current messaging, existing playbooks, and pipeline data.01 / 06
- Week 3 – 4MessagingRewrote core narrative, vertical angles, and persona messaging. Pressure-tested against live outbound.Rewrote core narrative, vertical angles, and persona messaging. Pressure-tested against live outbound.02 / 06
- Week 5 – 6CallsLive-call coaching blocks with a shared rubric and shared language for feedback.Live-call coaching blocks with a shared rubric and shared language for feedback.03 / 06
- Week 7 – 8CoachingRebuilt the manager operating rhythm, 1:1 cadence, deal reviews, forecast discipline.Rebuilt the manager operating rhythm, 1:1 cadence, deal reviews, forecast discipline.04 / 06
- Week 9 – 10PlaybooksDocumented ICP, personas, cadences, objection handling, and discovery into written playbooks.Documented ICP, personas, cadences, objection handling, and discovery into written playbooks.05 / 06
- Week 11 – 12Operating RhythmInstalled the weekly and monthly operating rhythm so the system runs after the engagement ends.Installed the weekly and monthly operating rhythm so the system runs after the engagement ends.06 / 06
The manager's week rebuilt into fixed 1:1, review and coaching blocks.
One-page pipeline shape used identically across managers.
Moments of progress inside the twelve weeks.
Not milestones. Points where the operating system moved from theory into practice.
- Week 01Inconsistent qualification observed.
Every SDR manager was interpreting 'qualified' differently. Discovered before any recommendation was made.
01 / 05 - Week 02Outbound messaging standardized.
Vertical narratives, persona angles and proof points consolidated onto a single messaging spine.
02 / 05 - Week 04Leadership coaching aligned around one framework.
Managers began coaching from the same rubric instead of individual instinct.
03 / 05 - Week 07Shared scorecards introduced.
Pipeline reviews began using one template. Same shape, same language, same standards for what counts as qualified.
04 / 05 - Week 10Operating rhythm became repeatable.
1:1s, deal reviews, coaching blocks and forecast checkpoints held their protected time for three consecutive weeks.
05 / 05
Artifacts from the Rebuild
A partial view of the documented infrastructure installed during the engagement. Previews are redacted to protect client confidentiality.
Vertical narratives, persona angles, and objection-ready proof points on a single spine.
Weekly manager view of coaching, forecast discipline and pipeline health.
Shared standard for what counts as qualified, stalled or at-risk.
Buying signals separated from company fit, with grading criteria.
Shared language for feedback on openers, discovery and next steps.
Weekly and monthly rhythm reps and managers execute against.
Fit, intent and access graded across account tiers.
Committee-level personas covering platform, SRE, cloud ops and security.
Operating Assets
The following artifacts were installed inside Kentik's own tools and remained in operation after the engagement closed. They are the documented infrastructure of the rebuild.
- Messaging Library01
- SDR Playbooks02
- Call Coaching Sessions03
- Manager Coaching04
- Email Frameworks05
- ICP Reviews06
- Weekly Workshops07
- Pipeline Reviews08
- Persona Matrix09
- Account Matrix10
Leadership Model
The operating model mattered more than any individual seat.
- Weekly alignment on strategic direction
- Decisions on scope, sequencing, and priorities
- Roadblock removal across the org
- David KleinChief Marketing Officer
- Justin BiegelCo-Founder & COO
- Day-to-day coaching and rubric enforcement
- Forecast discipline and pipeline reviews
- Implementation of the manager operating rhythm
- Sal YousufiHead of Global Sales Development
- Live workshops and messaging pressure-tests
- Roleplay against the new frameworks
- Daily execution inside the new operating system
- ~15 SDRs
What Changed
- Inconsistent messaging across reps
- Broad, instinct-based targeting
- Rep-by-rep execution
- Scattered outbound documentation
- Coaching varied by manager
- Persona-first, shared messaging spine
- Documented account and persona prioritization
- Consistent SDR execution against a written playbook
- Operationalized sales infrastructure
- Shared coaching rubric and weekly rhythm
These are operational shifts inside the SDR system, not business outcomes. Business outcomes are the client's to report.
Operating Principles Reinforced
What Kentik taught us — written as principles the practice still runs on.
The team you meet on day one is already telling you what to rebuild. Watch the calls, read the documents, sit in the reviews, then write the recommendation.
Messaging built on top of inconsistent qualification collapses under real pipeline. Qualification is the substrate every other system compounds on.
Coaching, forecasting and pipeline discipline do not exist as skills. They exist as protected time on a manager's week. Rebuild the calendar and the outputs follow.
Frameworks that live only in workshops decay within weeks. Frameworks written into the client's tools with owners and review cadence outlive the engagement.
Every SDR org has one or two reps who compensate for missing infrastructure. Rebuilding the system replaces heroics with a floor the whole team executes against.
Predictability is not a talent problem. It is the compounding output of a weekly rhythm that repeats until the team stops noticing it is there.
Language of the Rebuild
Named ideas the practice runs on. Not vocabulary. Operating decisions with a shared name so they can be coached against, referenced and enforced.
The engagement watches the team run before writing any recommendation. Diagnosis precedes prescription.
ICP is fixed before messaging. Copy cannot compensate for a target that catches every plausible signal.
The strongest outbound wedge is usually already inside the product story, waiting to be named and operationalized.
Coaching quality is rarely a skill gap. It is a calendar gap. Rebuild the manager's week first; coaching consistency compounds on top of it.
Frameworks pressure-tested live in workshops hold for weeks. The same frameworks delivered as documents alone decay within a week.
Documentation written during the rebuild — inside the client's tools, with named owners and a review cadence, outlives the engagement. Documentation written after rarely gets opened.
The rebuild compounds beside the existing business rather than replacing it. Parallel installation preserves what is already working.
The reliable signal that the operating system is working is unprompted use, not a launch date, an announcement, or an internal memo.
Methodology Notes
The engagement started by watching the team run, live calls, existing documentation, team cadence, targeting logic, and how managers actually spent the week, before any recommendation was written down.
The rebuild was installed as operating infrastructure, not a launch. Messaging, coaching, reviews, playbooks, and weekly rituals were designed to reinforce each other and to survive after the engagement ended.
Every framework was written down in the client's own tools so it could be run, coached against, and updated without the consultant in the room.
The work avoided artificial ROI claims and focused on the durable mechanics required for a growing SDR organization to execute consistently after the engagement ended.
Looking Back
Kentik was the engagement that shaped the Revenue Rebuild methodology. The team had executive backing, capable managers and motivated reps. What it did not have — and what most organizations do not have, was an operating system underneath the activity.
The lesson from that twelve weeks was straightforward. Organizations rarely have an activity problem. They have an operating system problem. Reps are usually working hard against inconsistent qualification, drifting messaging, and coaching that varies by manager. The rebuild is not more effort. It is shared infrastructure.
Every Revenue Rebuild that followed traces back to what was documented at Kentik. Qualification before messaging. The manager calendar as the operating system. Frameworks written down, not narrated. Systems over heroics. Those principles were not invented in a workshop. They surfaced during the work and became the shape of the practice.
Revenue Operating System Assessment
Most organizations don't need another audit. They need a documented understanding of how their outbound operating system actually functions before making changes.
A Revenue Operating System Assessment documents what's already running underneath your team, messaging, qualification, coaching cadence, pipeline reviews and manager rhythm, as it exists today, not as it's meant to.
No manufactured ROI. No generic audit. A documented view of the operating system underneath your revenue engine, and the specific places a rebuild would compound.