Email writing · Practical guide

Post-discovery follow-up: validate the problem before proposing a solution

Ask the recipient to confirm the problem and constraints you heard. A discovery recap should make misunderstandings visible before a proposal is built on them.

Reviewed · Examples are illustrative

Who this helps: Writers preparing specific sales follow-ups, trigger-based outreach and useful offers.

Define the decision

Discovery notes often mix direct statements with the seller's interpretation. Label those differences. A buyer saying that reporting takes time does not necessarily mean they want to replace the current system, have budget or consider the issue urgent. Preserve what is known and identify what still needs validation.

Work through the procedure

  1. Separate direct facts from your hypotheses about consequences and urgency.
  2. Summarize the present process, the desired decision and the constraints the recipient mentioned.
  3. Identify the most important unanswered question rather than sending an exhaustive questionnaire.
  4. Offer the next action agreed on the call and invite correction of the summary before investing in a larger proposal.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

I heard that your team manually reconciles regional reports before the weekly review. The priority is consistent definitions, while keeping the existing data sources.
I have not yet confirmed who owns changes to those definitions.
Is that a fair summary? If so, I will prepare the example mapping we discussed.

Read the result

The recap confirms scope and explicitly leaves ownership unresolved. That is better than presenting a complete buying process the prospect never described. If the recipient corrects the summary, update the record before drafting a solution. A useful correction is progress, even when it narrows the opportunity.

Check before moving on

  1. Keep the recipient's constraints in the proposal brief.
  2. Do not convert exploratory interest into a committed timeline.
  3. Check that the promised next artifact addresses the validated problem.

Limits and next action

This example is a manual sales communication, not a claim that Zintara records calls or extracts meeting notes. Use approved notes and review any AI-generated summary against them. Avoid including private information irrelevant to the agreed next step.

Source: Zintara writing assistance context; examples are original editorial material

Source references

Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.

Related guides

Explore the Zintara workflow