Guide

How to Price a One-Off Task So You Actually Get Responses

Pricing a one-time job wrong in either direction costs you — too low and nobody replies, too high and you overpay for a two-hour job. Here's a framework that works whether you're hiring or posting.

Why one-off pricing is different from a company quote

A company quote bakes in overhead, insurance, and a business's need to keep the lights on between jobs. A one-off task or gig doesn't carry that overhead, but it also doesn't come with an established price list — which means most posters either guess low, guess high, or copy a number from a completely different kind of job. None of those work reliably, but there's a straightforward way to land on a fair number.

Start from a real hourly range, not a guess

The single biggest pricing mistake on a one-off task is picking a number that has nothing to do with what the work actually costs in your area. Rates vary by category and city, but the ranges are public and easy to check before you post:

• Handyman work: $50–$150 per hour, plus a minimum call-out fee that covers roughly the first hour
• Local moving help (two people plus a truck): $50–$150 per hour, or $40–$53 per hour per mover in most major markets
• House cleaning: $25–$75 per hour per cleaner, with most jobs needing at least two hours
• Junk removal: about $42 per hour on average, ranging $21–$55 depending on the city
• Errand running and light personal-assistant work: roughly $25–$35 per hour in most metro areas, averaging around $28

If your task falls outside these categories, find two or three quotes or cost guides for the closest comparable service before you write a number down. A price that's 30% under market doesn't get you a discount — it gets you silence, or the one person inexperienced enough to accept it.

Match the pricing model to how well-defined the job is

Fixed price works when you can describe the entire job in a sentence and nothing about it depends on what someone finds once they start: assembling three named pieces of furniture, hauling a specific pile of junk, mowing a yard of a known size. Hourly makes more sense when the scope depends on conditions nobody can see in advance — a repair that might be a five-minute fix or a wall-opening job, a cleaning job in a home nobody's toured. For more on making that call, see our full breakdown of hourly vs. fixed pricing.

Price the job, not the hour you imagine it taking

New posters routinely estimate task length as if the person doing it already knows the space, has all the tools staged, and hits no surprises. A "quick" furniture assembly job of five pieces is realistically 3–4 hours once you include travel, unboxing, and hardware sorting — not the 45 minutes it might take in your head. Under-timing the job and pricing to that fantasy timeline is the same mistake as underpricing outright. If you're unsure whether your job is quick, moderate, or spans more than a day, walk through our guide to scoping task size correctly before you set a number.

Build in a small buffer for anything you can't fully see

If there's any chance the task is bigger than described — an attic you haven't measured, a yard you haven't walked, a move where you're not sure how many boxes you actually have — price 10–15% above your estimate and say so in the post: "Budget is $200–230 depending on final box count." That range does more to get quality responses than a hard number, because it tells serious taskers you've thought about the job instead of picking a round figure.

When it's fine to ask for quotes instead

For jobs with real regional volatility — full-day yard restorations, multi-room painting, anything depending heavily on materials you haven't priced yet — it's reasonable to post a wide range or ask responders to quote against your description, provided the description is detailed enough that the quotes will be comparable. What you should never do is leave both the price and the scope vague at the same time; that combination gets you either no replies or replies you can't compare to each other.

The two mistakes that quietly kill response rates

Underpricing to "see what happens." A price under market doesn't test demand — it filters out anyone with other options, leaving you with the applicants least likely to show up reliably.

Hiding the budget entirely. Posts with no price or range attached get fewer responses, not more negotiating leverage, because most taskers skip posts where they can't tell in five seconds if it's worth opening. Pair your number with a description that's actually clear — see how to write a task description that gets quality responses for the structure that pairs well with a fair price.

A quick reference before you post

Before you publish, run through this short checklist: does your number sit inside a real hourly or per-job range for the category, not a round guess? Have you accounted for travel and setup time rather than just the "hands-on" portion of the job? Does the post state whether the price is fixed or an estimate, and if it's an estimate, have you said what could move it? And if the job has any real unknowns — access you haven't confirmed, a pile you haven't measured — have you posted a range instead of pretending to more precision than you actually have? A post that can answer yes to all four rarely sits unanswered for long, because it reads as though a real person thought about the job before writing the number down, which is exactly the signal that gets a serious response instead of a guess back.