Playbook 1 of 4
🎯

The Mission Playbook

How to launch, staff, and run a successful mission on GameChangers from day one.

🌟 What you’ll achieve

By the end of this playbook, you will have a live mission with a clear scope, at least 3 applications from verified professionals, and a signed contract with escrow locked — all within 14 days.

Before you start — you’ll need:
✓A verified GameChangers profile (Explorer tier or higher)
✓A clear problem you want to solve (a paragraph is enough to start)
✓An idea of the skills you need (specific expertise > job titles)
✓15–30 minutes to write your first mission brief
The 7 Steps
1
Define your mission scope
Owner: You · Est. 20 min

Start with one clear paragraph: what challenge are you solving, why it matters, and what a successful outcome looks like. Don’t over-engineer it — you can refine later.

➤Write the “so what” first — why does this mission matter to the world?
➤Describe the outcome you want, not the method
➤Name the sector: Space, Health, Energy, Defense, Food, Water, Air, Transportation, Communications, or Sports
Template
We are launching [Mission Name] to [solve specific problem] for [who it affects]. Success in [timeframe] means [specific, measurable outcome]. This mission requires [3-5 key skills] and operates under [compliance regime if applicable].
✓Done when: Your one-paragraph scope is written and you could explain it to a stranger in 60 seconds
2
Define 3–5 milestones
Owner: You · Est. 15 min

Break your mission into discrete, verifiable deliverables. Each milestone becomes a payment release point in the contract. Be specific enough that both parties can objectively say “done.”

➤Milestone 1 should be achievable in the first 2–4 weeks to build momentum
➤Each milestone should produce a tangible artifact: a report, a prototype, a dataset, a design
➤Include acceptance criteria: how will you know the work meets the standard?
Template
Milestone 1: [Deliverable] — accepted when [criteria] — target date: Week [N] — value: $[amount] Milestone 2: ...
✓Done when: 5 milestones defined with acceptance criteria and estimated values
3
Set visibility and compliance flags
Owner: You · Est. 5 min

Choose who can see and apply to your mission. Set ITAR, DFARS, HIPAA, or other compliance flags if your work touches regulated data or technology.

➤Public: anyone can apply — best for research, climate, health, infrastructure missions
➤Request Access: you review each applicant before granting full access — best for sensitive programs
➤Private / Invite Only: you control the team from day one — best for classified or competitive work
➤When in doubt about ITAR, mark it and consult a licensed export counsel before sharing technical data
⌴ Decision point
Does your mission involve defense/space technical data, controlled technology, or classified contexts? If yes → set ITAR flag and Request Access visibility. If no → Public visibility is fine.
✓Done when: Visibility setting chosen. Compliance flags applied. Mission brief saved as draft.
4
Write the team brief
Owner: You · Est. 15 min

Describe the exact skills you need, the Trust Score minimum you’ll consider, and any credential requirements. Be specific — vague briefs attract volume, specific briefs attract quality.

➤List 5–8 specific skills, not job titles: “AERMOD atmospheric dispersion modeling” beats “Environmental Engineer”
➤Set a minimum Trust Score if your mission requires verified credentials (we recommend 400+ for contract work)
➤State whether security clearance or government registration (SAM.gov, CAGE) is required
✓Done when: Team brief complete with skill requirements, Trust Score minimum, and credential requirements stated.
5
Publish and invite
Owner: You · Est. 10 min

Go live. Your mission appears in the marketplace with all your filters applied. Simultaneously, search for verified professionals whose profiles match your requirements and send personalized invitations.

➤Your first invitation message should name the specific skill you’re looking for and why you picked them
➤Send 5–10 targeted invitations in the first 48 hours — don’t wait for organic applications
➤Include a link to your mission brief in every invitation — context drives response rates
Template
Hi [Name], I reviewed your profile and your background in [specific skill] is exactly what the [Mission Name] program needs. We’re a [brief mission description]. Would you be open to a Get-to-Know session this week? [Mission link]
✓Done when: Mission live. 5+ invitations sent. At least 1 application or Get-to-Know request received within 72 hours.
6
Run Get-to-Know sessions
Owner: You + Applicant · Est. 30 min each

Before committing to a contract, run a 15–30 minute async Get-to-Know session with your top 2–3 applicants. Ask 3 questions. Review their responses at your schedule. Make your shortlist.

➤Use the platform’s built-in question library or write your own — “Walk me through a similar mission you’ve worked on” is always a strong opener
➤Look for: clarity of thinking, relevant experience, realistic expectations about scope
➤A good Get-to-Know response is concise, honest, and specific — not rehearsed
⌴ Decision point
After Get-to-Know: Does this person’s actual experience match what their profile suggests? Are their expectations aligned with your scope and timeline? If both yes → propose contract. If uncertain → ask one follow-up question.
✓Done when: 2–3 Get-to-Know sessions completed. 1 candidate selected for contract proposal.
7
Sign contract and lock escrow
Owner: You + Contractor · Est. 10 min

Generate the contract from your mission scope. Both parties review, sign, and escrow locks automatically via Stripe Connect. Work begins.

➤The contract is auto-generated from your milestone definitions — review all fields before signing
➤Read the compliance disclosure section carefully — especially the ITAR self-certification clause if applicable
➤Both parties must sign — the platform sends reminders if the other party hasn’t signed within 48 hours
✓Done when: Contract signed by both parties. Escrow locked. Mission status → Active. First milestone underway.
Anti-pattern to avoid

Don’t wait until your mission brief is “perfect” before publishing. The act of publishing is what generates the first applications, and the first applications teach you what’s missing from your brief. Publish at 80% and iterate.

Next playbook
Community Playbook

Build your following, grow your network, and establish your reputation before your next mission.

Next →