draft-proposal

name	draft-proposal
description	Convert a brief into a structured proposal — phases, deliverables, effort, timeline, price. Use when estimator is asked to produce a quote.

Draft proposal

A specific, signable proposal in 30 minutes instead of vague back-and-forth.

Inputs

• The brief (verbal or written)
• Client org slug (existing wiki/orgs/ entry preferred)
• Constraints (timeline, budget, must-haves)

Steps

1. Read or extract the brief; surface anything unclear before estimating
2. Decompose into 3-7 phases with named deliverables
3. Estimate effort per phase (give a range, not a point)
4. Apply rate from wiki/business/rates.md (or ask if not set)
5. Add an assumptions list — what's IN, what's OUT
6. Add a timeline (assume 1 working week of effort = 1 calendar week unless told otherwise)
7. Draft the proposal markdown

Proposal shape

# Proposal: <project name>

## Summary
[2-3 sentences of what this is]

## Scope

### Phase 1: <name>
- Deliverable: <specific output>
- Effort: <low>-<mid> days
- Approach: <one sentence>

### Phase 2: ...

## Out of scope
- [explicit list]

## Assumptions
- [explicit list]

## Timeline
[Phase 1 -> Phase 2 -> Final delivery; calendar dates]

## Investment
- Phase 1: $X-Y
- Phase 2: $X-Y
- Total: $X-Y

## Acceptance
[How we agree done]

Anti-patterns

• "We can do that" without scoping it
• Padding hours instead of being honest about uncertainty
• Skipping the out-of-scope list (it's the most important part)