What's Your Next Software Partner Actually Worth? Run the Numbers with this Calculator

A Vice President spent three months choosing a software partner. She had a spreadsheet with six potential partners, color-coded by budgeted cost. She picked the cheapest one.

Fourteen months later, the project shipped late, over budget, and missing two of the three features that mattered. All in all, the "savings" cost her company more than the most expensive option on her original list.

She is not unusual. In fact, her experience is the norm. Her mistake was optimizing the wrong variable.

The right question is not, "What does this cost?" The right question is, "What is this worth to me if it works, and how much of that value will this partner actually deliver?" Those are different questions, and the gap between them is where most bad software buying decisions live.

As the co-CEO of a custom software consultancy, I have sat in the room when buyers made this call well, and I have sat in the cleanup meeting when they made it badly. The difference is almost always the variables they ignored when selecting a partner.

Below, I will explain how I think about this and then show you an example with real numbers you can plug into a calculator and verify yourself.

Smart buyers consider more variables than cost

Most buyers compare proposals on one dimension: the quoted price. That is like buying a car based on the sticker and ignoring fuel economy, safety rating, maintenance costs, reliability, and resale value. You would never do that with a car, but buyers do it with six-figure software projects all the time.

(Screenshot of the Partner Value Calculator running the below scenario.)

Here is a Partner Value Calculator I built that runs this math across all the dimensions that matter. Plug in your numbers, and it generates a scorecard with an Excel export you can bring to your next partner selection review.

There are several dimensions that actually determine what a software partnership is worth. I will walk through the four that matter most, then put two hypothetical partners side by side and run the numbers.

Start with what the project is worth

Before you score any partner, put a number on what dollar value the project creates if it ships and works. That value can come from:

• Revenue gained
• Costs avoided
• Risk reduced
• Time saved
• Compliance pain eliminated

Whichever of those applies, write down what the project is worth to your business.

Every number below is anchored to this one. The ballpark matters, but precision does not. If you are not sure whether this project is worth $500,000 or $5,000,000, spend some time answering that question for yourself before you look at bids.

Dimension 1. Expected value capture (EVC)

This is the one nobody writes down, and it affects the outcome more than anything else.

I used to call this probability of success, but that framing is too binary. A project can miss its schedule, go over budget, and cut scope, and still deliver most of the business value it was meant to create. A cleaner frame is expected value capture: across the realistic range of outcomes, what share of the project's value will this partner actually deliver?

For each of your potential partners, write down an expected value capture percentage. Not the odds they ship something, this is the share of the project's value you wrote down above — where 100% means capturing every dollar of that upside.

Here are three indicators you should use to drive that percentage up or down:

1. Track record. Have they shipped similar work in your market before? Will they let you talk to those clients, and what do those clients say about quality, communication, and outcomes (not just delivery)?
2. Process. Do they run real discovery, testing, and feedback loops? If you are in a regulated industry, do they actually understand the standards, or are they learning on your dime?
3. Access. Can you reach the team and their leadership directly? Are they in a timezone, culture, and geography where fast, honest communication is realistic, or are there gaps that will cost you later?

A team that is below average on all three factors lands around 40% expected value capture. The industry baseline is 60% (more on that below). A proven team with a strong process and direct access to decision-makers can reach 95%. It’s not realistic to set expected value capture at 100%; a small slice of risk is always outside the partner's control: your team's capacity, requirement changes discovered during build, market timing.

That capture gap, from 40% to 95% (below average vs. proven), applied to a project worth a million dollars, is $550,000 in expected value difference before you look at a single proposal.

Where the 60% baseline comes from. The Standish Group's CHAOS 2020 report, which has tracked software project outcomes since 1994, looked at more than 50,000 projects and sorted them three ways: 31% successful (on time, on budget, on scope), 50% challenged (late, over budget, or reduced scope), 19% failed or cancelled. Weight those outcomes by the business value they actually delivered — roughly 100% for successful, 50% for challenged (our estimate: Standish classifies outcomes by delivery, not by business value), and 0% for failed:

(0.31 × 100%) + (0.50 × 50%) + (0.19 × 0%) = 56%

That’s why I recommended setting it 60% as your working baseline. This is close enough for a directional estimate, and it’s easier to anchor the rest of the scale on. Smaller projects run higher; large enterprise projects run well below it.

Dimension 2. Cash cost to ship

Now bring in the full partner cost. Not the quoted number. The quoted number plus your estimate of the rework it does not account for.

Every project has rework, and it usually traces back to one of two reasons: (1) either the team built the wrong thing because requirements were fuzzy and nobody pushed to clarify them, or (2) they built the right thing badly, and testing did not catch it until late. Strong partners invest in discovery, validation, and QA — each one attacks a different cause of rework, keeping the number low. Weaker partners ship whatever the first conversation produced and let you absorb the cost of finding out.

You will not get a clean rework percentage from a spreadsheet. You will get it from reference calls. Ask past clients whether scope thrashed mid-project, whether features got rebuilt after user testing, whether bugs kept surfacing after "done," whether the team pushed back when the ask was unclear. Then drop each partner into a bucket:

• Low rework risk (~0–5%). References describe tight discovery, clear specs, strong testing, and clean handoffs. Few surprises post-launch.
• Moderate rework risk (~15–25%). References mention some scope churn, some back-and-forth, some quality issues caught and fixed along the way.
• High rework risk (30%+). References describe rebuilt features, scope that got away from the team, or a "we had to redo parts of it" story. At the extreme, this can reach 40–50% of the budget. If you're seeing projects go over that, they often don't ship at all.

Before you assume the partner bears the cost of rework: they usually do not. Rework from unclear requirements gets reclassified as a change order and billed. Rework the partner does absorb on fixed price gets recovered through scope cuts — you end up with less product for the same money. On time-and-materials, every rework hour bills directly to you. The cost moves around, but it does not disappear.

When you see two quotes (say, $150,000 and $300,000), ask to what degree rework is included in each. If the $150,000 bid does not include real discovery and the references land it in the moderate-risk bucket, the real cash cost is closer to $180,000. If the $300,000 bid includes discovery, QA, and the references land it in the low-risk bucket, it stays at $300,000. The gap is not $150,000. It is closer to $120,000.

Dimension 3. Internal time cost

This is the cost that never appears on a proposal but shows up on your calendar every week.

How many hours of your team's time will each option consume? Consider:

• Your executive sponsor reviewing decisions. 
• Your project manager coordinating deliverables. 
• Your subject matter experts answering questions. 

Ask each partner directly: "How much of my team's time will this project take?"

The answers can vary wildly. A partner who runs a tight process and owns project management might need two hours a week from your executive sponsor. A partner who expects you to provide the PM and chase down decisions might need eight hours of sponsor time plus five hours of coordinator time. Over a 6-month engagement, at $400 an hour in opportunity cost for sponsor time and $150 for a coordinator, that difference is roughly $80,000. And if the heavy-involvement partner slips, every extra month compounds the cost. You are paying for it in opportunity cost instead of cash.

This is the dimension that makes people angry when they see it. Nobody budgets for it; everybody pays it.

Dimension 4. Time to value

What does it cost your business when the project ships late against your deadline? That cost can come from:

• Revenue lost
• Contract deadlines missed
• Competitive windows closed
• Cost savings delayed

Put a dollar figure on one month of delay, even a rough one, before comparing budgets.Then pick the month by which your business actually needs this live. That is your target. 

For each option, compare their actual engagement — quoted duration plus whatever slip you are modeling from D3 — against that target. If a partner runs past it, months late times your cost of delay is the price you pay. If they hit the target, that cost is zero.

The point: a partner who misses their own quote by a month but still delivers inside your window costs you nothing on this dimension. A partner who hits their quote but finishes after you needed it costs you real money.

Example scenario

Let me make this concrete. Plug the same numbers into the Partner Value Calculator as you read and the scorecard will match this scenario line for line.

Let’s pretend that you have a project that is worth $1,500,000 to your business if it ships and works.

Now, let’s pretend you are looking at two quoted options.

Option 1 is the half-price bid. They quote $150,000 and know your vertical well. But their references mention some rework, they expect heavy involvement from your team, their process feels sloppy, and their timeline feels optimistic. Score them above average on track record, below average on process, below average on access. That puts their expected value capture at 58%.

Option 2 is the premium partner. They quote $300,000, double the price. Their references consistently mention on-time delivery. They bring their own PM and have strong testing baked in. You got direct time with the team and their leadership during the sales process. Score them well above average on all three factors. That puts their expected value capture at 95%.

Both partners quoted a 6-month timeline.

Your instinct is to pick Option 1. Half the price, knows your industry, done. That is the decision most executives make in the first ten minutes.

Now run the dimensions.

D1. Expected value capture. Option 1’s track record, process, and access gives you 58% EVC. Option 2’s track record, process, and access gives you 95% EVC.

D2. Cash to ship. Option 1's $150,000 budget plus 20% rework gives you $180,000 in actual cash cost. Option 2's $300,000 with zero rework stays at $300,000.

D3. Internal time. Both partners quoted a 6-month timeline. But because we are nervous about Option 1's track record, we model 2 months of expected slip on their side — a total 8-month engagement. Option 2 stays at 6 months.

• Option 1 needs 8 hours per week of sponsor time and 5 hours of coordinator time over those 8 months. At $400/hr and $150/hr, that is roughly $137,000.
• Option 2 needs 2 hours of sponsor time, no coordinator, over 6 months. About $21,000.

D4. Time to value. Let’s assume that for this project the cost of delay to the business is $50,000/month. The business needs this live by month 6. Option 2 hits that target — zero months late, zero delay cost. Option 1 runs 8 months, which is 2 months past the target, which is $100,000 in delay cost.

Subtotal (true cost):

Stop here and notice what happened. The option that quoted half the price actually costs more when you add rework, internal time, and delay against the business target. The $150,000 budget became $417,000. The $300,000 budget moved up more modestly to $321,000.

Now add expected value capture against the $1,500,000 project value.

Expected value: $1,500,000 × 58% = $870,000 for Option 1. $1,500,000 × 95% = $1,425,000 for Option 2.

Net value (expected value minus true cost):

Option 2 delivers $651,000 more in net value. The "expensive" partner is worth more than twice as much to the business as the "cheap" one. That is the whole argument.

What moved the needle

Look at what drove the gap. The budget difference between the two proposals was $150,000. The net value gap is $651,000. Most of that difference ($555,000) came from the 37-point gap in expected value capture. The rest ($96,000) came from non-budget costs: internal time saved Option 2 $116,000 and hitting the business target saved another $100,000, partially offset by the $120,000 cash premium. Three of those four levers sit within $50,000 of each other. Expected value capture is bigger than all three combined, and it is the one lever that never shows up on the proposal.

This is the pattern I see over and over. Buyers fixate on the number that is easiest to compare and ignore the numbers that move the outcome the most.

“But can't we just manage Option 1 more rigorously?"

Here is the objection I hear most often at this point in the argument. "Fine, Option 2 wins on paper. But what if we pick Option 1, bank the cash on the cover, and spend more time managing them? We close the gap with effort."

It does not work. And understanding why is the last piece of this framework.

Expected value capture is a structural property of the partner, not a dial you can turn up by spending more. Track record, process, and access are baked in before you sign the contract. A partner with a weak process is not going to install a strong process because you paid them more. A partner whose references mention rework is going to produce rework. You cannot buy your way out of how they work.

The fantasy version sounds like this: "We'll assign a senior PM on our side, do weekly deep-dives, and catch issues early." What you are describing there is piling more internal time onto the project to compensate for weak processes. That is D3, and the framework already charges you for it. Option 1 already assumed 8 hours of sponsor time and five hours of coordinator time a week — not a light load. Doubling it does not meaningfully move EVC; it just moves the cost of Option 1 up without moving its outcome.

There are three situations where picking the lower-EVC partner is a defensible choice. Each of them rearranges the question rather than closes the gap.

The premium partner is not actually available. Capacity, fit, geography, timing. If Option 2 is not on your shortlist in reality, Option 1 at $453,000 in net value is still positive. Do it. Better than waiting 6 months or doing nothing.

The stakes do not justify the premium. If the project is small and 58% capture is acceptable, save the cash. But you are not raising EVC here; you are lowering the stakes to match the partner.

Portfolio economics. If the $150,000 you save has a clear, better home — another project with a stronger net value profile — the cheaper partner may be the right call for this one. This only works when the next dollar has a real destination, not when "we'll hold it" is the plan.

None of these is "pay more and it gets better." They are all "the second option is not what it looked like, or the first project is not what we thought it was."

The VP in the opening of this piece was trying to buy the first story. It did not work; it never does.

The real job

Your job as a buyer is not to minimize what you pay. It is to maximize what you get. Those sound like the same thing. They are not.

This framework is not about cheap versus expensive; it is about realistically determining expected value capture. There are expensive partners with weak EVC and inexpensive partners with strong EVC. Score each option on its own merits, not by its price tag.

Before your next partner selection meeting, build this comparison for every option on your shortlist. Do not walk in with a budget comparison. Walk in with a net value comparison. If your finance partner pushes back, show them the math — the Partner Value Calculator does it for you and exports a scorecard you can take into the meeting. The number that matters is net value to the business, and it is almost never the number on the cover page of the proposal.

Run the full numbers. It’s worth it.