Skip to content
OutreachGuy

How to follow up after a demo when your contact needs approval

Give your contact a recap they can forward: scope, price, open questions, and a decision. Includes an example and what to do when the approver is away.

Two paper-cut hands pass a proposal with an orange approval seal.
In this article

If your demo contact needs someone else's approval, help them explain the purchase. Send the agreed scope, cost, and unresolved questions in a form they can forward without rewriting it.

Another demo invitation is useful only if there is something the approver needs to see. First, find out what they need to decide.

The company, people, and prices in this guide are fictional worked examples.

Ask what the approver will want to know

At the end of the demo, your contact might say, “I like it, but my director signs off on software.” Ask what that review involves. You need enough context to make the next message useful, without making the contact feel interrogated.

Useful questions include:

  • What does your director usually need to approve a purchase like this?
  • Is there a budget or review date we should work around?
  • Is anything still unclear about the scope or setup?

Do not assume that a job title gives you permission to go around your contact. Ask before introducing another person to the conversation.

Send a recap with one open decision

In this example, Sofia wants a scheduling tool for twelve staff. Her director needs a monthly cost and an explanation of what the tool would replace.

Subject: Scheduling tool — summary for your director

Hi Sofia,

Here is the short version you can forward.

The job: let twelve staff publish availability and reduce the manual work of arranging appointments.

The scope we discussed: one shared workspace, twelve users, and calendar connections. Your current payment system would stay in place.

The quote: £180 per month on monthly billing. Setup help is included in this quote. There is no annual commitment in the proposal we discussed.

Still to check: whether the calendar connection works with your team's permissions. We should verify that before you commit.

Would your director prefer the written quote first, or a short call about the calendar question?

Alex

The useful part is the specificity. It names both the proposed change and the unanswered question. Replace every commercial term with the approved quote. Never add “no annual commitment” or “setup included” because it makes the email sound easier to accept.

Attach the material that supports the decision

An approver may need the written quote, an implementation outline, a security answer, or a procurement document. Send the thing they asked for. Five unrelated decks make your contact do the sorting.

Keep each answer tied to a source. If the calendar behavior needs a technical check, say who is checking and when you expect an answer. If no one has confirmed it, leave it open.

For a proposal that has gone quiet without an explanation, use the proposal follow-up guide to ask what is holding it up before guessing.

When the director is away

Suppose Sofia replies: “He is away until 15 September.” Record the date and agree on the next contact.

Thanks, Sofia. Would it make sense for me to check back on 17 September, once he has had a little time to catch up?

If she agrees, record 17 September as the next action and stop the intervening reminders. The date is an agreement, not a reason to run the same sequence faster.

When the day arrives:

Hi Sofia,

You suggested we pick this up after your director returned. Has he had a chance to review the quote, or is there a question I can help with?

Alex

If she says the review has moved, update the record. If she declines, close the opportunity. A reply should change the work that follows.

Make the handoff legible

A useful sales record lets a colleague continue without asking the same questions again.

Field Example value
Contact Sofia, operations manager
Approver Director; introduction not yet agreed
Proposed scope Twelve users, shared workspace, calendar connections
Approved quote Quote v3, £180/month, monthly billing
Open question Calendar permissions need verification
Next action Check back 17 September, agreed with Sofia
Stop condition Decline, opt-out, or request to pause

Record what is known separately from what someone needs to check. “Director will approve” is not a fact unless the director has actually approved.

Keep the next step small

The aim of this email is to help the contact get a decision. It does not need to repeat every feature from the demo or claim a return on investment you have not measured.

If the purchase no longer makes sense, a clear answer is useful too. Give the buyer room to say so. For the brief and handoff rules to give an agent, see lead follow-up with OutreachGuy.

Put the example to work.

See the inputs and handoffs for this workflow.

Explore this use case