The examples in this newsletter are drawn from real partnership experiences. Names and identifying details have been altered to protect privacy.
Who's This For
You're approaching the end of a funded project. The final report is on the horizon. And somewhere in the space between wrapping up deliverables and writing closing narratives, there's a question nobody has said out loud:
What happens to us when the money stops?
This newsletter is for anyone navigating that transition. For PIs who have built something real with partners and don't want to see it dissolve. For project coordinators who sense the partnership has more to give but aren't sure how to continue without dedicated funding. For anyone who has watched a productive collaboration end not because the relationship failed, but because nobody planned for what came after.
Here's what I've learned: when legacy thinking is embedded throughout a project, the "what happens now?" conversation rarely requires the question. When partners have been building toward continuation all along, the path forward emerges naturally. The challenge is when that thinking wasn't embedded - when the project ran its course and now both parties are looking at each other wondering who speaks first.
The Partnership Moment
Picture this: You're three months from project end. The partnership has been productive - real outcomes, good relationships, work both parties are proud of. Your partner sends an email: "We should talk about next steps before things wrap up."
You agree. But as you prep for the conversation, you realize you don't actually know what you want.
Continue? That would be great, but there's no immediate funding. The proposal you submitted for continuation got rejected. Your institution's bridge funding doesn't cover partnerships.
Let it end? That feels wrong. You built something. Walking away from it feels like waste.
Keep it "warm"? That sounds nice but means nothing concrete. You've seen partnerships go dormant with promises to stay connected, and most of them don't resurface.
Meanwhile, you're not sure what your partner wants either. They might have the same uncertainty. They might be relieved it's ending. They might be hoping you'll propose something you can't actually deliver.
This is the transition moment. And how you navigate it determines whether the partnership continues, concludes gracefully, or just fades.
Under the Surface
Here's what makes this moment hard: academia and most partner organizations operate on fundamentally different rhythms.
In academia, you can pick up and set down a project. Lose focus on a collaboration for six months, then reconnect when a new opportunity emerges. That's not dysfunction - it's how the semester cycle and proposal cycle work. Projects hibernate and revive.
Partners in industry, community organizations, and education don't share that rhythm. When a project ends, their staff get reassigned. Their attention shifts. The institutional memory on their side starts degrading immediately.
So the question isn't just "do we want to continue?" It's "can we design for continuity the way we'd design for grad student funding overlap?" You wouldn't let a grad student finish without planning who picks up their work. Why would you let a partnership end without planning who maintains what?
The paths forward typically look like three options:
Continuation with legacy structure. This is the mutual goal: sustained collaboration with some form of ongoing support. A new grant, institutional commitment, or partnership that funds itself.
Graceful ending. This deserves to be an explicit option. Every partnership deserves an off-ramp. When priorities diverge, when capacity shifts, when the work has simply run its course - ending well is better than ending poorly. Acknowledge what was accomplished, express genuine gratitude, leave the door open for future if circumstances change.
Strong momentum without support. This is the hardest path. When the partnership has real momentum but funding doesn't continue, both parties face a drain on trust. You can't ask partners to maintain investment without resources. You can't promise things you can't deliver.
The navigation for this third path is what takes skill.
