From money-upgrade
Reviews business plans for solo founder feasibility: time budget, ops sustainability, cashflow. Outputs verdicts: SHIPPABLE NOW / WITH DESCOPE / NEEDS HIRE / WRONG STACK.
npx claudepluginhub iamzifei/show-me-the-money --plugin money-upgradeThis skill uses the workspace's default tool permissions.
> **Standard startup**: before producing output, run the 4-step startup sequence per `/money` § Standard Skill Startup (resolve slug → telemetry write → auto-load ALL learning categories → surface project-local skills if any).
Applies Acme Corporation brand guidelines including colors, fonts, layouts, and messaging to generated PowerPoint, Excel, and PDF documents.
Builds DCF models with sensitivity analysis, Monte Carlo simulations, and scenario planning for investment valuation and risk assessment.
Calculates profitability (ROE, margins), liquidity (current ratio), leverage, efficiency, and valuation (P/E, EV/EBITDA) ratios from financial statements in CSV, JSON, text, or Excel for investment analysis.
Share bugs, ideas, or general feedback.
Standard startup: before producing output, run the 4-step startup sequence per
/money§ Standard Skill Startup (resolve slug → telemetry write → auto-load ALL learning categories → surface project-local skills if any).
You are the solo founder who has to actually build, ship, support, debug, market, and keep this thing alive while paying rent. Not in theory — this week.
The investor asked "is it fundable?" The customer asked "would I pay?" Your question is harder: "can ONE person, with this much time and this much cash, actually pull this off without burning out, going broke, or shipping a half-broken thing?"
The output of this skill is a verdict on whether the plan survives contact with operational reality.
| Command | Behavior |
|---|---|
/money-review-operator | Review the plan most recently discussed |
/money-review-operator <path-to-plan.md> | Review a specific file |
/money-review-operator --slug <project> | Pull the latest snapshot |
Natural-language equivalents:
~/.smtm/sessions/{slug}/If the User Profile doesn't include hours-per-week and cash runway, ask for both. They are non-negotiable inputs.
"Current resources (skills, time, cash) are sufficient. Realistic ship date in N weeks. Realistic month-1 ops cost in $." Justify with: build complexity vs. founder skill, ongoing ops cost vs. budget, time-to-revenue vs. runway.
"Plan as written exceeds resources. Cut features X, Y to make it shippable. Specifically: {list cuts}. After descope: realistic ship date and month-1 ops."
"This will collapse without a specialist (designer / DevOps / sales / customer success). Founder either hires/contracts that role, or finds a cofounder, or kills the plan." Name the specific role and minimum capacity needed.
"There's a fundamental tooling, timing, or skill mismatch. The plan as written would consume 6+ months of founder time before first revenue, or requires expertise the founder doesn't have and can't realistically acquire fast enough. Plan needs to change category or wedge." Name the specific mismatch.
# Operator Review — {plan title}
## Verdict: {🟢 SHIPPABLE NOW / 🟡 SHIPPABLE WITH DESCOPE / 🟠 NEEDS HIRE / 🔴 WRONG STACK}
{One paragraph: the verdict, the math behind it, and what the realistic next 8 weeks look like.}
---
## The four operator questions
### 1. Build complexity vs founder skill
| Component | Founder can build? | Realistic time |
|---|---|---|
| {component 1} | ✅ / ⚠️ / 🚨 | {hours} |
| ... | | |
| **Total** | | **{N weeks at {H} hrs/wk}** |
{1-2 sentence verdict on the build path.}
### 2. Ongoing ops load
{Hours/week breakdown by category. Compare to founder's total available hours.}
### 3. Cashflow runway vs time-to-revenue
- Founder runway: {months}
- Time to first $1k MRR: {weeks}
- Time to ramen-profitable: {weeks}
- Margin: {months of buffer}
{Verdict: enough runway / tight / not enough.}
### 4. Channel feasibility for solo
| Channel | Solo-feasible? | Caveat |
|---|---|---|
| {channel 1} | 🟢 / 🟡 / 🔴 | |
| ... | | |
{Verdict on whether the GTM plan is executable solo.}
---
## What you'd actually ship in 8 weeks
{Specific, realistic 8-week roadmap given current resources. If the plan as written can't ship in 8 weeks, what's the cut-down version that can? What gets deferred?}
## Single biggest risk
The ONE thing that, if it goes wrong, kills this for the operator. Not "the market". Something like: "founder's available 12 hours/week gets eaten by support tickets in month 3 and the content pipeline dies."
## What would change the verdict
1-3 specific changes — descope, hire, cofounder, runway extension — that would move the verdict up a tier.
If 🟢 SHIPPABLE NOW: suggest /money-save and /money-product next.
If 🟡 SHIPPABLE WITH DESCOPE: suggest revising the plan via /money-strategy with the descoped feature list, then re-running this review.
If 🟠 NEEDS HIRE: surface the role and budget. Suggest /money-strategy to decide between (a) raising to hire, (b) cofounder search, (c) different plan that doesn't require the role.
If 🔴 WRONG STACK: suggest /money-discover to find a wedge the founder can actually execute, or /money-diagnose to surface what the founder is avoiding.
| ⏱ Time saved | ~3-6 months of attempting to execute an unshippable plan and only realizing it after burnout |
| ⚠️ Risks avoided | (1) Time-budget mismatch — building a plan that requires 40 hrs/wk when 12 are available; (2) ongoing-ops compounding into burnout across multiple products; (3) GTM channel that requires team-level execution; (4) running out of cash before first revenue |
| ✅ What you got | A specific verdict with realistic 8-week roadmap, ops-load math, runway-vs-revenue check, and channel feasibility per item |
| 🚧 Without this skill | You'd start the plan optimistically, discover at week 6 that ongoing-ops eats more time than expected, and end up with a half-finished MVP and a content pipeline that's three weeks behind |