IT Consulting Proposal Follow-Up: Ask for the Next Decision

Follow up on an IT consulting proposal by asking what decision remains and helping the customer resolve it. Agree a review conversation when you send the proposal, identify the buying participants, and track their next action. A proposal in the customer's inbox is not evidence that the customer is ready to approve it.

Microsoft defines opportunity stages. Microsoft co-sell opportunity management. GitLab documents customer evidence and requirements as opportunities progress. GitLab commercial sales opportunity stages. The practical workflow below is a proposed management approach, not a claim that a particular tool or provider produces guaranteed results.

Arrange the review before the document disappears

When possible, agree who will review the proposal, which questions the review should answer, and how the buyer will decide what happens next. The conversation may need a business sponsor, technical reviewer, procurement contact, or finance approver. Let the customer explain its process rather than imposing a seller's preferred close date.

If the buyer does not want a meeting, ask for an appropriate alternative. A clear written review process can work. What matters is whether your team understands who is deciding and what evidence they need. Sending repeated reminders without that understanding can create activity while leaving the underlying decision untouched.

Use a proposal decision log

Keep one record for the proposed engagement. Capture the current version, customer outcome, key scope questions, review participants, required approvals, and next agreed action. Link the approved commercial document and relevant discovery findings so the account owner can explain the offer without searching several message threads.

• Fit: does the proposal address the customer's current priority?
• Scope: do deliverables, assumptions, and exclusions make sense to the reviewers?
• Readiness: can the customer provide the inputs and decisions the work requires?
• Approval: who can authorize the engagement, and which reviews remain?
• Timing: what real event influences the decision, and has it changed?
• Next step: what will the customer and your team each do?

Keep uncertain information labelled. Your contact may believe a budget is available without having an approval. Record that distinction. A manager reviewing the pipeline needs customer evidence, not a confident interpretation that cannot be traced to a real conversation.

Match the follow-up to the blocker

If the customer is uncertain about scope, offer a bounded clarification with the appropriate consultant. If procurement needs a document, coordinate the approved response. If the business priority changed, revisit relevance. If there is no decision owner, ask the sponsor how the project can move forward.

Avoid using an arbitrary discount or deadline to solve a problem that is actually about fit or readiness. Your commercial team should control any approved change in terms. The account owner should be able to explain why the proposed action helps the buyer reach a decision, not simply why it might provoke a reply.

Keep technical clarification bounded

Some proposal questions require additional investigation. Decide whether that work is reasonable clarification, further discovery, or a change in the proposed engagement. Protect your consultants from an open-ended stream of presales analysis without making the customer feel that basic questions are unwelcome.

Use a short agenda for any specialist session: the question, the evidence available, the decision required, and the expected output. The sales owner remains responsible for commercial progression while the consultant validates technical statements. A useful session can conclude that more discovery is required rather than that the initial proposal should be accepted unchanged.

Illustrative example: a proposal stalls after internal circulation

Suppose a sponsor likes a proposed systems assessment but forwards it to a finance approver who has not attended discovery. The approver sees effort and deliverables without understanding the business problem. Sales receives no reply and assumes the project is lost. This example is illustrative.

A useful follow-up asks whether the internal reviewers have what they need. With the sponsor's agreement, your account owner can summarize the business outcome and arrange a short review. If finance questions the value or timing, record that issue honestly. Do not describe the engagement as approved until the actual authorized decision occurs.

Define active, nurture, and closed states

An active proposal has a plausible current buying process and a customer-owned next action. A nurture opportunity may still be relevant but lacks a near-term decision. A closed opportunity has a recorded outcome or a clear reason that active pursuit should stop.

Set these definitions for your business and apply them consistently. Do not leave an opportunity active indefinitely because the proposal required substantial effort. Equally, do not mark a competitor win without evidence. Record what is known and preserve the relationship through an appropriate future contact plan when the customer wants one.

Improve the management conversation

Review proposals with no agreed next action, repeated scope questions, missing decision participants, and decision dates that moved without a new customer commitment. Those signals identify where qualification or proposal preparation may need improvement.

Start with the live proposals your team currently finds hardest to forecast. Replace the next status-chasing message with a clear question about the remaining decision. The objective is a more accurate pipeline and a better customer conversation, while recognizing that useful qualification sometimes ends with a decision not to proceed.

Put clear ownership around the work

Escencion provides Managed Sales & Business Operations for technology companies. Our current client focus is MSPs and MSSPs. Explore our Managed Sales approach, or discuss the responsibilities you need managed. Your technical team retains technical validation, approved commitments, engineering, and service delivery.