Organizations and networks
Use this route when you want to co-build programs, a knowledge library, an operating layer, or a long-term learning branch.
Partner
The route for long-term collaboration, co-building, and structured implementation
Partner is for contexts that need more than a short question: co-designing a program, building infrastructure together, testing a collaboration model, or opening a new long-term execution branch.
Who should use the partner route
The three groups that fit this intake best
Operating teams
Use it when you have a clear need around structure, process, governance, content, or human-technology coordination.
Long-term operating partners
Use it when the interest is not only a short project, but how to sustain, extend, and coordinate value over time.
Collaboration types
The collaboration shapes this route is designed to receive
-
Programs and pathways
Co-designing curriculum, learning paths, resource layers, or onboarding systems for a clear audience.
-
Content and knowledge systems
Developing frameworks, libraries, playbooks, or knowledge systems that can endure and be reused.
-
Infrastructure and operations
Designing intake, governance, CRM, automation, or coordination layers for more durable operations.
What is being looked for
Partner works best when the problem, scope, and context are already named
-
Current context
What stage you are in, what the team looks like, and where the problem originates.
-
Collaboration aim
Whether you want to clarify the problem, run a small experiment, or move toward a more durable structure.
-
Constraints and cadence
Timeline, resources, openness, and decision rhythm so the intake can be understood correctly from the start.
Send collaboration context
This form goes into the Partner intake flow. If you only need a short question, use Contact so operations can handle it faster.
What happens after submission
Partner does not end with the form submission
-
Your context enters the intake flow
The submission enters the contact model and form log so continuity is preserved between the public surface and the operations team.
-
The context is reviewed by collaboration type
Program, content, infrastructure, or strategy requests are sorted so the response cadence matches the context.
-
The next route is opened
Depending on the context, the next step may be a direct conversation, a resource handoff, or a clearer working structure.