- Move infrastructure into businesses/00-infrastructure; add 01-06 numbered dirs ordered by importance (secure, support, systems, cloud, web, software) - Add per-business branding.html (accent color scheme + ChatGPT logo prompt) - Add NN-name.md scaffold/research/todo docs for the six planned divisions - Make divisions/ the formal-docs library: parent + infrastructure briefs, legal-structure, investment-research - Add root README map and businesses/ index; empty READMEs per dir - Fix all relative links broken by the moves
29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
# SNS Support
|
||
|
||
**Parent:** SnS Network Solutions · **Tagline:** *Always On*
|
||
|
||
## Scope
|
||
Ongoing managed services — the recurring-revenue engine that maintains what the
|
||
other divisions build. Recommended single home for **all** managed-service
|
||
contracts (consolidating overlaps from Systems and Cloud).
|
||
|
||
## Services
|
||
- Managed IT / helpdesk and remote monitoring (RMM)
|
||
- Patch management and preventive maintenance
|
||
- Backup monitoring and disaster-recovery testing
|
||
- SLA-based response and escalation
|
||
- Recurring documentation and health reporting
|
||
|
||
## Positioning
|
||
The relationship layer — where "long-term partnership" (a core brand promise)
|
||
actually lives. Turns one-time projects from every division into durable,
|
||
recurring client relationships.
|
||
|
||
## Liability & Ops Notes
|
||
- **Medium–High** — SLA commitments create contractual exposure; downtime and
|
||
data-loss claims are the main risks. Contracts and E&O coverage are critical.
|
||
- **Entity:** operating subsidiary **SNS Support LLC** under SnS Network Solutions
|
||
Holdings LLC. **Liability tier: Medium–High** (SLA/contractual exposure +
|
||
recurring revenue worth ring-fencing) — form its own LLC when launched. A natural
|
||
Business #2/#3 candidate.
|