CRM and Forecasting Tips for Relationship-Driven, Deal-by-Deal SaaS Revenue Operations

Tatiana, fun build, because most of the SaaS RevOps playbook actually works against you here. Three things that have held up for me when the motion is relationship-driven and deal-by-deal. First, model the CRM around relationships and capital flow, not a linear pipeline: your "opportunity" is usually a firm or asset you track for quarters, so stages should reflect conviction and access, not a forecast date, and forcing SaaS stages onto it wrecks data quality fast. Second, treat forecasting as probability-weighted scenarios rather than one committed number, since in secondaries the timing is the hard part, not the intent, so time-in-stage and last-touch decay become your real early-warning signals. Third, instrument relationship coverage over activity volume: who owns each GP/LP relationship, when it last moved, and where it is going quiet tells you more than call counts. Happy to trade notes if useful, I have stood up ops in a few non-standard motions and CRM design is usually where it breaks.