scope-cut://

[ scope-cut:// ] experimental

cat: ai model: @cf/meta/llama-3.1-8b-instruct

You're over-budget. Paste the planned delivery + the gap → get a ranked cut list (with impact) to close the gap.

// system prompt

You produce a ranked cut list to close a budget gap. User provides planned items + the gap.

Output format:

  Cut list (ranked — cut top-down until gap closes):

  N. CUT: <item>
     Saves: <time / money>
     Customer visibility if cut: <high / medium / low>
     Defer to: <next quarter / when X / never>
     Problem horizon: <when this becomes urgent>

  Must keep (would break the delivery to cut):
  • <item> — <why this is foundational>

  Running cut total: <how much was saved by the cuts above>
  Gap remaining: <how much still to close>

Rules:
- Rank cuts by best-effort dollars-or-time saved per customer-visibility unit. Cheapest visible cost goes first.
- Always flag at least 2 "Must keep" items so the conversation isn't a free-for-all.
- "Defer to" must be specific (next quarter / after pilot / when usage > N) — never "later".
- "Problem horizon" — when does the deferred item become urgent? Some are months away; some are immediate.
- If even cutting everything doesn't close the gap, say so at the end: "Even cutting all of the above gives only X. Remaining gap = Y — needs a budget / timeline conversation, not a scope conversation."

Planned delivery items + budget gap (e.g. "need to cut 2 weeks" or "over by $80k")

⚡ powered by Cloudflare Workers AI · quota deducted on success

// output

// sample output

Cut list (ranked — cut top-down until gap closes ~3 weeks):

1. CUT: Localisation — 3 languages
Saves: 1.5-2 weeks
Customer visibility if cut: medium (depends on target markets)
Defer to: next quarter
Problem horizon: 3-4 months (only if pursuing non-English markets)
Why first: Largest single saving with no impact on the core experience for the launch market.

2. CUT: Reporting dashboard
Saves: 4-5 days
Customer visibility if cut: low (internal tool)
Defer to: month 2 post-launch
Problem horizon: 6-8 weeks (need it before second exec update)
Why second: Internal users can survive on the existing data export for a few weeks.

3. CUT: Google Pay integration
Saves: 3-4 days
Customer visibility if cut: medium (depends on platform mix)
Defer to: next sprint after launch
Problem horizon: 2-3 months — Android conversion may suffer before this lands.
Why third: Apple Pay covers ~half the wallet flow; Google Pay can fast-follow.

4. CUT: Dunning emails (failed payment recovery)
Saves: 3 days
Customer visibility if cut: low at launch (no failed-payment volume until month 1-2)
Defer to: month 1 post-launch
Problem horizon: 4-6 weeks — once volume builds, revenue leakage starts. Real money.
Why last in this list: Lower up-front impact BUT becomes a revenue leak fast. Cut only if needed.

Must keep (would break the delivery to cut):
• Core checkout flow — foundational. Cutting this is "no product".
• 3D Secure handling — regulatory requirement in most EU jurisdictions. Cutting this is "can't launch in EU".
• Subscription auto-renewal — if this is a subscription product, this is the revenue engine. Without it, MRR doesn't exist.
• Refund self-serve workflow — every payment system needs this. Cutting it means customer support drowns in tickets.

Running cut total: ~3 weeks (cuts 1-3 alone close the gap; cut 4 only if we want buffer).
Gap remaining: 0 (closes cleanly with cuts 1-3).

// powered by cloudflare workers ai · quota deducted on success ← back to catalog