Affinity's visual relationship graph is genuinely remarkable. You can see a family office network spread across a canvas, trace money flows between entities, spot hidden decision-makers buried three levels deep. For relationship intelligence in wealth management, it has no peer. Then you try to invoice a client. Affinity does one thing with extraordinary depth: it maps who knows who, and why that matters. The moment your workflow branches into operations—billing, contracts, team coordination, client onboarding—Affinity becomes a beautiful data warehouse with no doors out. Your invoices live in a separate tool. Your signed agreements scatter across email. Your team talks about clients in Slack while Affinity sits silent. You end up maintaining two parallel systems: Affinity for relationship truth, and a patchwork of tools for everything else. This article is for wealth advisors, family office operators, and relationship-driven advisors who are deciding: do I build on Affinity alone, or do I layer in an operational CRM? What Affinity actually wins at Affinity's strength is relationship graph depth . It lets you record: Multi-generational family structures and decision hierarchies Cross-entity connections (board seats, fund stakes, co-investments) Historical context (how a contact came to you, who introduced them, what deals preceded this one) Relationship strength and interaction frequency Opportunity pipelines that branch across a network, not a single contact If your core workflow is relationship intelligence —knowing which family members matter, which board members can unlock a larger fund commitment, where hidden synergies live—Affinity's canvas beats a table in a spreadsheet or a linear pipeline in most CRMs. The connectors (to Outlook, Gmail, LinkedIn) pull in email and activity signals. You see last interaction dates, how often someone emails. It's passive intelligence on top of active relationship mapping. Affinity's real edge: It turns relationship data into a visual truth. You see the structure. Most CRMs bury it in contact fields and notes. Where Affinity breaks: the operational wall Here's what Affinity does not do, or does poorly: Invoicing and billing Affinity has no invoicing module. You cannot issue an invoice, set payment terms, track payment status, or reconcile cash against a deal. You'll use Stripe, QuickBooks, FreshBooks, or another accounting tool, then manually sync what got paid to Affinity's deal status. When a client disputes an invoice or you need to issue a credit note, that lives outside Affinity. Your source of truth splits. Contract execution and approval Affinity has no e-signature or approval workflow. You draft an agreement, email it out (external tool), get signatures back (external tool), then upload a PDF to a deal record. If you need approval routing—a partner reviews before you send, finance signs off after—you're juggling email and message threads. Speed suffers. Audit trails scatter. Team workflows and handoffs Affinity is a relationship database, not a team operations platform. You cannot assign a task, set a reminder for a team member, or see who owns what without reading a notes field. If you're a small advisor team and one person needs to hand off a client relationship, there's no native handoff workflow. Team chat and task coordination happen elsewhere—Slack, email, or a separate project tool. Client onboarding and portals Affinity has no client portal. New clients can't upload documents, sign intake forms, or see the status of their onboarding. You'll build a separate portal or use a form tool, then manually log that the client submitted KYC documents into Affinity's notes. Automation stops at Affinity's edge. Reporting and forecasting Affinity's deal pipeline view is basic. You can't forecast AUM growth across a family office network or report on relationship value over time with the same visual richness that the relationship graph gives you. Custom reporting requires exporting data and pivoting it elsewhere. Why connectors don't solve this Affinity's marketplace has integrations: Salesforce, HubSpot, Zapier, Slack, and others. Some advisors think: I'll connect Affinity to my invoicing tool, my contracts tool, my team chat, and call it solved. In practice, connectors are one-way funnels, not bridges. A Zapier automation might push a new deal from Affinity to your accounting software, but it won't pull payment status back. You'll miss deal-to-invoice mapping. If a payment comes in early or a customer disputes an amount, you're logging back into your accounting tool, not seeing it reflected in Affinity. The relationship record stays incomplete. Connectors also hide latency. A Zapier task runs every 5 minutes. If you close a deal at 3 PM, the invoice might not generate until 3:05 PM. For low-velocity workflows, this is fine. For a team of advisors managing urgent client needs, it creates friction and data staleness. The connector trap: You end up with two systems o