top of page

Diagnose, build, run

Three stages. Everyone starts with the first one.

 

I do not quote a build before I have seen what is actually happening in your function. Not because it is a sales process, but because the alternative is guessing. Every SDR team I have walked into looked one way in the reporting and a different way in the records, and the gap between those two is usually where the problem lives.

 

So the diagnostic comes first, always. It is short, it is fixed, and what you get out of it is yours whether we work together afterwards or not.

01

The pipeline diagnostic

Two weeks.

I look at how pipeline actually gets created in your business right now, rather than how it is described.

 

That means the SDR setup end to end: the tooling and how much of it is genuinely wired together, the data and routing, the sequences and who owns them, CRM hygiene, call quality, and the handoff from SDR to AE. I read records rather than reports, and I listen to calls rather than reading a summary of them.

 

I also look at the management layer, because it is usually the answer. What the frontline managers actually inspect, what happens when a standard is not followed, and whether anyone would notice.

What you get

A written assessment of where the function is breaking, in what order the problems should be fixed, and what each one is costing you now.

 

It is written to be used by somebody else. If you take it and act on it with your own team, that is a good outcome and a cheap one.

02

The build sprint

Four to six weeks.

Installing what the diagnostic found was missing, working alongside your existing leadership rather than replacing it.

 

What gets built depends on what is broken, but it comes from the same places every time.

 

The interface with everyone downstream. Rules of engagement between SDRs and the people who receive their work. A written definition of a qualified opportunity, and a scorecard that applies it the same way whoever is judging the call. A feedback loop that tells an SDR why an opportunity was rejected, and tells you whether the rejection was fair.

 

The work itself. Playbooks and standard procedures that make the output the same on Tuesday as it was on Monday. Role-based onboarding, so a new rep is genuinely job-ready in weeks rather than nominally trained. Sequences and cadences that somebody owns.

 

The stack, and what it should be doing. Whether the tools are actually wired together or six separate purchases nobody integrated. Account research automated properly, so a rep reads a brief instead of assembling one. Administrative work taken out of the day rather than tolerated in it. Practice run against AI rather than booked into a calendar and cancelled. Tiering that means something: tier one gets human effort, tier three gets automated outreach that does not embarrass you.

 

The management layer. A coaching rhythm that runs continuously rather than getting scheduled when the quarter goes wrong, built off recorded calls and analysis so managers coach from evidence instead of impressions. Frontline managers coached on how to develop their own people, which is the job nobody teaches them. A reporting cadence and a manager cadence with an agenda that does not drift.

 

The bias throughout is towards controls that do not depend on anybody remembering. Anything a permission, a system setting or an objective can enforce should not be left to a weekly ritual that dies the first time somebody's diary gets busy.

What you get

An operating system your managers can run. Written down, owned, and specific enough that a new manager could pick it up and know what is expected.

Fractional SDR leadership

03

Ongoing.

I run the function. Weekly funnel inspection, coaching the managers and the reps, call blitzes, the manager cadence, and keeping SDRs, AEs, marketing and leadership pointed the same way.

 

This is for companies that need the function led properly but are not ready to hire a full-time SDR director, or are hiring one and need somebody holding it together in the meantime.

What you get

Governed pipeline generation without a full-time leadership hire, and a function that is in a fit state to hand over when the permanent person arrives.

How it fits together

Most companies start with the diagnostic and decide from there. Some take the roadmap and build it themselves. Some want the build and then run it with their own leadership. Some want all three.

 

The system is fixed. How it lands is not. I bring a system and adapt it to your people, your culture and your stage, never the other way round.

 

Everything is sized to the team. A four-rep function gets a shorter version of the same three stages, not a different product.

 

Built this way, a function needs fewer people doing more valuable work rather than more people doing the same work faster.

Start with the diagnostic

Thirty minutes on a call first. Tell me how pipeline gets made in your business right now, who owns what, and where it stops. I will tell you what I think is going on and whether the diagnostic is worth running.

bottom of page