Proposal vs No-Proposal Sales Process

A proposal is a document, not a buying signal

"Send me a proposal" can mean the prospect is ready to inspect the terms. It can also mean they want the call to end.

You need to know which conversation you are having.

An agency proposal is useful when it records scope, responsibilities, commercial terms, or information needed for an internal decision. It becomes a problem when the founder sends it because asking about the decision feels uncomfortable.

There isn't one correct answer for every agency. A simple engagement and a project involving several stakeholders may need very different processes. What matters is whether the document has a clear job.

Don't confuse no proposal with no written agreement

Some advice about closing without proposals gets taken too far. The owner hears that documents slow down sales and starts treating a verbal yes as enough.

The buyer still needs to understand what they are agreeing to. Scope, terms, responsibilities, exclusions, and material conditions should be clear and properly documented.

A no-proposal process usually means avoiding an unnecessary custom sales document before the commercial decision. It does not mean keeping the agreement vague or skipping the protections both parties need.

You may explain a standard service on a call, confirm the decision, and send the agreement. A complex project may require substantial written detail before anyone can approve it. Match the process to the work.

Find out what the proposal is meant to do

When the prospect asks for a proposal, ask what they need it to help them assess.

"What would you want the proposal to confirm?"

That can reveal a scope question, an internal reviewer, a requirement to compare suppliers, or an unresolved concern about the recommendation.

If they say, "Just everything we've discussed," summarise the main points and check whether they agree. You may discover that their understanding differs from yours.

This is not an attempt to refuse the document. It is how you avoid spending hours writing something that does not answer the buyer's actual question.

Establish whether they want the recommended work

Before discussing concessions or writing options, check commitment to the work itself.

An illustrative example: a prospect asks a web agency for three packages. The owner starts reducing pages and moving features between tiers. But the prospect hasn't decided whether a redesign is needed or whether the existing website needs targeted repairs.

The owner is negotiating scope before agreeing the problem.

Go back to the recommendation. "Before I put options together, do you think the redesign is the right work, or are you still deciding whether to change the site at all?"

Those answers lead to different documents. One records an engagement. The other supports a decision about whether there should be an engagement.

A proposal should reflect discovery, not advertise the agency

The FSI call-review approach keeps returning to a simple point: explain your work against the problems the buyer described.

Apply the same standard to the proposal.

If the first several pages could go to any prospect, ask whether the buyer needs them. Company history and a long service menu may add weight without adding understanding.

Lead with what you understood, the recommended scope, the intended change, and the responsibilities involved. Use the buyer's actual situation, not a dramatic version designed to make your offer look essential.

Include evidence where it helps assess the recommendation. Don't fill the document with unrelated results or imply guarantees the agreement doesn't support.

Handle internal approval as a real process

A prospect may genuinely need a colleague, co-founder, finance team, or procurement reviewer to assess the engagement.

Don't treat every additional decision-maker as an excuse. Find out how the decision works.

Who needs to be comfortable with the work? What do they care about? Will they have questions about delivery, access, security, budget, or timing? Can they join a conversation, or is a written summary the appropriate route?

The person on your call may support the recommendation but not have authority to approve it. Your job is not to pressure them into pretending otherwise.

Make the information useful for the next person. A long transcript of your sales pitch is rarely the best internal decision document.

Agree what happens after the document arrives

"I'll send it over" is incomplete.

Confirm when you will send it, what the buyer intends to review, and whether a follow-up conversation would help. If they need to circulate it internally, ask what timing is realistic rather than imposing an arbitrary deadline.

You can say, "Once you've checked the scope with your co-founder, would it help to have a short call for any questions? When is that discussion likely to happen?"

The purpose is to establish an actual next step. It isn't to keep adding meetings until the prospect gives in.

If they cannot describe any review process or reason to revisit the proposal, the opportunity may be earlier than you think.

Don't let proposal options become premature negotiation

Multiple options are useful when they represent genuinely different scopes or priorities. They are less useful when the founder adds a cheap option because they assume the prospect will object to the fee.

Explain the trade-offs. If reducing scope means leaving a known problem unresolved, say so. Don't describe the smallest package as if it will achieve everything the larger one is designed to address.

A buyer may reasonably choose a narrower engagement. That is different from an agency quietly accepting full responsibility while removing the resources needed to do the work.

Read how to handle price objections before using package changes to answer concerns you haven't understood.

What to do when the proposal goes quiet

Start with the agreement you made before sending it.

If there was a specific review date, follow up on that discussion. If there was an unresolved question, refer to it. Don't send a sequence of generic reminders pretending that the buyer owes you a decision on your schedule.

You might write, "You were checking whether the team could provide approvals in the timeframe we discussed. Has that become clearer?"

If you never established a decision process, acknowledge that. Ask whether they are still considering the work or whether it is better to close the conversation for now.

Silence can have several explanations. Don't invent certainty about why it happened. But don't count a proposal as an active opportunity indefinitely just because you put effort into it.

Choose the process that helps the buyer inspect the decision

A proposal is useful when it reduces uncertainty about real work. It is unhelpful when it adds another step without answering anything.

Review your recent proposals. Which ones had a clear purpose? Which were sent after vague enthusiasm? Which required extensive rewriting because the call never established scope?

That comparison will tell you more than a blanket rule about never sending proposals.

Keep written agreements clear. Respect genuine buying requirements. And stop asking a document to do the job of a conversation you avoided. The guide to agency call structure shows where to establish those decisions before the call ends.