Presales Win Blueprint

Problem

Presales work often breaks down when requirements are vague, competitor positioning is shallow, and delivery boundaries are weak. A customer asks for a feature, and the response becomes a module list. A POC starts without clear acceptance criteria, turning into an open-ended pilot. A bid file repeats generic industry claims, while commercial negotiation keeps drifting on price, scope, and delivery promises. This skill targets that stage: from initial qualification to commercial closing, not generic sales talk.

How It Works

The skill compresses presales context into structured parameters such as --industry, --stage, --competitors, --budget, --decision-role, and --signals. From that context, it generates stage-specific playbooks instead of a static checklist: in the requirements phase it reframes feature requests into business problems; in the POC phase it defines acceptance criteria and boundaries; in bidding it turns industry understanding into scoring responses; in commercial negotiation it constrains price, scope, and delivery commitments. The output usually includes stage tactics, industry focus areas, competitor strategy, risk warnings, proposal self-checks, and next actions.

Boundaries

This skill is positioned as industry insight and practical playbooks, useful for early proposal strategy and internal review. It should not replace real customer research, compliance review, pricing approval, or delivery assessment. Where local industry rules, legal clauses, or procurement scoring details matter, the actual project materials remain the source of truth.