| name | premium-client-proposal-strategy |
| description | Use when positioning a proposal for executives, enterprise buyers, investors, affluent markets, or high-ticket services; use premium-pricing for fee mechanics and premium-writing for sentence-level craft. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
Premium Client Proposal Strategy
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
Use When
- The proposal is for a CEO, board, investor, enterprise, donor, public-sector leader, luxury brand, affluent-market business, or high-value SME.
- The offer is premium-priced or should not compete on cheapest compliant bid.
- The proposal must sell strategic value, trust, risk reduction, speed, exclusivity, or measurable commercial outcomes.
Domain Method
- Identify the buyer level and decision path: executive sponsor, technical reviewers, procurement, finance, users, and political or reputational risks.
- Frame the problem in executive terms: cost of delay, lost revenue, risk exposure, operational drag, missed opportunity, customer experience, or strategic control.
- Build the evaluator journey: what the buyer must understand, believe, trust, and defend before awarding at a premium rate.
- Position the firm as the premium answer: specialist insight, method, proof, comparable results, senior team, governance, service quality, and implementation support.
- Write the value case before the activity list: outcomes, evidence, risk controls, delivery path, and what changes for the client.
- Defend the price through value, risk reduction, seniority, quality gates, total cost of ownership, and support rather than broad prestige language.
- Prepare ethical objection responses for price, risk, timeline, staffing, technology, local context, and post-launch support.
- Run the premium proposal gate before final submission.
- Use the premium commercial writing layer to turn the strategy into concise, proof-led, evaluator-friendly prose.
Quality Bar
- The proposal respects executive time: clear point, concrete evidence, no generic self-description.
- Premium value is proven through method, team, proof, governance, and commercial logic.
- The methodology makes invisible work visible through phases, artefacts, controls, and decision gates.
- The financial proposal is aligned with the promised level of seniority, quality, and risk control.
- The proposal explains the premium choice in terms the evaluator can defend internally.
- Persuasion remains ethical: no false urgency, exaggerated scarcity, unsupported authority, or fear-based selling.
Existing Deliverables
- Premium proposal strategy.
- Executive-summary and methodology improvements.
- High-ticket pricing and negotiation guidance.
- Evaluator journey and objection-handling notes.
- Support, maintenance, and service-quality commitments for premium delivery.
- Proposal review findings and fix list.
SaaS Premium-Buyer Lens
For premium SaaS implementation and SaaS product-development bids, the buyer-level map is more specific than generic premium:
- CEO / MD: cares about value at stake, time to value, strategic control, board defensibility.
- CFO / Finance Director: cares about TCO, payback, sensitivity, NRR (for resale SaaS), Rule of 40 / magic number (for investor-grade buyers).
- CIO / CTO: cares about tenant isolation, integration realism, operating model change, exit and portability.
- CISO: cares about regulator alignment, sub-processors, BCDR, incident response, audit posture.
- COO: cares about adoption capacity, change-management staffing, operating-model shifts.
- Sponsor (sector executive): cares about vertical depth, comparable engagement evidence, and after-go-live commitment.
Tune the proposal's themes, evidence, and tone to the dominant buyer level. For investor-grade buyers (PE-owned SaaS targets, VC-backed clients), the investor-grade vocabulary opt-in (Rule of 40, magic number, burn multiple, NRR, ARR) signals the agency speaks the buyer's commercial language.
Do Not Use When
- Do not use this skill when a neighbouring specialist named in the description owns the primary decision; route there first and use this skill only as a supporting layer.
- Do not use it to invent buyer facts, evidence, legal positions, statutory rules, delivery capacity, or current external claims.
Inputs
| Artefact | Source/provider | Required? | Missing-input behaviour |
|---|
| buyer mandate, decision criteria, proof, risk, budget context, and executive audience | Buyer, ToR, approved project record, accountable owner, or verified evidence source | Yes | Stop the affected decision, name the missing source, and return only a qualified outline or assumption register. |
Outputs
| Artefact | Consumer | Acceptance condition |
|---|
| premium positioning brief and proposal spine | Executive sponsor and proposal team | Claims trace to supplied evidence; assumptions, owners, exclusions, decisions, and observable acceptance tests are explicit. |
Evidence Produced
| Evidence | Consumer | Acceptance condition |
|---|
| Decision and source trace for the output | Reviewer and release owner | Each load-bearing choice identifies its source, rationale, accountable owner, and any unassessed check. |
Capability Contract
Default to read-only for analysis, critique, discovery, and review. Minimum capability is access to the supplied artefacts and permission to inspect or calculate relevant evidence. Edit only the requested working copy. Do not publish, send, spend, change production systems, certify compliance, make a statutory claim, or approve a commercial concession without explicit authority.
Degraded Mode
If required files, interviews, finance doctrine, search evidence, calculation tools, network access, or specialist review are unavailable, return the narrowest useful qualified result. Mark unavailable checks as not assessed, separate facts from assumptions, and state what is needed to resume. An unassessed gate is never a pass.
Decision Rules
| Choice | Action | Failure/risk avoided |
|---|
| Lead with value, assurance, or transformation | Choose the buyer concern best supported by evidence and delivery authority. | Prestige language without buyer-specific proof. |
| Evidence conflicts or authority is absent | Stop the affected recommendation, record the conflict, and seek the named owner’s decision. | Invented facts or unauthorised commitments. |
| Evidence and approval are complete | Proceed within scope and retain the decision trace. | Irreproducible approval or scope drift. |
Workflow
- Confirm the consumer, decision, neighbouring-skill route, authority, and required inputs; stop if the primary route or accountable owner is unknown.
- Inspect supplied evidence and record facts, assumptions, conflicts, and unavailable checks; stop on a load-bearing contradiction.
- Apply the domain method and decision rules, preserving the repository’s proposal voice and specialist constraints.
- Draft the contracted output with observable acceptance conditions and an evidence trace.
- Review alignment with scope, work plan, team, pricing, risk, and dependent proposal sections; recover by revising the affected choice and rerunning the check.
- Run the critical-analysis and anti-slop gates; block release on unsupported claims, failed safety or finance gates, or an F slop grade.
Quality Standards
- Every load-bearing claim is verified or explicitly qualified, and the output distinguishes fact, assumption, recommendation, and commitment.
- Scope, method, work plan, staffing, pricing, risks, dependencies, and acceptance conditions remain mutually consistent.
- The output preserves domain constraints, names accountable owners, covers failure paths, and blocks unsupported or unauthorised promises.
- British English and the repository’s East African professional tone are used unless the buyer requires another standard.
- The critical-analysis and anti-slop gates pass before release, with no unassessed check represented as passed.
Anti-Patterns
- Inventing a buyer fact or proof point. Fix: cite the supplied source or mark the statement as an assumption requiring confirmation.
- Treating an unavailable check as passed. Fix: mark it not assessed and name the evidence needed to resume.
- Copying a neighbouring skill’s method without routing. Fix: use the specialist for the primary decision and retain only the supporting layer here.
- Writing acceptance as “satisfactory” or “appropriate”. Fix: state an observable measure, evidence record, and decision owner.
- Adding premium or technical claims without delivery capacity. Fix: reconcile the claim with named people, time, budget, dependencies, and authority.
Worked Example
A board is funding a regulated-system redesign. Lead with decision risk, senior governance, proof, and measurable assurance rather than adjectives about exclusivity.
References
