The People + Pipeline Systems Audit

Often, and the way to find out is to score them separately and then read the two results against each other. Four outcomes are possible. Both foundations missing is a Dual Build: one capacity problem wearing two hats, where the hiring plan assumes revenue the pipeline cannot support and the sales motion is run by whoever also approves every offer letter. Growth working with people missing is a People Gap, where hiring throttles a motion that already works, usually within a quarter or two. People working with growth missing is a Growth Gap, where the constraint is pipeline rather than headcount. Both working is Optimization Mode, where a narrow diagnostic fits better than either audit.

Because two companies can reach the same total from opposite corners and need opposite engagements. A company scoring twelve on go-to-market and two on people has the same sum as one scoring two and twelve, and they are not remotely the same business: the first needs a hiring process, the second needs a pipeline. A single number averages away the only thing worth knowing. The audit routes strictly on which quadrant you land in, never on the sum.

Because they are literally the same twelve questions, read from the same place. If you have already run that scorecard, your go-to-market track here will score identically, which is intentional: the two tools should never disagree about your pipeline. What this adds is the second track and the cross-read.

Two tracks sequenced against each other rather than listed side by side, in thirty-day blocks, with each step linked to the guide that explains it. The sequence is the output: in a Growth Gap the pipeline work comes first and the hiring plan follows it, because a hiring plan built on a forecast the pipeline cannot support will overstaff you. In a People Gap the dependency runs the other way.