> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fundwork.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Writing a Strong Opportunity That Attracts Great Talent
> Best practices for writing Contracts, Bounties, and Campaigns on Fundwork that attract skilled talent and produce the results you need.
A well-written opportunity sets the tone for everything that follows — the quality of applicants, the relevance of submissions, and the smoothness of the engagement. Invest a few extra minutes in your posting and you'll spend far less time filtering noise later.
Think of your opportunity as a brief to a professional. Treat it the same way: be specific, be direct, and give enough context for someone to do excellent work without having to guess.
Your title is the first thing talent sees. Make it descriptive enough to communicate the scope and subject at a glance.
**Strong examples from live opportunities:**
* *Build a mobile-first landing page* — communicates format (mobile-first), deliverable (landing page), and action (build)
* *Refresh brand system* — clear scope, implies creative work
* *Edit 10 short-form videos* — quantity and task type in the title itself
* *Find and document onboarding bugs* — dual deliverable (find + document) in a single phrase
**What to avoid:**
* *Designer needed* — no scope, no deliverable
* *Help with project* — vague and uninviting
* *Landing page* — missing the action (design? build? review?)
Lead with the verb: Build, Design, Research, Write, Edit. Then add the object and any scope qualifier (mobile-first, 10 videos, 20-second).
The overview is your chance to explain *why* this work matters and what success looks like. Don't just restate the title — add background that helps a worker understand your project, audience, and constraints.
Include:
* What your product or organization does (briefly)
* Why you're doing this work now
* Who the end audience is
* Any relevant existing assets, brand guidelines, or prior work
**Example:** For a bounty like *Rewrite onboarding copy*, your overview might explain that your current onboarding flow has a high drop-off rate, that your users are crypto-native but not developer-technical, and that you want the tone to feel approachable without being patronizing.
A strong overview surfaces the constraints that matter. Mention your tech stack if it's relevant to a dev contract, or your brand personality if it's a design or writing task.
Deliverables are the outputs you expect to receive. Write them as a list, not a paragraph. Each item should describe a discrete, verifiable thing.
**Weak:** Deliver a polished landing page.
**Strong:**
* Fully responsive HTML/CSS landing page (mobile-first)
* All source files in a shared GitHub repo
* One round of revisions included
* Loom walkthrough of the build (5–10 min)
If you're posting a Contract with milestones, assign deliverables to specific milestones so workers know what's expected at each stage.
Milestones break a Contract into reviewable stages with associated payments. A well-structured Contract gives the worker a clear path and gives you natural checkpoints to course-correct before it's too late.
**Live example — Build a mobile-first landing page (\$1,200, 3 milestones):**
* Milestone 1: Wireframes and content structure
* Milestone 2: Designed mockups + stakeholder review
* Milestone 3: Production-ready build + handoff
**Live example — Refresh brand system (\$900, 2 milestones):**
* Milestone 1: Audit of existing assets + proposed direction
* Milestone 2: Delivered brand system (colors, type, components)
**Tips for good milestones:**
* Give each milestone a clear, standalone deliverable — not just "Phase 1"
* Front-load discovery and planning (milestone 1) so misalignment surfaces early
* Make the final milestone the completion of all work, not just "final touches"
Keep milestones to 2–4 for most projects. Too many milestones introduce friction; too few leave large chunks of work unverified until the end.
Judging criteria are the standards you'll use to evaluate submissions and select winners. Be explicit — workers use your criteria to calibrate their effort, and you'll use them to defend your selection.
**Live example — Create 20-second launch video (\$250, single winner):**
* Video must be exactly 20 seconds or under
* Must use provided brand assets (logo, color palette)
* Judged on: pacing, visual clarity, emotional tone
**Live example — Find and document onboarding bugs (\$500, 3 winners):**
* Each bug must include: reproduction steps, screenshot or screen recording, expected vs. actual behavior
* Judged on: severity, reproducibility, quality of documentation
**What to include:**
* Any hard constraints (length, format, file type)
* The qualities you'll weigh most heavily (creativity, accuracy, brand alignment)
* How you'll break ties if multiple submissions are close
If you're awarding multiple winners (like a 3-winner bug bounty), explain whether all winners get equal amounts or if prizes are tiered.
Requirements tell workers what they need to be eligible to submit. Use this section to prevent clearly unqualified submissions from cluttering your review queue.
**Examples:**
* Must have at least 3 published video editing samples
* Submissions must be original work, not AI-generated
* Design submissions must be in Figma
* Must have experience with Base or EVM-compatible chains (for technical bounties)
Keep requirements proportional to the prize. A $150 design bounty doesn't need a five-point eligibility checklist — a $500 technical bounty might.
State your budget in USDC and make sure it reflects the actual scope of work. Underpaying signals that you don't understand the effort required and will deter skilled workers.
**Reference points from live opportunities:**
* *Build a mobile-first landing page* — \$1,200 (3 milestones)
* *Refresh brand system* — \$900 (2 milestones)
* *Research consumer apps on Base* — \$350 (2 milestones)
* *Edit 10 short-form videos* — \$600 (2 milestones)
* *Create 20-second launch video* — \$250 (bounty, single winner)
* *Design X header* — \$150 (bounty, single winner)
If you're unsure about market rate, search similar opportunities on Fundwork to calibrate. For Campaigns, set your per-submission reward based on the effort each qualifying submission genuinely requires.
Skills tags help workers find your opportunity when filtering by category. Select only the tags that genuinely apply.
Available categories: **Design**, **Development**, **Design+Development**, **Video**, **Video Editing**, **Research**, **Marketing**, **Product Testing**, **Writing**.
Choose the most specific match. A landing page contract is likely **Design+Development** or **Development** depending on whether design is included. A bug-finding bounty is **Product Testing**. An onboarding copy rewrite is **Writing**.
Adding too many categories doesn't broaden your reach — it muddies your posting and attracts mismatched applicants. Pick the one or two tags that best describe the core skill.