Your proposal makes sense. But who is willing to sign their name to it?

A supplier can spend twenty hours improving a proposal and still answer the wrong question. The document describes the problem, the approach, the timeline and the price. Perhaps it even includes references. Yet signing means the customer must change processes, allocate time, possibly stop using familiar suppliers and explain to leadership why the decision was justified. That is not the same task as deciding whether a PDF is well structured.

Foundational research treats organisational purchasing as a decision process embedded in individual, social, economic and situational influences. Webster and Wind outlined that perspective in 1972. [1] Johnston and Bonoma later examined the structure and interactions of industrial buying centres for equipment and service purchases. [2] Their work explains why approval from one person is not the same as organisational authorisation. It does not identify which stakeholder is delaying your deal. That requires investigation within the actual buying situation.

Consider an operations director who believes in a new platform. A team manager thinks about the extra workload during migration. Finance wants to see costs beyond the supplier invoice. IT needs clarity about security, integration and supplier dependence. Procurement must demonstrate that the organisation followed its purchasing procedure. None of these concerns is necessarily hidden or irrational. They may all be legitimate at the same time, even if everyone likes the product.

The first shift is therefore straightforward. Do not ask only why was the proposal not signed? Ask what change must this organisation approve, resource and carry out before it can sign? The proposal is one document within that process, not a substitute for it. This perspective reduces the temptation to obsess over follow-up frequency and encourages examination of the genuine conditions for a decision.

'Doubt' sounds like one obstacle. In reality, the same proposal may activate quite different associations. Some are consciously expressed; others may be difficult to articulate. Not all are problems the salesperson can or should fix. The following categories are a working framework, not seven scientifically established universal buying switches.

The phrase 'we need to discuss this internally' could describe any of these situations. It is irresponsible to diagnose a hidden psychological cause from that sentence. A better response asks what review is needed, who is involved, which questions must be answered and when the result is expected. When the buyer does not yet know, the immediate job is clarifying a process, not increasing persuasive pressure.

A risk association can also be accurate. If the supplier genuinely lacks capacity for implementation, an IT manager's concern should not be re-framed away with attractive wording. The risk must be reduced, reflected in the contract or accepted openly. A useful association map identifies weaknesses in the offer as well as opportunities to communicate it better.

Sales data is essential. You can see proposal volume, pipeline value, document views and eventual signatures. Yet the same observable behaviour can have different causes. A long decision cycle might reflect uncertainty, holiday schedules, a mandatory purchasing procedure or low priority. Document-view data may not even capture how a PDF has been forwarded and discussed internally.

Mistaking signals for causes leads to inappropriate action. The salesperson calls more often, cuts the price or sends another long case study. Those steps may sometimes help, but they can also increase friction. The right question is what the observation supports and which alternative explanations remain plausible.

A mature CRM should therefore record more than 'proposal sent'. Is the need recognised? Is there an economic justification? Who holds approval rights? Which conditions remain outstanding? What is the agreed next action, who owns it and how certain is the date? 'No response' is a communication status, not a neurological diagnosis. It is not a licence to contact people repeatedly against their wishes.

A conversation can feel very positive without producing any concrete next step. It is tempting to interpret courtesy and intellectual agreement as buying readiness. But a buyer can sincerely appreciate your work, like the salesperson and still see no reason to introduce the change. Or they may not have authority to approve it.

Commitment and trust are distinct constructs in relationship marketing. Morgan and Hunt describe both as important variables in relationships, not as proof that a pleasant meeting creates a contract. [4] Doney and Cannon investigated how industrial buyers develop trust in a supplier organisation and its salesperson. [3] Their findings support distinguishing confidence in the supplier from a personal relationship with the account manager. They do not provide a magic technique for extracting a signature.

A useful question after positive feedback is: 'What would have to happen within your organisation for this proposal to receive final approval?' It is less dramatic than a closing trick, but it reveals the distance between enthusiasm and decision-making. Then you can work together on evidence, timing and whether the process can reasonably be completed.

Ask what an unsuccessful implementation would mean as well. Not to intimidate anyone, but to make risk explicit. Sometimes the main concern is not whether the product works. It is whether the team will have enough time to implement and use it properly. A fifth demo might add less value than an honest discussion about staffing and delivery.

A B2B purchase often has three different bills. The first is the supplier's price. The second is the customer's internal investment in learning, integration and change. The third is the consequence if the project fails to deliver the intended result. The first bill is often clearly priced. The second and third may remain buried in assumptions.

Kahneman and Tversky's work on decision-making under risk provides an influential account of how uncertain outcomes are evaluated relative to reference points. [9] Samuelson and Zeckhauser studied a tendency to retain existing choices. [5] Neither paper explains any particular stalled B2B contract. Together they provide reasons to investigate the alternative of doing nothing rather than treating it as an absence of choice.

Imagine a company still using a dated system. Employees know its weaknesses and have learned how to work around them. A replacement may offer measurable improvements but also introduce unfamiliar consequences. The useful question is not simply 'are we better?' It is 'are the expected improvements credible enough, given the costs and risks of switching?'

Responsibility complicates the picture. Someone expected to defend a decision to colleagues, executives or an audit committee may evaluate an option differently from someone focused on functionality. Tetlock's work on accountability considers how the social context of having to justify judgments can shape choices. [6] It is a theoretical starting point, not proof that every procurement manager fears losing face. Investigate the person's real responsibilities and the criteria they will face.

A seller who genuinely wants to reduce risk should therefore surface implementation implications, assumptions in the business case, exit conditions, guarantees, client-side resources and realistic failure scenarios. Verbal reassurance is of limited use when the contract contradicts it. Sometimes the responsible answer is that the proposal is not yet sufficiently robust to sign.

Sales presentations often describe the current process as a collection of problems. That is understandable: the supplier wants to sell change. Yet the existing system also has meaning. It is familiar. People know its workarounds. The organisation knows whom to call when trouble arises. Operational mistakes have already been experienced and managed. 'Old' can therefore signify 'under control', not only 'inefficient'.

Research on status quo bias shows that existing options can receive preferential treatment in some decision contexts. [5] But there is an important practical correction: staying with the existing supplier can be objectively sensible. Change consumes resources and may introduce costs that exceed expected benefits. A fair proposal compares two realistic futures, with assumptions and uncertainty visible, rather than comparing an idealised future with a deliberately unattractive present.

Put the scenarios side by side. What happens if the customer continues for twelve months with the current process? What happens if the proposal is adopted? Show known and variable costs, required people, effects on service, contractual dependencies and unresolved questions. The purpose is not to make the current choice look foolish. It is to provide a comparison that the organisation can defend.

Trust may also operate at more than one level. The customer may trust the account manager personally but question the firm's ability to deliver. Or trust the brand but doubt the proposed implementation partner. Doney and Cannon's research provides a reason to keep those objects of trust distinct. [3] A single 'trust score' would obscure where proof is needed.

The software supplier, company, people, figures, reactions and proposed changes in this example are entirely fictional. This is not Neurofactor customer research, not a real won or lost contract, and there are no measured association scores.

A medium-sized logistics company receives a proposal for a planning and reporting platform. In this illustration, the annual licence is EUR 64,000 and the supplier proposes a twelve-week implementation. The operations director knows that planning is inefficient and is impressed by the demo. The proposal contains a feature overview, schedule, general implementation phase and a financial benefit calculated from assumptions. The meeting ends positively. Three weeks later, no contract has been signed.

The supplier initially labels the delay as price resistance and considers a ten percent discount. In a hypothetical follow-up, five different decision questions emerge. The operations director expects time savings but does not know who will lead implementation. The team manager remembers an earlier migration that required weekend work. Finance cannot validate the projected saving because internal labour hours are missing. IT asks about data ownership and integration. Procurement is unable to approve the multi-year agreement without standard checks.

The proposal was not necessarily bad. It was mainly written around the benefits of the solution rather than the consequences of the decision. A brighter 'sign now' button cannot repair that difference. It would also be wrong to dismiss these internal concerns as irrational or unconscious. Each requires a specific, verifiable response.

Three possible improvements are considered. A - Delivery: realistic phases, internal effort by team, migration and fallback plan. B - Accountability: a checkable business case containing assumptions, uncertainty, total costs and alternatives. C - Approval path: a view of formal reviews, responsible owners and expected inputs. These are not tested winning versions. The customer may need several elements, different measures, or may conclude that implementation is currently the wrong decision.

Suppose the customer concludes that sufficient capacity will not be available this quarter. Another reference case is unlikely to be the decisive response. A later start may be better than manufactured urgency. A limited pilot is useful only when it is genuinely feasible and the scope, obligations, costs and exit conditions are clear. Calling a trial 'risk-free' while hiding real commitments would undermine trust.

The learning lies in the questions, not in an invented success story. What does the proposal mean to the person who approves it, the person who executes it and the person who accounts for the outcome? What proof would allow them to act responsibly? The actual answer cannot be derived from a job title or this fictional scenario. It requires real interviews, evidence and an accurate understanding of the customer's process.

Step 1 - Define the business problem precisely. Are too few proposals accepted, is internal approval slow, or do signed contracts repeatedly stall after closing? Separate proposal volume, qualification, contract value, decision time, realised value and unintended consequences. A higher signed amount is not automatically better when customers cannot implement. Define the decision point and your primary measure before starting.

Step 2 - Check commercial and operational constraints. Verify available budget, tender rules, validity periods, signing authority, the business case, supplier delivery capacity, customer resources, contract dependencies and competitive suitability. This audit matters more than a psychological interpretation while demonstrable obstacles remain. A company forbidden to sign during a spending freeze does not need a hidden association to explain the delay.

Step 3 - Map the actual approval process. Identify who experiences the problem, who selects the vendor, who owns the budget, who assesses risk, who signs and who will make implementation work. Ask which individuals are truly involved, rather than relying on a generic decision-making-unit chart. Research on buying centres supports investigating these distinctions. [1][2] Respect confidential internal information; do not attempt to compile inappropriate dossiers on employees.

Step 4 - Collect the buyer's own account before writing more persuasive copy. Ask separately what appeals, what is not yet defensible and what could go wrong. Invite stakeholders to describe the evidence they lack. Distinguish directly stated reasons, documented processes and hypotheses held by the sales team. Make room for the possibility that the offer genuinely fails to deliver enough value.

Step 5 - Examine associations when they are relevant. Explore spontaneous meanings attached to the supplier, offer, implementation and decision moment. 'Control', 'more work', 'dependency', 'professional', 'safe' and 'hassle' may warrant investigation. Carefully developed explicit or implicit association tasks can be useful for suitable groups, with attention to stimulus design, validity, reliability and interpretation. Do not treat one person's reaction time as a measure of purchasing intent.

Step 6 - Test what the proposal actually communicates. Give a realistic task: 'You have to recommend this proposal to your internal committee. Which three points can you defend, and which remain unsupported?' Observe whether people can locate and accurately describe costs, phases, ownership and risks. Use document tasks, interviews or eye tracking when visual findability is a material question. Looking at a page does not prove that its argument was understood.

Step 7 - State a testable change hypothesis. For example: 'When the implementation section shows internal hours per department and a realistic fallback option, stakeholders will be better able to judge feasibility.' Specify the proposed mechanism, factual input required, responsible owner and behavioural outcome. If nobody knows the required hours, the next action is estimating them, not designing a more reassuring graphic.

Step 8 - Compare alternatives and real decisions. Let people evaluate different versions without misleading promises. Where enough comparable live opportunities exist, use a suitable experimental or quasi-experimental comparison with prespecified outcomes. Account for industry, deal size, seller, cycle length, competition and seasonality. A shift from two to three signed deals in a tiny sample should not be announced as a universal causal effect.

Step 9 - Check whether the signature led to healthy delivery. After contracting, verify that agreed resources exist, onboarding succeeds, major assumptions remain realistic and margins and service obligations are sustainable. Include deals appropriately declined or delayed where relevant. A worthwhile intervention may prevent a bad agreement and protect trust rather than increase closing pressure.

This protocol is consistent with Neurofactor's research approach, which selects methods according to the behavioural question. A method stack is not an excuse to expose a prospect to as many measurements as possible. It should reduce uncertainty with evidence that can actually distinguish competing explanations.

A label such as 'difficult' is too vague to improve a proposal. Difficult for whom? During which task? Compared with what? And with which consequences? An association-to-evidence matrix makes those questions explicit. The goal is not only to identify a negative meaning, but also to determine whether the concern is justified and what can be changed.

The matrix requires genuine evidence. If the supplier cannot demonstrate adequate support capacity, the answer is not simply to write a more reassuring sentence. Research should reveal that weakness. A useful finding might lead to a better implementation plan, amended terms or a responsible no-go. A negative finding is still valuable.

The dominant question may also change over time. At the first meeting, 'interesting' and 'innovative' might be enough to justify a demo. At proposal stage, 'reliable', 'feasible', 'defensible' and 'aligned with our priorities' may require stronger proof. This is a hypothesis about evolving decision tasks, not a universal sequence of neurological buying stages.

1. Start with the decision, not your service catalogue. State what the customer needs to decide, why the issue matters and what outcome can reasonably be achieved. Explain which situations the offer does and does not suit. Twenty features without a clear decision question create length, not necessarily usefulness.

2. Include the option of not changing. Describe the consequences of continuing with the current approach, including known costs and risks. Avoid inflated 'cost of doing nothing' estimates. If the current process is adequate for another year, that belongs in the comparison. A real alternative makes the business case more defensible.

3. Give every assumption an owner. An attractive savings calculation is not evidence if the client data are missing. Document volumes, labour costs, error rates, adoption assumptions, provenance and uncertainty. This helps the person who must present the business case internally. If the forecast changes materially with one assumption, show that sensitivity rather than concealing it.

4. Describe the work required from the customer. Implementation may demand staff time, training, integrations, decisions and changes in routine. Klein and Sorra's implementation model considers organisational context and alignment with user values. [7] It does not guarantee adoption, but it provides a reason to treat implementation conditions as part of the purchasing decision.

5. Substantiate trust at the relevant level. A reference praising a pleasant account manager cannot establish security compliance or financial return. Match each meaningful claim to evidence that genuinely supports it. Secure permission for customer names, images, quotations and case figures before using them.

6. Bring formal requirements forward. Ask early about procurement, contract review, information security, privacy requirements and supplier approval. Do not encourage a sponsor to bypass colleagues whose responsibility is to protect the organisation. Shortcuts can produce a signature that cannot legally or operationally stand.

7. Compare risks consistently. Describe the risks of changing and staying, including likelihood, impact and safeguards where adequate data exist. Do not invent precision. Calling a complex B2B implementation 'risk-free' undermines the credibility of the very promise you want buyers to trust.

8. Offer a feasible next step. A technical workshop, structured proof of concept or internal financial review can help when it has a defined objective, available capacity and reasonable conditions. A pilot is not a psychological bypass. Scope, customer data, costs, evaluation and exit arrangements must be genuine.

9. Agree on a concrete decision step without false urgency. Who will review which item, by when, and what happens afterwards? Research on implementation intentions shows that specific plans can support the translation of intentions into action. [8] That is not a finding that adding a date increases B2B signature rates. The next step is meaningful only when the customer genuinely agrees and can carry it out.

10. Say when the customer should not sign. Make relevant exclusions, dependencies, technical limitations and unsuitable scenarios explicit. A supplier who helps a buyer avoid a poor fit gives trust a factual basis. That is better than celebrating a contract that collapses during onboarding.

These choices do not guarantee higher revenue. A standardised, low-risk service and a multi-year implementation with several approval layers will require different evidence. Diagnose the situation, then choose the two or three changes that might plausibly matter most and test them rather than applying a generic closing formula.

A research programme begins with a business question. What happens between 'proposal considered' and 'decision made'? Which parts relate to funding, formal rules, uncertainty and the meaning of the offer? Methods come afterwards. An association test without a well-defined decision context might generate interesting words without leading to a useful commercial decision.

Direct interviews help uncover stated needs, buying criteria, process stages and doubts. Speaking with more than one relevant stakeholder can reveal differences without pretending every CFO or buyer is alike. Experience, hierarchy and social desirability can affect what people say. A spoken objection may be genuine, strategic or underdeveloped; do not guess which without further evidence.

Association research can examine meanings attached to the supplier, contract, price and implementation. A suitably validated implicit task may investigate relative associations, but its scores are not individual purchase-intention diagnoses, and they do not replace proof of authority or budget. Stimuli, practice effects, order, reliability, group comparability and representativeness must be considered in the research design.

Profiling and buying-journey analysis can investigate patterns in situations where decisions stall, such as types of purchase, implementation demands and stages of internal review. This is more useful than assigning simplistic personality traits based on job titles. Small or skewed samples warrant hypothesis language, not confident statements about entire buyer categories.

Eye tracking can be considered when an actual proposal or portal raises a visual-findability question. It can indicate what people look at or skip, not whether they trust the seller. EEG can explore time-related brain responses under appropriately designed experimental conditions. It cannot produce a universal 'this person will sign' signal. In many proposal situations, process interviews, contract checks and an improved financial model provide more actionable evidence first. A sophisticated instrument is not automatically a better research choice.

Neurofactor's sales and frictionless-buying approach focuses on what makes buying difficult, risky or unclear. Applied to proposals, that means distinguishing expressed reasons, associations and observable buying behaviour. Collect no more personal information than required, and protect confidential internal perspectives.

A useful follow-up is not a sequence of increasingly urgent reminders. It helps determine whether another step would create value. If a buyer says 'we are still reviewing it', ask what is being reviewed, what information is needed and whether the initial timeline remains realistic. Allow people to say no. A trustworthy supplier should be able to accept a clear rejection.

Questions such as 'Which elements have already been approved, and which are still open?' or 'Who needs to review feasibility?' or 'Which consequence of this decision is hardest to explain internally?' can surface the real work. Their value disappears if every answer is immediately countered with a standard objection-handling script. Understand first; then provide proof or change the offer.

Sometimes no-bid or no-go is the most professional outcome. When the customer does not have a problem your solution solves, funding is absent or purchasing law requires another route, recognise that reality. A process with clear criteria for stopping saves both organisations time. A lost proposal may contain useful learning without being reclassified as evidence of a hidden association.

There are at least five serious alternatives to an associative barrier. The offer is not competitive. Funds are unavailable. The right people have no capacity. The contract cannot legally be agreed. Or the project is genuinely less important than other priorities. These situations may coexist with associations, but business facts should be checked first.

Price may also be the actual obstacle. The buyer can understand the value perfectly well and still be unable to afford it. A lower price can make sense when it produces a sound deal for both parties. Yet a discount cannot create implementation capacity, decision authority or evidence that does not exist. Without knowing whether the concern relates to cost, value or financing, a pricing change is largely speculation.

Avoid universal neuroscientific claims as well. Findings about risky choices do not imply that a brain scan can identify which member of a buying group will block a contract. Studies of the status quo concern particular decision settings. [5] Research on trust and buying centres uses particular samples and methods. [1][2][3] Translating those ideas into a new sales context always requires a hypothesis and a relevant test.

Improving proposal acceptance may be commercially valuable. But without controlling for lead quality, margin, deliverability and customer outcomes, the metric may mislead. Heavy discounts can increase signatures while reducing sustainable value. Overpromising implementation can convert now and trigger conflict later.

Choose a primary behavioural outcome aligned with the business goal, such as the share of qualified, financially appropriate proposals approved within a meaningful decision window. Track time to decision, reasons for postponement or rejection, relevant approvals, realised gross margin, start-date adherence, implementation deviation and customer experience after signing. Separate observable facts from interpretations of motives.

Compare like with like. A EUR 5,000 service agreement and a EUR 500,000 implementation programme do not have identical approval paths. Sales experience, industry, competition, contract length and economic conditions can also affect results. Experiment responsibly where feasible, but avoid drawing sweeping conclusions from tiny subgroups. Report sample sizes, observation windows, uncertainty and selection criteria.

Finally, determine whether your proposed mechanism actually improved. Could the buyer identify risks more clearly? Did stakeholders understand the implementation workload? Was the approval route known earlier? Were unsuitable deals identified sooner? And did those changes lead to healthier agreements, or to earlier, justified decisions not to proceed? Both can indicate a better buying process. Not every signature is worth winning.

A proposal can be compelling, correctly priced and well presented. Yet signing may make a manager accountable for new risk, impose more work on a team or require change at the wrong moment. The problem is not necessarily the copy or the closing technique. The important question is which associations, conditions and internal consequences remain insufficiently understood or supported.

Move from 'what does the prospect think of our offer?' to 'what must this organisation know and be capable of doing to decide responsibly?' Examine the buying process, real alternatives, evidence, implementation and differences between stakeholders. Use association research when meaning and resistance remain unclear. Then test improvements against decisions that are actually approved and implemented.

The best proposal is not the one that asks most forcefully for a signature. It helps the right customer make a sound decision, including the decision not to sign yet.

Evidence note: These studies support specific theoretical mechanisms and context-dependent observations. They do not demonstrate that a particular proposal, discount, pilot or Neurofactor measurement will increase signing rates in any given organisation.

• Neurofactor research methods - select the method stack based on the buying and behavioural question.
• Sales and frictionless buying - mental friction, buying behaviour and relevant evidence.
• Associations in sales: why interested customers still do not buy
• Why do customers not buy even when they see the value?
• Why a CFO, procurement and end users judge the same offer differently
• Procurement is not just the department that pushes prices down