Relationship intelligence is not decision integrity.
Affinity is a relationship-intelligence CRM that automatically captures network signal from email and calendar metadata. Capital Refinery is the structured record of the investment decision after the relationship has produced an opportunity. The two answer different questions and most teams will keep both.
What Affinity does well, and where the line is.
What Affinity is built for
Auto-captured relationship intelligence on top of the deal pipeline.
Reads email and calendar metadata to surface who knows whom, when they last connected, and how warm the relationship is. Removes the manual data-entry tax that kills most CRMs. For sourcing-heavy teams (early-stage VC and growth equity especially), the relationship layer is the headline value.
What it is not built for
Holding the investment decision after the relationship produces a deal.
Affinity models the network and the workflow up to the moment the deal team starts diligence. It does not model the thesis, the assumptions, or the conditions the IC relied on at approval. The investment decision is downstream of the CRM workflow — and Affinity has no schema for it. After IC, the relationship continues to be tracked; the decision validity is not.
Where Capital Refinery sits next to it
Underneath the IC stage, on the other side of close.
Most teams will keep Affinity. Capital Refinery is not a CRM replacement — it is the layer the CRM hands off to. The structured investment record, the deterministic-first extraction kernel, the operator-data binding, the decision validity scoring across the life of the position. None of these are relationship-intelligence problems.
Where the lines fall.
| Capability | Affinity | Capital Refinery |
|---|---|---|
| Auto-captured relationship and network intelligence | Strong — core capability | No — different layer |
| Pipeline and deal-flow tracking | Strong | No |
| Domain model for the IC decision | No | Yes — first-class object |
| Structured investment record at IC | No | Yes — bound at approval |
| Operator data → entry assumption mapping | No | Yes — the data model |
| Decision validity scoring across the position | No | Yes |
Your team will keep Affinity. The question is what holds the decision after the relationship produces it.
Bring us a deal that came out of your Affinity pipeline. We will show you the structured decision layer the CRM is not designed to produce.