Executive Sow Pricing

Executive SOW and pricing

Write for the owner or executive who approves the work. Preserve the latest user-approved scope, price, phases, platforms, quantities, company names, exclusions, and wording.

Route the work

• For founder interviews, pre-sales diagnosis, or 24/48-hour follow-up: read references/discovery-to-proposal.md.
• For staffing benchmarks, coefficients, price comparisons, first-year economics, or pass-through costs: read references/cost-model.md.
• Before final PPT or Word delivery: read references/inspection-checklist.md.

Load only the applicable references. Use the presentation or document skill separately when the requested artifact format requires it.

Proposal contract

For a full proposal, build a compact requirement matrix covering desired business results, decision owner, authoritative source, scope, deliverables, timeline, pricing, exclusions, accepted wording, and facts that need current evidence. Resolve conflicting revisions in favor of the user’s latest explicit instruction.

For targeted edits, use only the affected requirements; do not rebuild the full proposal or create unrequested PPT/Word outputs.

A full proposal should explain the decision:

1. What business result changes and why it matters now.
2. How the operating workflow produces that result.
3. What the first phase proves and what evidence the executive can inspect.
4. What the investment includes, replaces, excludes, and leaves as a future option.

Turn stated outcomes into acceptance standards with baseline, target, measurement window, evidence source, and decision owner. Do not invent motives, results, attribution, fixed asset counts, or “human in the loop” positioning the user did not request.

Solution and economics

• Name modules by business action and produced evidence. Show inputs, rules, handoffs, exceptions, permissions, outputs, ownership, rollback, and audit trail where relevant.
• Include only diagrams that improve a decision: the investment-to-evidence business loop, the primary operating or engineering flow, and the project path with decision gates. Add domain flows only when in scope.
• Keep in-house, outsourced, tool-only, and proposed-service comparisons economically equivalent or label where they are not.
• State units, periods, role medians, phase months, coefficients, and assumptions. Keep hardware, subscriptions, API usage, media spend, and rights separate when the brief requires it.
• Do not double-count included allowances. Separate first-year economics from later-year operating economics. Treat forecast revenue or GMV as a validation hypothesis unless the user explicitly defines it otherwise.

Research only claims that affect the decision. Prefer current primary sources and keep source URLs in notes or a source table.

Completion

The work is complete only when every matrix item is represented or deliberately excluded, calculations reconcile, editable diagrams remain legible, final artifacts render correctly, stale or placeholder text is gone, failures are fixed, and the final outputs are re-rendered and rechecked.