Find the premium-worthy features, the natural upgrade moments, and the billing friction between users and paying you.
Free & open · no signup · read-only — it ends by asking · nothing leaves your machine
You are working inside this repo. Mission: map how this product makes money — or could — by finding premium-worthy value, natural upgrade moments, and the friction between a willing user and a completed payment.
Read-only pass. Your only write is the report file.
Phase 2 sweeps the codebase through every one of these, citing file and line for each finding.
features that are high-value, costly to serve, collaborative, or power-user-only: natural paid-tier material
where a user hits a limit or a success high point; is there a well-placed, honest prompt there?
free-tier generosity (too much? too little to feel value?); tier logic clarity; what each tier is FOR
pricing-page clarity, checkout steps, trust signals, what happens on failed payment
seats, usage, add-ons: revenue that grows as the customer succeeds
can users actually upgrade/downgrade/cancel in-product; are limits even enforced in code?
One structured report at the repo root — or in reports/, if you keep one — the same shape every time, ready for a teammate — or the optional Studio — to act on.
REVENUE.md already exists from a previous run, read it first and lead with what changed since.Every Goal Prompt follows the same four steps, so results are consistent and repeatable — no matter which one you run.
What exists today.
Premium-worthy value — features that are high-value, costly to serve, collaborative, or power-user-only.
Every proposal names the willingness-to-pay signal behind it (usage pattern, cost, alternative price).
Create REVENUE.md at repo root.
Copy it and paste it into your agent inside the repo you want checked.
Install the goal plugin once — two commands — then just type /goal:monetization-map.
/plugin marketplace add GhostlyGawd/goal-prompts/plugin install goal@goal-promptsOr install only this Goal Prompt as /goal-monetization-map:
curl -fsSL https://goal-prompts.vercel.app/install | BRIEF=11 shLet an agent fetch it mid-conversation, or pull the raw Goal Prompt by URL.
https://goal-prompts.vercel.app/raw/11.mdNothing hidden — this is the whole Goal Prompt, verbatim. Read it in a minute, edit it, or copy it as-is.
# Goal: Monetization Map You are working inside this repo. Mission: map how this product makes money — or could — by finding premium-worthy value, natural upgrade moments, and the friction between a willing user and a completed payment. Read-only pass. Your only write is the report file. ## Phase 1 — Understand the current model - What exists today: free, paid, tiers, trials? Where does billing code live, if anywhere? - What is expensive to serve (compute, storage, third-party costs) — and is that cost gated? - What do power users do here that casual users don't? (infer from features and data model) ## Phase 2 — Audit through 6 lenses 1. **Premium-worthy value** — features that are high-value, costly to serve, collaborative, or power-user-only: natural paid-tier material 2. **Upgrade moments** — where a user hits a limit or a success high point; is there a well-placed, honest prompt there? 3. **Packaging** — free-tier generosity (too much? too little to feel value?); tier logic clarity; what each tier is FOR 4. **Payment friction** — pricing-page clarity, checkout steps, trust signals, what happens on failed payment 5. **Expansion paths** — seats, usage, add-ons: revenue that grows as the customer succeeds 6. **Plumbing gaps** — can users actually upgrade/downgrade/cancel in-product; are limits even enforced in code? ## Phase 3 — Curate - Every proposal names the willingness-to-pay signal behind it (usage pattern, cost, alternative price) - Flag churn risks: aggressive gating that would poison goodwill - Prefer honest value gates over dark patterns — always ## Phase 4 — Report Create `REVENUE.md` at repo root: 1. **Current model snapshot** — what exists, what's enforced, what leaks 2. **Packaging proposal** — tiers with the one-line job of each 3. **Upgrade moment placements** — where in the UI/code, with trigger conditions 4. **Friction fixes** — pricing page and checkout, ranked 5. **Quick wins vs structural changes** Start the report with today's date. If `REVENUE.md` already exists from a previous run, read it first and lead with what changed since. ## Rules - Monetize value delivered, not hostage features - Every gate needs a "still generous" free story - No monetizable product surface in this repo? Say so in a one-paragraph null report and stop — a null result is a valid finding. - If a `reports/` directory exists at the repo root, write the report there instead of the root. - Before asking, present the top findings as a ranked list in plain words - Report only — end by asking which changes to make
reports/ directory exists at the repo root, write the report there instead of the root.Reconstruct the signup → activation → habit funnel from code, count the steps, and rank every drop-off point.
Research real rivals on the web, then split the gaps: table stakes you must match vs differentiation bets only you can make.
Where an LLM feature genuinely earns its place — automation, drafting, summarization — and where it would be a gimmick.
Titles, metadata, structured data, crawlability, and social unfurls — every place a search engine or a shared link fails to find, index, or render your pages.