Turning Talent into Predictable Revenue
People and rhythm
A public sector team is rarely uniform.
1. Segmentation, and what each group gets from me weekly
A public sector team usually holds long-tenured reps who know the procurement calendar better than I ever will, steady producers with room to scale, and one or two people whose inputs are off plan. I run all three from the same operating rhythm, with different asks and different support.
| Segment | Who they are | What they get | What I ask in return |
|---|---|---|---|
| Institutional anchors | Long-tenured reps who carry state buyer dynamics, agency history and procurement cycles | Marquee account sponsorship, executive-to-executive introductions, a formal peer coaching role, credit in front of their peers | Modern proof-of-value standards and clean forecast hygiene. Tenure earns influence, not an exemption |
| Core producers | Consistent performers with headroom | Friction removal (approvals, escalations, internal noise), cross-architecture expansion plays, visible career path | Multi-threading depth: more than one relationship per account, and an Economic Buyer on record |
| Re-evaluations | Reps whose results or inputs are off plan | A written skill versus will diagnostic, weekly deal coaching, joint customer calls, and 30/60/90 criteria they have seen in writing from day one | Honest engagement with the plan |
No rep learns they are in the third group from a spreadsheet. They hear it from me, with the criteria, in week one. At day 90 there are two outcomes: retained and performing, or transitioned with the people team, decided on evidence both of us have been looking at the whole time.
Where I have done this
At Bridgevine I ran this rhythm with a direct team of 12, lifting retention by 32 percent and closing the year at 116 percent of the 2012 bookings goal.
2. The weekly operating rhythm
| When | Session | Length | Purpose | Output |
|---|---|---|---|---|
| Monday | Team call on the four leading inputs | 30 min | The four weekly inputs on one page, by rep, before anyone talks about closed revenue | The input picture for the week |
| Weekly | 1:1 deal strategy | 45 min each | Two or three deals, MEDDPICC evidence, unblock the rep | Next three actions, with names |
| Thursday | Forecast call | 45 min | Commit, upside and risk, with the covering engineer's technical viability read on every Stage 4 and 5 deal read out beside the rep's number | One number I own |
| Friday | Engineering sync | 30 min | Co-chaired with the systems engineering leader: proof-of-value queue, coverage, capacity flags | Go or no-go list |
| Monthly | Partner review | 90 min | Aggregator and regional resellers: registered deals, sourced pipeline, gaps | Joint action list |
| Quarterly | Territory reset | Half day | Tiering, coverage, vehicle map, plays retired and launched | Revised territory plan |
The 1:1 is a deal strategy session, not an interrogation. Inspection happens in the evidence, not in the tone.
3. MEDDPICC stage gates
| Gate | Required evidence | Not sufficient |
|---|---|---|
| Stage 3: Validation | Pain confirmed in the customer's own words; champion identified and tested (gave Economic Buyer access, shared decision criteria); decision criteria documented | "They like us" |
| Stage 4: Proposal | Economic Buyer meeting completed one to one; metrics validated and the business case reviewed with that buyer; decision process mapped with named committees and dates; the covering engineer has confirmed the proposed architecture is buildable in that environment | An RFP response in flight |
| Stage 5: Commit | Economic Buyer approval; signed Mutual Action Plan; paper process mapped with a named procurement officer and a named vehicle | A verbal close date |
A deal that cannot show the evidence moves back a stage. I tell the rep why, the deal waits until the evidence exists, and it does not count against them. Moving a deal backwards is a forecasting act, not a punishment.
4. The four leading indicators I track
Lagging numbers tell us where we were. These four are the inputs I watch weekly, because in my experience they give roughly 60 to 90 days of warning. I set the thresholds against a region's actual baseline in the first 30 days rather than importing numbers from a previous territory.
| Indicator | What it predicts |
|---|---|
| First-time Economic Buyer meetings | Multi-threading depth into the agencies and institutions that actually hold budget |
| Stage 1 to Stage 2 velocity | How fast discovery turns into a validated opportunity, and whether qualification is real |
| Partner-sourced pipeline share | Health of the aggregator and reseller co-sell motion, and local procurement reach |
| Scoped versus qualified proof-of-value ratio | Proof-of-value discipline and whether engineering capacity is being protected |
5. Hiring and coaching: the P.A.C.E. rubric
P.A.C.E. comes from John McMahon's The Qualified Sales Leader. This is how I score it for public sector hires.
| Pillar | What I look for | How I coach it |
|---|---|---|
| Preparation | Reads state IT master plans, legislative budget sessions and grant cycles, and walks in with a hypothesis | Pre-call prep reviewed in the 1:1 before the meeting, not after |
| Adaptability | Takes critical feedback in a roleplay and applies it on the next call | Live roleplay in 1:1s, the same scenario twice |
| Curiosity | Asks layered business questions before reaching for product | Score discovery calls on questions asked versus features named, with the covering engineer scoring the technical half of the same call |
| Energy and drive | Owns the number without being asked, and stays resilient through procurement delays | Recognize consistency of inputs, not only closed revenue |