anotb Proposal Development
Produce a persuasive, compliant proposal for the client's specific buying decision. Start at the requested stage: opportunity assessment, win themes, proposal, SOW, or oral presentation. Do not require qualification of an already approved pursuit or recreate a signed agreement when the request is for a limited edit.
Use the RFP, conversation notes, firm credentials, staffing, and commercial inputs provided. Preserve mandatory format, section order, page limits, and submission requirements. Complete supported sections and flag missing credentials or inputs precisely. Do not invent client results, team members, certifications, competitor intelligence, references, or outcome percentages.
Understand the buying decision
Distinguish must-pass requirements from scored criteria and inferred preferences. Record submission deadlines, format, mandatory attachments, eligibility, evaluation weights, and clarification procedures. Trace each material requirement to its source, response location, evidence, owner, and completion status. A persuasive response that fails a mandatory requirement may be unusable.
For qualification when requested, assess fit, capability, capacity, economics, strategic value, and the cost of pursuit. State the basis for a go/no-go recommendation. Do not invent win probabilities or conclude that a deal is wired from one unusual requirement; identify evidence and questions to test that concern.
Develop win themes from the client's priorities and proof the firm can substantiate. A differentiator explains why this team or approach fits this problem and what evidence supports it. Conditional wording does not justify an unsupported savings range or implied track record.
Draft the requested artifact
For a proposal, connect the client's challenge to approach, deliverables, outcomes, team, evidence, investment, assumptions, and next decision. Adapt this arc to the required response order. Write the executive summary against the completed proposal so it reflects the actual scope and terms.
For a SOW, use proposal and SOW mechanics. Define boundaries, acceptance, client obligations, dependencies, pricing basis, and change control. Respect supplied contract terms and distinguish proposed provisions from agreed terms. Do not impose deemed acceptance, liability caps, or signature requirements as universal rules.
For a pitch or oral defense, use pitch deck. Preserve the time slot, audience, and decision objective. For pricing, engagement-pricing can help when available, but this skill remains usable independently.
Persuasion and evidence
State the outcome and how the approach could achieve it. Separate delivery commitments from forecast business benefits that depend on client action or external conditions. Use relevant real cases, with permitted attribution, and accurately label hypothetical examples. A missing proof point can remain a specific draft marker; do not fill it with fabricated prose to make the document look finished.
Address supported objections and material risks. Explain what the client must provide and the trade-off being proposed. Avoid generic capability claims, unsupported superlatives, and a menu of services unrelated to the request.
Complete and check
Deliver the proposal, SOW, pitch, or assessment requested. When a file is requested, use available document or presentation tools and format skills if present; no particular host or plugin is required. Check the saved artifact and rendered layout when tools allow.
Verify requirement coverage, section and page constraints, consistency of scope, dates, staffing and fees, substantiation of credentials, and visibility of unresolved items. Check arithmetic with available tools. Preparing a response does not authorize submitting it, contacting the buyer, or agreeing terms. State the material gaps that prevent the draft from being submitted as-is.