Feature deep-dive
When scope isn’t fully defined, a fixed quote feels wrong and an hourly rate feels worse. PaymentPing lets you quote a range like “$1,000 to $1,500” — without scaring off the client.
14-day free trial · No credit card · Range pricing on every plan
The problem
Every freelancer knows the trap. Quote too low and the first surprise — the extra round of feedback, the stakeholder you didn’t know existed, the wall behind the wall — eats your margin. Quote too high to protect yourself and you lose the gig to someone less scarred. The number you write down is supposed to be a commitment, but in practice most fixed quotes are guesses with a confident font. You’re pricing a project you can describe but can’t precisely measure, and pretending you can. Then you spend the project either eating scope creep in silence or having an awkward conversation about a change order.
Range pricing is the way out, and it’s not new. Trades have done it forever — a contractor walks the basement, sees the panel, and tells you “eight to twelve grand depending on what we find behind the drywall.” Consultants do it constantly — engagement letters with a low and high based on stakeholder count. Wedding photographers do it — a package floor with optional hours stacked on top. The format is older than software. It’s honest. It says: I can describe the work, but the final number depends on a few things we haven’t pinned down yet, so here are the goalposts.
And yet invoicing software has refused to support it for twenty years. Every tool on the market — FreshBooks, Wave, QuickBooks, HoneyBook, Bonsai, Harvest — assumes one quote equals one number. The workaround is to send two quotes (a low version and a high version) and let the client pick, which is dumb and defeats the point. Or to send a single inflated quote and quietly hope you came in under it. Or to charge hourly and inflict a heart-attack invoice at the end of the month. None of these are good. All of them exist because the software wouldn’t bend.
Whether you’re a contractor, a consultant, or a photographer pricing wedding packages, you’ve hit this wall. PaymentPing is the first invoicing tool that treats range pricing as a first-class concept — not a workaround, not a spreadsheet trick, not two quotes glued together.
The concept
A sliding scale quote is a quote with a minimum and a maximum instead of a single fixed price. You describe the work, you describe the goalposts, you give the client a range — say $3,500 to $4,800 — and you commit to landing somewhere inside that range based on how the project actually unfolds. The range is the contract. You’ll never come in below the floor and you’ll never exceed the ceiling. Anything in between is fair game.
The format is honest about uncertainty. A fixed quote pretends the future is knowable; a sliding scale quote admits that scope has known unknowns and prices the uncertainty into the agreement up front, in plain language, before any work starts. That clarity is worth more than the false confidence of a fixed number you’re going to blow through anyway. Clients aren’t scared by ranges — they’re scared by surprises. A range eliminates the surprise.
When to use range pricing
Not every quote should be a range. But these four situations come up constantly, and a fixed price for any of them is a coin flip dressed up as a commitment.
You can describe the work, but the final size depends on something you haven’t measured yet — “depends on what we find when we open the wall”, “depends on how many stakeholders the audit needs to interview”, “depends on how many drafts the client wants.” A range names the variable instead of pretending it doesn’t exist.
The client is choosing between a base scope and an expanded one. A range like “$X to $Y based on workshop count” lets them flex up or down without renegotiating the whole quote. They feel like they have agency, you don’t have to issue change orders, and both ends of the range are agreed up front.
If you’re catching yourself adding a 30% buffer to every fixed quote because of how often scope creeps, just quote the range. Padding hides the uncertainty and feels expensive; a range surfaces the uncertainty and feels honest. Same total dollars, much better client trust.
Hourly billing has the inverse problem: the client has no idea what they’ll owe until the invoice lands, and the number is always larger than they expected. A range gives the client predictable bounds — they know the worst case before signing — without locking you into a fixed number you can’t honestly commit to.
How it works
When you create a quote, there’s a checkbox at the top: Use price range. Tick it. Two new fields appear — minimum and maximum. Enter your floor and ceiling. That’s the whole setup. Validation makes sure min is greater than zero and max is greater than min, and from that point on, every surface in PaymentPing understands the quote as a range instead of a single number.
What clients see is clean. The accepted quote, the public acceptance link, the PDF, and the email template all show the range — something like $3,500 - $4,800 on detail surfaces (with two decimals when needed) and a compact $3,500-$4,800 on list views. If both ends are whole dollars, the decimals drop off so the number stays readable. Tax is computed against both ends, so the client sees the post-tax range, not just the subtotal range.
The deposit is calculated from the minimum, not the midpoint or the max. This is deliberate — collecting 25% of the floor means you never over-collect at deposit time. Line items display as a clean “What’s included” bullet list with service names only: no quantities, no rates, no per-item totals. (Showing line item dollars next to a price range made clients reach for a calculator and get confused; stripping them keeps the quote calm.) When the project wraps and you convert the accepted quote to an invoice, the amounts come over blank on purpose — you fill in the final number after the client conversation, with the original range preserved as context.
Real example
Maya is a digital marketing consultant. A new client wants a brand audit plus three strategy sessions. She knows the shape of the engagement, but the final cost depends on how many stakeholder interviews the audit needs — somewhere between four and eight people, depending on what she finds in the first week. A fixed quote would either sandbag the client (high) or destroy her margin if the interview list runs long (low). So she sends a sliding scale quote: Brand audit + 3 strategy sessions: $5,000 - $7,500 depending on scope of stakeholder interviews.
The quote lands in the client’s inbox with a public acceptance link. The client clicks through, reads the range, sees the “What’s included” list (audit, three sessions, written report), and accepts in one click. PaymentPing auto-creates a draft invoice in Maya’s dashboard with the deposit calculated from the $5,000 floor. The client pays the deposit, the project starts.
Three weeks later, Maya wraps. The audit needed six interviews, not eight. She goes back to the accepted quote, hits convert-to-invoice, and PaymentPing pulls in the line items but leaves the dollar amounts blank. She enters $6,200 — the honest middle of the range, given how it played out — sends the final invoice, and the original quote stays linked. The client sees the final number, recognizes it as inside the range they already agreed to, and pays. Zero surprise. Zero change-order conversation. Zero awkward email about “the project was bigger than expected.”
Compared to most invoice tools
Most invoicing tools assume one quote equals one number. PaymentPing treats the range as a real thing — understood by the quote builder, the PDF, the public acceptance page, the deposit math, and the conversion to invoice.
| Feature | PaymentPing | Most invoice tools |
|---|---|---|
| Quote a price range (min and max) | Yes, native to the quote builder | Fixed prices only |
| Deposit calculated from the minimum | Yes, never under-collects | n/a — no range support |
| Line items shown as a “What’s included” list | Yes | No |
| Tax computed against both ends of the range | Yes | No |
| Range preserved on conversion to invoice | Yes, final number filled in after the project | n/a |
For the full quote-to-invoice workflow, see quote-to-invoice software or pair this with automatic payment reminders once the final invoice goes out.
FAQ
A fixed number on a fuzzy project is just a guess in nice handwriting. Quote the range, name the uncertainty, and let the project land where it lands.
No credit card required · 14-day free trial · Cancel anytime
