Entwine scores a partnership on what happened to the customer, not on how busy the partner looked. Four measures are read at the customer; one attribution layer says which parties produced the outcome and in what proportion. Nothing in the arithmetic distinguishes a partner from a customer — only what each party did, and when.
Every value starts from a customer record — its deals, its needs, its survey answers, its usage. Partner-level numbers are derived from the customers a partner touched, never scored directly.
Below a minimum sample the value is blank and says why. Entwine does not fill a gap with a default, an industry average or a model guess.
Each score is plain arithmetic over records you can open. The same inputs always give the same number, and the inputs are one click away from the score.
How much faster the ecosystem gets a customer from need to the right solution than they would have managed alone.
CDE = median days-to-close, direct
÷ median days-to-close, ecosystem-sourced
A ratio. 1.0× means ecosystem-sourced deals close no faster than direct ones; 1.8× means they close in a little over half the time. Median, not mean, so one stalled deal cannot drag the number.
Reading
Exceptional ≥ 3.0× · Strong ≥ 2.0× · Moderate ≥ 1.5× · Developing below.
How much of a referrer's credibility travels with the referral. Conviction, not speed.
TTI = win rate of deals referred by a party
÷ win rate of unreferred deals
A ratio, per referrer. The referrer can be a partner or a customer — same formula. 1.4× means a deal that party vouched for is 40% more likely to close than one nobody vouched for.
Is this customer actually succeeding? The customer's own score, 0–10. A partner's number is derived from the health of their customers.
CSI = weighted mean of
adoption · engagement quality · advocacy · outcomes · sentiment
0–10, per customer. Weighted over the components that have data; a component with nothing behind it is left out and the others are renormalised, never counted as zero.
Equal weights by default; each is a tunable parameter.
Reading
Excellent ≥ 8 · Healthy ≥ 6 · At risk ≥ 4 · Critical below.
How much of the customer's recorded needs the ecosystem meets. The source of switching cost, and your partner-recruitment brief.
ECS = needs met ÷ needs recorded
importance-weighted × 100
0–100, per customer. A critical unmet need costs more than a nice-to-have.
| ECS | Reading |
|---|---|
| > 80 | Complete solution — the ecosystem covers what this customer needs. |
| 60 – 80 | Strong; the gaps are specific and recruitable. |
| 40 – 60 | Partial; the customer is sourcing elsewhere for real needs. |
| < 40 | Thin; switching cost is low. |
Which parties produced this customer's outcome, and in what proportion? A share of 15 weighted points per customer, rolled up to a mean per party.
15 points per customer, split by lifecycle stage;
a party's share = points earned ÷ 15
Six stages, weighted by how much of the customer's lifetime value they carry. A party present only at acquisition can earn at most one point of fifteen.
Portfolio-level signals — the whole book ranked by attention needed, renewals due, stale relationships, coverage gaps — are included on every tier, including Free. The per-relationship scores on this page, and the reasons behind each of them, are kept continuously up to date for the relationships you have flagged for monitoring.
A monitored relationship is one the customer has explicitly flagged for continuous analysis. Monitoring is opt-in per relationship and toggleable by the customer at any time.
An unmonitored relationship still captures everything — every record, document and interaction stays in the workspace. Unmonitor one to free its slot for another.
Monitored relationships per tier. Full ladder on the pricing page.
Every value shown on www.entwineapp.io is illustrative. Inside the product a score is either computed from your records or withheld with the reason shown — Entwine does not estimate, backfill or model a value it cannot read from the data.
Free for 5 monitored relationships. Import your customers and partners, flag the relationships that matter, and the scores start from the first record. Prefer a spreadsheet first? Run the definitions on your own data with the Framework Calculator, an Excel workbook that uses the same v1.0 definitions.
