competitive-poc-rfp-plan
From the author
Plan a head-to-head evaluation - a POC, POV, pilot, bake-off, or RFP response - against a competitor or competitive set, with the buyer's requirements mapped, table stakes separated from the criteria that will decide it, each differentiator tied to a proof event, the questions that expose real trade-offs, where the competitor is stronger, and the conditions under which the team should not proceed. Use for "we're going into a POC against X", "help us shape the RFP response", "what should we prove in the POV", "how do we set up the evaluation around what matters", and scoring or requirement matrices. Not for general deal prep, one live objection, or a reusable battlecard.
Install
npx skills add LMTYdotcom/skills --skill competitive-poc-rfp-plan -a claude-code
Installs to .claude/skills/competitive-poc-rfp-plan/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- sales-engineeralirezarezvani/claude-skillsAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.Planning★ 28.7K
- competitive-deal-prepLMTYdotcom/skillsPrepare an account team for one specific competitive opportunity - the deal state, who they are actually up against, what the buyer said matters in their own words, the three questions that decide the next meeting, proof that fits this account, and the risks and unknowns - from current market truth plus CRM, call, and account context. Use for "prep me for this deal", "we're up against Northwind at Globex", "I have a call with this account tomorrow", "what should the team know before the next meeting", and any request about one named account or opportunity. Not for one live objection on its own, a reusable battlecard, or the design of a formal POC or RFP evaluation.Design★ 83
- competitive-roadmap-reviewLMTYdotcom/skillsTurn market and customer evidence into product questions worth investigating - for a product area or a roadmap under review - without treating competitor features as a roadmap. Establishes what competitors actually did and whether it is independent and buyer-relevant, pulls the company's own customer evidence for the same need, checks whether the problem is already solved another way, and frames each gap as table-stakes risk, differentiator opportunity, copycat noise, or evidence gap, with the evidence still needed before anyone prioritizes. Use for "what should product investigate based on the market", "competitors keep adding this - does it matter for our roadmap", "review this roadmap against market and customer evidence", "are we missing something". Not for deciding whether a market pattern is real, framing a launch, or making the priority call.Planning★ 83
- competitive-battlecardphuryn/pm-skillsCreate sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'Planning★ 27.4K
- speq-planmarconae/speq-skillPlans a feature or change through a clarifying interview, producing spec deltas, plan.md, and decision-log.md with adversarial review. Use to plan, spec, design, or scope a feature, change, removal, refactor, or fix, before any implementation.Planning★ 55
- competitive-objection-responseLMTYdotcom/skillsHandle one live competitive objection from a buyer, prospect, rep, or account with current facts, a concise response posture, discovery questions, supportable proof, and honest qualification. Use for "what do I say?", "the buyer just said...", competitor claims about price, features, integrations, security, implementation, or value, and other immediate objection-handling moments - including when the request bundles that objection with broader work such as a comparison document, a deal plan, or a team-wide claim, in which case answer the objection and hand the rest off. Not for a reusable battlecard on its own or for deciding the company's own pricing.Security★ 83
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in