Business impact model

Skill sujanbhuiyan/Skills/skills/business-impact-model

A curated, installable marketplace of production-grade Agent Skills for Claude — research, SEO/GEO, finance, deliverables & engineering, indexed by topic, lifecycle & domain.

Install

npx -y skills add sujanbhuiyan/Skills --skill business-impact-model

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generates a multi-sheet .xlsx financial impact model with live cross-sheet Excel formulas, three scenarios (Conservative/Base/Optimistic), and a consistent input/formula/result color convention. Use when building a revenue projection, ROI model, growth-strategy financial model, or business case that needs a real working spreadsheet rather than static numbers.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.7 KB, as published. Nobody here has run it

Business Impact Model

What this does

Produces a client-ready, multi-sheet Excel workbook that turns a set of assumptions into a Year-1 revenue projection, an investment plan, and an ROI/KPI dashboard — with live cross-sheet formulas so every number recalculates when an input changes. It runs three scenarios side by side (Conservative / Base / Optimistic) from a single assumptions block.

When to use it

Building the financial half of a growth strategy or proposal.
A stakeholder needs a "what if we change this input" model, not a snapshot.
You need ROI, payback, and a KPI dashboard derived from revenue pillars.
You want consistent, auditable spreadsheet conventions across deliverables.

How to use it

Read references/model-structure.md to understand every sheet, its columns, and the color/formula conventions.
Generate the starter workbook (deterministic — always prefer the script over hand-building cells):
```
python scripts/build_model.py                       # -> business_impact_model.xlsx
python scripts/build_model.py /path/to/output.xlsx  # custom output path
```
The script requires openpyxl (pip install openpyxl); it exits with a clear message if missing. No network access.
Open the workbook and replace the blue placeholder inputs on Assumptions & Inputs with the client's real numbers across the three scenario columns. All black and green cells are formulas and update automatically — do not overwrite them.
Add or rename pillar/revenue-stream build sheets to match the engagement (one sheet per pillar). Mirror the existing formula pattern so the Y1 Revenue Projection, Investment Plan, and ROI & KPI Dashboard roll-ups keep referencing them.
Sanity-check: every result cell should change when you edit a blue input, and the workbook should open with zero #REF!/#DIV/0! errors.

Inputs

The revenue pillars / streams for the engagement (1+).
Per-scenario assumptions (price points, volumes, ramp curves, conversion, spend) for Conservative / Base / Optimistic.
Investment line items (retainer + project costs + tooling).

Output

business_impact_model.xlsx (default in the working directory, or the path you pass) — a workbook with these sheets: Cover & Summary, Assumptions & Inputs, one or more Pillar build sheets, Y1 Revenue Projection, Investment Plan, ROI & KPI Dashboard.

Notes & constraints

Formulas are real Excel formulas (e.g. =Assumptions!C7*'Pillar 1'!N8), never hard-coded results — this is the whole point of the model.
Color convention (kept identical everywhere): blue font = manual input, black font = in-sheet formula, green font = cross-sheet link, yellow fill = key result.
openpyxl writes formulas but does not evaluate them; open the file in Excel / Google Sheets / LibreOffice once to compute values.
Keep state in a single assumptions block so scenarios stay consistent; never duplicate an input across sheets — link to it.
Use forward-slash paths. Don't assume openpyxl is installed elsewhere.

Gives 1 of the 12 instructions most pdf office docs skills give

Counted across 635 of the 690 authors here whose files we hold, read 2026-08-06

extract text using pdfplumberin 92 of 635, across 25 files
create PDFs using reportlabin 83 of 635, across 16 files
read FORMS.md to fill out PDF formsin 80 of 635, across 13 files
OCR scanned PDFs using pytesseractin 77 of 635, across 10 files
merge or split PDFs using qpdfin 70 of 635, across 3 files
use Excel formulas instead of hardcoded calculated valueshere, and in 68 of 635, across 12 files
unpack edit xml and repack existing documentsin 63 of 635, across 8 files
document sources for hardcoded valuesin 61 of 635, across 9 files
write minimal python code without unnecessary commentsin 59 of 635, across 7 files
run the recalculation script after adding or modifying formulasin 58 of 635, across 6 files
fix all identified formula errors and recalculatein 58 of 635, across 6 files
format years as text stringsin 57 of 635, across 5 files

Said here and by no other author read

read the model structure reference
keep scenarios in a single assumptions block
maintain the specified cell color convention
use forward-slash file paths

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.