Wealth advisors live in relationships. Not just contacts—relationships. The web of who introduced whom, which family members influence which decisions, what a prospect cares about across a five-year timeline, and who else at that firm might buy your services next. Affinity was built for this. Pipedrive was built for sales velocity. Neither was built for both. We watched two six-person advisory teams—one on Affinity, one on Pipedrive—scale from 20 contacts to 65 over eight months. Both teams owned multi-stakeholder deals (a family office needing trust structuring, tax planning, and investment management across three decision makers). Both teams needed to track relationships that preceded the software by years. Both hit walls. Different ones. Affinity's relationship graph: depth that costs Affinity wins on what it was designed for: mapping who knows whom, who influences whom, and what each node in that network cares about. Its graph database lets you see a prospect's advisors, their family members, their board connections, and the warm introductions embedded in your contact base. For a wealth advisor managing $500M+ in client assets, that visibility is invaluable. The Affinity team we watched spent 45 minutes building a single relationship map for a new prospect: logging the family structure, tagging decision makers, linking previous conversations with family members, and flagging who else in their network might introduce them elsewhere. That map took one advisor's institutional knowledge and made it portable. When that advisor left six months later, their successor could see the entire relationship tapestry. But here's where it breaks: Affinity's strength is also its friction. At 65 contacts, the team was spending 20–25 hours per month maintaining the graph. New relationships demanded structured data entry. Exports required manual cleanup. And the price—Affinity charges per contact, not per user. At 65 contacts across a six-person team, they were paying $1,950/month. Pipedrive's equivalent team cost $480/month. What Affinity does better Graph depth: Six-degree relationship mapping out of the box. No custom fields needed to model family offices or board networks. Warm introduction tracking: Built-in "who introduced whom" fields. Survives contact migration (unlike a Slack thread). Context richness: Each node can hold multiple relationship types—advisor, family member, referrer, co-investor—without forcing them into a single contact record. Knowledge export: If an advisor leaves, their relationship map stays intact and readable by their replacement. Pipedrive's deal depth: scale that Affinity can't match Pipedrive was built for sales teams chasing pipeline velocity. Its strength is not in the relationship graph—it's in the deal machinery. Multi-stakeholder deals, custom stages, forecasting across multiple deal layers, and integration depth. For a wealth advisory team managing concurrent $2M–$10M relationships, that machinery matters more than the graph. The Pipedrive team had a problem the Affinity team didn't: a single prospect (a family office) that owned three separate deals—trust structuring, tax-efficient asset transfer, and ongoing investment management—each with different timelines, different decision makers, and different approval workflows. Affinity let them model the family relationships. Pipedrive let them model the deal machinery: which partner owned which stage, when approval was needed, where the deal sat in forecast, and which deal could close first. Pipedrive's $6 per month per contact model meant the 65-contact base cost $390/month—one-fifth of Affinity's burn. And because Pipedrive wasn't fighting the relationship graph, data entry was lighter. New contacts didn't demand structured genealogy. Deal fields could stay sparse until they mattered. At scale, that lightness compounds. But Pipedrive's weakness emerged at months 5–6: relationship context. When a Pipedrive user logged in two weeks after their last touch, they couldn't quickly see why the prospect was important, who at the firm had history with the family, or what previous conversations had uncovered about the real decision maker. That context lived in deal notes or in Slack. It wasn't portable. When an advisor moved deals to a colleague, some of that institutional knowledge didn't move. What Pipedrive does better Deal layer separation: One prospect can own three separate deals with different stages, timelines, and approval gates without forcing them into a single record. Forecast machinery: Custom pipeline stages, weighted forecasts, and bottleneck detection. Works at 65 deals without lag. Integration breadth: Slack, email, calendar, and accounting integrations run tighter than Affinity's. Cost scaling: Per-contact pricing stays predictable. A 200-contact base doesn't triple your bill. Sync stability and data export: where both crack differently We tested data export from each platform. The Affinity team pulled 65 contacts and their rel