The PreSales Glossary

aka sales rep, account manager

The salesperson who owns a deal commercially — qualifying the opportunity, navigating procurement, negotiating, and closing. In complex B2B technology sales the AE sells alongside a Sales Engineer: the AE owns the commercial relationship and the close; the SE owns the technical win.

A living document — usually owned by the account executive and updated by the SE — that maps an enterprise customer's stakeholders, pains, current state, target state, sales motion and revenue potential. Distinct from a CRM opportunity record: an account plan covers the *relationship* across many deals, while an opportunity covers a single transaction.

An output in which a large language model states something false with full confidence — citing a capability the product doesn't have, a price a competitor doesn't charge, or a source that doesn't exist. In presales the liability lands on the SE, not the AI, which is why trustworthy systems trace every claim to a source document, attach confidence scores, and route uncertain answers to human review rather than improvising.

aka compete card, competitive brief

A one-page competitive intelligence brief that gives sales reps and SEs the talking points, trap questions, differentiators, and counter-objections needed to win against a specific competitor in a specific deal. Modern battlecards are deal-specific and refresh as competitor pricing, packaging or positioning changes — generic, evergreen battlecards date within weeks.

The formal decision of whether to respond to an RFP at all — based on win probability, fit with the ideal customer profile, strategic value, and the cost of responding (often 80–200 SE hours for an enterprise RFP). A disciplined bid/no-bid process is the single highest-leverage way to raise RFP win rate.

The high-level plan for how the vendor will win a specific RFP — covering pricing posture, partner involvement, win themes, ghost-of-the-competitor positioning, which questions to push back on, and how to influence the buyer's decision criteria before the document is finalised. Decided in a deal review before writing starts.

An internal advocate at the prospect organisation — typically a hands-on user or director-level stakeholder — who actively wants the vendor's solution and pushes the deal forward inside the buyer's company. Without a champion, a B2B deal stalls in procurement; with two champions, slippage drops dramatically. Identifying and developing a champion is a core MEDDIC element.

A vendor invited into an evaluation not to win, but to fill the comparison column that procurement requires — the buyer already has a preferred solution. Recognising column-fodder signals early (no access to the economic buyer, requirements written around a rival's feature set, compressed timelines) is a core part of a disciplined bid/no-bid process.

The systematic collection and analysis of public and internal information about competitors — their products, pricing, sales tactics, weaknesses and wins — used to position your own offering more effectively in active deals. Modern CI sources include G2 reviews, customer interviews, win-loss debriefs, public filings, and product trial data.

A rating an AI system attaches to each of its own outputs indicating how well-grounded the answer is in source material. In RFP analysis, every requirement match is scored (e.g. full match, partial match, gap) with a confidence level; low-confidence answers are flagged for human review by default, so SE attention goes where the risk actually is.

A consolidated, deal-relevant view of a prospect or customer — including industry context, financial health, strategic priorities, key stakeholders, technology stack and history with the vendor — assembled so the seller arrives at every meeting better-informed than the buyer expects.

A cross-functional review function — pricing, legal, finance, sales operations and product — that approves non-standard deals (custom discounts, bespoke terms, complex multi-product configurations) before they reach the customer. A maturing sales org spins up a deal desk once exception requests become a daily occurrence.

A specific, defensible capability or attribute of the vendor's offering that competitors cannot match — used as the foundation of positioning, demos, and proposal narratives. A real differentiator survives the question "and what's stopping the other vendor from doing this in six months?"

An early sales meeting — typically the first or second — where the seller asks structured questions to uncover the prospect's pains, decision criteria, budget, timeline, stakeholders and current solution. A good discovery call ends with the seller knowing whether the deal is worth pursuing.

aka ghosting the competition

Positioning your strengths so they implicitly expose a competitor's weakness — without ever naming the competitor. Ghosting shows up in RFP answers, demos, and proposals as deliberate emphasis on capabilities you know the rival can't match, planting evaluation criteria that favour you. A core element of bid strategy and battlecards.

aka HITL

An AI workflow design in which a person validates and refines machine-generated output before it takes effect — the AI drafts, the human decides. In presales this is the difference between an assistant and a liability: AI-generated RFP answers, battlecards and briefs are reviewed by an SE before anything reaches a prospect, and the corrections feed back into the knowledge base.

The specific type of company a vendor sells to most effectively — defined by sector, company size, buying roles, and the pains the product solves best. PreSales uses the ICP in bid/no-bid decisions: an RFP from outside the ICP costs the same SE hours with a fraction of the win probability.

Knowledge that belongs to the organisation rather than to individuals: captured as a by-product of doing the work, searchable when the next deal needs it, and intact after any single person leaves. The deliberate opposite of tribal knowledge — and the property that lets a new SE ramp on the team's accumulated history instead of shadowing whoever has spare time.

A searchable repository of approved product information, RFP answers, security questionnaires, demo scripts and competitive intel that SEs draw from to respond accurately and consistently across deals. Quality is a function of how often it's updated, not how much it contains.

The percentage of presales responses drawn from existing institutional knowledge versus created from scratch. A low reuse rate means the team keeps re-answering questions the organisation has already answered — compounding waste — and is the leading indicator that knowledge is still tribal rather than institutional.

A go-to-market motion where the vendor lands a small initial contract — one team, one workflow — then grows the account through seats, tiers, and use cases. PreSales matters twice: the technical win earns the land, and the documented value (POC results, win/loss evidence) fuels the expand.

A B2B sales qualification framework: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion — extended in MEDDPICC with Paper Process and Competition. Forces the deal team to validate each element before forecasting a deal as committed.

A jointly-owned document — built collaboratively with the prospect — that lists every step, owner and date between the current sales stage and a signed contract: legal review, security review, procurement, internal approvals, contract signature. Reduces slipped close dates and surfaces stalled deals early.

The skill and content used to address concerns a prospect raises during the sales cycle — price, security, integration, vendor risk, switching cost — without weakening the seller's position. The best objection handlers reframe the objection rather than fight it.

A limited production deployment — usually one team or one workflow — that runs for a defined period to validate the solution in real conditions before a full rollout. Different from a POC: a pilot is in production with real users; a POC is an evaluation against test data.

Of the proof-of-concept projects a team runs, the share that result in closed deals. A low ratio usually means POCs are being granted as a default concession rather than earned through qualification — consuming weeks of SE engineering time on deals that were never funded or never winnable. Most presales leaders have never calculated theirs.

aka Sales Engineering, Solutions Consulting

The function within a B2B sales organisation that handles all technical work before a contract is signed: discovery, demos, POCs, RFP responses, technical objection handling, and the technical win. Sits between Sales and Product, reports to either the CRO or the Head of PreSales.

The win rate on deals where presales was meaningfully engaged, compared against deals where it wasn't. Unlike overall win rate, it isolates the function's contribution from everything else in the funnel — making it the single strongest quantitative argument for presales investment.

The function that supports the PreSales organisation operationally — tooling, demo environments, RFP libraries, SE assignment workflows, knowledge management and analytics. Reports to the head of PreSales or RevOps. Emerges as a standalone role around 25-30 SEs.

A live or recorded walkthrough of a software product, tailored to the prospect's specific use cases and pains uncovered in discovery, typically delivered by a Sales Engineer. The best demos show the prospect's workflow being completed — not the vendor's feature list being toured.

A time-boxed evaluation in which the vendor's product is set up against the prospect's real data and use case to prove it can meet defined success criteria. A well-run POC has written success criteria, a defined duration, a named owner on each side, and a clear next-step on close.

A short, early-stage document a buyer issues to many vendors to gather general capability information before narrowing the field to a few for a formal RFP. Typically 10-30 questions. Responding to an RFI is cheap; declining is sometimes the right call.

A formal document a buyer issues to vendors asking for a detailed proposal — features, pricing, compliance, support, references — to evaluate which solution to purchase. Enterprise RFPs commonly run 100–300 pages and cost the vendor 80–200 SE hours to answer. The RFP is the largest single artefact the PreSales function produces.

The formal document the vendor returns to the buyer in answer to an RFP — typically hundreds of pages, structured to the buyer's template, combining technical answers, commercial terms, references and supporting materials. Quality and on-time delivery are both scored by procurement.

A document asking vendors for a price quote on a clearly-defined good or service. Used when the buyer already knows what they want and is comparing on price — typically commodity purchases, not strategic software.

The umbrella term for any request-for-X document a buyer issues during procurement, including RFP, RFI, RFQ, RFT (tender), and DDQ (due diligence questionnaire). Used inside the PreSales team to refer collectively to "the documents we have to respond to."

The elapsed time and sequence of stages from first contact with a prospect to a signed contract. In B2B technology sales the cycle commonly runs months — and roughly 80% of it is the technical-win phase: validation, RFPs, demos, POCs, security review. Shortening the cycle is usually a matter of accelerating that middle, not closing harder.

The phase of the sales cycle dedicated to understanding the prospect's situation, problems, implications and needed outcomes — before any solution presentation. Frameworks include SPIN, Sandler, GAP and Command of the Message. The single largest determinant of close rate.

A technical role that supports the sales team by leading product demos, scoping POCs, answering technical questions, writing RFP responses and translating customer requirements into solution architectures. Also called Solutions Consultant, Solutions Engineer, or PreSales Consultant.

The transfer of deal context from the account executive to the SE before a technical engagement: what discovery revealed, who the stakeholders are, the competitive landscape for this specific deal, and what has already been promised. When the handoff is a Slack message and a calendar invite, SEs walk in blind and deals die from handoff gaps rather than product gaps.

The process of allocating Sales Engineer hours across active deals based on deal value, win probability, technical complexity and SE skill fit. SE capacity is typically the bottleneck on enterprise-segment growth — every committed deal claims 40-120 SE hours, and there are only ~1,800 productive hours in an SE's year.

aka onboarding time-to-productivity

How long a newly hired sales engineer takes to reach full productivity — commonly cited at six to nine months. Long ramp times are usually a knowledge-access problem rather than a training problem: the organisation already possesses what the new hire needs, but it lives in individual heads instead of a searchable institutional base.

aka vendor security assessment, DDQ

A buyer-issued document — often hundreds of questions — probing a vendor's security and compliance posture: SOC 2 controls, ISO 27001, data residency, encryption, processor obligations under GDPR. Increasingly mapped to contractual representations, which turns inconsistent answers into legal exposure. Best managed from a canonical, source-traced answer base rather than last quarter's spreadsheet.

A senior technical role that designs the end-to-end solution architecture for a customer — typically more strategic than a Sales Engineer, often involved in complex enterprise deals and post-sale implementation. The "engineer of last resort" for hard customer problems.

A structured picture of the people involved in a buying decision: who champions, who blocks, who holds budget, who evaluates technically, and what each cares about. SEs use it to pitch at the right altitude — a deep-dive aimed at the wrong stakeholder loses the room in minutes.

A structured assessment of Strengths, Weaknesses, Opportunities, and Threats. In presales it is most useful at deal level — your position against the specific competitor in front of the specific buyer — feeding bid strategy and battlecards. Generic company-level SWOTs date quickly and persuade no one.

aka technical selling

The discipline of selling complex technology products where the buyer must be convinced the solution works — technically, in their environment, against their constraints — before any commercial close is possible. It covers the people (sales engineers, solution architects, and the account executives selling alongside them), the activities, and the process between first discovery and the technical win.

What technical sales work includes:

• Technical discovery — mapping the prospect's environment, stack, constraints, and success criteria
• Demos and proofs of concept — showing the product working against the buyer's real use case
• RFP, RFI, and security questionnaire responses — often hundreds of structured answers per deal
• Competitive positioning — battlecards, trap questions, and deal-level SWOT against named rivals
• Solution architecture — integration design, sizing, and deployment planning
• Multi-stakeholder persuasion — translating the same solution for DevOps, security, finance, and the executive sponsor

In B2B technology deals, roughly 80% of the sales cycle is spent in this technical-win phase — yet it is the least-tooled part of the revenue stack. CRMs track the pipeline and enablement platforms serve marketing content, while the technical middle traditionally runs on documents, spreadsheets, and the memory of the most senior engineer. Closing that gap is the premise of the technical sales operating system category.

A single platform for running the technical side of B2B selling — the category WinIQ builds in. Where a CRM is the system of record for pipeline, a technical sales operating system is the system of intelligence for the technical-win phase: RFP analysis, battlecards, customer intelligence, demo prep, and team operations on one knowledge layer, so every deliverable feeds the next deal instead of evaporating.

The buyer-side process of confirming a proposed solution actually fits: architecture review, security assessment, POC success criteria, integration checks, reference calls. The mirror image of the vendor's technical win — when validation completes in the vendor's favour, the technical win has happened.

The moment in a sales cycle when the prospect's technical evaluators agree the vendor's solution meets their requirements — typically a precondition to the commercial close and the SE's primary success metric. A confirmed technical win lifts deal close-rate by 2–3× in benchmarks.

The elapsed time from a technical question or RFP arriving to a substantive answer going back to the prospect. Speed is a trust signal: buyers read response time as a preview of what working with the vendor will be like — in both directions.

A question designed for the prospect to ask the competitor — phrased so that an honest answer exposes the competitor's weakness on a capability the seller is strong in. A core element of competitive battlecards. Good trap questions feel reasonable to the buyer, not loaded.

Critical know-how that lives only in individual heads: edge-case product behaviour, competitor-specific positioning, compliance nuance, the political read on a recurring objection. Invisible while its holders stay, lost the day they leave. Converting it into institutional knowledge — captured, searchable, compounding — is the core knowledge-ops problem in presales.

A structured review of closed deals — whether the vendor won or lost — to identify why, surfacing patterns that improve future product, pricing, positioning and execution decisions. Often outsourced to third-party interviewers because buyers are more candid with neutral parties.

The percentage of qualified opportunities that close as wins. Useful only when segmented — by competitor, by deal source, by presales engagement (see PreSales-Influenced Win Rate), by RFP versus non-RFP deals. A single blended win rate hides exactly the patterns a team needs to see.

The 2-4 unifying messages the deal team agrees to reinforce across every proposal section, demo and stakeholder conversation — chosen to map the vendor's strengths onto the buyer's stated decision criteria. The deal-level analogue of brand positioning.