u/Voluptuousss

I’m the head of partnerships at a mid-market B2B SaaS. Right now I’m managing 30+ referral agencies and losing my mind over how to track these relationships in a CRM. Partnership pipelines fundamentally don’t fit into sales CRMs. Surely I’m not the only person who sees this?!

Each partner relationship has a revenue share structure (these are not uniform), contract dates, referral volume tracking, relationship health signals, and payout history. Our CRM is built around deals. Deals have stages, a close date, and an amount. That’s it. This makes zero sense for an ongoing partnership that has variable monthly revenue.

I’m basically managing my partner ecosystem in a spreadsheet with conditional formatting. It’s ridiculous. What I need is a CRM with flexible data modeling. I want to define my own objects and fields and create custom relationship types. I want it to create a payout schedule that auto-calculates amounts based on the rev share terms I define.

It’s possible I can get closer to what I need with Airtable but then I’m rebuilding reporting from scratch. And it still doesn’t integrate cleanly with where my deal data is housed.

Please tell me there is an easier way to do this. Do I just have to manually build something?

breaking this down because the amount of vague "just add value in your followups" advice floating around is making me lose my mind. i run the rev ops side for our SDR team at a series B company and while i dont personally send the cold emails i build every system and workflow that makes them happen. followups are where i see the most waste in our pipeline and honestly most of the fixes are structural not creative.

THE ACTUAL PROBLEM WITH FOLLOWUPS

most SDRs treat followups like theyre just re-sending the first email with "bumping this" slapped on top. the open rates crater, reply rates are basically zero, and the whole sequence turns into noise. when i audited our sequences about 14 months ago i found that our followup emails had a 0.4% reply rate across the board. the initial emails were sitting around 2.8% which isnt amazing but its something. the followups were doing literally nothing.

the issue wasnt the copy. it was the system. nobody had thought about what data should flow into a followup, what the timing logic should actually look like, or how to make each touchpoint structurally different from the last one. it was all vibes and no architecture.

THE ENRICHMENT LAYER

this is where it starts. you cant write a good followup if your initial outreach was generic, and your initial outreach will be generic if your data sucks. we run Pro͏speo for enrichment on every list before it hits the sequence, and email accuracy sits around 82-85% which is solid enough that we're not wasting sends on dead addresses. for company-level data like tech stack, funding rounds, job postings we pull from Cl͏ay. the key thing is that these two sources feed different parts of the email. Prospeo gives us the contact-level stuff, Clay gives us the account-level context.

what changed everything for us was building a pre-sequence enrichment step where we tag each contact with 2-3 "followup hooks" before they even enter the sequence. these are just fields in our CRM (we use Pipe͏drive) that get populated during enrichment. things like: recent job change, company just raised, uses a competitor tool, posted on linkedin about a relevant topic. the SDR doesnt have to research anything at send time because the hooks are already sitting there in the contact record.

SEQUENCE ARCHITECTURE

ok heres the actual process. this is what we run right now and its been stable for about 8 months.

email 1 is the cold open. standard stuff. personalized first line using one of the enrichment hooks, value prop, soft CTA. nothing revolutionary here.

email 2 goes out 3 days later. this is NOT a bump. this email uses a completely different hook from the enrichment data. if email 1 referenced their recent funding round, email 2 might reference a job posting that suggests theyre scaling the team we sell into. the subject line is different. the angle is different. the only thing thats the same is the value prop underneath.

email 3 goes out 5 days after email 2. this one is short, like 40-50 words max. its a case study or a specific number. "we helped [similar company] cut their [metric] by 34% in 11 weeks" type thing. no fluff. the whole email is the proof point.

email 4 goes out 7 days later and this is the one most people skip or do badly. this is a breakup email but not the cringe "is this goodbye" kind. its a genuine pivot. something like "if [original pain point] isnt a priority right now, totally get it. one thing i keep hearing from [their role] at companies your size is [adjacent problem]. worth a conversation?" you're opening a new thread not closing the old one.

email 5 only fires if they opened email 3 or 4 but didnt reply. this is conditional and most sending tools can handle it. we use Inst͏antly for sequencing and the conditional logic works fine for this. email 5 is ultra short, 2 sentences, and just asks a direct question. no pitch.

TIMING AND THE TECHNICAL BITS

the spacing matters more than people think. we tested 2 day gaps vs 3 day gaps vs 5 day gaps on the first followup for about 6 weeks across roughly 4,200 contacts. 3 days won with a 1.9% reply rate vs 1.2% for 2 days and 1.4% for 5 days. not massive differences but when youre sending volume it adds up.

all of this runs through Instantly on the sending side. each SDR has 4 inboxes managed through Mail͏scale and we keep daily volume at 28-32 sends per inbox. warmup runs for minimum 21 days before any inbox touches a real prospect, no exceptions. i had to learn that the hard way after we burned through 6 inboxes in february because someone on the team started sending from day 8 of warmup. that was a fun week of scrambling to set up replacements.

verification happens in two places. Prospeo handles the initial enrichment and email finding, then we run everything through ZeroB͏ounce before it enters a sequence. double verification sounds redundant but it dropped our bounce rate from around 4.1% to under 1.3%. the cost is like $30/mo extra for ZeroBounce at our volume which is nothing compared to losing an inbox.

HOW THE DATA FLOWS BACK

this is the part that actually makes the followups better over time. every reply gets tagged in Pipedrive with the email number that generated it and the hook type that was used. after 90 days we had enough data to see that job-change hooks outperformed funding-round hooks by almost 2x on reply rate (3.1% vs 1.7%). tech-stack mentions were somewhere in between at 2.2%.

that data feeds back into the enrichment step. we now prioritize certain hook types when building the followup fields. its a loop. enrichment feeds sequences, sequences generate reply data, reply data optimizes enrichment priorities.

the part that drives me insane is when tools dont have proper APIs to make this loop work. Pipedrive's API is decent, Instantly has webhooks that mostly work, but some of the enrichment tools we've tried (not gonna name them all) have these half-baked REST APIs where you cant even do a proper batch lookup without hitting rate limits after 50 requests. Prospeo's API has been fine for our volume which is around 2,000-3,000 contacts a month. Clay's API is powerful but honestly overkill for what most people need and the pricing gets weird fast once you start doing anything at scale.

WHAT ACTUALLY MOVED THE NUMBERS

after rebuilding the whole system our overall sequence reply rate went from 1.8% to 4.3% over about 4 months. the biggest single improvement came from the pre-sequence hook tagging, not from better copy. the second biggest came from the conditional email 5 which alone pulls a 5.1% reply rate but only fires on a subset of the list so its not huge volume.

the copy improvements helped too but honestly less than i expected. we spent 3 weeks rewriting every template and it maybe added 0.5% to the overall reply rate. the structural changes, different hooks per email, proper timing, conditional logic, those were worth probably 1.5-2% combined.

one thing i still havent figured out is how to properly integrate linkedin touchpoints into the sequence without it feeling forced. we have Waa͏laxy running separately but its basically its own silo. the data doesnt flow back into Pipedrive cleanly and i cant get the timing to sync with the email sequence. if anyone has solved that i'd actually love to hear about it because right now our linkedin and email motions might as well be run by different companies.

anyway thats the system. its not perfect and we're still iterating on the hook taxonomy and the timing logic but the core architecture has been stable. the main takeaway if youre building this yourself is stop thinking about followups as individual emails and start thinking about them as a data pipeline where each touchpoint is informed by enrichment and optimized by reply data. the emails are just the output layer