# Proposal Sow Delivery

> Professional services delivery encompasses writing proposals, defining Use when this capability is needed.

- Skill: `tomevault-io/proposal-sow-delivery` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/proposal-sow-delivery`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/proposal-sow-delivery/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/proposal-sow-delivery

---


# Proposal Sow Delivery

## Skill Profile
*(Select at least one profile to enable specific modules)*
- [ ] **DevOps**
- [x] **Backend**
- [ ] **Frontend**
- [ ] **AI-RAG**
- [ ] **Security Critical**

## Overview
Professional services delivery encompasses writing proposals, defining scope of work (SOW), managing client expectations, and delivering projects successfully. Essential skills for consultants, agencies, and freelancers.

## Why This Matters
- **Win rate**: Clear proposals win more business
- **Scope control**: SOW prevents scope creep
- **Client satisfaction**: Managed expectations = happy clients
- **Profitability**: Accurate scoping = profitable projects

## Core Concepts & Rules

### 1. Core Principles
- Follow established patterns and conventions
- Maintain consistency across codebase
- Document decisions and trade-offs

### 2. Implementation Guidelines
- Start with the simplest viable solution
- Iterate based on feedback and requirements
- Test thoroughly before deployment


## Inputs / Outputs / Contracts
* **Inputs**:
  - <e.g., env vars, request payload, file paths, schema>
* **Entry Conditions**:
  - <Pre-requisites: e.g., Repo initialized, DB running, specific branch checked out>
* **Outputs**:
  - <e.g., artifacts (PR diff, docs, tests, dashboard JSON)>
* **Artifacts Required (Deliverables)**:
  - <e.g., Code Diff, Unit Tests, Migration Script, API Docs>
* **Acceptance Evidence**:
  - <e.g., Test Report (screenshot/log), Benchmark Result, Security Scan Report>
* **Success Criteria**:
  - <e.g., p95 < 300ms, coverage ≥ 80%>

## Skill Composition
* **Depends on**: None
* **Compatible with**: None
* **Conflicts with**: None
* **Related Skills**: None

## Quick Start
#

## Assumptions
- Working with B2B clients on consulting projects
- Projects have defined scope and deliverables
- Client has budget and decision-making authority
- Team has relevant domain expertise
- Standard business tools available (email, video conferencing, project management)

## Compatibility
- **Project Management Tools**: Jira, Asana, Trello, Monday.com
- **Document Tools**: Google Docs, Microsoft Word, Notion
- **Communication Tools**: Slack, Microsoft Teams, Zoom
- **Proposal Tools**: PandaDoc, Proposify, DocuSign
- **Billing Tools**: QuickBooks, Xero, Stripe

## Test Scenario Matrix
| Scenario | Input | Expected Output | Verification |
|----------|-------|-----------------|--------------|
| Create proposal | Client requirements | Professional proposal document | Peer review |
| Define SOW | Project scope | Complete SOW document | Legal review |
| Change request | Scope change | CR form with impact assessment | Client approval |
| Status report | Weekly progress | Status report with metrics | Client acknowledgment |
| Project handover | Completed project | Handover checklist complete | Client sign-off |
| Retrospective | Project completion | Lessons learned document | Team review |

## Technical Guardrails
#

## Agent Directives & Error Recovery
*(ข้อกำหนดสำหรับ AI Agent ในการคิดและแก้ปัญหาเมื่อเกิดข้อผิดพลาด)*

- **Thinking Process**: Analyze root cause before fixing. Do not brute-force.
- **Fallback Strategy**: Stop after 3 failed test attempts. Output root cause and ask for human intervention/clarification.
- **Self-Review**: Check against Guardrails & Anti-patterns before finalizing.
- **Output Constraints**: Output ONLY the modified code block. Do not explain unless asked.


## Definition of Done
A professional services deliverable is complete when:

- [ ] Proposal is tailored to client's specific needs
- [ ] SOW has clear in-scope and out-of-scope items
- [ ] Deliverables are measurable and time-bound
- [ ] Payment milestones align with deliverables
- [ ] Change management process is documented
- [ ] Communication plan is established
- [ ] Weekly status reports are sent
- [ ] All decisions are documented in writing
- [ ] Client sign-off is obtained for each milestone
- [ ] Handover documentation is complete

## Anti-patterns
1. **Generic proposals**: Template-heavy, not tailored to client
2. **Vague scope**: Unclear deliverables and acceptance criteria
3. **Hidden costs**: Pricing not transparent, surprises later
4. **Verbal agreements**: Scope changes without written CR
5. **Poor communication**: Infrequent updates, bad news late
6. **No change process**: Accepting all requests without impact assessment
7. **Unrealistic promises**: Over-promising to win business
8. **Poor documentation**: Missing handover materials, knowledge not transferred

## Reference Links
- [Proposal Writing Best Practices](https://www.proposalsmartz.com/proposal-writing-tips/)
- [SOW Templates](https://www.pandadoc.com/sow-template/)
- [Project Management Institute](https://www.pmi.org/)
- [Consulting Success](https://www.consultingsuccess.com/)

## Versioning & Changelog

* **Version**: 1.0.0
* **Changelog**:
  - 2026-02-22: Initial version with complete template structure

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/amnadtaowsoam) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->