# Monetize

> Use when turning a project into a money-making product, or when the user mentions pricing, charging, subscriptions, payments, Stripe, or a landing page. Run it early - pricing shapes scope.

- **Type:** Skill
- **Install:** `agentstack add skill-t4lel-claude-arsenal-monetize`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [T4LEL](https://agentstack.voostack.com/s/t4lel)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [T4LEL](https://github.com/T4LEL)
- **Source:** https://github.com/T4LEL/Claude-Arsenal/tree/main/skills/monetize

## Install

```sh
agentstack add skill-t4lel-claude-arsenal-monetize
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Monetize

Turn a product into revenue. Run BEFORE building most features — what people pay for defines the MVP.

## Step 1 — Foundation (answer honestly before anything else)

Delegate to the **biz-strategist** agent with the product idea and target user:

- Who exactly is the customer, and what painful problem does this solve?
- What do they use today (including "nothing"), and why switch?
- Competitor scan with real current prices.

If the answers are weak, stop here and report that — integrating Stripe into a product nobody pays for is wasted work.

## Step 2 — Model & pricing

From the biz-strategist output, lock in: ONE monetization model, 2-3 price tiers max with concrete numbers, and the "needed to charge the first customer" feature list. Everything not on that list is deferred.

## Step 3 — Payment integration (when there's something to sell)

Default: **Stripe**. Standard shape for a SaaS webapp:

1. Stripe Checkout (hosted) for purchase — do not build custom card forms.
2. Webhook endpoint (`checkout.session.completed`, `customer.subscription.updated/deleted`) that updates the user's plan in the database; verify webhook signatures; make handlers idempotent.
3. Stripe Customer Portal for self-serve cancel/upgrade — don't build billing UI.
4. Gate features by the plan column in the database (server-side checks, not client-only).
5. Test end-to-end in Stripe test mode with test cards before going live. Fetch current Stripe docs via the context7 MCP tools — API versions change.

Implementation goes to backend-builder; keys are env vars, never in code. Anything beyond this standard shape (usage-based billing, invoicing, marketplace splits) goes through /product-spec's feasibility gate before implementation.

## Step 4 — Landing page

biz-strategist writes the copy (headline = customer outcome, pain, 3-step how, proof, one CTA); frontend-builder ships it. Include: pricing table matching Step 2, and analytics (choose a simple one, e.g. platform analytics or a lightweight script — no heavyweight suites for v1).

## Step 5 — Launch checklist

- Payments verified live with one real transaction, refunded after. Switching to live keys and making the real charge require the user's explicit go-ahead — never run them unprompted (a refunded charge still costs the Stripe fee); until then, test-mode evidence is the bar.
- Legal minimums: terms + privacy pages (templates fine), refund policy stated.
- Money-path actions only here — the first 3 with dates; channel planning and announcements belong to /launch.
- Metric to watch weekly: visitors → signups → paid conversion. One number per stage, tracked from day one.

## Report (use exactly these sections)

- **Model & prices:** chosen model and tiers with concrete numbers.
- **MVP-to-charge list:** features required to charge customer #1; everything else deferred.
- **Integration status:** built and tested vs planned (Stripe test-mode evidence when built).
- **Launch actions:** the first 3 concrete actions with dates.
- **Assumptions to validate:** market/pricing assumptions not yet backed by real users.

## Source & license

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

- **Author:** [T4LEL](https://github.com/T4LEL)
- **Source:** [T4LEL/Claude-Arsenal](https://github.com/T4LEL/Claude-Arsenal)
- **License:** MIT

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

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-t4lel-claude-arsenal-monetize
- Seller: https://agentstack.voostack.com/s/t4lel
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.