How Should a Data Analytics Consultancy Follow Up on an Unanswered Proposal?

Ditch the proposal reminders and set up a follow-up sequence that identifies approval blockers, further solidifies the project value you are trying to defend, and most importantly tells the buyer what you need them to do next.

Why Data Analytics Consultancy Proposals Stall After Scoping or Pricing

An unanswered proposal is a symptom, not a cause. Your interested buyer may be busy with other things, struggling to justify your fee, or waiting for necessary data to become available.

Silence is not a diagnosis. Find out from your buyer what he has confirmed and what your team has assumed about the budget, the stakeholders, the technical possibilities and the degree of urgency of the proposed analytics work.

Broader B2B research supports treating stalled decisions as a buying-process problem: 86% of B2B purchases stall during the buying process, according to Forrester. Gartner also found that 74% of B2B buyer teams demonstrate unhealthy conflict during the buying decision process.

Note that these findings are relevant to B2B buying in general and not specifically to analytics consultancies. The practical application here is to investigate the decision making rather than assume that the contact has simply forgotten.

For an analytics project, distinguish between:

• Approval uncertainty: Your contact supports the work but cannot authorize spending.
• Value uncertainty: The deliverables are clear, but their business use is not.
• Delivery uncertainty: Nobody has confirmed data access or internal participation.
• Changed priority: The original problem no longer has an active deadline.

Each of these requires a different message. Another copy of the proposal will not answer all of these.

A Data Analytics Consultancy Proposal Follow-Up Cadence

Use the agreed decision date of the buyer as a starting point. If no decision date was agreed then use the following sequence as a starting point and note that this is not based on research to establish an optimum.

First follow-up: two to three business days after the proposal

Ask one diagnostic question. Don’t ask for a general update or ask if they have read the document.

Suggested email template:

Subject: Approval path for the reporting project

Hi [Name],

Before we can propose a start date we need to establish the appropriate approval path. Can you approve the scoped work, or does someone else need to review the budget or business case?

If there is another reviewer, I would be happy to prepare a short decision summary for you to share.

[Name]

You get a useful answer even if the buyer hasn’t written a review yet.

Second follow-up: four to five business days later

Test a different blocker using something you discussed during the scoping.

Suggested email template:

Subject: Data readiness for [project]

Hi [Name],

left [data owner/access requirement] unresolved during scoping - is this an issue for proceeding with the project?

If the function is available, a short call with the function owner should determine what is available to make changes to the project scope.

Is [day] the right day or are there other dependencies that need to be cleared first?

[Name]

Do not invent a data issue to have a reason to write.

Third follow-up: five to seven business days later

Be explicit in offering a choice: continue with the action defined here, come back on a specific date, or pause for now.

Stopp follow-up sequence if there is no reaction from buyer anymore. Reopen conversation only if there is a good reason to do so or if there was an agreed revisit date in the past.

Data Analytics Proposal Follow-Up Questions That Uncover Approval Blockers

Choose the best question for the evidence you have. A questionnaire after a stalled proposal proposal adds a lot of unnecessary work to the person whose attention you are trying to get.

When the analytics proposal may lack an approval owner

Ask: “Who needs to approve this scope, and what will they need to make that decision?”

Help your contact prepare a handoff summary to Business stakeholders. A brief summary of the business problem being addressed, proposed fees, deliverables expected and the decisions needed to move forward is required.

Be willing to jump into the reviewer conversation with your contact’s permission. Going through a supportive buyer to fix a problem can create a new problem.

When analytics project pricing receives no response

Ask: “Is the concern the total investment, the timing of the spend, or confidence in the proposed outcome?”

These are distinct objections. Reducing the discount does not address the uncertainty of value, and reducing the scope of a purchase does not address a spending freeze.

If budget is an issue, decide on the smallest project that will be of value and negotiate down from there. Specify exactly what you will remove and what you will keep and whether it will still answer a useful question to the business.

When data access may be delaying approval

Ask: “Which data source or internal owner would need to be confirmed before you could approve a start?”

There is a separate approval to buy a skill versus readiness to deliver against a source system. Thus an executive can approve the fee for a skill whereas the person owning a source system has not been approached to participate.

List out the unresolved dependencies here (i.e. do not assume that access, data quality, and/or stakeholder availability have already been addressed).

When the buyer’s priority may have changed

Ask: “Is [original decision or deadline] still driving this project, or has something else taken priority?”

Accept the answer and only agree a revisit if the underlying need has moved, agreeing a sensible revisit time instead of trying to force urgency around your availability.

How Data Analytics Consultancies Can Clarify Proposal Value and Secure a Next Step

Proposals should tie the related analytics work to decisions that the buyer needs to make. Just sending deliverables to your contact is not enough to allow them to get a return on investment within their organization.

Make the decision visible. A proposal listing out the various reports, data models and even the various forecasts can have the buyer build out a business explanation for why you decided to go with the various components listed out.

Prepare a short, forwardable decision note containing:

• The business question the project will answer.
• The person who will use the output and the action it will inform.
• The fee and scope boundaries.
• The unresolved assumption or approval needed next.

Use only numbers confirmed by the buyer. If you don’t know the potential savings or additional revenue yet, state these numbers as assumptions to be verified later, rather than promising any returns.

Hypothetical example: a stalled inventory analytics proposal

A consultant pitches a demand-forecasting project to a distributor. There was commercial lead to do the work as described in the proposal, but no response was received from the prospect.

The founder doesn’t ask for feedback on the status, but instead asks if the delay is due to lack of budget or lack of confidence in the historical sales data. The buyer states that there is disagreement between finance and purchasing as to what to improve first with the project.

Rather than another cycle of proposing alternatives, hold a short meeting to decide on a single business question and data owner.

A useful meeting invitation would state:

This sets out the first forecasting decision the project should take to support it.

Attendees: commercial sponsor, finance reviewer, and purchasing owner.

Output: Initial scope confirmed, further data required, approved on.

This is an illustrative scenario, not a real customer's result.

Remember after the conversation to record out who does what by when. “Keep discussing internally” is not a next step unless someone owns the discussion and agrees when to respond.

Where LemonLime Supports a Small Data Analytics Consultancy’s Sales Work

LemonLime can augment a small consultancy’s sales and marketing capacity while the founder retains responsibility for proposal negotiations and delivery commitments.

LemonLime continuously studies the company, industry, competitors, and content. It evaluates over 50 lead sources, targeting methods, and buying signals to identify high-potential prospects, then prepares personalized outreach and selects the relevant channel.

The customer receives a relevance-filtered email at 9:00 AM local time. That does not mean every delivery contains every type of work.

For proposal follow-up, keep the boundary clear: do not assume LemonLime knows private scoping discussions or an unanswered proposal’s approval status. No internal-data connection is required to start, and nothing is sent to a prospect or posted publicly unless the customer approves and triggers it.

Use the playbook here for live deal decisions. Consider LemonLime for company-specific customer-growth work that reduces preparation burden without adding another full-time role.

Data Analytics Consultancy Proposal Follow-Up FAQ

How do I follow up on a data analytics proposal without sounding pushy?

Ask the buyer one question about their situation. Such as who owns the approval, is there a known dependency, or has the business priority changed. Explain what their answer will do for you and be sure to keep your message brief. It is perfectly fine to pause your discussion with the buyer in these instances.

How long should I wait before following up on an analytics proposal?

Send follow-up messages on the date you agreed with the buyer. If no date was agreed, send your first follow-up message two to three business days after your initial message. Space out subsequent messages and change their purpose. There is no magic number of days that guarantees a response or a decision.

Should I discount an analytics project when the buyer goes silent?

Silence is not necessarily equivalent to price being an issue. Are budget, timing to spend or perceived value at issue? Even if a smaller engagement is offered, specify the reduced deliverables and confirm that what remains will address a key question of value to business.

What should I send instead of asking whether the buyer read my proposal?

Send a short decision note that makes internal approval easier. State the business question, intended user, proposed fee, scope boundaries, and unresolved decision. Just end the document with one question (e.g. who is the approver for this? or would you like to schedule a call with the data owner for this?). Then only create another very long document if the buyer specifically requests it.

When should I stop following up on an unanswered analytics proposal?

Stop the active sequence of messages after a few purposeful attempts and give up on the opportunity. Record the reason for inactivity and any agreed revisit date. Later messages must have a valid reason to send them, not to repeat identical reminders. Reasons could include a change to a previously agreed timing at the buyer’s request.

Identify one stalled proposal and send one question specifically targeted at one of the blockers. For ongoing customer-growth preparation alongside your consultancy’s sales work, get started with LemonLime.