The program worked. That was the problem.
One person at Drups Ventures managed the entire influencer program. They knew the influencers personally, had built those relationships over time. They knew who'd been paid, what the rates were, what content was pending approval. The program generated content and drove sales. From the outside, it looked like a functioning operation.
It wasn't a functioning operation. It was a relationship that one person was maintaining in their head.
When that person became unavailable
The exact circumstances aren't the point. What matters is that when this person couldn't be in the seat, for whatever combination of capacity, availability, and circumstance, the program stopped functioning immediately.
Posts went live. Nobody reviewed them before they did. Some content that hadn't been properly approved under the brand guidelines went out.
There was no record of which influencers had active agreements. No documentation of what each influencer had been paid, what the agreed rates were, or what the payment trigger was. The payment system was Refersion, with a $100 threshold for payouts, but nobody outside this one person knew with confidence which influencers were enrolled, what their payment status was, or whether any outstanding commitments existed.
We didn't know what was live. We didn't know what was approved. We didn't know what we'd agreed to pay or who'd already been paid.
The rebuild process
What do you do when you inherit a program with no documentation? You start from scratch and treat everything as unknown until you verify it.
The first step was a complete audit of Refersion: who was enrolled, what their payout history showed, what was pending. That gave us a list of influencers with at least some payment history. A starting point, not a complete picture.
The second step was building the structure that should have existed from the start. An Asana project with defined stages: outreach, agreement, content submission, review and approval, post live, payment triggered. Each influencer relationship as a card moving through those stages. Every card with the agreement terms, the payment rate, the content status, and the approval status documented.
The third step was defining what "approved" actually meant. Content review criteria, who had approval authority, what the turnaround time was. The previous process had those answers living in one person's judgment. The new process had them written down so that anyone with access to the Asana project could make the same call.
The goal was to get the rebuilt program running by October 1st, in time for holiday season. That timeline was tight given that we were starting from zero documentation, but hitting it mattered because the influencer content pipeline needs lead time to build.
Why this pattern is predictable
The "single point of failure" problem in marketing programs is almost universal in companies under about 50 people. A program gets built by whoever had the energy and relationships to build it. That person does it because they care, because they're good at it, and because nobody else stepped up. The program succeeds partly because of their individual competence and relationship quality.
But the program becomes dependent on their presence in a way that's invisible until they're not there. Nobody notices the fragility while it's working.
This is different from a key-person dependency on a revenue-generating founder or a technical lead. Those dependencies are at least visible. Everyone knows the business would be in trouble if that person left. The influencer program dependency is invisible precisely because the program is working. "Working" becomes the evidence that no process is needed, when working is actually the evidence that the informal process is covering for the absence of a formal one.
The minimum viable infrastructure for an influencer program (Asana project structure, documented rates and payment rules, approval workflow, enrolled influencer list) takes maybe two hours to set up correctly. That two hours is worth considerably more than the months of lost pipeline that happen when the person who's been holding it together in their memory becomes unavailable.
Document while it's working. Not after it breaks.
