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

​
Creating your first bounty

1

Choose your platform

Create bounties from:
  • GitHub: Comment @bountydotnew 100 on any issue (repo collaborators only)
  • Bounty.new dashboard: Select a repository and fill out the form
  • Discord: Use /bounty create command
  • Linear: Create bounties from Linear issues (mirrored to GitHub)
Integrations we expect to support in the coming months:
  • Slack (Coming soon)
  • X (Twitter) (Coming soon)
2

Define the bounty

Provide clear details:
  • Title: Short, descriptive name
  • Description: What needs to be built or fixed
  • Reward: Payment amount in USD (Bounty reward must be paid up front - if skipped, submissions for bounties are disabled)
  • 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 100−100-500 for small tasks, 500−500-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

​
Deleting and cancelling bounties

​
Deleting unfunded bounties

You can delete a bounty directly if it hasn’t been funded yet. Simply click the delete button on the bounty card or detail page.

​
Cancelling funded bounties

For funded bounties, you must request cancellation:
  1. Click Request cancellation from the bounty menu
  2. Optionally provide a reason
  3. Support team will process your refund manually
  4. You’ll receive the bounty amount minus the 5% platform fee (non-refundable)
You cannot cancel a bounty that has an approved submission. The solver must be paid.

​
What happens during cancellation

  • All pending submitters receive a notification email
  • Bounty badge changes from “Funded” to “Cancelling”
  • Delete button becomes available while waiting for refund
  • Once refunded, bounty status changes to “Cancelled”

​
Bounty lifecycle

1

Draft

Bounty created but not yet funded.
2

Open

Bounty is funded and accepting submissions.
3

Under review

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

Completed

Submission approved and payout processed.
5

Cancelled

Bounty cancelled and refunded (if funded).

​
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.

​
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

​
Next steps

Set up integrations

Connect your favorite platforms.

Payment settings

Configure payouts and billing.