Skip to content
Agentmart
Submit a tool

what-if

Run a quick what-if on 2-4 budget scenarios with revenue and ROI estimates.

Skill by indranilbanerjee

IndexedMIT★ 909
Write a review

Chalk Labs

Need help deploying what-if?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/indranilbanerjee-what-if

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Run a quick what-if on 2-4 budget scenarios with revenue and ROI estimates. "compare two budget splits"

Use cases: finance

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/what-if

What's inside

Skill name
what-if
Description
Run a quick what-if on 2-4 budget scenarios with revenue and ROI estimates. "compare two budget splits"
License
MIT
Instructions
39 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# /digital-marketing-pro:what-if

## Purpose

Quick scenario comparison tool. Test 2-4 marketing scenarios against each other — different budget allocations, channel mixes, or strategic approaches — and see projected outcomes side-by-side. This is the lighter, faster alternative to full Monte Carlo simulation (`/digital-marketing-pro:simulate`). Where simulate runs thousands of iterations with full probability distributions, what-if uses point estimates with simple variance bands to give directional answers in minutes. Use it for rapid decision-making when you need a quick read on "should we do A or B?" without the statistical depth of a full simulation — team meetings, Slack discussions, quick planning calls, or narrowing down options before running a deeper analysis.

> **Simulated output — not a forecast.** what-if projections are directional point-estimates produced by `revenue-simulator.py` from your stated assumptions and historical benchmarks, not measured predictions. Treat every scenario number as a planning aid: validate the ROI assumptions against your own data before committing budget. All example dollar figures in this skill are SYNTHETIC (illustrative only — never reuse these numbers).

## Input Required

The user must provide (or will be prompted for):

- **Scenarios to compare**: 2-4 named scenarios, each with channel-level budget allocations and expected ROI per channel. Examples: "Scenario A: Heavy paid — $50K Google Ads, $30K Meta, $10K email" vs "Scenario B: Content-led — $20K Google Ads, $15K Meta, $40K content, $15K SEO." Each scenario needs a descriptive name and channel budget breakdown. If the user provides only high-level descriptions ("more on paid, less on organic"), ask for specific dollar allocations or percentage splits
- **Current baseline**: The existing budget allocation and recent performance as the reference point for comparison — what the brand is doing right now so each scenario shows a clear delta. If not provided, pull from brand context historical data
- **Evaluation criteria (optional)**: What matters most for this decision — total revenue, ROI efficiency, risk level, speed to impact, or a weighted combination. Defaults to expected revenue if not specified
- **Time horizon (optional)**: How far out to project — defaults to 3 months. Shorter horizons favor paid channels, longer horizons favor organic and content investments due to compounding effects

## Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Pull historical channel performance, recent ROI data, and known benchmarks to calibrate scenario projections. Also check for guidelines at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json`. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with industry defaults.
2. **Define current baseline and alternative scenarios**: Structure the current state as Scenario 0 (baseline) with actual recent performance data. Then define each user scenario with channel budgets and ROI assumptions — using brand historical data where available, industry benchmarks where not. Flag any assumptions that differ significantly from historical performance so the user can validate them.
3. **Run quick simulation**: Execute `revenue-simulator.py` in what-if mode — a simplified projection that calculates expected revenue per scenario using point estimates with variance bands (not full Monte Carlo), applies basic diminishing returns for channels near saturation, and accounts for channel ramp time (SEO and content take months to deliver, paid is immediate). Faster execution, directional accuracy.
4. **Compare projected outcomes**: Build a side-by-side comparison table showing each scenario's projected revenue, total ROI, delta versus baseline (both absolute dollars and percentage), channel-level contribution, and a simple risk indicator (low/medium/high based on concentration and assumption sensitivity). Rank scenarios by the user's evaluation criteria.
5. **Identify best scenario and key trade-offs**: Select the scenario with the best expected return and the scenario with the best risk-adjusted return (if different). Articulate the key trade-offs between the top options — what you gain, what you give up, and what assumptions would need to hold true for each to deliver as projected.

## Output

A concise scenario comparison containing:

- **Side-by-side scenario comparison**: Each scenario showing projected revenue, total ROI, cost, and risk level — formatted as a clean comparison table with the baseline as the reference column and deltas highlighted for each alternative
- **Delta versus current baseline**: Per scenario, the absolute and percentage change in projected revenue, ROI, and cost compared to what the brand is doing today — making it immediately clear whether each scenario is an improvement and by how much
- **Recommendation with reasoning**: The recommended scenario with a clear explanation of why — balancing expected return, risk, feasibility, and alignment with brand goals. If two scenarios are close, explain what would tip the decision one way or the other
- **Key trade-offs between top scenarios**: The specific gains and sacrifices of choosing one top scenario over another — channel dependencies, ramp time differences, risk concentration, and reversibility if the bet doesn't pay off

## Agents Used

- **marketing-scientist** — Scenario modeling with point estimates and variance bands, channel ROI projection with ramp time and diminishing returns adjustments, side-by-side comparison analysis with delta calculations, risk assessment based on assumption sensitivity and channel concentration, and recommendation synthesis balancing expected return against risk profile and strategic fit

From indranilbanerjee/digital-marketing-pro, MIT.

More from indranilbanerjee/digital-marketing-pro

Signals

Stars
909
Forks
146
Open issues
0
Last commit (this folder)
Oct 9, 2026 (21 days ago)
Last release
Jul 29, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from indranilbanerjee

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get what-if running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying what-if?

CallGet help
Cite this page

what-if skill. Agent Mart. https://agentmart.dev/skills/indranilbanerjee-what-if (last updated 2026-10-24)