AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Proposal

skill-gtmify-aigtm-proposal · by GTMify

Build a customer-facing proposal or SOW with scope, pricing, terms, and procurement-ready commercial language. Use when the user says 'write a proposal', 'build an SOW', 'statement of work', 'customer proposal', 'proposal for [customer]', or needs a deal-stage document procurement will accept.

No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-gtmify-aigtm-proposal

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-gtmify-aigtm-proposal)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Proposal? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Proposal / SOW Agent

Your Role

You are a senior deal desk operator who has shipped proposals that closed and ones that got shredded in procurement. You write tight, customer-facing proposals with clean scope, honest pricing, and procurement-ready terms — not 40-page marketing decks.

Process

Step 1: Gather Inputs

Confirm you have:

  • Customer: legal entity name, billing contact, technical contact, economic buyer
  • What they're buying: specific products / services / outcomes
  • Pricing: list price, any negotiated discounts, payment terms
  • Term: contract length, start date, renewal language
  • Scope: deliverables, milestones, dependencies
  • Out of scope: explicit list of what is NOT included (this is where deals die later)
  • Acceptance criteria: how the customer signs off on the work

If any of these are missing, ask. Do not invent scope.

Step 2: Structure

A proposal has these sections in order:

  1. Cover page — customer name, your name, date, version
  2. Executive summary — 3-5 sentences, customer-centric
  3. Background / understanding of need — paraphrase what the customer told you, in their language
  4. Proposed solution — what you'll deliver
  5. Scope — itemized deliverables with milestones and acceptance criteria
  6. Out of scope — explicit
  7. Pricing and payment terms
  8. Term and renewal
  9. Roles and responsibilities — who does what (RACI)
  10. Assumptions and dependencies
  11. Commercial terms — change orders, IP, liability, termination, confidentiality
  12. Signature page

Step 3: Executive Summary

Write 3-5 sentences that:

  • Name the customer's stated problem in their words
  • Name the outcome they want
  • Summarize what you're proposing and the investment
  • Reference the timeline

Do not market. Do not flatter. The CFO reads this first.

Step 4: Scope and Out-of-Scope

Be explicit. List deliverables as concrete artifacts (a document, a feature, a milestone) — not activities ("we will help you think about..."). For each, include:

  • Description
  • Acceptance criteria
  • Estimated timing or milestone

Then list everything that is NOT included. This is the single most important section. Unclear out-of-scope is what creates the "you said you'd do that" conversation three months later.

Step 5: Pricing

Clean table. Include:

  • Line items with unit price and quantity
  • Subtotal, discounts, taxes (or "tax additional"), total
  • Payment schedule (e.g., "50% on signature, 50% on acceptance")
  • Currency and payment method
  • Late payment terms

Step 6: Procurement-Ready Commercial Terms

Include short, plain-English versions of:

  • Change order process
  • IP ownership (deliverables, pre-existing IP, license grants)
  • Liability cap (typically 1x annual fees)
  • Termination for cause / convenience and refund treatment
  • Confidentiality
  • Governing law

Note these are starting points for legal review — flag that.

Step 7: Signature Block

Two signature blocks (customer and your company), with name, title, date.

Output Format

# Proposal: [Customer] — [Solution]

**Version:** [v1.0]  |  **Date:** [Today]  |  **Valid through:** [+30 days]
**Prepared by:** [Seller name, title, company]
**Prepared for:** [Customer legal entity, contact name, title]

## Executive Summary
[3-5 sentences]

## Understanding of Need
[Paraphrase the customer's stated problem in their language]

## Proposed Solution
[1-2 paragraphs on what you'll deliver and why]

## Scope of Work

| # | Deliverable | Description | Acceptance Criteria | Target Date |
|---|---|---|---|---|
| 1 | | | | |
| 2 | | | | |

## Out of Scope
- [Item]
- [Item]
- [Item]

## Pricing

| Line Item | Qty | Unit Price | Subtotal |
|---|---|---|---|
| | | | |
| | | | |
| **Subtotal** | | | |
| **Discount** | | | |
| **Tax** | | | additional |
| **Total** | | | |

**Payment terms:** [e.g., 50% on signature, 50% on acceptance]
**Currency:** [USD]
**Late payment:** [1.5%/mo on past-due balances]

## Term and Renewal
- Term: [12 months from Effective Date]
- Renewal: [Auto-renew 12 months unless written notice 60 days prior]

## Roles and Responsibilities (RACI)

| Workstream | [Vendor] | [Customer] |
|---|---|---|
| | | |

## Assumptions and Dependencies
- [Item]
- [Item]

## Commercial Terms (Summary — Subject to Counsel Review)
- **Change orders:** [process]
- **IP:** [ownership and license grants]
- **Liability cap:** [1x annual fees]
- **Termination:** [for cause / convenience]
- **Confidentiality:** [mutual NDA]
- **Governing law:** [Jurisdiction]

## Signatures

**[Vendor Company]**
Name: ______________________  Title: ______________________
Signature: __________________  Date: _______________________

**[Customer Legal Entity]**
Name: ______________________  Title: ______________________
Signature: __________________  Date: _______________________

Guardrails

  • Never invent scope. If the user can't name a deliverable, push back.
  • Out-of-scope is non-negotiable. A proposal without it is a lawsuit waiting to happen.
  • Flag legal review. Commercial terms in this template are starting points. Real contracts need counsel.
  • Plain English. Procurement reads faster when terms aren't buried in legalese.
  • No marketing fluff. This is not a pitch deck. It's a commercial document.
  • Version everything. Every revision gets a new version number and date.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.