Should You Include Pricing in a Proposal, or Wait for the Call?

Should you include pricing in a proposal, or hold the number back for a call? For the offer you're about to send a real client, the answer is simpler than the advice you'll find searching for it, because most of that advice is answering a different question than the one you're actually asking.

TL;DR: Include pricing in a proposal by default — a written offer without a price turns into a second email exchange instead of a decision the client can act on. The advice to hold pricing back almost always describes live sales calls for complex, multi-stakeholder deals, not a document sent to one small-business client for one job. Wait only when the scope isn't defined enough to price honestly yet. DocsAura, an AI document design tool, takes the offer you've already priced and turns it into something that looks like it came from a business that has this figured out.

Should You Include Pricing in a Proposal? Start With What You're Actually Sending

A proposal is a document, not a conversation. By the time you're writing one, the client has already asked, directly or indirectly, what this is going to cost them. Leaving the number out creates a second round of back-and-forth: a reply asking for the figure you already had, or worse, silence while they wait for something you could have included on page one.

Default to putting the price in the offer, attached to the scope you just described, on the same page. If the client is comparing you against someone else — which most small-business clients are, even informally — the one who makes the decision easy usually wins, and a decision needs a number attached to it.

The "Wait for the Call" Advice Is Answering a Different Question

Search for pricing advice and you'll find two camps that sound like they're arguing with each other. One says put the price in the document. The other says never reveal the price before a conversation. Both are right, because they're talking about different things.

The "wait for the call" guidance almost always comes from B2B sales content aimed at complex software or enterprise deals — situations where the buying group has six or more stakeholders, the scope depends on choices the buyer hasn't made yet, and a number without context genuinely means nothing. In that world, price-first conversations skip the discovery that makes the number defensible.

A small-business offer is a different animal. You've already scoped the job. You know what it involves, roughly how long it takes, and what you charge for it. There's no discovery call left to run — you already ran it, or you didn't need one because the job is one you've done before. Applying enterprise sales advice to a $1,800 landscaping quote or a one-page design proposal borrows caution from a situation that doesn't apply to yours, and it costs you the deal to a competitor who just sent a number.

When It's Actually Right to Hold the Price Back

There's one real exception, and it has nothing to do with sales psychology: hold the price back when you genuinely can't price the job honestly yet. That's a scoping problem, not a strategy.

If you need to see the site before you can quote it, if the client's request is vague enough that two different jobs could hide inside it, or if the final number depends on something you haven't measured, send a short scoping outline instead of a proposal with a placeholder number — then follow up with the priced offer once you know what you're actually quoting. That's not the same as leaving the price out on purpose. It's finishing the job of scoping before you write the document.

Where small-business owners go wrong is borrowing the "hide the price" instinct for jobs they've already scoped, usually out of nerves about stating a number rather than any real ambiguity about the work. If you know enough to write the proposal, you know enough to price it.

What We Found When We Read How the Pricing-Disclosure Advice Actually Splits

We pulled the top-ranking pages currently answering "should you include pricing in a proposal" and the adjacent "should you reveal price before a sales call" question, and sorted each one by what it was actually advising about. The split was clean: of the pages discussing a written proposal or quote document specifically, nearly all of them said include the price as a basic requirement, not a judgment call. The pages arguing to hold the number back were a different group almost entirely — built around live B2B sales conversations for complex, multi-stakeholder software deals, where a number genuinely can't mean anything until the buyer understands the scope. None of the "wait" advice was written about a document already being sent to one small-business client for one defined job — the two pieces of guidance are talking past each other, not disagreeing.

The Default for Most Small-Business Offers

For the offer you're about to send: if you've scoped the job, price it and put the number in the document. That's true whether you're quoting a repair, a design project, a consulting engagement, or a one-time service call. The document should let the client say yes without a phone call standing between them and the decision.

If you want flexibility without hiding the number entirely, a price range or a tiered set of options does that job better than a blank space where the price should be — the client still sees a number, and you keep room to adjust once you know more. What you shouldn't do is send a proposal with no price at all and wait for the client to ask, because that's the version of "wait for the call" that costs deals instead of protecting them.

Once the price is decided, the document carrying it matters almost as much as the number itself. A priced offer formatted in a plain email or a bare Word table reads like a placeholder even when the number is final. DocsAura, an AI document design tool, takes the offer text you've already priced, scope and all, and returns a designed, client-ready page in about two minutes. Your pricing decision and any negotiation stay entirely yours — DocsAura's job starts after that, turning the number you already decided on into a page that looks like you meant it.

If your last few offers went out as plain text with the price buried at the bottom, drop the next one into DocsAura and see what comes back before your next call.

Related reading: quote vs estimate vs proposal covers which document to send and when pricing fits into each one, and AI document design tool: what to look for walks through what actually matters when picking a tool to format the offer itself.