Reef went from zero to sold in twelve months. That's a short enough timeframe that the feedback loop is tight — you find out quickly what works.
Here's what I learned about which systems transferred to the next context and which ones didn't.
What transferred
The hiring funnel architecture. The specific sequence — sourcing criteria, screening framework, assessment structure, onboarding cadence — turned out to be largely portable. The inputs change (different roles, different industries) but the shape of the process holds.
The performance review cadence. Weekly check-ins at the individual level, monthly strategic reviews at the client level. This rhythm worked because it created accountability without creating overhead. It could be dropped into almost any client context with minimal adjustment.
The GTM repositioning method. When we pivoted the positioning, we closed 8 new clients in the first week. The method — identify the most defensible positioning, update the messaging, test immediately — transferred directly to advising founders on their own GTM decisions.
What didn't transfer
The specific screening criteria. The questions and assessments we built for BDM hiring didn't work for other roles without significant rework. The architecture transferred; the content didn't. That's worth knowing before you claim a "playbook" is portable.
The operational load assumptions. We built Reef assuming a certain founder time commitment from clients. Some had it. Some didn't. The system needed more modular design to accommodate different levels of client involvement.
What this means for portfolio operations
When you're deploying systems across a portfolio, the question isn't "does this playbook exist?" It's "which parts of this playbook are actually portable across different company contexts?"
The answer is usually: the architecture transfers, the content needs to be rebuilt for each context. Knowing that in advance changes how you scope the work.