Proposal Creator Skill
Produces a complete, client-ready proposal package for any Teqfocus engagement:
- Bottoms-up effort estimate — phased, role-based, with gap analysis
- Phased Word proposal document (.docx) — full commercial proposal
- Executive PowerPoint deck (.pptx) — 10 slides for a live meeting or RFP submission
Step 1 — Read Reference Files and Sales Play Documents
Before doing anything:
Search the project knowledge folder for a sales play document matching the vertical or technology in scope. If one exists, it is the primary source for offering scope, pricing assumptions, and delivery model. It overrides the reference files below for those areas.
Load the reference files:
references/knowledge.md — Teqfocus context, team models, hour benchmarks by engagement type
references/process.md — Workflow, section-by-section document build instructions
references/tech-rules.md — docx-js and pptxgenjs rules, formatting standards
- Load
offerings-catalog.md — for accelerator component specs and "done looks like" descriptions.
Step 2 — Identify Engagement Type
Before estimating, confirm:
| Question |
Why it matters |
| What technology is in scope? |
Determines team model, hour benchmarks, reference architecture |
| Which Step in the ladder? (1/2/3/4) |
Determines phase structure and commercial framing |
| Which accelerator or solution pattern? |
Determines component list and "done looks like" |
| Is there an uploaded sales play? |
If yes, it drives scope — use it |
Step 3 — Ask 3 Clarifying Questions
Before producing any output:
- Engagement type: Which Step and which technology / accelerator pattern?
- Timeline preference: Standard duration for the step, or compressed?
- Client and engagement name: For document headers and file naming
Step 4 — Bottoms-Up Estimate
Build the estimate using hour benchmarks from references/knowledge.md for the identified engagement type.
For ALL engagement types — check these 7 items:
| Item |
Why it's missed |
Typical hours |
| Data migration or data preparation |
Assumed client handles it |
80–120h |
| Environment setup and provisioning |
"Someone else handles this" |
20–40h |
| Integration testing across all systems |
Estimated as unit testing only |
60–80h |
| User training and enablement |
Added but under-scoped |
40–60h |
| Cutover planning and hypercare |
Treated as a deployment event |
30–40h |
| Change management and adoption |
Never in scope until go-live fails |
20–40h |
| Security, compliance, and governance design |
Retrofitted after build |
40–80h |
PM buffer must be ≥ 15% of total. Correct if below.
Present as markdown table. Wait for confirmation before building documents.
Step 5 — Build Word Proposal Document
See references/process.md for section instructions.
Required sections:
Cover → Executive Summary → Client Situation → Proposed Solution → Scope and Phasing →
Effort Breakdown → Team and Credentials → Timeline → Deliverables →
Client Responsibilities → Commercial Terms → Success Criteria → Next Steps
Commercial terms standard:
- Payment milestones: 30% on contract, 40% on Phase 1 completion, 30% on go-live
- Step 1 Assessment: 50% on kickoff, 50% on report delivery
- Never publish dollar amounts — reference "commercial schedule (Appendix A)"
Step 6 — Build Executive Deck (10 slides)
- Title
- Client situation — the problem in the client's language
- The Teqfocus approach
- Solution architecture — visual
- Phasing and timeline
- Solution / accelerator detail
- Business value — outcomes tied to client objectives
- Why Teqfocus — credentials + relevant proof point (Summit Partner where relevant)
- Team — roles, not names
- Next steps — one specific CTA
Step 7 — Create-First, Then Escalate
After producing the estimate and proposal draft:
- Surface to the rep with a summary of the estimate and top 3 risks
- Flag for Gate review per the escalation framework:
- Gate 1 — Andy: scope matrix, ROI, UI mockup (if applicable)
- Gate 2 — Andy: technical design (trigger the solution-design skill if not already done)
- Gate 3 — Vinod: final proposal + commercials
- Commercials lock only after Naveen + Vinod approval — the proposal document goes out with a placeholder commercial schedule until they confirm
Step 8 — QA Checklist
Estimate
Word document
Deck
Output File Naming
[ClientName]_[Vertical]_[Technology]_Proposal.docx
[ClientName]_[Vertical]_[Technology]_Deck.pptx
[ClientName]_[Vertical]_Revised_Estimate.docx
1---2name: proposal-creator3description: |4 Full-stack proposal creation skill for Teqfocus. Use this skill whenever the user wants to5 create ANY sales or proposal artifact for a client engagement — across any technology:6 Salesforce (Health Cloud, Agentforce, Data 360, Revenue Cloud, FSC, Life Sciences Cloud),7 Snowflake, Databricks, AWS, Azure, GCP, Anthropic Claude API / MCP agent builds, custom8 application development, or data transformation. Triggers include: "create a proposal",9 "write an estimate", "build a deck", "make a presentation", "review this RFP", "audit this10 estimate", "generate a proposal for [client]", "create a pitch deck", "scope this11 engagement", "estimate this project", or any request involving a client brief, RFP, SOW,12 or vendor brief. Always use this skill before attempting to write any proposal, estimate,13 or presentation — do not attempt from memory alone.14metadata:15 source: https://skillmd.com/skills/teqfocusadmin/proposal-creator16---1718# Proposal Creator Skill1920Produces a complete, client-ready proposal package for any Teqfocus engagement:21221. **Bottoms-up effort estimate** — phased, role-based, with gap analysis232. **Phased Word proposal document** (.docx) — full commercial proposal243. **Executive PowerPoint deck** (.pptx) — 10 slides for a live meeting or RFP submission2526---2728## Step 1 — Read Reference Files and Sales Play Documents2930Before doing anything:31321. **Search the project knowledge folder for a sales play document** matching the vertical or technology in scope. If one exists, it is the primary source for offering scope, pricing assumptions, and delivery model. It overrides the reference files below for those areas.33342. Load the reference files:35```36references/knowledge.md — Teqfocus context, team models, hour benchmarks by engagement type37references/process.md — Workflow, section-by-section document build instructions38references/tech-rules.md — docx-js and pptxgenjs rules, formatting standards39```40413. Load `offerings-catalog.md` — for accelerator component specs and "done looks like" descriptions.4243---4445## Step 2 — Identify Engagement Type4647Before estimating, confirm:4849| Question | Why it matters |50|---|---|51| What technology is in scope? | Determines team model, hour benchmarks, reference architecture |52| Which Step in the ladder? (1/2/3/4) | Determines phase structure and commercial framing |53| Which accelerator or solution pattern? | Determines component list and "done looks like" |54| Is there an uploaded sales play? | If yes, it drives scope — use it |5556---5758## Step 3 — Ask 3 Clarifying Questions5960Before producing any output:61621. **Engagement type**: Which Step and which technology / accelerator pattern?632. **Timeline preference**: Standard duration for the step, or compressed?643. **Client and engagement name**: For document headers and file naming6566---6768## Step 4 — Bottoms-Up Estimate6970Build the estimate using hour benchmarks from `references/knowledge.md` for the identified engagement type.7172**For ALL engagement types — check these 7 items:**7374| Item | Why it's missed | Typical hours |75|---|---|---|76| Data migration or data preparation | Assumed client handles it | 80–120h |77| Environment setup and provisioning | "Someone else handles this" | 20–40h |78| Integration testing across all systems | Estimated as unit testing only | 60–80h |79| User training and enablement | Added but under-scoped | 40–60h |80| Cutover planning and hypercare | Treated as a deployment event | 30–40h |81| Change management and adoption | Never in scope until go-live fails | 20–40h |82| Security, compliance, and governance design | Retrofitted after build | 40–80h |8384**PM buffer must be ≥ 15% of total. Correct if below.**8586Present as markdown table. Wait for confirmation before building documents.8788---8990## Step 5 — Build Word Proposal Document9192See `references/process.md` for section instructions.9394**Required sections:**95Cover → Executive Summary → Client Situation → Proposed Solution → Scope and Phasing →96Effort Breakdown → Team and Credentials → Timeline → Deliverables →97Client Responsibilities → Commercial Terms → Success Criteria → Next Steps9899**Commercial terms standard:**100- Payment milestones: 30% on contract, 40% on Phase 1 completion, 30% on go-live101- Step 1 Assessment: 50% on kickoff, 50% on report delivery102- Never publish dollar amounts — reference "commercial schedule (Appendix A)"103104---105106## Step 6 — Build Executive Deck (10 slides)1071081. Title1092. Client situation — the problem in the client's language1103. The Teqfocus approach1114. Solution architecture — visual1125. Phasing and timeline1136. Solution / accelerator detail1147. Business value — outcomes tied to client objectives1158. Why Teqfocus — credentials + relevant proof point (Summit Partner where relevant)1169. Team — roles, not names11710. Next steps — one specific CTA118119---120121## Step 7 — Create-First, Then Escalate122123After producing the estimate and proposal draft:1241251. **Surface to the rep** with a summary of the estimate and top 3 risks1262. **Flag for Gate review** per the escalation framework:127 - Gate 1 — Andy: scope matrix, ROI, UI mockup (if applicable)128 - Gate 2 — Andy: technical design (trigger the solution-design skill if not already done)129 - Gate 3 — Vinod: final proposal + commercials1303. **Commercials lock only after Naveen + Vinod approval** — the proposal document goes out with a placeholder commercial schedule until they confirm131132---133134## Step 8 — QA Checklist135136**Estimate**137- [ ] All requirements have hours allocated138- [ ] 7 commonly-missing items addressed139- [ ] PM buffer ≥ 15%140141**Word document**142- [ ] All 13 sections present143- [ ] No dollar amounts inline — reference Appendix A144- [ ] Teqfocus credential appears once, naturally145146**Deck**147- [ ] All 10 slides present148- [ ] Solution architecture slide has a visual149- [ ] Business value connects to client's stated objectives150151---152153## Output File Naming154155```156[ClientName]_[Vertical]_[Technology]_Proposal.docx157[ClientName]_[Vertical]_[Technology]_Deck.pptx158[ClientName]_[Vertical]_Revised_Estimate.docx159```