The Wedge Is a Team Sport
The Wedge has too many moving parts for one person to carry forever. It's a system — and systems run on roles and rhythm, not heroics.
Let me be honest about where precision prospecting usually goes to die. Not in the research, not in the letter, not even in the follow-up — but in the sheer weight of one person trying to do all of it. You've seen how many moving parts the Wedge has: choosing the accounts, mapping the people, verifying the details, crafting the message, building the package, delivering it with care, following up until closure. Now picture carrying every one of those, for every account, week after week, entirely on your own. It doesn't matter how disciplined you are. Eventually it stalls. That's not a personal failing; it's simply what happens to any system when you ask one person to be the whole machine.
Because that's what the Wedge actually is — not a clever trick, but a system. And every system relies on roles. This is the part that trips up talented individual producers, the ones used to being the person who does everything. The Wedge asks something different of you: not to work harder as a soloist, but to think in roles, and to make sure each one is owned. It's also, as we've discussed, a big part of why some prospecting systems stick and most quietly don't — the ones that last are built to be run by a team, on a rhythm, rather than white-knuckled by one person until they burn out.
The four roles that make it work
So here are the four essential functions. On a full team, each can belong to a different person. In a small shop, one person might own two, or even all four — but each still has to be owned deliberately, not left to chance.
- The Researcher — the intelligence arm. Builds the target list, qualifies companies against your criteria, verifies names, titles, and reporting lines, and keeps the records clean. Detail-driven, resourceful, strategic — the person who doesn't just find names, but uncovers access points.
- The Message Architect — the owner of the value proposition and the words. Crafts the letter, shapes the language of the value package, keeps the message relevant to each target, and sharpens the templates as the team learns what lands. Their whole job is to make the message open doors.
- The Logistics Coordinator — the operations center. Assembles the packages, manages delivery, schedules the follow-up timelines, and keeps everyone posted on status. The unglamorous role that keeps the machine running on rhythm — and the one most often skipped, to a team's peril.
- The Relationship Builder — the front-line voice, and very often you. Makes the calls, engages gatekeepers with respect, books the appointments, builds the rapport, and moves the opportunity forward. The closer, who relies on the other three to make the job possible.
Look at that list and you'll notice something: these are genuinely different kinds of people. The researcher who thrives in the data rarely loves the phone. The closer who lights up on a call often has no patience for spreadsheets. That's not a problem to solve — it's the whole reason a team beats a soloist here. When each role is handled by someone who's actually good at it and enjoys it, the Wedge becomes a living, repeatable, scalable system. When it all falls to one exhausted generalist, it becomes a burst of effort that eventually runs out of gas.
Roles need a rhythm
Roles alone aren't quite enough. Any system that lacks rhythm eventually breaks down, and the Wedge is no exception. Once the roles are in place, you need a simple operating cadence — a predictable weekly cycle that keeps everyone moving without burning out or getting lost in the spreadsheets. The centerpiece is a short weekly check-in, and I want to be precise about what it is and isn't. It is not a sales meeting. It's a systems meeting: Who did we reach this week? What's come back? What's going out next? Who's behind, and who needs support? Keep it to half an hour, keep it focused on the flow rather than the results, and you protect the whole machine from the quiet failures that kill this work — packages stuck in production, follow-ups forgotten, opportunities dying in an inbox while everyone means to “get to it later.” This is the Wedge's version of a principle we hammer on elsewhere: do the right things, do them right, and do them every day.
Even a team of one
Now, maybe you're reading this as a solo operator thinking, “That's lovely, Keith, but there's only me.” I hear you — and the honest truth is the Wedge was designed for teams, and it's genuinely harder alone. But the principle still holds, and it may matter more for you than for anyone: even a team of one has to think in roles, not just tasks. You still put on the researcher's hat and do the digging, then deliberately switch to the architect's hat to craft the message, then the coordinator's, then the closer's — and you have to know which one you're wearing. And where you can, you enlist help: a part-time researcher, a contractor for logistics, anyone who lets you spend more of your time in the role only you can play. This is the difference between delegating and abdicating. Delegating the roles you're not built for is how the system survives contact with a real week.
How Prospect & Flourish approaches this
This is the note the whole category builds toward. Most of what we teach in Prospect & Flourish can be carried out by an individual — but precision prospecting is where the whole team comes into the fold. The Wedge is deliberately the most collaborative thing in the program, precisely because it's the most systematic. What this means to you is a shift in how you think about opening hard doors: stop asking “how do I do all of this?” and start asking “who owns each part, and what's our rhythm for keeping it moving?” Answer those two questions honestly — even if the answer to the first is sometimes “me, wearing four hats” — and you've turned a heroic, unsustainable effort into a system that actually lasts.
Frequently asked questions
Can I really run the Wedge as a solo operator?
You can — but I'll be straight with you: the Wedge was built for teams, and it's genuinely harder alone. A soloist has to consciously wear each of the four hats and switch between them, and even then the sheer load is why most solo attempts stall out. The honest play is to reserve the full method for your highest-value targets, enlist help wherever you can (even part-time or contract), and resist the urge to run it at team-scale volume by yourself. Think in roles, protect a rhythm, and pursue fewer accounts well rather than many badly.
Do I actually need four separate people?
No — you need four roles owned with intention, which is a different thing from four headcount. On a small team, two people might carry two hats each; on a bigger one, each role gets a dedicated owner. What matters far less is the number of bodies and far more that no role silently goes unowned. The failures don't come from having too few people; they come from assuming someone is handling the research, or the follow-up, when in fact no one is.
Which role is the most important?
None of them in isolation — a system fails at its weakest link, not its strongest. That said, the role most often neglected is the logistics-and-rhythm function: the unglamorous coordination that keeps packages moving and follow-ups from being forgotten. The research and the closing get all the attention because they feel like “the work.” But the Wedge usually dies from the boring role being skipped — the package that never got assembled, the follow-up that fell off the calendar. Protect the unglamorous part.
Isn't assigning roles just bureaucracy for a small shop?
There's a real risk of over-engineering — a two-person shop doesn't need org charts and job descriptions, and I'd talk you out of that. But “think in roles, not tasks” isn't bureaucracy; it's the difference between a system that sustains itself and a burst of effort that runs out of gas. Here's the honest catch: it takes discipline and a real weekly cadence to hold together. If you won't protect that rhythm — that half-hour systems check-in that keeps nothing from slipping — then no way of dividing the roles will save you. The structure only works if you actually keep it.
Photo by Pavel Danilyuk via Pexels
