القائمة
Use when responding to an RFP or writing a new-business proposal — to decide whether to pursue it, shape the offer, and produce a document a client can say yes to.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | client-proposal-rfp |
| description | Use when responding to an RFP or writing a new-business proposal — to decide whether to pursue it, shape the offer, and produce a document a client can say yes to. |
Run this for any pursuit that would put the agency's name on a proposal. A good proposal is a decision made twice: first whether to chase it at all, then how to win it without giving away the margin.
PURSUIT: <client / RFP> RECOMMENDATION: <pursue / decline> — <reason>
CLIENT PROBLEM: <in their words>
APPROACH: <2-4 sentences>
DELIVERABLES: <bulleted>
OUT OF SCOPE: <bulleted>
PRICE: <tiers/options with what each buys>
ASSUMPTIONS: <bulleted>
PROOF: <1-2 relevant points>
NEXT STEP: <the easy yes>
Use when you need to assess whether a client account is healthy, at risk, or slipping — before renewal, after a rough patch, or on a regular cadence — and decide what to do about it.
Use when a client request is ready to become production work and you must brief creative or media — turning a vague ask into an objective, an audience, and constraints the team can build against.
Use when preparing the quarterly review a client account faces — to report results against the objective honestly, read what worked, and set what the next quarter buys.
Use when you need to write or change a statement of work — turning an agreed offer into a scope, deliverables, price, and terms that both protect the client and defend the agency's margin.
Use when reviewing compensation for a role, a team, or the whole population — checks where people sit against defensible bands, finds equity gaps, and produces a ranked, costed set of adjustments.
Use when building or maintaining the self-serve answers employees reach for — turns the questions people actually ask into clear, sourced FAQ entries that deflect repeat questions and stay consistent with policy.