Can Apollo run your partnerships desk? Yes, because BD is a memory problem

A salesperson sends two hundred cold emails on Monday and counts it as a good day. A business development lead sends four messages in a week and lands a partnership that doubles the company’s distribution. Same job title to a recruiter. Completely different motion underneath.

That gap is where most software for “sales” quietly fails the partnerships desk. The tools were built for the two hundred. The four are a different animal, and the difference is not effort, it’s memory.

Business development is not a volume problem. It’s a memory problem wearing a sales costume. The research you did on the partner three weeks ago, the warm intro you almost asked for, the joint pipeline neither side updated, the deal that went quiet on a Thursday and nobody noticed, those are the job. Hold them and you have a partnerships function. Drop them and you have a CRM full of dead threads.

This post takes the BD desk apart, one motion at a time, and shows why each one is something a company brain does better than a calendar reminder ever could.

Why a partnerships desk is not just a slower sales desk

The naive way to staff partnerships is to take your best closer and tell them to “go find partners.” It feels right. They’re good at relationships, BD is relationships, ship it.

Then you watch what actually happens to their week. The closer’s instincts are tuned for a motion that doesn’t apply. Sales rewards speed and volume: touch more accounts, advance more deals, move the number this quarter. So the closer treats a prospective partner like a lead, fast follow-ups, a pitch deck, a push to close. And the partner, who was evaluating whether your two companies should be tied together for years, feels rushed and goes cold.

The motion is wrong because the clock is wrong. A sales cycle is paced by the quarter. A partnership is paced by the relationship, by when the other side is ready, by a piece of news that makes the timing right, by a mutual contact who can vouch for you. You can’t sprint it. You also can’t forget it, because the window to act often opens months after the first conversation, long after a quota-driven brain has moved on.

So the real requirement isn’t a faster closer. It’s a system that remembers slowly and acts at exactly the right moment, which is the opposite of what outreach tools optimize for. The partnerships desk needs the four things below, and each one is a place where memory, not volume, is the bottleneck.

Motion one: research the partner, not the lead list

Cold outreach researches a category. BD researches a company, deeply, specifically, before the first word is sent.

The naive version is a tab explosion. You open the partner’s site, their latest funding note, two of their executives’ profiles, a press mention, the thread where someone on your team met them at a conference last year. You stitch a picture in your head, write the message, and close the tabs. The picture evaporates by Friday. When the partner replies three weeks later, you re-open every tab and rebuild the picture from scratch, and you’ve lost the half of it that lived only in your memory.

The cost here is not the research time. It’s that the research has no home. It lives in a closed browser and a tired brain, so it has to be redone at every touch, and the version you redo is always thinner than the one you had.

Apollo’s version starts from the company brain. Ask it to research a prospective partner and it pulls what’s already there, the conference note, the email thread from last year, the mutual connection nobody remembered, and adds what’s public: the recent news, the strategic shape, the reason your two companies might fit. Then it writes the picture down, in the brain, attached to the partner. The next touch doesn’t start cold. It starts from everything you and the company ever knew about this relationship, assembled into one brief instead of a scavenger hunt.

The difference is where the research lives. In a browser, it dies on close. In a brain, it compounds, every conversation makes the next brief sharper.

Motion two: draft the warm intro, because cold is the wrong door

The single highest-leverage move in BD is the warm introduction, and it’s the one that gets skipped, because asking for it is awkward and tracking it is tedious.

Here’s the naive failure. You want to reach a company. You vaguely recall someone in your network knows someone there. To use that, you’d have to: remember who, find the thread that proves the connection, figure out whether the relationship is warm enough to ask, draft a forwardable note that makes it easy for your contact to say yes, and then remember to follow up if they don’t. That’s five steps of friction standing between you and the best door in. So you skip it. You send the cold email instead, through the worst door, and wonder why the response rate is what it is.

The path existed. It just cost too much to walk, so it functionally wasn’t there.

A company brain collapses that cost. It already holds the relationship graph, who on your team has talked to whom, in what context, how recently. Ask it to open a door to a target company and it can find the warmest path, surface the contact who can make the intro, and draft the forwardable note: a clean, short message your contact can pass along with one line of their own. It doesn’t send it for you, a warm intro you didn’t approve isn’t warm, it’s a liability. It does the tedious five steps so that the only thing left for you is the human judgment: yes, ask them, or no, not yet.

The mechanism is the same one under all four motions: the work that blocked the right move was assembly, and assembly is exactly what a system that never forgets is good at.

Motion three: keep the joint pipeline both sides can see

A partnership produces a pipeline that belongs to two companies at once. That’s the structural reason it rots.

The naive setup is two CRMs that never agree. Your side logs the deals it sourced through the partner; their side logs theirs; neither sees the whole. A deal you thought the partner was driving sits untouched because they thought you had it. The quarterly partnership review becomes an hour of reconciling spreadsheets to discover that the joint number nobody owned is smaller than either side assumed. The pipeline didn’t fail. The bookkeeping of it failed, because it was split across two systems with no shared memory.

The deeper problem is ownership. In a normal pipeline, one person owns each deal. In a joint pipeline, every deal is half-owned by someone you don’t manage, which means the part of the work that falls through the cracks is structurally invisible to you. You can’t manage what you can’t see, and you can’t see your partner’s CRM.

Apollo’s version treats the joint pipeline as one object in the company brain, fed from your side and reconciled continuously, so the state is always assembled rather than reconstructed once a quarter in a panic. Every deal carries its real status, its last movement, and which side touched it last. When something stops moving, the system knows, not because someone ran a report, but because watching the pipeline for silence is a standing job it never sets down. Which is the fourth motion, and the one that pays for the desk.

Motion four: nudge the deal that quietly stalled

Every deal that dies in BD dies the same way. Not with a no. With a silence.

The naive way to catch a stall is to remember to check. You tell yourself you’ll review the partner deals every Friday. For three Fridays you do. Then a launch eats a month, and the deal that went quiet in week two surfaces in week eight as a postmortem: “whatever happened with that?” Nothing happened with it. That was the problem. Nobody was watching the gap between the last message and now, because watching a thing for the absence of activity is precisely the job humans are worst at. We notice events. We do not notice non-events.

Say a partner conversation goes warm and then quiet. A week of silence is normal. Three weeks is a deal cooling. Six is a deal you’ve lost and don’t know it yet. The signal isn’t an event you can react to, it’s the steady accumulation of nothing, and nothing doesn’t trip a notification.

Apollo watches for the non-event. Because the joint pipeline lives in the brain and the brain never stops reading it, a deal that hasn’t moved past the threshold for this relationship surfaces on its own, with the context already attached: who it was with, what was last said, why it mattered, and a drafted nudge ready for you to send or rewrite. Not a generic “just checking in.” A specific, warm follow-up that picks up the actual thread, because the system remembers the actual thread.

That’s the clause that earns the whole desk. The research is preparation. The intro is leverage. The pipeline is hygiene. But the deal that would have died in silence and didn’t, flagged in week three instead of mourned in week eight, that’s the partner you keep, the channel that compounds, the distribution you’d otherwise have lost in your sleep.

The turn: stop making your best relationship-builder a database clerk

Here’s the part that isn’t about software.

In most companies, the partnerships desk is one person who is genuinely good with people, and you’ve buried that gift under bookkeeping. They spend their best hours re-researching partners they already met, reconstructing context that should have been saved, reconciling a pipeline across two systems, and feeling guilty about the deals they let go quiet. The relationship work, the part only a human can do, gets the scraps of attention left over after the memory work eats the day.

That memory work feels like diligence. It’s a tax. Every hour spent reassembling what the company already knew is an hour not spent on the conversation that actually moves a partnership, the read of whether the other side is ready, the judgment call on when to ask for the intro, the warmth that no draft can fake. You made your best relationship person a clerk because no system would hold the memory for them. That was never a good trade.

The promise isn’t an agent that blasts more partner outreach. The world has enough of that. It’s that the research is already written, the warm path is already found, the pipeline is already current, and the stalled deal already surfaced, so the most relationship-capable person in the company stops doing the remembering and gets to do the relating.

---

That’s what we’re building at Apollo Space, not a faster outreach machine, but a partnerships desk with a memory: research that compounds, intros that find the warmest door, a joint pipeline that doesn’t rot, and a watch on every deal for the silence that means it’s slipping. Business development was always a memory problem wearing a sales costume. If you’ve ever lost a partner to a thread you forgot to pick back up, you already know which problem to solve first.