6d76305c6d
- 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
27 lines
1.1 KiB
Markdown
27 lines
1.1 KiB
Markdown
# SNS Software
|
|
|
|
**Parent:** SnS Network Solutions · **Tagline:** *Software Engineered to Fit*
|
|
|
|
## Scope
|
|
Custom business applications and automation built to solve a specific client
|
|
problem — not off-the-shelf products resold.
|
|
|
|
## Services
|
|
- Custom web/business applications
|
|
- Business process automation and internal tooling
|
|
- API integrations between existing systems
|
|
- Data pipelines, reporting, and dashboards
|
|
- Scripting/automation handed off with documentation
|
|
|
|
## Positioning
|
|
The problem-solving layer. Where the other divisions deploy infrastructure,
|
|
Software makes it do something specific to the client's operation.
|
|
|
|
## Liability & Ops Notes
|
|
- **Medium** — professional liability / E&O; IP ownership and licensing terms
|
|
matter. Contracts should specify who owns delivered code (parent favors client
|
|
ownership per the open-standards principle).
|
|
- **Entity:** operating subsidiary **SNS Software LLC** under SnS Network Solutions
|
|
Holdings LLC. **Liability tier: Medium** — form its own LLC when this becomes an
|
|
active business; until then it can run as an assumed name of an existing operating sub.
|