START HERE — SnowOps client-facing assets¶

For: Nidhi (review + compliance sign-off) and Sagar. Status: everything here is built and QA'd, but not approved. Nothing in this folder should reach a client until Nidhi signs off the claims.

What's in this folder¶

Folder	What's in it
1 — Brand kit	The logo, the brand system, and the two master templates every future asset is built from
2 — Land	The capabilities deck and the three solution one-pagers — what a prospect sees before the audit
3 — Audit	The sanitized sample audit — the "here's exactly what you'll get" proof

Opening things: the .pptx deck opens in Google Slides and the .docx masters open in Google Docs (right-click → Open with). One-pagers and the sample audit are PDFs — comment directly on them in Drive.

⚠️ Read this before editing anything¶

The repo is the source of truth, not this folder. Every asset here is generated from source files in the snowops-sales repo. These are copies for reviewing.

That means: edits made here will be silently lost the next time an asset is rebuilt. So:

✅ Comment on anything — that's the whole point of this folder, and comments are what Sagar works from.
✅ Suggest wording changes in comments.
❌ Don't rely on direct edits sticking. If you change something here, tell Sagar so the change goes into the repo source too.

Nidhi — what we need from you¶

Every asset here makes compliance or capability claims, which is why they're all sitting at "pending sign-off." Three specific things need your call, all found while building these:

1. The sample audit's numbers don't add up¶

The source copy says the sample environment has "2 critical, 6 high, 3 medium" findings. But its own list of findings adds up to 2 critical, 7 high, 2 medium. (The total, 11, is right — the split isn't.)

The PDF in this folder uses the corrected split. The original source still has the wrong numbers and is being fixed separately. Please confirm 2 / 7 / 2 is right before this goes to any prospect.

2. "23 passing test suites" — we can't prove it, so it's not on the deck¶

Our positioning doc and the deck outline both claim "23 passing test suites", citing the Terratest folder. That folder now holds roughly 68 test functions across ~35 files, and the "23" appears to trace to a different runbook test tier instead.

We couldn't verify the number, so the deck says "tested before shipped — Terratest, Conftest, Kyverno" with no number. That claim is true and checkable. A wrong number in front of an engineer costs us more than no number. Decide whether to fix the source claim or drop it.

3. Advanced's (roadmap) tags are untouched — on purpose¶

The Advanced one-pager tags most of its capabilities (roadmap), exactly as the approved copy has them. Several of those (the E-series evidence adapters, Sentinel, SOAR playbooks, the compliance scorecard, WAF/DDoS) are now code-complete in the repo.

Removing a (roadmap) tag upgrades a claim, and that's your call, not a build step. Please review which — if any — have earned the tag's removal. When in doubt it stays; under-claiming is survivable, over-claiming isn't.

Also worth your eye¶

The deck's coverage slide (9) shows qualitative bands — "high", "partial", "strong" — not percentages, because our coverage matrix has no computed percentages yet. Inventing one is the exact over-claim that would sink us. The methodology note is on the slide.
No prices appear anywhere. The pricing slide and one-pagers show structure only (fixed project + retainer). Sagar owns the final numbers.
The logo is pending IP clearance (reverse-image + trademark search) before any public launch. Fine to use in these private reviews.
Language rule, applied throughout: "audit-ready", "audit-defensible", "compliant by construction" — never "certified", never "guaranteed".

Sagar — what's still open¶

The audit report (PA08) is generated per client by the discovery-auditor tool. The design is done; wiring the tool's PDF output to use it is app work, still to do. The sample audit here shows what the theme produces.
PA01 (website) is the next asset in the plan.
Full plan, state tracker and build instructions live in the snowops-sales repo at 02-brand-and-presentation/.