Skip to content

SnowOps — Client-Facing Presentation Plan

What this is: the master plan for every presentable asset a client sees, from the first cold touch to final offboarding. It is the design & production layer that sits on top of SnowOps's existing written content (docs/gtm/, docs/client-guides/, and the tool outputs in apps/).

Who it's for: SnowOps (Sagar/Nidhi) to plan and track the work, and external design tools/AIs (Claude design, Gamma, Figma AI, etc.) that will actually produce the designs. Every brief here is written to be self-contained — a designer who has never heard of SnowOps can read the primer + brand system + one asset brief and produce the deliverable.

Status: v0.1 · Created 2026-07-16 · Owner: Sagar (delivery) · Nidhi (compliance-claim review)


How to use this folder

If you are a designer / design AI: read these three files, in order, before touching any single asset: 1. 00-business-primer.md — what SnowOps is, who it sells to, the vocabulary. ~5 min. 2. 01-brand-system.md — the visual language: logo direction, palette, type, iconography, layout rules, do/don't. 3. The stage file that contains your asset's brief (see the registry below). Each brief names its source content file, its exact deliverable spec, and its design direction.

If you are SnowOps planning the work: the Asset Registry below is the single source of truth for state. Update the State column there as assets move through the pipeline. Do not track state anywhere else.

To actually get these designed: follow HANDOFF.md — the phased kit that says exactly what to give Claude (or Gamma/Figma/Word) and in what order, with a copy-paste prompt template.

Golden rule (non-negotiable): SnowOps sells to companies in or near a compliance audit. Over-claiming is an existential risk. No designed asset may state or imply a capability that isn't real, and no asset may promise "guaranteed certification." Every compliance/capability claim traces to a real shipped feature or is explicitly labelled (roadmap). See the primer §"The compliance-claim rule". Nidhi signs off every asset that makes a compliance claim before it ships to a client.


Folder map

docs/presentation/
├── README.md                 # this file — index + master state tracker
├── HANDOFF.md                # phased "what to give a design AI, in what order" kit
├── 00-business-primer.md     # self-contained SnowOps context for an external designer
├── 01-brand-system.md        # visual language / design system brief
├── brand/                    # PA00 — the brand kit itself
│   ├── logo/                 #   Signet vector master (mark, lockups, favicon)
│   ├── templates/            #   deck master (.pptx) + document master (.docx) + logo PNGs
│   └── report-theme/         #   PA08 — the theme behind the generated audit report
├── deliverables/             # the real, built client-facing assets
│   ├── PA04-one-pagers/      #   3 one-pagers (Letter + A4)
│   ├── PA06-capabilities-deck/
│   └── PA09-sample-audit/
└── stages/
    ├── 1-land.md             # PA01–PA09  Prospecting → Discovery call → Discovery Audit
    ├── 2-close.md            # PA10–PA16  Proposal/SOW → Contract
    ├── 3-deliver.md          # PA17–PA21  Onboarding → Delivery & Handover
    └── 4-retain.md           # PA22–PA27  QBR/Expansion → Offboarding → Credibility

The client journey (at a glance)

LAND ─────────────────────────► CLOSE ──────────► DELIVER ─────────► RETAIN / EXPAND
 │                                │                 │                  │
 1. Cold touch / prospecting      4. Proposal & SOW  6. Onboarding      8. QBR / posture report
 2. Discovery call                5. Contract        7. Delivery &      9. Offboarding
 3. Free Discovery Audit (WEDGE)                        handover        + credibility (trust center)

The free Discovery Audit (stage 3) is the single most important presentable asset — it is the wedge that converts a cold prospect into a paying engagement. Design investment should be weighted toward it, the capabilities deck, the proposal, and the QBR posture report.


Asset Registry & State Tracker

State vocabulary: ⬜ Not started · 🟨 Content ready — needs design · 🟦 In design · 🟪 Designed — pending sign-off · 🟩 Designed & approved · — N/A / roadmap

🟪 exists because "designed" and "approved" are different things. An asset is 🟪 when it's built and QA'd but Nidhi hasn't signed the compliance claims yet — it must not reach a client in that state. Only Nidhi's sign-off moves 🟪 → 🟩.

Priority: P0 = needed to run the sales motion today · P1 = needed to close & deliver well · P2 = polish / scale.

ID Presentable asset Stage Format Source content Priority State
PA00 Brand identity system (logo, palette, type, templates) Foundation Brand kit 01-brand-system.md · masters P0 🟩
PA01 Website / landing page 1 Prospect Web Y1, Y8 one-pagers P0
PA02 LinkedIn presence kit (banners, post templates) 1 Prospect Social images Y1, Y4 P1
PA03 Email signature + cold-email formatting 1 Prospect HTML email Y4 P1
PA04 Solution one-pagers (Discovery Audit / Baseline / Advanced) 1 Prospect 1-page PDF ×3 (Letter + A4) Y8 · built P0 🟪
PA05 Vertical one-pagers (SaaS / FinTech / HealthTech) 1 Prospect 1-page PDF ×3 Y8 P1 🟨
PA06 Capabilities deck (12 slides) 2 Discovery call Slide deck (.pptx) Y8 deck-outline · built P0 🟪
PA07 Discovery-call agenda / leave-behind 2 Discovery call 1-page PDF Y5 P2 🟨
PA08 Discovery Audit report (branded) 3 Audit (WEDGE) Multi-page PDF/HTML apps/discovery-auditor/ · theme P0 🟪
PA09 Sanitized sample audit 3 Audit Multi-page PDF Y9 sample · built P0 🟪
PA10 Proposal / SOW documents (QW / Baseline / Advanced) 4 Proposal Multi-page PDF ×3 Y6 P0 🟨
PA11 Findings-to-roadmap document 4 Proposal Multi-page PDF Y6 findings-to-roadmap P1 🟨
PA12 Compliance coverage matrix 4 Proposal Infographic / 1–2pp Y7 P1 🟨
PA13 Reference-architecture blueprints (SaaS / FinTech / HealthTech) 4 Proposal Diagram + BOM ×3 Z1–Z3 P1 🟨
PA14 Pricing & packaging sheet 4 Proposal 1–2-page PDF Y2 P1 🟨
PA15 Case study 4 Proposal 2-page PDF Y9 case-study.template P1 🟨
PA16 Contract pack (MSA / DPA / NDA / SOW / cloud-access auth) 5 Contract Branded document templates Y12 P1 🟨
PA17 Kickoff / welcome deck 6 Onboarding Slide deck Y11, client-guides P1
PA18 Onboarding & access-request guide 6 Onboarding Checklist PDF apps/client-bootstrap/ P1 🟨
PA19 Milestone handover guides 7 Delivery Multi-page PDF ×N docs/client-guides/ P1 🟨
PA20 Architecture-diagram deliverable 7 Delivery Styled diagram apps/diagram-generator/ (V2) P1 🟨
PA21 Operational runbook pack 7 Delivery Styled PDF/site apps/runbook-generator/ (V3) P2 🟨
PA22 Client Cloud Posture Report (QBR) 8 Retain Multi-page PDF/HTML apps/posture-report/ (V5) P0 🟨
PA23 Client Overview dashboard 8 Retain Grafana theme J8 (roadmap) P2
PA24 Compliance dashboard 8 Retain Web app theme apps/compliance-dashboard/ (S2) P2 🟨
PA25 Expansion / upsell one-pager 8 Retain 1-page PDF Y11, V5 upsell teasers P2
PA26 Offboarding / exit pack 9 Offboard Multi-page PDF docs/runbooks/offboarding/ (W4) P2 🟨
PA27 Trust-center page (public credibility) Cross-cutting Web trust-center/ P2

The wedge cluster is built. deliverables/ holds the real assets — PA09 sample audit (PDF + self-contained HTML), PA06 capabilities deck (12 slides + speaker notes), PA04 one-pagers ×3 (Letter + A4) — plus the PA08 report theme that brands the generated audit report. All are 🟪: built and QA'd, awaiting Nidhi's compliance sign-off, and three specific claim issues are listed in deliverables/README.md.

Reading the State column today: most assets are 🟨 Content ready — needs design because the words already exist in the repo. PA00 is 🟩: the brand kit is complete — direction "Signal" + mark "Signet" locked, plus both masters shipped at brand/templates/ as editable Office files (deck .pptx → Google Slides/Canva; document .docx → Google Docs/Canva; and a Pandoc theme that brands auto-generated reports). Phase 1 is unblocked. Two open items ride alongside, neither blocking design work: IP clearance for the logo (a legal gate before public launch — see brand/logo/README.md) and wordmark-outlining/PNG export.


  1. PA00 — Brand system.Complete. Direction "Signal" + mark "Signet" locked (tokens in 01-brand-system.md); vector logo master in brand/logo/; deck + document masters in brand/templates/. Everything below is unblocked.
  2. The wedge cluster (P0).Built — PA08 report theme + PA09 sample + PA06 deck + PA04 one-pagers, all in deliverables/, all 🟪 pending Nidhi. Remaining in this cluster: PA01 website, and wiring the theme into apps/discovery-auditor (its PDF path still renders unbranded via xelatex — see the theme README).
  3. The close cluster (P0/P1): PA10 proposals → PA14 pricing → PA12 coverage matrix → PA13 reference architectures → PA15 case study.
  4. The deliver cluster (P1): PA17 kickoff deck → PA18 onboarding guide → PA19 handover guides → PA20 diagram styling.
  5. The retain cluster (P0/P2): PA22 QBR posture report → PA25 upsell one-pager → PA24/PA23 dashboards → PA26 offboarding → PA27 trust center.

Change log

  • v0.6 (2026-07-17): The wedge cluster is builtdeliverables/. PA08 shipped as a report theme (Pandoc HTML template + CSS + Chrome renderer) rather than a file, because the audit report is generated per client — verified against the auditor's real output shape. PA09 sample audit, PA06 12-slide deck with speaker notes, PA04 three one-pagers (Letter + A4, each asserted to one page). All 🟪 pending Nidhi. New state 🟪 Designed — pending sign-off added to the vocabulary. Claim issues surfaced while building: the Y9 sample's severity split is internally inconsistent (2/6/3 claimed vs 2/7/2 enumerated — corrected in the deliverable, source still needs fixing); the "23 passing test suites" claim in Y1/Y8 doesn't trace and was left off the deck; PA04 Advanced keeps its (roadmap) tags pending Nidhi, though several tagged assets are now code-complete.
  • v0.5 (2026-07-17): Document master shipped → PA00 🟩 complete, Phase 1 unblocked. brand/templates/snowops-doc-master.docx — editable in Google Docs + Canva; cover, usage rules, style gallery, and scaffolds for the audit report / proposal / handover guide. Built on snowops-doc-reference.docx, a Pandoc --reference-doc theme (derived from Pandoc's own default so every generated style is branded) — this is the theme for the auto-generated Discovery Audit report (PA08). Serves PA09/PA10/PA11/PA19/PA26.
  • v0.4 (2026-07-17): Presentation/slide master shipped as an editable .pptx (Google Slides + Canva ready) at brand/templates/ — 10 branded layouts on the Signal system + Signet mark, native chart, reusable logo PNGs, generator source. Advances PA06 → 🟦.
  • v0.3 (2026-07-17): Logo mark "Signet" selected (a stone cleft by a negative-space checkmark; the persimmon shard is the cut). Vector master produced at brand/logo/ (mark / on-dark / mono ×2 / favicon / horizontal + stacked lockups) and locked into 01-brand-system.md §2 — pending IP clearance before public launch.
  • v0.2 (2026-07-16): Brand direction "Signal" locked (attention/conversion-optimised) — 01-brand-system.md rewritten with concrete tokens (light + dark palette, IBM Plex type, soft geometry, reserved-Action-color rule). PA00 → 🟦 In design.
  • v0.1 (2026-07-16): Initial plan — 28 presentable assets (PA00–PA27) mapped across 9 journey stages, with business primer + brand-system brief + 4 stage brief files.