Write a one-page project brief
Before contacting anyone, describe the outcome, audience, timescale, budget or resources, decisions that still need to be made and the work that is already underway. A small, honest brief is better than an impressive but vague pitch. It gives a potential collaborator something concrete to respond to.
Separate essential responsibilities from nice-to-haves
List the responsibilities the project cannot progress without. Then list the capabilities that would be useful but could be learned, shared or sourced later. This prevents a search from becoming an impossible wish list and makes room for people with different but complementary experience.
Make an invitation, not a demand
A respectful invitation explains why you are reaching out, what you know about the person’s work, what you are asking for and what they can reasonably say no to. Share the uncertainty as well as the ambition. People can judge fit more fairly when expectations are visible.
Use an exploratory conversation
The first conversation is for discovering mutual interest, not forcing a commitment. Ask what the person would need to understand, which part of the work interests them, what constraints they are managing and what they would change about the brief. Leave enough space to decide after the conversation.
A reusable project-brief checklist
- What is the outcome, audience and timescale?
- Which responsibilities are essential, and which are useful extras?
- What resources, decisions or unknowns should be visible?
- What is the smallest invitation that lets someone decide whether to talk?
Avoid vague asks, hidden expectations and premature commitment. QuanTies can hold context for a conversation; it does not replace the conversation or guarantee a collaborator.