TITLE: The gap list your customers already wrote for you
SUBTITLE: The Ecosystem Completeness Score (ECS): how much of what your customers need can your ecosystem deliver, and where the gaps are. Part 3 of the ecosystem-metrics series.
BYLINE: Sion Welchart, Director of Marketing, Entwine
---
The first two metrics in this series ask how well your ecosystem handles the customers you already have. This one asks something you may not want the answer to. Of everything your customers have asked you for, how much has anyone actually delivered?
Most scores in this category are built to reassure. This one is not, and I would not trust it if it were.
Start from the need, not the partner
Most ecosystem measurement starts at the partner list: who signed, who sourced, who renewed. ECS starts at the other end, with a register of what your customers have said they need.
A need here is concrete. A named customer asked for a named capability, with a priority and a target date. Not a market hypothesis. Not a segment.
Each need resolves over time, met or not, and the score is built from that register in two parts. Fulfilment rate is the backbone: of everything your customers have asked for, what share has actually been met? Alignment quality is the refinement: of the needs that were met, how well matched was the partner who met them? Meeting a need is good. Meeting it with the right partner, at the right depth, is better.
The two combine into a score from 0 to 10, weighted toward fulfilment by default and configurable per company. Same principle as CSI last week. The platform computes, you define what counts.
The gap list is the product
The number is the least useful thing ECS produces.
What matters is what falls out of computing it. Every unmet need becomes a row in a gap analysis: which capability, for which customer, at what priority, overdue or not. Sort that list by priority and date and you are holding something genuinely rare in partnership work. It is a partner recruitment shortlist, written by your own customers.
High-priority unmet needs are your next partner conversations, already qualified, with somebody waiting on the other side of each one.
Overdue needs are churn risk wearing a different name. A customer who asked for something months ago and is still waiting has started looking elsewhere, whether or not they have told you.
Five customers missing the same capability is not five problems. It is one build-or-partner decision that you can now put a date and a customer list against.
That is why we call it a completeness score rather than a coverage score. Coverage sounds like a market-sizing exercise. Completeness is personal: these specific customers, these specific asks, this much of it handled.
Almost nobody has a needs register, and that is the point
I should be straight about the prerequisite. Very few companies keep a register of customer needs. The asks are scattered across QBR notes, support threads, a product board and somebody’s inbox, which is precisely why nobody in the business can answer the question.
So do not start with the score. Start with ten accounts and one question in your next round of reviews: what have you asked us for that you are still waiting on? Write down the capability, how badly they want it, and when they wanted it by. Ten rows in a spreadsheet is a working register. It takes an afternoon, and in my experience the first overdue row on it is the one you wish you had found a quarter earlier.
ECS will not flatter an empty register either. No recorded needs does not produce a triumphant 10 out of 10 on the grounds that nobody asked for anything. An empty register means the discovery work has not been done, and the score’s breakdown says exactly that rather than rewarding the silence.
The three together
CDE asks whether your ecosystem gets customers from need to solution faster than you manage alone.
CSI asks whether those customers then succeed across their lifecycle.
ECS asks whether your ecosystem can deliver what they need next.
A partnership programme that can answer all three from its own records has stopped counting logos and started managing an ecosystem. One that can answer none of them is running on anecdotes, however good the slides look.
Where the numbers come from
Needs reach the register three ways: typed in by your team, imported from wherever you already track requests, or submitted by the customer directly through their own portal view. This register is the only thing in the whole series that asks you to collect something new, which is why I would start it by hand this quarter whatever tooling you end up using.
Run the five-customer audit
Same offer as the last two letters, and this time the gap list is the output. Five accounts, one question each, and you will have the beginnings of a register plus your first overdue row. The template is free and ungated:
If you would rather see all three scores side by side for your own book, computed as the data arrives, the free Entwine workspace monitors five relationships and takes no card:
Start with the needs register. The rest follows from it.
This concludes the three-part series on the ecosystem metrics. Next: the four depths of partnership, and why moving one partner from transactional to strategic beats signing ten new logos.
This concludes the three-part series on the ecosystem metrics. Next up: the four depths of partnership, and why moving one partner from transactional to strategic beats signing ten new logos.