PROJECT RED TEAM Start a conversation
← Insights
Start here

What a red team is, and why your project needs one

The name points to a specific practice, and the reason it belongs on every serious project before the outside world ever sees it.

A red team stress-tests your case firstYour casebefore a funder sees itreviewReleasedevidence attachedHeldrefused, honestly
Stress-test your case before a funder does.
Key takeaway

The value is timing: a weakness your own team catches is cheap to fix, while the same one caught by a lender or funder can sink the deal.

A red team is a group given one job: attack your own plan as hard as an opponent would, so you find the weaknesses yourself, first. The term comes from the military and intelligence world, where planners assign a team to think like the adversary, probe the strategy, and report where it breaks. Cybersecurity adopted it directly. A company hires people to break into its own systems, on purpose, because it would rather learn about the hole from someone on its payroll than from an intruder.

The logic is the same everywhere it is used. A flaw is cheapest to fix at the moment you discover it, and most expensive at the moment someone else does. The whole discipline exists to move the discovery of a problem from the second moment to the first.

Every project gets red-teamed. The only question is by whom.

Here is the part that matters for a real project, a business, a development, a public investment. Before it can move, someone with a cold eye is going to test it. A bank's credit committee will pull apart the pro forma. A grant reviewer will look for the assumption that does not hold. A city council, an opposing county, a party across a negotiating table will search for the number that falls apart under pressure. That review is coming whether or not you invite it.

You do not get to choose whether your project gets red-teamed. You only get to choose whether it happens early, on your side, while the findings are still cheap to act on, or late, in a room you do not control, where the weak spot becomes the reason you were turned down. Do it early and it is a working session you control. Do it late and the weak spot becomes the reason you were turned down.

What red-teaming a project actually looks like

Attacking a project honestly is a specific process, not a gut check.

Done well, it hands you the case a skeptic would make against your project, while there is still time to answer it.

Red-team the project, never the client

There is one rule that keeps this from being adversarial toward the people who commissioned it. The target is the project, not the person. A red team exists to make your idea survive contact with the people who will decide its fate. The skepticism is aimed where the real skepticism is coming from, so that when it arrives, you have already met it.

That is why the finding a red team most wants to deliver is a specific, fixable problem you can still address, together with the one piece of evidence worth gathering before you commit.

Why we built a firm around it

Economic and feasibility studies are easy to build for persuasion instead of decision-making. They are commissioned to support a decision already made, and they read that way to anyone experienced enough to be dangerous. We built this firm to work the other way. Every study runs through analysis designed to attack its own findings, and and every number it hands you comes with the argument behind it, so you can see exactly what it rests on. Where a single-point study reports one confident figure, ours reports where the answer holds, where it breaks, and what would change it.

That is the whole idea behind the name. We red-team your project before a lender, a funder, or a board does, so the review you cannot avoid becomes one you have already passed.

That is the work we do, on projects across the interior West. Tell us what you are weighing and where, and we will lay out what it takes to red-team it before anyone else does.

Start a conversation