From sizing math to signed deal.
Deal Pack eats the JSON exports from your RVTools Analyzer, Server Sizer, Storage Sizer and Network Sizer — and spits out the thing that actually moves a deal: a customer-facing refresh proposal with an executive summary, a consolidated BOM, a quote sanity checklist, a TCO model, and a downloadable report. 100% in your browser, nothing uploaded.
How it works
1️⃣ Import the suite's exports
Drop in the portable .json project files from the RVTools Analyzer, Server Sizer, Storage Sizer and Network Sizer (💾 Projects → Export in each app). Any subset works — the proposal fills in whatever you've got. No exports handy? The demo deal loads a full synthetic engagement in one click.
2️⃣ Get the proposal
Deal Pack recomputes every number with the same math as the source apps — no re-typing, no drift. Out comes an executive summary, current-state findings, the proposed architecture per cluster, and one consolidated BOM: servers, switches and storage capacity in a single list.
3️⃣ Check, cost, ship
Work the quote sanity checklist (optics, phantom cores, oversubscription, rails, PSUs — the classics that cause quote rework), sanity-check the money on the TCO tab, then download the whole thing as a clean standalone HTML report you can send to the customer.
What it reads
| App export | What Deal Pack takes from it |
|---|---|
rvtools-analyzer-*.json | Current-state findings: hosts, VMs, clusters, licensed cores (16-core/socket min), snapshots |
server-sizer-*.json | Per-cluster builds: platform, host counts, binding constraint, spares, licensed cores |
storage-sizer-*.json | Per-pool raw capacity required by the horizon year, with protection & reduction settings |
network-sizer-*.json | TOR + FC switch plan, net-new vs existing inventory, oversubscription |
Each import is validated against the real export envelope of its app — wrong-app files get a clear "drop it on the matching card" message instead of silent garbage.
Honest limitations
- Re-export to refresh. Deal Pack recomputes from the JSON you import. If you re-tune a sizer afterwards, export again and re-import — it won't know.
- The TCO tab is a model, not a quote. No taxes, financing, discount tiers, or vendor price lists. Garbage in, garbage out — the inputs are yours.
- The BOM is quantities + descriptions, not orderable SKUs. Storage lines are capacity requirements ("not a SKU") — translate them into array configs in your vendor tool.
- Demo data is synthetic. It exists so you can see the whole flow in one click; don't quote it.
FAQ
Do I need all four imports?
No. Any subset works — import one sizer and you'll get that section of the proposal. The more you import, the more complete the pack.
Where does my data go?
Nowhere. Everything runs in your browser: the proposal, the BOM, the checklist, the TCO. Named projects and autosave use localStorage — still on your machine, never uploaded. Very large imports skip browser saves (you'll get a nudge) and the portable Export file still works.
The numbers look off — what gives?
Deal Pack runs the exact same math as the source apps, so a mismatch means the import is stale: re-export from the app after your last tuning change, then re-import here.
Can I send the report to a customer?
That's what it's for — the downloaded HTML is standalone and prints cleanly. But read it first: it's generated from your inputs, and you're the SE signing off on it.
Why do storage BOM lines say "not a SKU"?
Because the storage sizer outputs a capacity requirement (TB raw by year N), not something you can order. Map each line to array/shelf configs in your vendor configurator.