Why Most Proposals Go Silent After Being Sent
Sales professionals who track their proposal-to-close rate frequently discover the same uncomfortable pattern: the call goes well, the prospect seems engaged, the proposal gets sent within 24 hours — and then nothing happens. Follow-up emails get vague replies. The timeline slips. What felt like a near-certain deal becomes a stall that eventually dies without a clear reason.
The most common cause is not price. It is that the proposal did not give the prospect's internal champion the tools to sell it upward. A proposal that reads like a template — company name inserted in the right fields, generic capability statements, pricing as a line item — cannot be circulated internally because it does not answer the questions a decision-maker will ask. The champion receives a document they cannot easily explain to someone who was not on the call, so they either summarise it poorly or do not circulate it at all.
An AI sales proposal agent solves this by building the proposal around the actual sales conversation — the specific challenge discussed, the specific solution proposed, the specific value case made — not a generic framework with the customer name inserted.
The Champion Problem: You Sold to One Person, Multiple People Decide
In most B2B deals above a certain value, the person you had the sales conversation with is not the person who approves the purchase. The champion needs to sell the deal internally — to their manager, their CFO, their technical team, or some combination of all three. Each of those stakeholders has a different concern, and none of them were on your call.
The CFO asks: what does this cost and what do we get for it? Can this be justified? The technical stakeholder asks: how does this work, what does implementation involve, and what could go wrong? The manager asks: is this the right priority right now, and what happens if it does not work?
A proposal that only addresses the champion's perspective fails at the first internal hurdle. A proposal structured for the full buying committee — with an executive summary written for the decision-maker, a scope section written for the technical reviewer, and an ROI section written for the finance stakeholder — survives internal circulation and gets approved.
What a Proposal Needs to Do
A sales proposal has two jobs simultaneously. The first is to confirm, in writing, that you understood the prospect's specific situation and have a credible, specific solution. The second is to give the champion everything they need to sell the deal internally — to stakeholders who have never spoken to you and will form their entire opinion of you from what the document says.
This requires the proposal to: restate the challenge in the prospect's own language, not the vendor's; propose a specific solution with explicit scope and explicit exclusions; present pricing in the context of what it delivers; make the ROI case explicit enough that a finance team can evaluate it; and end with a clear next step and a named decision date. A generic template cannot do any of this. A deal-specific proposal built from the sales conversation can.
What Henry Asks During Intake
Henry leads a structured intake session with six targeted questions: who the proposal is for and their role in the decision, what was discussed in the sales call (the pain the prospect described, their goal, the context that makes this a priority now), what is being proposed and at what investment level, what the implementation or delivery timeline looks like, what proof points or relevant case studies are available, and who else is involved in the decision and what their concerns are likely to be.
These six questions take ten minutes to answer. They surface everything Henry needs to build a proposal the champion can send to their CFO without modification. The specificity of the answers determines the specificity of the proposal — the more precise the input, the more targeted and credible the output.
The Proposal Structure That Gets Approved
Henry follows a structure designed for the buying committee, not just the champion. An executive summary of three sentences covering the problem, the proposed solution, and the expected outcome — written for the decision-maker who reads only this section and makes a judgment from it. The challenge restated in the prospect's own language, demonstrating that you listened and understood their specific situation rather than mapping their problem to your standard pitch.
The proposed solution with explicit scope — and explicit scope exclusions, which prevent misunderstanding later and demonstrate that you have thought about the boundary of what is being agreed. Implementation timeline with milestones. The investment section placed after the value case, not before it. An ROI business case making the return explicit with conservative assumptions the finance team can interrogate. Social proof or relevant case study. Specific next steps with a named decision date — because proposals without a decision date create indefinite stalls.
Pricing That Contextualises Rather Than Apologises
Most proposals present pricing as a line item on page three. This forces the reader to evaluate the number in isolation — without context for what it delivers or what the alternative costs. Henry presents pricing after the ROI section, so the investment is always seen in the context of the return it generates.
A £15,000 project investment reads differently after a paragraph showing it replaces £60,000 of annual manual process than it does as a cold number at the top of a page. A £3,000 monthly SaaS subscription reads differently after demonstrating it saves 12 hours of senior time per week than it does as a line item next to a competitor's £2,500 quote. Context does not sell the price — but it gives the buyer the framing they need to justify it internally.
Speed Matters: Proposals Sent Within 24 Hours Win More
There is a consistent pattern in B2B sales data: proposals sent within 24 hours of the sales call have significantly higher close rates than those sent two to five days later. The reason is simple — the energy of the call is still present, the prospect is still in the decision mindset, and the delay of a late proposal creates doubt about responsiveness and execution quality.
Henry makes same-day or next-day proposals possible. The intake session takes ten minutes. The proposal is produced in one session. A sales professional who finishes a discovery call at midday can have a proposal in the prospect's inbox by end of day — without the hours of manual drafting that proposal writing typically requires.
How to Start a Proposal Session with Henry
Load the Henry skill file into Claude Projects. Paste the activation prompt after the call while the conversation is still fresh. Henry asks his six intake questions one at a time. Answer specifically — the more detail you provide about what the prospect actually said, the more the proposal will sound like it was written for them rather than adapted from a template. Henry works with Claude, ChatGPT, or any AI chat that accepts system prompts.
The agent behind this guide. Henry turns your sales call into a deal-specific proposal built for the whole buying committee — executive summary, scoped solution, ROI case, and a dated next step.