Skip to main content

Overview

Creating a bounty on bounty.new is simple. Define your challenge, set a reward, and publish it across multiple platforms to reach developers wherever they are.

Before you start

Have a clear problem or feature you need built
Determine a fair reward amount
Prepare any necessary documentation or requirements
Fund your bounty.new account

Creating your first bounty

1

Choose your platform

Create bounties from:
2

Define the bounty

Provide clear details:
  • Title: Short, descriptive name
  • Description: What needs to be built or fixed
  • Requirements: Acceptance criteria
  • Reward: Payment amount in USD
  • Deadline: When you need it completed
3

Review and publish

Double-check all details and click Publish. Your bounty goes live immediately.

Bounty details

Writing a good title

Keep it clear and specific:
Fix authentication timeout bug in mobile app

Description best practices

Include:
  • Problem statement: What’s broken or needed
  • Context: Why this matters
  • Technical details: Stack, versions, environment
  • Expected outcome: What success looks like
Example:
## Problem
Users are experiencing timeout errors when logging in via mobile app.

## Context
This affects ~20% of iOS users on version 2.1.0. Error occurs after 
entering credentials but before reaching the dashboard.

## Technical details
- iOS app version 2.1.0
- Backend API: Node.js + Express
- Auth: JWT tokens with 15min expiry

## Expected outcome
- Login completes within 3 seconds
- No timeout errors
- Existing sessions remain valid
- Unit tests included

Setting the right reward

Consider:
  • Complexity: How difficult is the task?
  • Time required: Hours or days of work?
  • Urgency: Need it faster? Pay more.
  • Market rate: What do similar bounties pay?
Start with 100100-500 for small tasks, 500500-2000 for medium features, and $2000+ for complex projects.

Managing submissions

Reviewing work

When developers submit solutions:
  1. Test thoroughly: Verify it meets all requirements
  2. Check code quality: Review for best practices
  3. Ask questions: Request clarifications if needed
  4. Provide feedback: Help them improve if close but not quite there

Approving submissions

Once satisfied:
  • Click Approve in the submission
  • Payout processes instantly
  • Developer receives funds immediately
  • Bounty marked as complete

Rejecting submissions

If work doesn’t meet requirements:
  • Provide specific feedback
  • Explain what needs to change
  • Give them a chance to revise
  • Be respectful and constructive

Bounty lifecycle

1

Open

Bounty is published and accepting submissions.
2

In progress

A developer has claimed the bounty and is working on it.
3

Under review

Work has been submitted and you’re reviewing it.
4

Completed

Submission approved and payout processed.

Tips for success

Be responsive

Answer questions quickly to keep developers engaged.

Set clear deadlines

Give enough time but create urgency.

Provide examples

Share mockups, specs, or similar implementations.

Start small

Test the platform with smaller bounties first.

Advanced options

Private bounties

Create invite-only bounties for specific developers:
  1. Create bounty as normal
  2. Toggle Private in settings
  3. Share invite link with selected developers

Recurring bounties

Set up bounties that repeat:
  • Weekly bug fixes
  • Monthly feature additions
  • Ongoing maintenance tasks
Configure in dashboard under Recurring Bounties.

Team bounties

Allow multiple developers to collaborate:
  1. Enable Team Mode when creating
  2. Set total reward to split
  3. Approve team submission
  4. Payouts split automatically

Troubleshooting

  • Increase the reward amount
  • Clarify requirements
  • Share on more platforms
  • Extend the deadline
  • Add more specific requirements
  • Include acceptance criteria
  • Provide examples or specs
  • Screen developers before approval
Ensure your account has sufficient funds. Add funds in Settings > Billing.

Next steps