SnS Network Solutions — Division Directory

Parent: SnS Network Solutions Holdings LLC (holding company) Structure: Each division is a separate operating subsidiary LLC owned by the parent Holdings LLC. See ../legal-structure.md for the formation plan, fees, and timing. Inherits brand from: ../sns.md

The parent Holdings LLC owns the brand and every subsidiary but does no client work and carries no operating liability. Each division operates as its own LLC so its liability is walled off from the others. Divisions are formed as each begins real billable work — not all at once (per-entity bookkeeping is the real cost).

Status: SNS Infrastructure is Business #1 and now lives in its own folder: ../business-01-infrastructure/. The owner will stand it up and get it running self-sufficiently — intentionally kept right-sized, not scaled aggressively — before starting Business #2.

---

Division Index

Launch order is sequential and owner-chosen — one business at a time. Business #1 is SNS Infrastructure (active). When it stands on its own, the owner selects Business #2. The liability tier below is a separate signal: it tells you how urgently each division needs its own LLC once launched (and suggests a sensible order), but it is not a committed launch sequence.

Order	Division	Entity	Focus	Tagline	Liability Tier
#1 — ACTIVE	SNS Infrastructure	SNS Infrastructure LLC	Networking, cabling, wireless	The Physical Foundation	High (physical/on-site)
#2+ (TBD)	SNS Secure	SNS Secure LLC	Cameras, access control, cyber	Protected by Design	High (physical + cyber E&O)
#2+ (TBD)	SNS Support	SNS Support LLC	Managed services	Always On	Medium–High (SLA)
#2+ (TBD)	SNS Systems	SNS Systems LLC	Linux, servers, virtualization	Systems That Endure	Medium
#2+ (TBD)	SNS Cloud	SNS Cloud LLC	AWS, Azure, hybrid	Infrastructure Without Limits	Medium
#2+ (TBD)	SNS Web	SNS Web LLC	Sites, hosting, presence	Your Presence, Engineered	Low–Medium
#2+ (TBD)	SNS Software	SNS Software LLC	Custom applications	Software Engineered to Fit	Medium

When the owner does pick Business #2, the higher liability tiers (Secure, Support) are the natural front-runners — but that's a suggestion, not a commitment. Full rationale in ../legal-structure.md.

---

Boundary Notes (resolve before launch)

These divisions overlap in the source brand doc and need clear service lines so they don't compete internally:

• Managed Services appears under Systems, Support, and Cloud. Consolidate all recurring/managed-service contracts under SNS Support as the single "always-on" revenue engine; Systems and Cloud deliver project/build work that Support then maintains.
• SNS Secure blends physical security (cameras, access control — low-voltage install) and cybersecurity (audits, monitoring, hardening) — different insurance, licensing, and liability. Consider a future split into Secure (Physical) and Secure (Cyber).
• Cloud vs. Systems vs. Infrastructure — draw the line at where compute lives: Infrastructure = the wire and the LAN, Systems = on-prem servers/OS/virtualization, Cloud = anything hosted off-prem.

---

Brand Inheritance (all divisions)

• Colors: Navy #0A1628, Cyan #10C8D8, Secondary Blue #00A8C6, Accent #4CE0D2, White #F6F7F9, Dark Gray #20252B
• Accent-per-division system: one shared identity; each business keeps the navy base and gets a signature accent — parent = Cyan #10C8D8, Infrastructure = Signal Blue #1E6FFF, Secure = Amber, Systems = Emerald, Software = Violet, Web = Magenta, Cloud = Sky, Support = Orange. See ../sns-master-branding-prompt.md and each business's branding-prompt.md.
• Type: Geometric, legible open-source fonts (IBM Plex Sans / Inter for body; Oxanium / Sora / Rajdhani for display)
• Voice: Professional, clear, educational, transparent — never flashy or sales-driven
• Logo lockup: SNS wordmark + division descriptor (endorsed sub-brand — the parent brand always shows; a subsidiary never gets a standalone logo that hides SnS)