Affinity's relationship graph is brilliant until it isn't. The platform maps connections between contacts, companies, and deal stage with unusual depth—but only while your contact base stays under 200 active nodes. Past that threshold, graph queries slow noticeably. Relationship mapping, which is supposed to surface hidden deal patterns, starts to feel like scrolling through molasses. If you're a venture capital firm or a deal-focused wealth manager, that constraint might never bite. You're managing 50–100 high-signal relationships, and depth matters more than scale. But if you're running a sales org, a mid-market services firm, or an operations team that touches hundreds of customers and vendors, Affinity's architecture starts to work against you rather than for you. The question isn't whether Affinity is good. It is, for its intended use case. The question is: which CRM scales relationship mapping while keeping the parts that actually drive revenue? Why Affinity's graph slows at 200 Affinity stores relationships as edges in a graph database. Each contact is a node; each interaction, connection, or deal association is an edge with metadata. The platform then runs queries to surface second- and third-order connections—the partner's investor, the CEO's previous company, the warm intro path to a target account. Graph traversal is computationally expensive. At 200 active contacts, query time scales polynomially. By 300, the platform noticeably slows. By 500, relationship mapping becomes a background job rather than an interactive feature. This isn't a bug. It's a deliberate architectural trade-off. Affinity optimized for depth over breadth because its customer base—venture firms, M&A advisors, wealth managers—rarely manages more than a few hundred high-priority relationships. When your deal size is ₹10Cr+ and your sales cycle is 18 months, relationship depth per contact justifies the speed cost. But the moment you scale to 500 customers, 200 prospects, 100 vendors, and 50 team members, that trade-off breaks. You need to find the warm intro path to a prospect—fast. Affinity can't deliver that reliably when your graph has 1,000+ nodes. HubSpot: Flatness that scales HubSpot doesn't store relationships as a graph. It stores them as contact properties: a company field, a deal field, an account owner field. When you search for connections, HubSpot runs a relational query, not a graph traversal. This is faster at scale but shallower by design. A HubSpot contact can link to a company, and that company can link to multiple deals. But HubSpot won't automatically surface that your prospect's board member was a founder at one of your existing customers. You could build that relationship manually, or via a workflow, but it requires you to know what you're looking for. Where HubSpot wins: You can scale to 10,000+ contacts without graph slowdown. Deal association, account mapping, and custom properties are fast and reliable. HubSpot's real cost isn't speed—it's depth. You lose the serendipitous relationship discovery that makes Affinity powerful. Where HubSpot loses: At 20 sales reps, your per-user cost hits ₹61,000/month, not the ₹3,000 entry price. Workflows and custom properties eat up implementation time. And relationship mapping requires manual maintenance or third-party integrations (like RocketReach or Hunter) that add complexity and cost. Pipedrive: Deal-focused speed, relationship debt Pipedrive optimizes for deal velocity, not relationship depth. Contacts are attached to deals and companies, but Pipedrive doesn't maintain a separate relationship graph. When you migrate from Affinity to Pipedrive, your relationship metadata either becomes custom fields or gets orphaned entirely. Where Pipedrive wins: If you're managing 50–100 deals at any time, Pipedrive's pipeline UI is faster than Affinity's. Custom fields and activity history let you track deal progression reliably. At 10 sales reps, Pipedrive costs ₹2,000/month per seat—less than HubSpot's entry tier. Where Pipedrive loses: Relationship mapping is manual. There's no built-in way to surface warm intros or connection paths. If you migrate 300 contacts from Affinity, you'll export your relationship data as a CSV, and most of it will become orphaned during the import. Your forecasting also becomes unreliable past ₹50 crore in pipeline—Pipedrive's forecast math assumes deal independence, which breaks when shared decision-makers span multiple deals. Orin: Relationship depth without graph slowdown Orin stores relationships relationally but indexes them for speed. A contact can link to multiple companies, multiple deals, and multiple custom relationship fields. Unlike a pure graph database, relationship queries don't traverse edges—they run indexed lookups. This means relationship mapping stays fast at 1,000+ contacts. When you migrate from Affinity, Orin imports your contact relationships, company mappings, and deal histories without orphaning metadata. You keep the wa