Service Boundary Statement

SoAtomic is a managed service provider focused on technology assessment, problem solving, security, administration, documentation, and long-term stewardship for businesses and organizations across industries.

SoAtomic does not create or redesign client websites, produce site content, manage editorial calendars, publish routine page updates, operate marketing campaigns, or act as a creative agency. SoAtomic also does not sell computer hardware or software of any kind.

When a client's public site affects technology operations, SoAtomic may support the surrounding infrastructure: domain ownership, DNS, SSL, hosting, uptime, security, administrative access, backups, vendor coordination, and incident triage.

Creative, editorial, merchandising, and campaign work remains with the client or a qualified specialist.

When clients require hardware, mobile devices, or software licenses; SoAtomic will obtain a minimum of three competetive bids (unless instructed otherwise by the client) and will always value engineer the best solution prioritizing a balance between quality, functionality, and reasoable spend outlined by the client.

Foreword

Why This Playbook Exists

Technology providers often document what they sell and how they sell it. Fewer explain why they operate the way they do, how they define responsibility, or which principles guide their decisions.

The SoAtomic Playbook establishes the philosophy, service model, operational boundaries, and decision-making framework for the SoAtomic managed technology workshop. It is not a marketing brochure or sales script. It is the operating reference for how SoAtomic assesses environments, delivers improvements, supports organizations, coordinates specialists, protects client ownership, and communicates risk.

Every service, recommendation, policy, proposal, support process, automation, public statement, and future offering should be consistent with the principles established here. When several technically valid choices exist, this Playbook helps identify the choice that best reflects the organization SoAtomic intends to be.

Technology changes constantly. The commitment to clarity, stewardship, and client ownership should not.

How to Use This Document

This Playbook is both a guide and a reference.

New readers should begin with the mission and principles. Those sections provide the context for the service model and policies that follow. Readers seeking a specific answer may go directly to the applicable chapter; each chapter is intended to be useful on its own without contradicting the rest of the document.

The Playbook is organized around four questions:

1. Why does SoAtomic exist?

2. What does SoAtomic believe?

3. How does SoAtomic operate as an MSP?

4. What does SoAtomic assess, improve, and support?

Whenever possible, the Playbook explains why before explaining how. The reasoning behind a decision is as important as the procedure itself.

Authority and Version Control

The SoAtomic Playbook is the primary reference for how the Workshop operates. Proposals, public site content, service descriptions, support agreements, internal documentation, AI prompts, standard operating procedures, and client-facing materials should align with it.

If another document conflicts with this Playbook, the most recently approved source governs in this order:

1. Signed client agreement or statement of work for that engagement

2. Current published service and pricing documentation

3. This Playbook

4. Supporting procedures and templates

This order ensures that a current legal or service commitment is never overridden by an older internal description. Conflicts should be corrected in the next Playbook revision.

Changes should reflect lessons learned, service improvements, material changes in technology, or changes in organizational responsibility. They should not be driven solely by trends, temporary sales pressure, or competitor language.

Founder's Letter

Why I Built SoAtomic

Technology has never been more accessible, but it has also never been more fragmented. Even small organizations are expected to manage identity, email, endpoints, cloud services, security, domains, vendors, automation, subscriptions, and a growing collection of specialized platforms. None of these systems is particularly useful in isolation. They become valuable when they work together reliably and remain understandable to the people who depend on them.

Throughout my career, I have been drawn to the work behind those systems: establishing stable foundations, improving cloud infrastructure, documenting environments, and helping people understand the technology that supports their work. The objective has remained consistent: build something dependable, explain it clearly, and leave it in better condition than I found it.

SoAtomic grew from the belief that organizations deserve thoughtful technology stewardship. Many teams do not have an internal IT department or an enterprise budget, but they still deserve secure systems, honest advice, professional documentation, and support that respects their work.

I did not start SoAtomic to become the largest provider. I started it to build the kind of technology partner I would want to hire.

A Managed Technology Workshop

SoAtomic is an MSP, but the Workshop metaphor remains important. A workshop evaluates, repairs, improves, maintains, documents, and hands off work with care. It values craftsmanship over volume and long-term reliability over short-term sales.

The MSP model provides continuity: support does not end when a configuration is completed. People join and leave, permissions drift, vendors change, devices age, threats evolve, and organizational priorities shift. Stewardship means helping the environment evolve without allowing it to become opaque or dependent on a single provider.

Giving Businesses and Organizations Solid Technology Footing

The need for dependable technology is just as real for a nonprofit, foundation, chamber, clinic, school, faith organization, community program, professional office, local business, or growing company as it is for a large enterprise. These organizations frequently carry comparable responsibilities with fewer staff, tighter budgets, mixed access patterns, regulatory or contractual requirements, and limited time for technology administration.

SoAtomic helps establish solid technology footing before adding unnecessary complexity. Sometimes the right answer is stronger identity governance. Sometimes it is cleaning up access, documenting a cloud environment, securing endpoints, reducing unused licenses, stabilizing DNS, implementing an automation, or coordinating the right specialist.

The solution changes. The objective does not: reduce friction, improve reliability, protect organizational data, and give leaders confidence in the systems supporting their work.

Why Trust Matters More Than Technology

Platforms change. Trust is harder to build and easier to lose.

SoAtomic is built around clear expectations instead of open-ended promises. Services have defined boundaries. Pricing is published and straightforward. Clients own their accounts, domains, configurations, and data. Documentation is part of every engagement. When a relationship ends, clients should be able to continue without unnecessary obstacles.

Not every recommendation should produce more work for SoAtomic. Sometimes the best advice is to retain what already works, engage another specialist, or postpone a change until the timing and budget are appropriate. Long-term relationships are built by putting the client's interests first.

If SoAtomic has done its job well, the client leaves every engagement with a stronger environment, better documentation, clearer options, and greater confidence.

How to Read This Playbook

Intended Audience

Business Owner

This Playbook is the primary reference for service boundaries, operating principles, technology standards, and future decisions. It should be reviewed before introducing a service, changing a plan, adopting a platform, or making an operational commitment.

SoAtomic Collaborators

Employees, contractors, and specialist partners should use this Playbook to understand how SoAtomic approaches assessments, implementation, support, communication, client ownership, and handoffs. Shared principles allow several contributors to present one coordinated experience.

AI Engineering Agents

AI-assisted tools should treat this Playbook as the source of truth for SoAtomic terminology, service definitions, MSP boundaries, technology standards, and client-facing claims. AI should implement documented decisions rather than inventing business rules from isolated prompts.

Conflict Resolution

When a new situation falls outside existing guidance, apply the principles in this Playbook, document the decision, and propose a revision. Do not silently create a new policy through a single support interaction or implementation choice.

Revision Philosophy

This is a living operating document. Revisions should improve clarity, strengthen delivery, reflect actual service capabilities, or correct inconsistency. A revision is successful when it makes future decisions easier and client expectations more accurate.

Part I - Purpose and Philosophy

Chapter 1 - Mission

Mission Statement

SoAtomic helps businesses and organizations understand, secure, improve, and maintain the technology they depend on through clear assessment, fixed-scope solutions, and long-term managed support.

Technology should support an organization's work without becoming its focus. Whether SoAtomic is reviewing access, securing endpoints, administering cloud services, reducing software waste, coordinating a wireless project, or automating a workflow, the goal is the same: dependable systems that remain understandable and owned by the client.

Vision Statement

SoAtomic envisions a future in which businesses and organizations can access the quality of technology stewardship traditionally associated with much larger enterprises without inheriting enterprise complexity, opaque billing, or vendor dependence.

Every client deserves systems that are secure, documented, maintainable, appropriately governed, and proportionate to the way the organization operates.

Long-Term Purpose

The purpose of SoAtomic extends beyond individual tickets and projects. Every engagement should leave the organization stronger than it was before. Improvements may include clearer documentation, safer user access, fewer unused licenses, more reliable devices, better cloud governance, stable communications, improved backups, stronger security, or reduced manual work.

Over time, these improvements create operational stability. Stable systems reduce risk, conserve staff time, strengthen stewardship of organizational resources, and make growth easier to manage.

Definition of Success

A successful Screen gives the client an evidence-based understanding of the environment and a practical roadmap.

A successful Solution delivers a defined outcome that is tested, documented, and owned by the client.

A successful Support relationship makes technology more reliable and understandable over time while reducing unresolved risk and operational friction.

A successful business grows sustainably without sacrificing quality, honesty, responsiveness, or the relationships that made growth possible.

Chapter 2 - Core Principles

Honest Engineering

Recommend technology because it solves a meaningful problem, not because it is new, fashionable, or profitable to resell. If an existing system works well, improve it rather than replace it without cause.

Engineering Maxim: Recommend what solves the problem.

Transparency Before Upselling

Clients should understand what they are buying, why it is recommended, what is included, what is excluded, and what happens next. SoAtomic publishes pricing where services are standardized and identifies separately priced work before it begins.

Engineering Maxim: Clear expectations build lasting relationships.

Simplicity Over Complexity

Every platform, account, integration, policy, and exception creates a maintenance burden. Use the simplest dependable solution that satisfies the organization's real requirements.

Engineering Maxim: Every layer of complexity should justify its existence.

Craftsmanship Over Volume

SoAtomic is intentionally relationship-driven. Assess carefully, configure deliberately, test thoroughly, communicate clearly, and document the finished state. Growth must never outpace the ability to support existing clients responsibly.

Engineering Maxim: Serve a manageable number of clients exceptionally well.

Cloud-First, Not Cloud-Blind

Managed cloud platforms often provide better security, resilience, portability, and administrative capability than infrastructure a small organization can maintain itself. Prefer cloud services when they reduce risk and operational burden, but evaluate real requirements, connectivity, cost, privacy, and continuity before making a recommendation.

Engineering Maxim: Prefer managed services when they create a better operating outcome.

Predictable Pricing Builds Trust

Published and clearly structured pricing helps clients budget with confidence. Screens and Atomic Actions use fixed prices. Support plans use a defined recurring basis and clearly documented scope. Additional charges require prior explanation and approval.

Engineering Maxim: Predictability is part of the product.

Stewardship Over Dependency

Ongoing support should increase the client's stability without reducing its ownership. SoAtomic may hold delegated access required to provide service, but the client remains the owner of its accounts, data, domains, configurations, and vendor relationships.

Engineering Maxim: Support the client without trapping the client.

Technology Should Become Quieter

Good technology works reliably in the background. Devices remain healthy. Access reflects current staff responsibilities. Email is trustworthy. Backups are verifiable. Alerts are actionable. Automations run consistently. People spend less time managing technology and more time advancing the mission.

Engineering Maxim: The best systems are the ones people do not have to think about.

Chapter 3 - Engineering Maxims

Complexity Is a Cost

Every new system introduces financial, administrative, security, training, and support costs. When complexity is necessary, it should be intentional, documented, and matched with the support capacity required to maintain it.

Clients Buy Confidence Before Technology

Most leaders are not looking for another dashboard. They are looking for confidence that risks are understood, responsibilities are clear, and qualified help is available. Technology is the means; confidence is the outcome.

Every Recommendation Should Reduce Future Maintenance

Favor standard platforms, managed services, automation, documented configurations, and consistent policies over fragile customization and one-person knowledge.

Build Systems That Survive Your Absence

No organization should depend on a single person to keep its technology working. Accounts should be client-owned, administrative access should be recoverable, permissions should be reviewable, and configurations should be understandable by another qualified provider.

Engineering Maxim: If it works only because one person remembers how, it is not finished.

Own Less. Document More.

SoAtomic should not create dependency by owning client assets. Delegated administration and complete documentation are more professional than exclusive control.

Explain First. Engineer Second.

Before a material change, explain the problem, the options, the recommended approach, the tradeoffs, and the operational impact. Clients do not need to become engineers, but they should understand significant decisions.

Simple Systems Age Better

Well-supported platforms, consistent policies, and clear architecture are easier to update and troubleshoot than highly customized systems. Longevity comes from adaptability, not prediction.

Chapter 4 - The SoAtomic Promise

Clients Own Everything

Wherever practical, accounts, domains, cloud tenants, email services, DNS, endpoint-management tenants, security platforms, automation services, documentation, and data are created in the client's name and remain under client control.

SoAtomic administers these systems through delegated access. Temporary exceptions may exist during migration or staging, but the intended end state is client ownership.

Engineering Maxim: We configure it. You own it.

No Vendor Lock-In

Clients remain because SoAtomic provides value, not because departure is technically difficult. Use widely supported platforms when practical, document configurations, transfer credentials appropriately, and avoid proprietary dependency without a compelling and disclosed reason.

Fair and Predictable Pricing

Standard services should use standard pricing. Non-standard work should have a documented scope, assumptions, price, and approval before work begins. No material invoice should surprise the client.

Professional Documentation

Documentation is part of the service. Screens produce findings and roadmaps. Solutions produce implementation records and handoff information. Support keeps inventories, ownership records, access information, and operational procedures current according to plan scope.

Respectful Offboarding

When a relationship ends, SoAtomic will provide reasonable transition assistance, confirm ownership, update documentation, remove delegated access, and coordinate with the incoming provider as defined by the agreement.

We Earn the Relationship Through Service

Support exists because it creates ongoing value. Agreements should be understandable, cancellation should be professional, and renewal should result from dependable service rather than artificial barriers.

Part II - The Workshop

Chapter 5 - The Managed Technology Workshop

Why a Workshop

SoAtomic is a managed service provider expressed through the idea of a technology workshop. The MSP model defines the ongoing responsibility. The Workshop defines the character of the work: careful assessment, skilled repair, deliberate improvement, preventive maintenance, clear documentation, and professional handoff.

Clients should expect honest advice, organized service, and confidence that the work will be completed responsibly. The Workshop does not exist to sell the largest stack. It exists to establish and preserve dependable technology foundations.

Engineering Maxim: Solve the problem before selecting the tool.

Engineering Instead of Selling

Every recommendation begins by understanding the organization, its people, risk, budget, governance, and operating constraints. Cloud platforms, endpoint tools, automation, communications systems, security controls, and vendor services are tools used to achieve operational outcomes.

If the current system can be secured and simplified, improve it. If a specialist is better suited, coordinate or refer. If no change is justified, document that conclusion.

Building Technology Footing

Every organization depends on a technology foundation: identity, email, endpoints, cloud services, domains, DNS, backups, security, documentation, subscriptions, communications, and business applications. Weakness in one area can create risk across the organization.

Technology maturity is not measured by the number of products deployed. It is measured by how reliably systems support the people using them and how confidently the organization can govern them.

Long-Term Stewardship

Technology changes continuously. Staff and volunteers join and leave. Vendors alter terms. Platforms add features. Devices age. Threats evolve. Support should make these changes manageable rather than disruptive.

Good stewardship values durability over novelty, prevention over repeated emergencies, and documented continuity over personal dependency.

Boutique by Design

SoAtomic remains intentionally focused and selective. A manageable client base makes it possible to understand each organization's work, systems, constraints, and history. The goal is not maximum ticket volume. The goal is a consistently high standard of stewardship.

Chapter 6 - Brand Identity

Brand Personality

SoAtomic should feel like an experienced technology steward who enjoys explaining complex subjects without making others feel inexperienced.

The brand is confident without arrogance, technical without obscurity, professional without unnecessary formality, and friendly without becoming casual about responsibility.

Tone of Voice

Use plain language whenever it communicates the idea accurately. Introduce technical terms only when they improve understanding, and explain them when the audience may not know them.

Assume the reader is intelligent, responsible, and busy. Marketing should sound like honest engineering. Support communication should be calm, direct, and useful. Incident updates should distinguish known facts, open questions, risk, actions taken, and next steps.

Engineering Maxim: Clarity earns trust.

Naming Conventions

Customer-facing service names should explain the journey:

• Screen - assess and document

• Solutions - fix or improve through defined Atomic Actions

• Support - maintain, administer, protect, and guide over time

Support plans are named Support, Support Plus, Support Pro, and Support Enterprise. Clarity takes priority over thematic naming. Internal terminology may retain the Atomic and Workshop identity when it improves consistency without obscuring meaning.

Workshop Vocabulary

The Workshop assesses, documents, configures, secures, monitors, maintains, coordinates, improves, and hands off systems. It does not use agency language that implies creative production, advertising, or content operations.

Examples:

• Conduct a Screen rather than a speculative sales audit.

• Deliver an Atomic Action rather than open-ended hourly project work.

• Provide Support rather than selling an undefined retainer.

• Present completed engagements as case studies rather than visual showcases.

• Coordinate trusted specialists while making responsibilities visible to the client.

Customer Psychology

Many organizations approach technology with uncertainty. They may have experienced confusing proposals, unexpected invoices, unresponsive support, weak documentation, inherited administrator accounts, or vendors that retained control.

Every part of SoAtomic should reduce that uncertainty. Published pricing reduces financial anxiety. Defined boundaries reduce confusion. Documentation reduces dependence. Client ownership reduces lock-in. Clear explanations support governance and confident decisions.

Chapter 7 - Visual Identity

This chapter governs the SoAtomic brand and SoAtomic-owned materials. It does not establish a creative service offered to clients.

Visual Purpose

The visual identity should reinforce thoughtful engineering, practical craftsmanship, reliability, and calm operational control. Visual elements should support clarity and accessibility rather than decoration.

Blueprint and Workshop Language

Structured grids, measured spacing, technical diagrams, and restrained workshop references may suggest planning and precision. The presentation should feel engineered and organized without becoming theatrical.

Color and Typography

Color should communicate hierarchy, state, and interaction. Typography should remain highly legible across technical explanations, service details, policies, and long-form documentation. Readability takes priority over novelty.

Motion and Interaction

Motion should communicate state or spatial relationships. Avoid decorative movement that distracts, impairs accessibility, or makes the interface feel less dependable. Reduced-motion preferences must be respected.

Illustration

The Atomic Mechanic, technical diagrams, and workshop motifs may humanize the brand when they support understanding. Illustration should never trivialize security, incident response, compliance readiness, or client responsibility.

Case Studies

Completed work should be presented as operational case studies. A case study may describe the client's challenge, documented baseline, risk reduced, system configured, workflow improved, support model, and measurable outcome. The emphasis is on stewardship and operational improvement.

Part III - Business Model

Chapter 8 - Ideal Client

Practical Fit and Responsible Scope

SoAtomic supports businesses and organizations across industries. Every prospective engagement begins with a consultation and fit review before SoAtomic accepts responsibility.

Fit is practical, not ideological. Before accepting responsibility, SoAtomic reviews the environment, needs, expectations, risk, available access, platform supportability, security requirements, and whether the work can be delivered responsibly within SoAtomic's capabilities and service boundaries.

Strong-fit clients generally value:

• Clear and published pricing

• Professional documentation

• Client ownership and portability

• Security proportionate to real risk

• Plain-language guidance for leadership and staff

• Predictable support relationships

• Responsible use of organizational resources

• Long-term improvement rather than repeated emergency work

Nonprofits and Foundations

Nonprofits may manage donor information, program data, grant documentation, board records, volunteers, contractors, staff, and community communications across a limited administrative team. Technology should amplify the mission rather than consume resources.

SoAtomic accounts for restricted budgets, grant cycles, board accountability, seasonal programs, volunteer turnover, privacy responsibilities, and the need to demonstrate good stewardship.

Chambers and Community Organizations

Chambers and community groups often balance membership, advocacy, events, communications, and public trust with limited staff. Their systems should make access, communication, records, and transitions easier to manage.

Faith and Educational Organizations

These organizations may combine employees, volunteers, students, families, donors, and sensitive records. Support must reflect role-based access, shared resources, leadership transitions, and safeguarding responsibilities.

Medical Practices and Professional Offices

Small professional organizations may be a fit when their requirements align with supported platforms and the limits of SoAtomic's compliance-readiness role. SoAtomic does not provide legal determinations, certified audits, or formal attestations.

Local and Service Businesses

Commercial organizations may be supported when their environment, needs, expectations, and risk fit SoAtomic's capabilities and they value ownership, documentation, predictable service, and responsible technology operations.

Engagements We Decline

SoAtomic declines work that falls outside supported disciplines or creates an unmanageable duty of care.

Examples include:

• Residential technology support

• Consumer device repair

• Printer repair

• Hardware component repair

• Break/fix work without an appropriate assessment or support relationship

• On-premises server administration

• Active Directory or on-premises Exchange administration

• Structured cabling or construction labor

• Security camera and badge-system installation

• Certified compliance audits or legal advice

• Advertising, creative production, or routine site content publishing

• Arrangements requiring SoAtomic to own client assets or withhold access

When appropriate, SoAtomic will recommend or coordinate a qualified specialist.

Chapter 9 - Revenue Philosophy

Sustainable Growth

Revenue sustains the tools, people, training, insurance, security, documentation, and availability required to serve clients responsibly. Growth must never outpace operational capacity.

When demand exceeds capacity, the correct response is to manage intake, improve processes, or add qualified support - not lower standards.

Relationships Over Scale

Recurring revenue is not an excuse to maximize account count. It creates the continuity required to understand client environments, prevent recurring issues, and improve systems over time.

Predictable Pricing

Pricing should be easy to explain and appropriate to the responsibility assumed:

• Screens use a published fixed price per assessment.

• Atomic Actions use a published fixed price per defined outcome.

• Support uses a published recurring price based on the selected plan and stated billing unit.

• Separately priced services, equipment, specialist labor, and approved expenses are disclosed before commitment.

Current prices belong in the published pricing source, not hard-coded throughout this Playbook.

Value Creation

Value may appear as reduced risk, fewer disruptions, faster onboarding, stronger access control, clearer documentation, lower software spend, recovered ownership, better backup confidence, improved collaboration, or time returned to staff.

Technology is valuable only when it improves the organization's ability to do its work.

Capacity Planning

Every Support client represents an ongoing obligation. Capacity planning must account for user count, endpoint count, supported platforms, locations, service hours, ticket history, administrative complexity, security requirements, vendor coordination, automation, project load, and the unpredictability of incidents.

Support pricing and plan scope must remain sustainable enough to honor the promises made.

Chapter 10 - Decision Framework

When several approaches are possible, evaluate them using the following questions.

Does It Increase Client Ownership?

Prefer the option that keeps accounts, contracts, data, domains, and administrative recovery under client control.

Does It Increase Clarity?

Prefer configurations, naming, documentation, pricing, and communication that another qualified person can understand.

Does It Reduce Maintenance?

Prefer managed services, consistent standards, automation, and supported platforms when they reduce ongoing burden without creating unacceptable dependency.

Does It Improve Security and Resilience?

Consider identity, least privilege, MFA, endpoint protection, backups, recovery, monitoring, data handling, vendor risk, and continuity.

Does It Improve Portability?

Avoid unnecessary customization and proprietary dependencies. Document decisions so the environment can outlive the current provider.

Does It Respect the Work and Budget?

Evaluate total cost, staff time, operational constraints, renewal risk, accountability, and whether the recommendation diverts resources from higher-impact work.

Does It Simplify the Client Experience?

Services should be easy to understand. Processes should feel organized. Support communication should clearly identify responsibility and next action.

Does It Fit SoAtomic's Scope?

Do not accept responsibility that cannot be delivered safely, profitably, and consistently. Use specialists when their expertise creates a better outcome.

Chapter 11 - Partner Philosophy

Trusted Specialists

No MSP should pretend to be expert in every discipline. SoAtomic maintains relationships with professionals and providers whose reliability, competence, communication, and integrity have been evaluated.

Potential specialist areas include:

• Structured cabling and wireless installation

• Electrical and construction work

• Hardware repair and logistics

• VoIP and telecommunications

• Cybersecurity testing and incident response

• Certified compliance audit services

• Legal, privacy, and regulatory counsel

• Accounting and grant compliance

• Accessibility evaluation

• Creative, editorial, and communications services

Transparent Referrals

Clients should know who performs the work, why the provider was recommended, who holds the contract, how pricing is approved, and which party is responsible for each outcome.

Competitive Procurement

When SoAtomic manages a wireless infrastructure project, it coordinates qualified specialists, vendors, and service providers while overseeing technical coordination throughout the project. Equipment, cabling, construction, and specialist installation labor are separately priced. Before any separately priced work begins, customers receive three competitive bids for labor and materials.

Collaborative Service

When several providers contribute, SoAtomic documents decisions, coordinates dependencies, respects each specialist's expertise, and gives the client a coherent view of status and responsibility.

Engineering Maxim: Great collaboration should feel organized to the client.

Knowing When to Say No

Declining an engagement is appropriate when another provider is better suited, the responsibility exceeds SoAtomic's capability, the timeline would endanger existing commitments, or the requested model conflicts with client ownership and professional standards.

Engineering Maxim: Professionalism includes knowing your limits.

Part IV - Customer Lifecycle

Chapter 12 - The Managed Technology Cycle

Technology is not a one-time purchase. Organizations change, staff and volunteers transition, software evolves, threats emerge, budgets shift, and new operational needs appear. SoAtomic treats each engagement as part of a managed lifecycle rather than as an isolated transaction.

Stage 1: Screen

Every accepted relationship begins with understanding. After consultation and fit review, a Screen reviews one defined area of the environment, records ownership and configuration, identifies strengths and risk, and produces prioritized recommendations.

The purpose of a Screen is clarity. Its value does not depend on whether SoAtomic performs the recommended work.

Engineering Maxim: Assess before recommending change.

Stage 2: Solutions

Solutions convert documented findings into explicit outcomes. Work is divided into Atomic Actions so the scope, price, finish line, testing, and documentation are clear before implementation begins.

Solutions are organized as:

• Remedy - fix an active problem, ownership gap, security weakness, configuration failure, or operational obstruction.

• Boost - improve a working environment through stronger configuration, automation, cost control, collaboration, or operational efficiency.

Engineering Maxim: Define the outcome before starting the work.

Stage 3: Support

Support provides ongoing technology stewardship. Depending on the selected plan, SoAtomic may provide responsive assistance, proactive monitoring, patching, preventive maintenance, identity administration, endpoint management, vendor coordination, compliance-readiness guidance, and strategic oversight.

Support is not a vague promise to handle everything. Each plan has explicit inclusion, exclusion, coverage, and separately priced service definitions.

Engineering Maxim: Responsibility should be visible before it becomes recurring.

Continuous Improvement

Support clients may receive new Screens when the environment changes materially, when leadership requires a current baseline, or when an area has not been reviewed recently. New findings may become Remedies or Boosts. Completed Actions update documentation and become part of the supported environment.

The cycle repeats because organizations continue to evolve:

Screen -> Solutions -> Support -> Review -> Screen

The objective is incremental maturity rather than periodic crisis and replacement.

Chapter 13 - Screen

Purpose

A Screen establishes an evidence-based baseline for one area of technology. It answers:

1. What is working?

2. What is fragile, unclear, redundant, or risky?

3. Who owns the relevant assets and accounts?

4. Which improvements deserve priority?

5. Which findings can the client address independently?

6. Which findings require an Atomic Action, support-plan change, or specialist?

Standard Deliverables

Every Screen should produce:

• Findings report

• System and ownership documentation appropriate to the assessment

• Prioritized roadmap and next steps

• Identification of urgent risks

• Identification of unnecessary cost or duplication when applicable

• Clear distinction between observation, risk, recommendation, and optional improvement

Reports belong to the client and may be implemented by the client, SoAtomic, or another provider.

Screen: Cloud

The Cloud Screen evaluates cloud accounts, identity, permissions, and administrative control.

Areas may include:

• Google Workspace administrative configuration

• Google Cloud organization and projects

• Cloudflare account ownership and security settings

• Administrative roles

• MFA and recovery methods

• User and group structure

• Shared Drives and shared-resource ownership

• Third-party application access

• Cloud-service inventory

• Delegated administrator relationships

• Account recovery and continuity

Screen: Web Infrastructure

The Web Infrastructure Screen evaluates the operational foundation surrounding a client's public site. It is not a review of visual presentation, copy, information architecture, search strategy, merchandising, or routine publishing.

Areas may include:

• Domain and registrar ownership

• Administrative and recovery access

• DNS configuration and stability

• SSL certificate validity and renewal

• Hosting ownership, billing, and reliability

• CDN, proxy, and edge-security configuration

• Backup and recovery arrangements

• Uptime monitoring

• Platform and plugin update responsibility

• Form delivery and operational dependencies

• Vendor access and transition readiness

• Documented incident contacts

If the review identifies creative, editorial, usability, marketing, or accessibility work outside SoAtomic's scope, the report may recommend a qualified specialist without representing that work as a SoAtomic service.

Screen: Endpoints

The Endpoints Screen reviews the computers, phones, tablets, and management systems used by the organization.

Areas may include:

• Device inventory and assigned owner

• macOS, Windows, ChromeOS, iOS, iPadOS, and Android security baselines

• Encryption status

• Operating system and patch status

• Mobile-device or endpoint-management enrollment

• Endpoint threat protection

• Local administrator practices

• Backup and recovery

• Software inventory and licensing

• Lost-device response

• Lifecycle, warranty, and replacement planning

The Screen does not include physical repair or component diagnostics.

Screen: Spend

The Spend Screen catalogs technology subscriptions, license counts, vendors, contracts, renewals, and avoidable duplication.

Areas may include:

• Active software subscriptions

• Assigned and unused licenses

• Duplicate products

• Vendor ownership and contacts

• Contract and renewal dates

• Monthly and annual technology cost

• Grant-funded service commitments

• Former-user accounts that continue to incur cost

• Pricing anomalies

• Cancellation and data-export considerations

Screen: Reach

The Reach Screen reviews the systems used to communicate with staff, volunteers, members, donors, program participants, customers, and other stakeholders. It evaluates operational reliability and governance, not communications strategy or content production.

Areas may include:

• Organizational email and aliases

• Groups, shared mailboxes, and mailing lists

• Messaging and collaboration platforms

• Contact-form delivery

• Newsletter platform ownership and access

• CRM and constituent-system integration points

• Submittable or other intake systems

• List hygiene controls and consent records where supported

• Communication workflow automation

• Account ownership, recovery, and vendor responsibility

Reporting Standards

Every finding should identify the observed condition, operational impact, evidence, urgency, recommendation, and responsible party. Facts should remain separate from judgment. Uncertainty should be labeled rather than disguised.

Recommended Next Steps

A Screen may conclude with:

• Client-performed actions

• One or more Remedies

• One or more Boosts

• Support-plan recommendation

• Specialist referral

• A decision to keep the current state

• A future review date

The assessment concludes when the client understands the options, not when the client purchases more work.

Chapter 14 - Solutions

Solutions Philosophy

Traditional technology projects can become unpredictable when the client purchases hours rather than outcomes. SoAtomic divides implementation into clearly bounded Atomic Actions.

Each Atomic Action delivers one explicit technology outcome. If an initiative requires several outcomes, SoAtomic defines the required Actions and total price before proceeding.

What Every Atomic Action Includes

1. Planning - define the requirement, boundary, responsible accounts, dependencies, risk, and finish line.

2. Implementation - perform the approved configuration within client-owned systems.

3. Testing - verify function, security, permissions, failure handling, and expected result.

4. Documentation - update the technology inventory, configuration record, procedure, or decision record.

5. Handoff - explain the result, confirm client ownership, and identify ongoing responsibility.

No Action is complete with an undocumented or partially tested handoff.

Remedy

Remedies address active problems. Examples may include:

• Recovering administrative ownership of a domain or cloud account

• Removing former-user access

• Correcting email authentication or delivery configuration

• Repairing a broken onboarding or offboarding workflow

• Reorganizing shared-drive permissions

• Resolving endpoint-management enrollment failures

• Restoring backup visibility or recovery capability

• Correcting DNS, SSL, hosting, or form-delivery failures

• Consolidating technology ownership records

• Removing obsolete accounts or licenses

Remedies affecting a client's public site are limited to supported infrastructure and operational dependencies. They do not include visual changes, page creation, content editing, or campaign work.

Boost

Boosts improve an environment that already functions. Examples may include:

• Implementing stronger MFA and recovery standards

• Introducing device-management policies

• Improving Google Workspace governance

• Automating repetitive onboarding tasks

• Reducing software cost

• Improving shared-resource organization

• Establishing technology inventory and renewal records

• Configuring monitoring and alert routing

• Improving backup verification

• Connecting supported cloud platforms

• Improving collaboration and approval workflows

Scope Philosophy

An Atomic Action is defined by outcome, not effort. It must have a clear completion test. Requests that change the outcome require an approved new Action or revised statement of work.

Small implementation choices necessary to complete the stated outcome are part of professional execution and should not become surprise charges. New outcomes are new work.

Client Responsibilities

Clients provide timely access, accurate information, an authorized decision-maker, required licenses, and approval for material changes. Delays or undisclosed dependencies may change the schedule but should not silently change the scope.

Project and Partner Work

Some outcomes require specialist labor, equipment, construction, cabling, legal review, certified audit, or other external work. SoAtomic may coordinate the project while keeping third-party contracts, bids, costs, and responsibilities explicit.

Chapter 15 - Support

Support Philosophy

Support represents long-term technology stewardship, not merely a help desk. The objective is to keep systems stable, document the environment, respond effectively, prevent avoidable problems, and help the organization make informed decisions.

SoAtomic's responsibility is not to make itself indispensable. It is to maintain technology that remains understandable, reliable, secure, documented, and owned by the client.

Support Plan Structure

The public pricing source defines current prices and the precise billing unit. This Playbook defines the service logic. No price in an outdated Playbook should override the current published plan or signed agreement.

Support

Designed for organizations that need a dependable place to turn when technology stops working.

Typical scope:

• Email-based support

• Responsive troubleshooting and issue resolution

• Defined response coverage hours

• A defined emergency contact allowance

• Requested updates when included by the current plan

Typical exclusions:

• Proactive monitoring

• Scheduled patching

• Preventive maintenance

• Ongoing workspace administration

• Routine onboarding and offboarding

• Endpoint threat detection and response

Support Plus

Designed for organizations that want issues identified and addressed before they become disruptions.

Typical scope:

• Everything included in Support

• Proactive system-health monitoring

• Scheduled patching and updates

• Preventive maintenance

• Proactive remediation of detected issues

• Expanded coverage hours

• Phone support during coverage hours

Typical exclusions:

• Full Google Workspace or Microsoft environment administration

• Routine user-account administration

• Employee onboarding and offboarding

• Endpoint threat detection and response unless separately included

• Full device-fleet administration

Support Pro

Designed for organizations that need active administration of users, devices, accounts, and shared systems.

Typical scope:

• Everything included in Support and Support Plus

• User-account creation and administration

• Employee onboarding and offboarding

• Google Workspace administration

• Apple Business Manager administration

• Microsoft environment administration for reviewed and accepted environments

• Supported Linux environment administration

• Supported existing wireless environment administration

• Mobile-device and endpoint-fleet management

• Expanded coverage and priority phone support

Separately priced or limited items may include:

• Endpoint threat detection and response

• New infrastructure projects

• Hardware and equipment

• Specialist labor

Support Enterprise

Designed for complex organizations with multiple locations, cloud infrastructure, vendors, governance requirements, or specialized operational needs.

Typical scope:

• Everything included in lower Support plans

• Multiple-location support

• Google Cloud administration

• Technology vendor coordination and management

• Technology Spend Analysis and Anomaly Detection

• Supported Salesforce and Agentforce administration

• Priority service-level response commitments

• Compliance Readiness Reviews for supported frameworks

• Wireless infrastructure project management

• Coordination of specialist installation vendors

Scope Clarification: Wireless

SoAtomic plans and manages wireless infrastructure projects, coordinates qualified specialists, vendors, and service providers, and oversees technical coordination throughout the project.

Equipment, cabling, construction, and specialist installation labor are priced separately. Before any separately priced work begins, customers receive three competitive bids for labor and materials.

SoAtomic does not perform electrical, construction, cabling, or specialist installation labor unless a future approved service explicitly changes this boundary.

Scope Clarification: Compliance Readiness Review

SoAtomic performs technical readiness reviews and provides remediation guidance based on applicable, publicly available regulatory requirements and framework guidance current at the time of the review.

These reviews address technical readiness only. SoAtomic does not provide certified audits, legal advice, formal attestations, or regulatory determinations.

The client remains responsible for obtaining legal advice and engaging an authorized auditor, assessor, or certifying body when required.

Service Requests Versus Projects

Support covers work defined by the selected plan. Material migrations, new infrastructure, large-scale remediation, extensive automation, and other discrete outcomes may require Atomic Actions or a separately scoped project.

The distinction should be based on responsibility and deliverable, not used as a pretext to avoid ordinary support work.

Coverage and Response

Each plan must define:

• Coverage hours

• Contact methods

• Priority definitions

• Response targets or commitments

• Emergency procedures

• Supported users and endpoints

• Supported locations and platforms

• Planned maintenance practices

• Separately priced services

• Client responsibilities

Response time is not the same as resolution time. Communications must make that distinction clear.

Security and Incident Boundaries

Support may include security configuration, monitoring, endpoint controls, alert review, remediation, and incident coordination according to plan. It does not automatically include forensic investigation, breach counsel, ransom negotiation, regulatory notification, certified incident reporting, or services reserved for a specialized response firm.

When an incident exceeds SoAtomic's capability or contractual responsibility, preserve evidence, communicate known facts, coordinate the appropriate specialist, and avoid unsupported conclusions.

Chapter 16 - Nonprofit and Community-Sector Service Considerations

Speak the Organization's Language

Nonprofits and community organizations remain welcome clients and important sector experience. This section records expertise that may apply when serving those organizations; it is not a universal eligibility requirement.

Communication, assessments, recommendations, and support should reflect how nonprofit and community-sector organizations actually operate.

Relevant realities may include:

• Restricted and unrestricted funding

• Grant start and end dates

• Board governance and reporting

• Donor, member, patient, student, or participant data

• Volunteer and seasonal access

• Leadership transitions

• Small administrative teams

• Shared devices and temporary staff

• Distributed programs and multiple sites

• Fundraising, program, and reporting calendars

• Privacy and safeguarding duties

• Vendor discounts and nonprofit eligibility

• The need to demonstrate responsible stewardship

Budget Stewardship

Recommendations should consider total cost, renewal timing, staff time, implementation capacity, training, and long-term support. A technically superior product is not a better recommendation if it creates an unsustainable administrative or financial burden.

Whenever possible, identify nonprofit discounts, donated-license programs, appropriate tiering, and unused subscriptions. Discounts should not justify adopting a product that is otherwise a poor fit.

Identity and Access

Nonprofit and community-sector clients often have complex user lifecycles that include employees, volunteers, board members, contractors, interns, program staff, and temporary users. Access should be role-based, time-bounded when appropriate, reviewed regularly, and removed promptly at transition.

Shared credentials should be reduced. Ownership of shared resources should survive staff turnover. Recovery methods should not depend on a departed employee or personal account.

Board and Leadership Communication

Reports for leadership should explain risk, operational impact, cost, responsibility, and recommended action in plain language. Technical severity and organizational priority should be distinguished.

When appropriate, quarterly or annual reviews should provide:

• Material changes in risk

• Open recommendations

• Technology spend trends

• Upcoming renewals

• User and endpoint changes

• Security and backup status

• Major incidents and lessons learned

• Work completed

• Decisions requiring leadership approval

Data Stewardship

Technology recommendations should consider the sensitivity, purpose, retention, sharing, and recovery of organizational data. SoAtomic provides technical guidance within scope but does not decide legal retention obligations or regulatory applicability on the client's behalf.

Mission Continuity

Continuity planning should identify the systems necessary to continue core programs, communications, fundraising, and administrative operations. Backup alone is not continuity; recovery ownership, tested access, alternate communication, vendor escalation, and leadership decision paths also matter.

Engineering Maxim: Protect the systems that protect the work.

Part V - Operational Standards

Chapter 17 - Workshop Guardrails

Clear Boundaries

Good managed service depends on visible responsibility. Guardrails protect the client and SoAtomic by preventing assumptions from becoming unmanaged obligations.

Outcome-Based Project Scope

Screens and Solutions are defined by deliverables and completed outcomes. Clients should not need to monitor timesheets to understand whether the engagement is complete.

Support is defined by recurring responsibility, plan inclusions, users, devices, locations, platforms, and service conditions. It is not an unlimited pool of project labor.

Reasonable Flexibility

Professional service includes reasonable implementation judgment and minor adjustments required to complete the agreed outcome. Flexibility should support collaboration without turning one Action into several undocumented deliverables.

Supported Environment Boundary

SoAtomic is cloud-first and endpoint-aware. Supported services may include cloud identity, SaaS administration, endpoint management, Apple and macOS, Microsoft and Windows, Google, ChromeOS, supported Linux, iOS, iPadOS, Android, DNS, web infrastructure, automation, communications platforms, and coordinated wireless operations.

Unsupported or specialist-led areas include on-premises server administration, structured cabling, construction, electrical work, physical hardware repair, certified audits, legal advice, and creative or editorial services.

Client-Owned Tenant Policy

Production systems should reside in client-owned accounts whenever practical. SoAtomic may use temporary staging, vendor portals, or partner systems when necessary, but permanent client assets should not remain trapped in a SoAtomic-owned tenant.

Public Site Infrastructure Boundary

SoAtomic may support domain, registrar, DNS, SSL, hosting, CDN, uptime, security, administrative access, backup, vendor coordination, and operational recovery. SoAtomic does not assume responsibility for visual presentation, page composition, copy, imagery, routine publishing, campaigns, merchandising, or content calendars.

When a site change is necessary to complete a supported infrastructure outcome, the client or designated creative provider performs the content or presentation work unless a narrow technical change is explicitly documented in the Action.

Operational Signal Boundary

SoAtomic may configure and maintain systems that move information, trigger tasks, route alerts, and automate supported workflows. The client owns business policy, messaging, approvals, data accuracy, and operational decisions.

Support Eligibility

An environment may require a Screen and remediation before entering Support. SoAtomic should not accept recurring responsibility for undocumented, insecure, unsupported, or inaccessible systems without a written transition plan.

Scope Change Management

When requested work changes the agreed outcome or recurring responsibility, document the change, explain its operational and pricing impact, and obtain approval before implementation.

Access and Credential Handling

• Use named accounts wherever possible.

• Use delegated administration rather than shared credentials.

• Store secrets only in approved systems.

• Apply least privilege.

• Require MFA for administrative access.

• Remove access promptly at role or relationship changes.

• Record emergency and recovery procedures.

• Never place credentials in ordinary email, chat, or documentation.

Documentation Minimum

No supported environment should depend entirely on memory. At minimum, maintain ownership, administrative access path, vendor contacts, supported users and endpoints, major platforms, renewal responsibility, backup responsibility, and critical escalation information according to plan scope.

Chapter 18 - Technology Standards

Platform Selection

SoAtomic maintains a curated technology ecosystem. Platforms are evaluated for security, administrative control, documentation, interoperability, support maturity, portability, organizational fit, total cost, and long-term viability.

Supporting fewer platforms deeply is preferable to claiming shallow support for everything.

Google Workspace

Google Workspace is a preferred cloud identity, productivity, and collaboration platform. Supported responsibilities may include user lifecycle, groups, Shared Drives, administrative roles, security policies, recovery, application access, and governance according to plan.

Google Cloud

Google Cloud may support approved cloud workloads and services. Resources should be client-owned, documented, tagged or named consistently, protected by least privilege, monitored appropriately, and reviewed for cost.

Apple Business Manager and Apple Ecosystem

SoAtomic may administer Apple Business Manager, device enrollment, managed Apple identities where applicable, and supported MDM configurations. Device repair and component diagnostics remain outside scope.

Windows and Microsoft Environments

SoAtomic may assess, implement, and administer supported Microsoft business environments, Microsoft 365, Copilot governance needs, and Windows endpoints when reviewed, accepted, and included by plan or written scope. Traditional, highly specialized, legacy, on-premises, hybrid, or unusually complex Microsoft infrastructure may require separate scoping or a qualified specialist.

Linux Environments

SoAtomic may assess and administer supported Linux environments when the distribution, workload, access model, security requirements, and support expectations fit SoAtomic's capabilities. Linux support does not imply responsibility for every distribution, server role, application stack, kernel customization, or highly specialized workload.

ChromeOS and Mobile Platforms

ChromeOS, iOS, iPadOS, and Android devices may be managed when enrolled in approved administration platforms and covered by the selected plan.

Cloudflare

Cloudflare is a preferred platform for DNS, registrar services where appropriate, edge security, performance, and related infrastructure. Client ownership and recovery must be documented.

Endpoint Management and Security

Managed endpoints should have an accurate inventory, supported operating system, encryption, screen-lock policy, update policy, administrative standard, recovery method, and security tooling appropriate to risk and plan scope.

Endpoint threat detection and response may be separately priced. The tool, response responsibility, coverage, alert destination, and escalation procedure must be explicit.

Backup and Recovery

Backup claims must be verifiable. Documentation should identify what is backed up, where it is stored, retention, encryption, responsible party, monitoring, recovery procedure, and last meaningful test when in scope.

Domains, DNS, and Hosting

SoAtomic may administer these systems as infrastructure. Clients should know who owns each account, who pays it, who can recover it, where DNS is hosted, where production is hosted, and which vendor is responsible for application-level changes.

Supported Business Platforms

Supported administration or integration may include platforms such as Submittable, HubSpot, Shopify, Copper CRM, Salesforce, Agentforce, Stripe, QuickBooks Online, Zapier, Make, and other approved SaaS tools.

Support does not automatically include every feature of a platform. Each engagement should define whether SoAtomic is responsible for identity, configuration, integration, vendor coordination, monitoring, or another specific administrative layer.

For Shopify and similar public platforms, SoAtomic may support account ownership, access, integrations, security, DNS, vendor coordination, and operational troubleshooting. Product merchandising, creative presentation, catalog content, campaign management, and routine publishing remain outside scope.

Wireless Infrastructure

SoAtomic may assess existing wireless environments, administer supported configurations, plan improvements, manage projects, and coordinate specialist vendors. Equipment, cabling, construction, surveying, and installation labor are separately priced and performed by qualified providers unless explicitly stated otherwise.

Compliance Readiness

Technical readiness work should use applicable public requirements and framework guidance current at the time of review. Findings must distinguish observed technical conditions from legal or regulatory conclusions. The client should be referred to qualified counsel or an authorized assessor for determinations, audits, or attestations.

Explicit Technology Exclusions

Unless a current approved service states otherwise, SoAtomic does not provide:

• On-premises Active Directory administration

• Exchange Server administration

• Traditional server-room operations

• Mainframe or specialized industrial systems

• Printer repair

• Physical device repair

• Structured cabling labor

• Electrical or construction labor

• Security-camera installation

• Badge-system installation

• Residential technology support

• Unsupported or end-of-life platforms

Engineering Maxim: Focus creates expertise.

Part VI - Client Policies

Chapter 19 - Ownership and Portability

Technology should increase organizational independence. Ownership exists from the beginning of the engagement, not as a reward after a contract expires.

Domains and Registrars

Domains should be registered to the client with client-controlled billing, recovery, and administrative ownership. SoAtomic may receive delegated or named administrative access, but the domain must not become a SoAtomic asset.

DNS

DNS should remain documented and portable. Clients should know where it is hosted, who controls it, which services depend on it, and how administrative access can be recovered. Significant records created or changed by SoAtomic should be documented.

Hosting and Public Site Platforms

When SoAtomic supports public-site infrastructure, production hosting and platform accounts should remain under client ownership. SoAtomic may coordinate the hosting provider or designated site specialist without assuming creative or editorial responsibility.

Cloud Tenants

Administrative ownership of Google Workspace, Google Cloud, Microsoft cloud environments, device-management platforms, security systems, and other critical tenants should remain with the client. SoAtomic operates through named or delegated access that can be removed without disrupting client ownership.

Email and Communications

Organizational email, mailing systems, phone services, messaging platforms, and associated records belong to the client. Administrative access should never depend on a personal account controlled by a former employee or provider.

Endpoints and Management Platforms

The client owns its devices, procurement records, management tenants, recovery keys, configurations, and business data. SoAtomic may administer these assets but should not use enrollment or management controls to obstruct a transition.

Automation and Integrations

Wherever practical, automations should run inside client-owned accounts with documented connections, credentials, triggers, actions, error handling, ownership, and vendor costs. Source materials and configuration records should be delivered when included by scope.

Documentation and Reports

Client-specific inventories, findings, roadmaps, implementation summaries, operating procedures, architecture records, and reports prepared for the engagement belong to the client, subject to any documented third-party licensing restrictions.

Data Export and Recovery

Before adopting a critical platform, evaluate how the organization can export its data, recover administrative access, and continue operations if the vendor or support relationship changes.

Transition Assistance

Upon request and according to the agreement, SoAtomic will provide reasonable assistance transferring administrative access, documentation, vendor contacts, supported configurations, and operational context to the client or incoming provider.

Engineering Maxim: A client who is free to leave is free to stay because the service remains valuable.

Chapter 20 - Pricing Philosophy

Pricing Communicates Values

SoAtomic competes through clarity rather than opacity. Clients should understand the price, billing basis, scope, exclusions, and approval path before committing.

Published Pricing

Standard Screens, Atomic Actions, and Support plans should have published prices whenever operationally practical. Current public pricing and signed agreements are authoritative; historical values in archived documents are not.

Fixed-Price Outcomes

Screens and Atomic Actions are priced by defined deliverable or outcome rather than elapsed time. This aligns incentives toward completing dependable work efficiently.

Recurring Support Pricing

Support plans are priced using the billing unit stated in the current plan, such as per user per month, together with any documented minimum, endpoint assumption, location factor, platform condition, add-on, or onboarding requirement.

Public presentation should spell out the unit clearly. Abbreviations that require interpretation should not replace plain language.

Separately Priced Items

The following may be separately priced when not included by plan:

• Equipment and hardware

• Licenses and subscriptions

• Endpoint threat detection and response

• Specialist labor

• Cabling, construction, or installation

• Travel or onsite work

• Major migrations

• New wireless infrastructure

• Certified audit or legal services supplied by third parties

• Large remediation efforts

• Projects that require multiple Atomic Actions

The client should approve these costs before commitment.

Scope Expansion

When the requested outcome changes, document the new deliverable, price, assumptions, and schedule. Scope expansion is a normal business discussion, not a conflict.

Estimates and Quotes

Non-standard estimates should identify:

• Deliverables

• Assumptions

• Boundaries

• Client responsibilities

• Third-party dependencies

• Price and payment schedule

• Expected timeline

• Conditions that may change the estimate

• Acceptance criteria

No Hidden Incentives

Referral fees, resale margins, commissions, or partner incentives that could materially affect a recommendation should be disclosed. A recommendation should remain defensible based on client value even if SoAtomic receives no financial benefit.

Client Procurement

When client policy, grants, boards, internal controls, or procurement rules require competitive bids, SoAtomic should document the process and provide comparable information. It must not split work or frame third-party costs in a way intended to bypass client policy.

For nonprofit and community-sector clients, SoAtomic should also consider donated-license programs, TechSoup eligibility, nonprofit discounts, and grant-related purchasing constraints where relevant.

Chapter 21 - Support Agreements

Clear Recurring Responsibility

A Support Agreement should define the recurring relationship in plain language. It should identify supported users, endpoints, locations, platforms, services, coverage, contact methods, security responsibilities, exclusions, add-ons, data-handling expectations, and termination process.

Month-to-Month by Default

SoAtomic's standard philosophy favors month-to-month relationships so continued service is based on value and trust. If a different term is offered, the current agreement must state it clearly.

Annual Options

Annual pricing or prepayment may be offered for budgeting stability. Any discount, renewal, cancellation condition, and unused prepaid balance treatment should be explicit. Annual terms should reward commitment rather than create dependency.

Onboarding

Support onboarding may require:

• Initial Screen or environment review

• Administrative-access verification

• User and endpoint inventory

• Platform and vendor inventory

• Documentation baseline

• Security and recovery review

• Existing issue and risk register

• Remediation plan

• Support contact and authorization list

• Billing-unit confirmation

Support should not begin under the fiction that an unknown environment is fully managed.

Plan Changes

Upgrades or downgrades should reflect actual responsibility and complexity. Before a downgrade, explain which coverage, administration, tools, or commitments will end. Before an upgrade, explain the need and resulting operational benefit.

Cancellation

Cancellation should be straightforward and professional. Reasonable notice allows open work to be addressed, documentation updated, delegated access reviewed, and the transition coordinated.

Transition Process

Depending on scope, transition activities may include:

• Confirming ownership of accounts and contracts

• Reviewing administrative access

• Exporting current documentation

• Transferring or removing credentials securely

• Providing implementation and incident notes

• Identifying unresolved risk

• Coordinating with the incoming provider

• Removing SoAtomic management profiles or integrations at the agreed time

• Confirming responsibility for licenses and vendor billing

Service Reviews

Support Pro and Enterprise clients should receive periodic review appropriate to plan. Reviews may cover service activity, open risk, platform changes, user and endpoint counts, cost, renewals, security posture, backup status, vendor issues, and recommendations.

Chapter 22 - Referral Philosophy

Reputation Before Promotion

SoAtomic should grow through dependable work, useful education, professional participation, community relationships, and earned referrals rather than aggressive sales tactics.

Word of Mouth

Every interaction may become the client's description of SoAtomic to another organization. Clear communication, good documentation, honest boundaries, and respectful support are the strongest referral program.

Community

Educational material, nonprofit partnerships, chamber participation, professional relationships, and practical technology guidance can create value before an organization becomes a client.

Reviews

Reviews should reflect genuine client experience. Requests for feedback must be voluntary and should never pressure a client to conceal a legitimate concern.

Long-Term Relationships

Some clients may use a Screen once. Others may request several Actions or remain in Support for years. Success is measured by the quality of the relationship and the strength of the client's environment, not by maximizing transactions.

Part VII - AI Engineering Standards

Chapter 23 - AI-First Documentation

Documentation as Infrastructure

SoAtomic documents the business so people and approved AI tools can understand how it operates. Services, policies, naming, supported platforms, security expectations, and operational boundaries should exist as documented knowledge before they become public claims or automated behavior.

Source of Truth

The Playbook defines business philosophy and service boundaries. Engineering standards define implementation requirements. Client documentation defines the current state of a specific environment. Signed agreements define client-specific commitments.

AI must not substitute an older generic description for a current client agreement or verified configuration.

Prompting Standards

Prompts should identify:

• Objective

• Authorized scope

• Client and data sensitivity

• Applicable service plan

• Supported platforms

• Operational boundaries

• Ownership requirements

• Security requirements

• Naming and documentation standards

• Required verification

• Desired output

AI should implement documented decisions rather than invent scope, pricing, policy, regulatory applicability, or client consent.

Information Architecture

Documentation should follow a logical hierarchy. Philosophy comes before policy. Policy comes before implementation. Client-specific facts should remain distinct from reusable standards. Duplicate facts should be consolidated into an authoritative source.

Version Control

Material changes should identify what changed, why it changed, when it became effective, and which services or clients may be affected.

AI Governance

AI may assist with research, drafting, analysis, software, documentation, automation, and troubleshooting. It does not replace professional accountability.

Human review is required before AI-generated material becomes:

• A client recommendation

• A production change

• A security conclusion

• A compliance-readiness finding

• An invoice or pricing commitment

• A public claim

• A formal policy

• A message sent to an external party

Sensitive client data should be provided to AI tools only when authorized and handled according to applicable agreements and tool capabilities.

Chapter 24 - AI Development Principles

Explain Systems Before Features

Describe the business purpose, operating environment, data flows, dependencies, responsible parties, failure conditions, and boundaries before requesting an implementation.

Constraints Produce Better Systems

Clear scope, supported platforms, security standards, naming, ownership, and verification improve AI output. Unlimited freedom creates inconsistency and hidden assumptions.

Human Accountability

Responsibility for architecture, access, security, testing, deployment, documentation, and maintenance remains with the human engineer. SoAtomic does not attribute mistakes to AI.

Consistency

Interfaces, procedures, documentation, and client communication should use stable terminology and predictable behavior. AI should reinforce the approved system rather than introduce arbitrary variation.

Maintainability

Automation and software should remain understandable to future engineers. Use readable code, modular structure, documented decisions, error handling, version control, and restrained complexity.

Verification

AI-generated claims should be verified proportionately to risk. Technical changes require targeted tests. Security and regulatory guidance require current authoritative sources and clear limitations. Client-specific conclusions require evidence from the actual environment.

Documentation First

Document purpose, business rules, scope, data handling, failure behavior, ownership, and maintenance before significant implementation begins.

Engineering Maxim: AI assists. Humans decide.

Part VIII - SoAtomic Public Website Standards

This part governs SoAtomic's own public website and published service information. It does not describe a service SoAtomic sells to clients.

Chapter 25 - Public Website Architecture

Purpose

The public website is SoAtomic's front door. It should help visitors understand:

• That SoAtomic is an MSP and technology steward

• Who SoAtomic serves

• The Screen, Solutions, and Support journey

• Current pricing and billing units

• What is included and excluded

• How client ownership and documentation work

• How SoAtomic reviews fit, scope, and supported platforms

• Why SoAtomic retains nonprofit and community-sector fluency

• What happens after contact

The site should answer common questions before requiring a sales conversation.

Navigation

Primary navigation should use current, plain-language service names. The expected structure is:

• Home

• Screen

• Solutions

• Support

• Pricing

• About

• Resources

• Playbook

• Contact

Supporting pages may include FAQ, privacy, accessibility, and legal information. Navigation should remain predictable and accessible.

Home

The homepage should immediately establish SoAtomic as a technology steward for businesses and organizations across industries. It should introduce the service journey, fit-review expectation, principles, focus platforms, transparent pricing approach, and primary next step.

Screen

The Screen page should explain the assessment categories, deliverables, client ownership, flat-price structure, and the fact that recommendations do not obligate the client to hire SoAtomic.

The Web category must be described as infrastructure and operational stewardship. It must not imply creative, editorial, or marketing services.

Solutions

The Solutions page should explain Remedy, Boost, Atomic Actions, fixed-price outcomes, testing, documentation, and handoff. Examples should focus on identity, endpoints, cloud, access, spend, communications infrastructure, automation, security, and supported operational systems.

Support

The Support page should publish the plan ladder, positioning, current billing basis, included services, exclusions, add-ons, coverage, wireless project boundary, and compliance-readiness limitation.

Pricing

The Pricing page should be the authoritative public summary of current standardized prices. It should use plain language, identify the billing unit, and avoid requiring a sales call merely to learn routine cost.

About and Playbook

These pages should establish trust through principles, operating boundaries, ownership, stewardship, practical fit review, nonprofit and community-sector understanding, and transparent limitations. They should not rely on generic claims of excellence.

Contact

Contact should feel like the beginning of a professional conversation, not a high-pressure sales funnel. The form should collect only information needed to route and prepare for the conversation. Submissions must produce a real delivery outcome, not a simulated success state.

Case Studies and Resources

Case studies should explain the initial condition, evidence, risk, action, documentation, operational result, and client ownership. Resources should teach practical technology stewardship without manufacturing fear.

Chapter 26 - Public Content Standards

Clarity

Writing should be direct, conversational, and technically accurate. Explain terms when necessary. Avoid jargon, exaggerated claims, manufactured urgency, and language that makes readers feel uninformed.

Client Fit and Sector Fluency

Public content should welcome businesses and organizations across industries while explaining that every prospective engagement is reviewed for fit, scope, expectations, risk, and supportability. Nonprofit and community-sector fluency should remain visible through relevant examples such as volunteer access, board oversight, donor data, grant cycles, limited staffing, program continuity, and technology stewardship.

Truthful Scope

Every public claim must match actual operational capability and current plan scope. Do not imply that SoAtomic performs certified audits, legal determinations, physical installation, hardware repair, creative production, routine publishing, or other excluded services.

Pricing Accuracy

Prices, billing units, minimums, add-ons, and Enterprise quote language must remain consistent across Support, Pricing, FAQ, structured data, and proposals. When a price changes, update every authoritative public reference.

Accessibility

The SoAtomic site should meet current accessibility requirements and provide inclusive navigation, structure, forms, contrast, motion behavior, focus management, and readable content.

Performance and Reliability

Pages should load quickly, minimize unnecessary assets and external requests, work across supported devices, and avoid fragile interactions. Monitoring, form delivery, DNS, SSL, and deployment should be treated as operational responsibilities for SoAtomic's own site.

Search and Structured Data

Search information should represent SoAtomic honestly. Titles, descriptions, structured data, headings, and internal links should use current service names and should not advertise excluded offerings.

Calls to Action

Calls to action should identify the next step and what happens afterward. The preferred entry point is a Screen or a structured conversation when a Screen category is not yet known. Do not use false scarcity.

Trust Signals

The site should demonstrate trust through:

• Published pricing

• Defined scope and exclusions

• Client ownership

• Professional documentation

• Consultation and fit review

• Nonprofit and community-sector fluency where relevant

• Case studies and reviews

• Security and privacy practices

• Clear compliance-readiness boundaries

• Specialist coordination standards

• Accessible communication

Part IX - Future Roadmap

Chapter 27 - Future Services

Future services should deepen SoAtomic's MSP capability rather than expand into unrelated agency disciplines.

Security Operations

Potential expansion may include managed endpoint detection, security-awareness support, vulnerability management, backup monitoring, incident-response coordination, and stronger identity governance. Each capability must define response responsibility and staffing requirements before launch.

VoIP and Communications

Cloud communications may be offered through supported platforms and trusted specialists. Physical telecommunications infrastructure and installation remain specialist-led.

Automation

The Solution Pattern Catalog may grow through repeatable operational experience. New patterns should be added only after demonstrating value, maintainability, and a clear support path.

Training

Educational services may help staff, volunteers, leadership, and boards understand supported platforms, security responsibilities, access practices, and technology governance.

Compliance Readiness

SoAtomic may deepen technical readiness services for selected frameworks when qualified knowledge, current sources, review procedures, insurance, and specialist relationships support the responsibility. Certified audit and legal boundaries remain explicit.

Community Programs

Potential initiatives include nonprofit workshops, chamber presentations, technology clinics, resource libraries, and partnerships that strengthen organizations before they become clients.

Platform Expansion

Every platform must earn its place by satisfying security, administrative, interoperability, documentation, portability, organizational fit, and supportability requirements.

Services That Will Not Enter the Roadmap

Creative production, routine site publishing, advertising, campaign management, residential support, consumer repair, and vendor-lock-in business models do not belong in the SoAtomic roadmap.

Chapter 28 - Revision History

Version 2.1 - Broad Client Eligibility

This revision:

• Repositions SoAtomic as an independent corporate MSP serving businesses and organizations across industries.

• Makes consultation and practical fit review the standard entry point before SoAtomic accepts responsibility.

• Retains nonprofit and community-sector experience as sector-specific expertise rather than a client prerequisite.

• Adds clearer support for Apple, Microsoft, Google, Linux, Android, iOS, cloud, endpoint, web-infrastructure, and business-system environments within reviewed scope.

• Removes the categorical limitation against new Microsoft 365 environments while preserving specialist boundaries for complex, legacy, or highly specialized infrastructure.

Version 2.0 - MSP Edition

This revision:

• Repositions SoAtomic as a managed service provider and technology steward.

• Replaces the former website-production service architecture with Screen, Solutions, and Support.

• Removes client creative, editorial, routine publishing, and site-production responsibilities.

• Reframes web-related work as domain, DNS, SSL, hosting, uptime, security, access, backup, and vendor coordination.

• Adds endpoint, user-lifecycle, proactive maintenance, security, vendor-management, wireless-project, and compliance-readiness standards.

• Centered nonprofits and mission-aligned organizations in the then-current ideal-client and service model.

• Replaces Build and Care tier terminology with the current Support plan ladder.

• Makes published pricing and signed agreements authoritative for current rates.

Amendment Process

Every material revision should identify:

• What changed

• Why it changed

• Which sections were affected

• When it became effective

• Whether existing client commitments are affected

• Which public or operational sources also require updates

The founder remains steward of the Playbook. Collaborators and AI agents may recommend changes, but published revisions require human approval.

Workshop Reference

The preceding chapters establish philosophy, policy, and operating boundaries. The Workshop Reference provides repeatable material for daily assessment, implementation, support, review, and handoff.

Operational decisions should reference these appendices rather than recreate standards for each engagement.

Appendix A - Complete Service Matrix

Stage 1: Screen

Standard Screen Deliverables

• Findings report

• Ownership and control review

• System documentation appropriate to the category

• Prioritized recommendations

• Immediate risk identification

• Roadmap and next steps

• Client-owned copy of all deliverables

Stage 2: Solutions

Every Atomic Action Includes

• Planning

• Implementation

• Testing

• Documentation

• Handoff

Common Separately Priced Dependencies

• Vendor licenses

• Hardware and equipment

• Specialist labor

• Cabling, construction, and installation

• Travel or onsite attendance

• External audit or legal review

• Additional Actions required for additional outcomes

Stage 3: Support

The following matrix is a service summary. The current published plan and signed agreement define exact terms.

Support Enterprise Scope Notes

Wireless

SoAtomic plans and manages wireless infrastructure projects, coordinates qualified specialists, vendors, and service providers, and oversees technical coordination throughout the project.

Equipment, cabling, construction, and specialist installation labor are priced separately. Before any separately priced work begins, customers receive three competitive bids for labor and materials.

Compliance Readiness Review

SoAtomic performs technical readiness reviews and provides remediation guidance based on applicable, publicly available regulatory requirements and framework guidance current at the time of the review.

These reviews address technical readiness only. SoAtomic does not provide certified audits, legal advice, formal attestations, or regulatory determinations.

Appendix B - Solution Pattern Catalog

The Solution Pattern Catalog documents repeatable Remedies and Boosts. A pattern becomes standardized only after its scope, dependencies, test procedure, documentation, security considerations, and support impact are understood.

Pattern Requirements

Each pattern should identify:

• Pattern name

• Remedy or Boost classification

• Business problem

• Supported platforms

• Prerequisites

• Client inputs

• Security and data considerations

• Implementation steps

• Acceptance test

• Documentation output

• Ongoing support requirement

• Known limitations

• Separately priced dependencies

Representative Patterns

Access Recovery

Recover administrative control of a supported domain, cloud tenant, or SaaS platform; establish client-controlled recovery; remove obsolete provider access; and document ownership.

Joiner, Mover, Leaver Workflow

Create a documented and optionally automated process for onboarding, role change, and offboarding across supported identity, group, device, and business systems.

Shared Drive Governance

Establish Shared Drive structure, ownership, groups, permission standards, naming, and lifecycle guidance so organizational records do not remain tied to individuals.

License Reconciliation

Compare active users, licenses, contracts, and actual need; identify unused or duplicate cost; document renewal and cancellation decisions.

Email Authentication Remedy

Review and correct supported SPF, DKIM, DMARC, DNS, and sending-service dependencies; test expected mail flow; and document ownership and monitoring.

Endpoint Enrollment

Enroll a defined endpoint set in an approved management platform, apply the approved baseline, verify encryption and update status, and document exceptions.

Backup Verification

Confirm protected systems, retention, alerting, recovery ownership, and a meaningful restore test appropriate to scope.

Intake Automation

Connect a supported intake source to the approved destination, validate field mapping, access, error handling, notification, and data ownership.

Financial Bridge

Connect supported operational and accounting platforms so approved records move without duplicate entry. The client retains responsibility for accounting policy and final financial accuracy.

Inbox Triage

Identify supported messages, extract defined information, route work, and create appropriate records or tasks. The client owns classification policy and sensitive-data decisions.

Pattern Retirement

A pattern should be retired when its platform is unsupported, the security model is no longer acceptable, maintenance exceeds value, demand is insufficient, or a safer standard replaces it. Existing clients require a documented transition plan.

Appendix C - Platform Compatibility Matrix

Platform status should be maintained in a current operational register. The categories below define how status is assigned.

Preferred

Platforms in which SoAtomic maintains high confidence and expects to provide ongoing administration when included by plan.

Examples may include:

• Google Workspace

• Google Cloud

• Microsoft 365 for reviewed and accepted environments

• Apple Business Manager

• Approved MDM platforms

• Cloudflare

Supported

Platforms SoAtomic may administer or integrate within defined boundaries.

Examples may include:

• Windows endpoints

• Microsoft cloud environments for reviewed and accepted engagements

• Supported Linux environments

• ChromeOS

• iOS, iPadOS, and Android

• Submittable

• HubSpot

• Shopify operational administration and integrations

• Copper CRM

• Salesforce and Agentforce at Enterprise scope

• Stripe

• QuickBooks Online integrations

• Zapier and Make

Partner-Supported

Services coordinated through qualified specialists:

• Structured cabling

• Wireless surveys and installation

• VoIP infrastructure

• Hardware repair

• Penetration testing

• Incident forensics

• Certified compliance audits

• Legal and regulatory counsel

• Accessibility specialist review

• Creative and editorial services

Unsupported

• Residential technology

• Consumer repair

• On-premises Exchange Server

• Legacy or unsupported server platforms

• Unmaintained SaaS or automation tools

• Platforms that prevent reasonable client ownership or data export

• Systems outside SoAtomic's training, tooling, insurance, or operational capacity

Required Platform Record

Every platform entry should identify:

• Status

• Supported responsibility

• Exclusions

• Required plan

• Security confidence

• Administrative model

• Data export capability

• Known limitations

• Related patterns

• Vendor escalation path

• Review date

Appendix D - Pricing Reference Rules

Authoritative Source

The current published pricing source and signed client agreement are authoritative. This appendix defines presentation and governance, not permanent numeric values.

Price Presentation

• Show the complete currency amount.

• State the billing unit in plain language.

• Distinguish one-time and recurring charges.

• Identify taxes and pass-through costs where applicable.

• Identify whether equipment or licensing is included.

• State minimums or prerequisites.

• Avoid "starting at" language unless the starting condition is explicit.

• Avoid "Contact Sales" for standardized services that have a real price.

Service Pricing Categories

• Screen - fixed price per assessment category

• Atomic Action - fixed price per defined outcome

• Support - recurring price using the published plan and billing basis

• Support Enterprise - published or quoted as current policy determines, with scope documented

• Add-ons - separately identified recurring or one-time charge

• Equipment and specialist labor - separately quoted and approved

Change Control

When pricing changes, review:

• Pricing page

• Support page

• Screen and Solutions pages

• Homepage previews

• FAQ

• Structured data

• Proposal templates

• Support agreement templates

• Sales and onboarding materials

• Internal billing configuration

Existing client treatment must follow the signed agreement and documented notice policy.

Appendix E - Workshop Vocabulary

Customer-Facing Terms

Internal Terms

Retired Terms

The following former customer-facing service terms should not be used for the current MSP journey:

• Atomic Build

• Build Element

• Atomic Care

• Care Element

• Atomic Growth as a separate lifecycle stage

• Hydrogen, Carbon, Titanium, Gold, and Plutonium service tiers

• Hangar as a visual project portfolio if it obscures the meaning of case studies

Historical records may retain retired terms when necessary for context, but new proposals, site copy, and service documentation should use Screen, Solutions, and Support.

Appendix F - Glossary

Business Terms

Billing unit: The measurable basis for a recurring price, such as per user per month.

Deliverable: A defined item, record, configuration, report, or outcome provided by an engagement.

Managed service provider (MSP): A provider that assumes defined ongoing responsibility for supported technology under a recurring agreement.

Fit review: The practical review of environment, needs, expectations, risk, scope, access, security requirements, and supportability before SoAtomic accepts responsibility.

Scope: The work, responsibility, systems, users, locations, inclusions, and boundaries of an engagement.

Stewardship: Ongoing care that improves reliability and security while preserving client ownership and understanding.

Vendor lock-in: Dependency created by withheld access, provider ownership, proprietary barriers, missing documentation, or unreasonable transition friction.

Technical Terms

DNS: The system that directs domain names to services such as sites and email.

EDR: Endpoint detection and response tooling used to detect, investigate, and respond to suspicious endpoint activity.

Endpoint: A computer, phone, tablet, or other managed user device.

Identity provider: A platform that manages user identities and authentication for connected services.

MDM: Mobile device management or a broader endpoint-management system used to apply settings, security standards, and inventory controls.

MFA: Multi-factor authentication, which requires more than one form of verification.

RTO: Recovery time objective, the targeted time for restoring a service after disruption.

RPO: Recovery point objective, the acceptable amount of data loss measured in time.

SaaS: Software delivered and operated as an online service.

SSO: Single sign-on, which allows a central identity to authenticate to supported services.

Tenant: An organization's administrative environment within a cloud platform.

Compliance Terms

Attestation: A formal statement issued by an authorized party about compliance or control effectiveness.

Certified audit: A formal assessment performed by a qualified or authorized auditor under the applicable standard.

Compliance readiness: Technical preparation intended to identify gaps and improve alignment; it does not establish legal compliance.

Framework guidance: Published criteria or practices associated with a standard, regulation, or assurance framework.

Appendix G - Anti-Goals

Services SoAtomic Does Not Provide

• Residential technology support

• Consumer computer repair

• Printer repair

• Hardware component repair

• On-premises server administration

• Structured cabling labor

• Electrical or construction labor

• Security-camera installation

• Badge-access installation

• Certified compliance audits

• Legal advice or regulatory determinations

• Advertising or campaign management

• Creative production or routine client-site publishing

• Search-marketing campaigns

• General technology resale without a service purpose

Business Models SoAtomic Will Not Become

• A high-volume ticket factory

• A hardware reseller driven by product margin

• A commissioned sales organization

• A marketing or advertising agency

• A vendor-lock-in platform

• A residential repair shop

• A general contractor that performs regulated or specialist labor without qualification

• A provider that claims unlimited responsibility through vague agreements

Operational Anti-Goals

• Hidden pricing

• Undocumented environments

• Shared administrator credentials without necessity

• Provider-owned client domains or tenants

• Unsupported security promises

• Artificially difficult cancellation

• Fear-based selling

• Treating nonprofits as a generic market segment

• Accepting more clients than SoAtomic can responsibly support

• Allowing an urgent ticket to create an undocumented permanent policy

Appendix H - MSP Engineering Standards

Each standard should answer: How do we know this work is complete and supportable?

Identity Standard

• Client-controlled super-administrator recovery exists.

• Named administrative accounts are used.

• MFA is enabled according to policy.

• Roles follow least privilege.

• User lifecycle is documented.

• Shared resources are not dependent on departing individuals.

• Exceptions have an owner and review date.

Endpoint Standard

• Device inventory is current.

• Assigned user or function is recorded.

• Supported operating system is installed.

• Encryption is verified.

• Updates are configured.

• Management enrollment is verified when included.

• Security tooling and alert responsibility are documented.

• Backup or data-location expectations are clear.

• Lost-device procedure exists.

Cloud Standard

• Client ownership and billing are verified.

• Administrative access is named and recoverable.

• Major services and dependencies are inventoried.

• Logging and monitoring are appropriate to risk.

• Cost ownership and renewal responsibility are documented.

• Data export and transition considerations are known.

Web Infrastructure Standard

• Domain and registrar ownership are verified.

• DNS hosting and records are documented.

• SSL is valid and renewal responsibility is known.

• Hosting ownership, billing, and vendor contact are documented.

• Backup and recovery responsibility are known.

• Uptime or incident routing is defined when included.

• Administrative access is client-controlled.

• Creative and editorial responsibility is assigned to the client or designated provider.

Security Standard

• Identity, MFA, least privilege, updates, endpoints, backups, and recovery are addressed proportionately to risk.

• Alerts have an owner and escalation path.

• Security claims match the tools and staffing actually provided.

• Incident boundaries and specialist escalation are documented.

• Sensitive information is handled only through approved systems.

Documentation Standard

• Documentation is current enough to support the agreed responsibility.

• Ownership and recovery are explicit.

• Changes are dated or versioned when material.

• Credentials are not stored in ordinary documentation.

• Client-facing explanations use plain language.

• Known uncertainty and exceptions are visible.

Support Standard

• Supported users, endpoints, locations, and platforms are known.

• Coverage and contact methods are documented.

• Priority and response definitions are clear.

• Tickets record action, result, and next owner.

• Recurring issues produce a problem record or improvement recommendation.

• Documentation is updated after material change.

• Plan scope is reviewed when responsibility changes.

Solution Standard

• Outcome and acceptance test are written before implementation.

• Required access and client approval exist.

• Change risk and rollback are considered.

• Implementation is tested.

• Documentation is updated.

• Client ownership is confirmed.

• Ongoing support responsibility is assigned.

Compliance-Readiness Standard

• Applicable public source and review date are recorded.

• Technical observation is separated from legal conclusion.

• Evidence and limitation are documented.

• Remediation guidance is proportionate and actionable.

• Certified audit, attestation, and legal boundaries are repeated in the deliverable.

Wireless Project Standard

• Requirements and coverage goals are documented.

• Qualified specialist responsibility is explicit.

• Equipment and labor costs are separate.

• Competitive bids are documented according to the agreement.

• Installation, cabling, construction, and electrical responsibility are assigned to qualified providers.

• Testing and acceptance criteria are agreed.

• Final configuration and vendor records are delivered to the client.

Appendix I - Engineering Checklists

Screen Checklist

• ☐
  Client objective and authorized scope confirmed

• ☐
  Relevant accounts and assets inventoried

• ☐
  Ownership and recovery reviewed

• ☐
  Configuration evidence collected

• ☐
  Security and continuity considered

• ☐
  Observations separated from risks and recommendations

• ☐
  Findings prioritized

• ☐
  Client-performed actions identified

• ☐
  Remedies, Boosts, Support needs, and specialist referrals distinguished

• ☐
  Documentation package delivered

• ☐
  Client ownership confirmed

Atomic Action Checklist

• ☐
  One outcome defined

• ☐
  Acceptance criteria defined

• ☐
  Dependencies and client responsibilities documented

• ☐
  Required access approved

• ☐
  Change and rollback approach considered

• ☐
  Implementation completed

• ☐
  Functional and security testing completed

• ☐
  Documentation updated

• ☐
  Client handoff completed

• ☐
  Ongoing support owner identified

Support Onboarding Checklist

• ☐
  Agreement and plan scope confirmed

• ☐
  Billing unit, users, endpoints, and locations confirmed

• ☐
  Authorized contacts recorded

• ☐
  Administrative access verified

• ☐
  MFA and recovery verified

• ☐
  Platform and vendor inventory created

• ☐
  Endpoint inventory created

• ☐
  Existing issues and risks documented

• ☐
  Monitoring and alert routing configured as included

• ☐
  Backup responsibility documented

• ☐
  Security-tool responsibility documented

• ☐
  Coverage and emergency process explained

• ☐
  Remediation plan approved

User Onboarding Checklist

• ☐
  Authorized request received

• ☐
  Role and access template identified

• ☐
  Account created in supported identity system

• ☐
  MFA and recovery configured

• ☐
  Groups and shared resources assigned

• ☐
  Device enrollment completed as included

• ☐
  Required applications assigned

• ☐
  Sensitive access separately approved

• ☐
  User receives secure activation guidance

• ☐
  Inventory and documentation updated

User Offboarding Checklist

• ☐
  Authorized request and effective time confirmed

• ☐
  Sign-in blocked at the approved time

• ☐
  Sessions and tokens revoked as appropriate

• ☐
  Groups, roles, and third-party access removed

• ☐
  Device return or remote action coordinated

• ☐
  Organizational data transferred

• ☐
  Shared-resource ownership reassigned

• ☐
  Mail and communication disposition approved

• ☐
  Licenses reclaimed

• ☐
  Recovery methods reviewed

• ☐
  Documentation updated

Endpoint Checklist

• ☐
  Asset and assigned user recorded

• ☐
  Supported operating system verified

• ☐
  Encryption verified

• ☐
  Updates configured

• ☐
  MDM or endpoint-management enrollment verified

• ☐
  Security tooling installed and reporting

• ☐
  Local administrator standard applied

• ☐
  Backup or data-location expectation confirmed

• ☐
  Recovery information recorded securely

• ☐
  Exception documented if any control is not met

Support Review Checklist

• ☐
  User, endpoint, location, and platform counts reviewed

• ☐
  Ticket and recurring-problem trends reviewed

• ☐
  Open risks and recommendations reviewed

• ☐
  Identity and administrative access reviewed

• ☐
  Security-tool and backup status reviewed

• ☐
  Vendor and renewal calendar reviewed

• ☐
  Technology spend and anomalies reviewed as included

• ☐
  Major incidents and lessons reviewed

• ☐
  Upcoming organizational changes discussed

• ☐
  Plan fit reviewed

• ☐
  Decisions and next actions documented

Wireless Project Checklist

• ☐
  Business and coverage requirements documented

• ☐
  Site and specialist assessment coordinated

• ☐
  Responsibility matrix approved

• ☐
  Three competitive bids obtained

• ☐
  Equipment and labor approvals recorded

• ☐
  Installation schedule coordinated

• ☐
  Configuration and security plan reviewed

• ☐
  Acceptance testing completed

• ☐
  Final inventory, configuration, warranty, and vendor documentation delivered

Compliance Readiness Checklist

• ☐
  Supported framework and scope confirmed

• ☐
  Current public source recorded

• ☐
  Evidence request defined

• ☐
  Technical controls reviewed

• ☐
  Gaps and uncertainty documented

• ☐
  Remediation priorities developed

• ☐
  Legal and certified-audit exclusions stated

• ☐
  Qualified specialist referral made if required

• ☐
  Client report delivered

Offboarding Checklist

• ☐
  Effective date and transition owner confirmed

• ☐
  Client ownership of accounts and contracts verified

• ☐
  Current documentation exported

• ☐
  Open issues and risk transferred

• ☐
  Incoming provider coordination completed as agreed

• ☐
  Delegated SoAtomic access removed

• ☐
  Management profiles or integrations transitioned safely

• ☐
  Vendor billing responsibility confirmed

• ☐
  Final client acknowledgment received

SoAtomic Public Website Release Checklist

This checklist applies only to SoAtomic's own public site.

• ☐
  Service names match Screen, Solutions, and Support

• ☐
  Prices and billing units match the authoritative source

• ☐
  No excluded client service is advertised

• ☐
  Client eligibility and fit-review language are current

• ☐
  Nonprofit and community-sector language is concrete and respectful

• ☐
  Forms deliver real submissions

• ☐
  Accessibility checks pass

• ☐
  Performance and responsive behavior are verified

• ☐
  DNS, SSL, deployment, and monitoring are healthy

• ☐
  Privacy and tracking statements match implementation

• ☐
  Structured data matches visible content

Appendix J - Engineering Maxims

• Technology should become quieter.

• Assess before recommending change.

• Recommend what solves the problem.

• Clear expectations build lasting relationships.

• Every layer of complexity should justify its existence.

• Serve a manageable number of clients exceptionally well.

• Predictability is part of the product.

• Support the client without trapping the client.

• If it works only because one person remembers how, it is not finished.

• Own less. Document more.

• Explain first. Engineer second.

• Simple systems age better.

• We configure it. You own it.

• Responsibility should be visible before it becomes recurring.

• Define the outcome before starting the work.

• Protect the systems that protect the work.

• Focus creates expertise.

• AI assists. Humans decide.

• Good collaboration should feel organized to the client.

• A client who is free to leave is free to stay because the service remains valuable.

Closing

Every organization develops habits. Some are chosen. Most are formed through repetition.

The SoAtomic Playbook exists so the Workshop's habits are deliberate: assess before changing, explain before asking for trust, document before knowledge disappears, define responsibility before accepting it, and preserve client ownership throughout the relationship.

Technology will continue to change. Platforms will mature and disappear. Threats will evolve. AI will transform implementation. New services will become practical, and current assumptions will become obsolete.

When faced with uncertainty, choose clarity over confusion. When presented with unnecessary complexity, choose simplicity. When tempted by short-term gain, choose long-term trust. When asked to accept responsibility outside SoAtomic's capability, choose an honest boundary and the right specialist.

Good managed service improves technology.

Great stewardship improves confidence.

The Workshop Oath

I will recommend what serves the client, even when it benefits the Workshop less.

I will explain my reasoning before asking for trust.

I will assess environments before recommending change.

I will build and maintain systems that people can understand, own, and continue without me.

I will favor clarity over cleverness and simplicity over unnecessary complexity.

I will document my work so another qualified person can continue it.

I will respect the client's ownership of technology, data, accounts, contracts, and future choices.

I will set clear boundaries and honor them professionally.

I will protect sensitive information and use access only for its authorized purpose.

I will continue learning without assuming every new technology deserves adoption.

I will use artificial intelligence to improve engineering, never to replace judgment or accountability.

I will review each prospective relationship for fit, scope, expectations, risk, and supportability before accepting responsibility.

I will understand that organizations measure value through the work they can do for people, customers, members, patients, communities, and teams, not technology for its own sake.

I will leave every organization stronger than I found it.

Technology is rarely the goal.

People and work are.