What the $300/month company-site add-on covers.
This is the operating standard and hosting addendum for one accepted company website. The site’s current provider and CMS are recorded internally; this product is not tied to either one.
A recorded, supported production platform
For a site that passes preflight, the agency provisions or accepts a supported production environment and manages the hosting relationship while the add-on and underlying client engagement remain active. The implementation may be CMS-based, headless, static, or another supported architecture.
What we verify
- The production endpoint exists and the public domain resolves to it.
- The agency team and the client have the administrative or publishing access needed for the agreed work.
- The current platform, provider, delivery layer, dependencies, license ownership, and accepted functional baseline are recorded internally for that site.
Boundary
The add-on does not include a ground-up redesign, new application development, or unrecorded custom behavior. Named vendors, themes, plugins, frameworks, and build tools are implementation choices rather than perpetual product entitlements.
Platform and functional baseline are recorded at activationManaged HTTPS, caching, and delivery
After routine DNS cutover, we enable and verify HTTPS plus the caching and CDN capabilities supported by the recorded delivery platform. The exact delivery services can change with the accepted architecture and are recorded internally for the site.
Boundary
A managed web application firewall is not included unless that service is separately provisioned and recorded. Nameserver restructuring, email-routing changes, third-party DNS projects, and performance remediation are separately scoped.
Delivery mechanism is verified and recorded, not assumedA recorded recovery method and pre-change rollback point
Operations records the recovery mechanism appropriate to the accepted platform and verifies a current rollback point before a planned platform change. Depending on the architecture, this may use versioned deployments, repositories, provider snapshots, CMS backups, or exports.
Boundary
This is a recovery capability, not a promised recovery time or zero-data-loss guarantee. Long-term archives, off-platform backup retention, disaster-recovery drills, historical application logs, and custom RTO/RPO requirements require a separate scope.
Recovery method and rollback owner are visible in the registerPlanned maintenance for supported platform components
We plan applicable supported maintenance, verify a rollback point first, and perform a basic post-change check of the homepage, agreed key pages, primary lead path, tracking presence, and publishing or administrative access. Depending on the architecture, maintenance may cover supported CMS components, dependencies, runtimes, builds, or deployments.
Boundary
Paid licenses, incompatible or abandoned software, custom-code remediation, accessibility/legal remediation, significant malware reconstruction, performance work, and new functionality are not included. Provider-managed infrastructure patching remains the provider’s responsibility.
Rollback-first change control with a defined functional checkStandard migration, cutover, and functional-baseline QA
Subject to preflight acceptance, we take or verify the available source export, copy or deploy the accepted site to the supported destination, test it before cutover, coordinate routine DNS changes, and verify HTTPS, agreed public pages and URLs, the primary lead path, recorded redirects, tracking presence, search controls, and publishing access.
If the agency initiates a move to a different provider, CMS, headless stack, static build, or other supported architecture, the accepted functional baseline—not a specific vendor or plugin—is the transition target. We test the new implementation against that record before the source is decommissioned.
Boundary
Source-server logs, installed-but-unused components, and unrecorded behavior are not automatically migrated. Ground-up redesigns, substantial malware reconstruction, ecommerce or account-history synchronization, custom integrations, complex DNS/email changes, paid licenses, and net-new functionality are separately scoped before work begins.
Cutover is gated by the functional baseline and checklist belowPlatform-provider escalation and incident coordination
When evidence points to the underlying platform or provider, the agency opens a support case, supplies the relevant site and incident context available to us, and follows up through resolution or a clear next action.
Boundary
Provider response and resolution times are outside the agency’s control. The add-on does not include a 24/7 staffed help desk, guaranteed uptime, performance monitoring, or an SLA unless those terms are separately written and signed.
A recorded escalation path, without promising provider timingThe functional baseline
Plugins and themes are implementations, not the durable promise. Before activation or a platform transition, Operations records the accepted business functions that are actually present and in use.
Activation checklist
The add-on is not marked active until Operations records these items in the per-site service register.
Hosting addendum
This is an add-on for an active company or local-service engagement with the agency managing this site. It is not standalone hosting and does not cover personal-brand properties or products such as The Athlete Spotlight. If the underlying engagement ends, the agency will coordinate a written transition; continued standalone service is not automatic.
Each $300 monthly subscription covers one accepted company website. Charges recur monthly until canceled through the agency or the billing system.
No CMS, hosting provider, plugin, theme, framework, or delivery vendor is a perpetual product commitment. The agency may replace the CMS, host, delivery layer, or supporting components with another supported managed architecture, including headless or static delivery. An agency-initiated transition is tested against the accepted functional baseline.
The accepted baseline consists only of the public content, URLs, lead path, routing, search controls, measurement, publishing workflow, dynamic behavior, integrations, dependencies, and recovery method that Operations records. Installed-but-unused components and unrecorded functionality are not automatically included.
The agency may pause activation or transition and propose a separate scope if preflight finds unsupported infrastructure, ecommerce or user-account complexity, material malware, custom-code risk, missing access, missing licenses, or another condition outside this standard.
The six service sections, functional baseline, and activation checklist define the included work. Routine DNS cutover is included; domain registration, email hosting, nameserver/email restructuring, redesign, content publishing, SEO strategy, ad management, new development, custom integrations, premium licenses/extensions, third-party fees, and substantial remediation are not.
No specific uptime, response-time, recovery-time, recovery-point, performance, lead-volume, or revenue guarantee is included. Any different service level must be separately written and signed.
On cancellation, the agency will coordinate access and make a current site export, repository handoff, or backup available when the recorded platform permits. The client is responsible for choosing and funding the destination. Outbound migration, complex DNS changes, and third-party licenses or services owned by the agency are not included unless separately agreed.
Use the active Basecamp project for planned work and the billing or contact method shown on the order receipt for cancellation or access help. Do not place passwords in public messages.
Return to the company-site add-on.
Confirm the site and functional baseline in your active Basecamp project before checkout.
Back to the offer