Services

Proposition Inventory 2026 06 26

Assistance proposition inventory — 2026-06-26

Purpose: source-of-truth inventory of the proposition surfaces requested in TASK.md. This is an audit note only; it does not rewrite product positioning.

Audited surfaces#

  • apps/www/app/(pages)/services/ServicesContent.tsx — marketing /services landing page.
  • apps/www/app/(pages)/services/[slug]/page.tsx and ServicePage.tsx — generated /services/[slug] detail pages backed by docs guide MDX.
  • apps/www/app/consulting/page.tsx — marketing /consulting landing page.
  • apps/www/app/infrastructure/page.tsx — marketing /infrastructure landing page.
  • packages/navigation/navigation.json — shared primary/global navigation.
  • apps/docs/content/guides/services/index.mdx — docs services index.
  • apps/docs/content/guides/infrastructure/managed-infrastructure/index.mdx — docs managed infrastructure index.

Route and CTA mechanics#

  • /services is a bespoke landing page with three engagement modes and a portfolio grid.
  • /services/[slug] is generated from apps/docs/content/guides/services/<slug>/index.mdx first, then apps/docs/content/guides/infrastructure/<slug>/index.mdx; services content shadows infrastructure content when the same slug exists.
  • /services/[slug] default primary CTA is Get a quote using getQuoteHrefForSlug(slug); default secondary CTA is View pricing only when pricing exists and the slug is not in the managed-infrastructure set.
  • MDX frontmatter can override detail-page hero CTAs with heroCtaPrimary and heroCtaSecondary.
  • /consulting CTA is Book a consulting review → via contact FormTrigger.
  • /infrastructure CTA is Talk through the add-on → via contact FormTrigger.
  • Docs service index CTAs are Book a service assessment (/contact-sales) and Compare pricing plans (/guides/services/pricing).
  • Docs managed infrastructure index CTAs are Request infrastructure assessment (/contact-sales) and Compare pricing (/pricing).

Marketing /services proposition map#

Engagement modes#

ModeBoundaryPrimary route
Ongoing RetainerMonthly retained senior platform help across reliability, cost, security, CI/CD, Kubernetes, and IaC./services/devops-as-a-service
Project EngagementFixed-scope platform/cloud/security/reliability implementation with acceptance criteria and handoff./services/cloud-infrastructure
Emergency ResponseActive production incident stabilization, report, RCA, and remediation plan./services/emergency

Portfolio cards#

CardCategoryCTA routeNotes
AI & agent platformsAI/services/ai-agent-infrastructureScoped/on-request in pricing metadata.
Data platform engineeringData/services/data-as-a-serviceScoped/on-request.
DevOps as a ServiceDevOps/services/devops-as-a-serviceRetainer with pricing.
Cloud migrationCloud/services/cloud-infrastructureCard label says migration but routes to Cloud Infrastructure, not /services/cloud-migration.
Kubernetes adoptionKubernetes/services/managed-kubernetesManaged service / platform adoption.
DevSecOpsSecurity/services/security-complianceDiffers from nav's /services/devsecops-as-a-service managed-retainer route and /services/security-audit assessment route.
AWS Marketplace onboardingAWS/services/aws-marketplace-onboardingScoped/on-request.
Graviton migrationAWS/services/aws-graviton-migrationScoped/on-request.
Disaster recovery planningResilience/services/sre-as-a-serviceNav and generated docs also expose /services/disaster-recovery-planning.

Capability boundaries surfaced on /services#

The landing page frames capabilities broadly: Kubernetes, CI/CD, IaC, GitOps, AWS/GCP/Azure, PostgreSQL, MySQL/MongoDB, Kafka/OpenSearch, observability/logging, AI platforms, data platforms, cloud migration, security hardening, secrets, DevSecOps, FinOps, DR, service mesh, CDN/edge, self-hosted tooling, and data sovereignty.

Marketing /consulting proposition map#

GroupPropositionRouteBoundary
Advisory ReviewsKubernetes Migration/services/kubernetes-migrationMigration planning around risk, readiness, rollout, and rollback.
Advisory ReviewsGitOps/services/gitopsGit-driven delivery adoption and ownership model.
Advisory ReviewsSecurity Audit/services/security-auditAccess, delivery, and platform security risk review.
Advisory ReviewsInfrastructure Audit/services/infrastructure-auditReliability, ownership, and scaling assessment.
Advisory ReviewsCI/CD Audit/services/cicd-auditPipeline bottleneck, release-risk, and developer-friction review.
Decision SupportSaaS Platform Strategy/services/technology-consultingBuild/buy/simplify decisions across reliability, tenancy, compliance, and cost.
Decision SupportInternal Platform Foundations/services/technology-consultingFoundations, automation, and ownership boundaries.
Decision SupportCommerce Platform Review/services/infrastructure-auditCommerce operations review where uptime/security/ownership affects revenue.
Cloud cost governanceCost optimization/services/cost-optimizationAWS/Azure/GCP savings, rightsizing, commitments, tagging, showback, governance.

Marketing /infrastructure proposition map#

GroupPropositionRouteBoundary
Data & Observability Add-onsManaged PostgreSQL/services/managed-postgresqlBackups, recovery planning, and database health.
Data & Observability Add-onsManaged MySQL/services/managed-mysqlMySQL/MariaDB reliability, upgrades, and ownership.
Data & Observability Add-onsManaged MongoDB/services/managed-mongodbCapacity planning, backups, and guardrails.
Data & Observability Add-onsManaged Kafka/services/managed-kafkaEvent pipeline reliability, monitoring, and change control.
Data & Observability Add-onsManaged OpenSearch/services/managed-opensearchSearch/log analytics indexing, retention, troubleshooting.
Data & Observability Add-onsManaged Prometheus/services/managed-prometheusMetrics and alerting as operational signals.
Local Development & CI RunnersManaged Runners/services/managed-runnersSelf-hosted runner fleets for CI/local-dev predictability.
Local Development & CI RunnersRunner Documentation/docs/guides/runnersNon-commercial docs route from marketing page.
Delivery Platform Add-onsManaged Git Server/services/managed-git-serverOperated GitLab, Gerrit, Gitea, or Forgejo platform option with delivery-platform operations.
Delivery Platform Add-onsManaged Kubernetes (K3s option)/services/managed-kubernetesLightweight Kubernetes for edge/lab/constrained environments.
Delivery Platform Add-onsCertificate Management/services/managed-certificatesTLS lifecycle and certificate hygiene.
Delivery Platform Add-onsDNS as a Service/services/managed-dnsDNS ownership, change control, and uptime.

Primary navigation#

Nav areaCategory boundaryRoutes exposed
ConsultingConsulting/audits and implementation projects./services/technology-consulting, /services/infrastructure-audit, /services/security-audit, /services/cicd-audit, /services/cost-optimization, /services/kubernetes-migration, /services/gitops, /services/cloud-migration, /services/aws-graviton-migration, /services/aws-marketplace-onboarding
Managed ServicesRetainers plus AI delivery./services/sre-as-a-service, /services/devops-as-a-service, /services/managed-kubernetes, /services/devsecops-as-a-service, /services/ai-as-a-service, /services/generative-ai-engineering, /services/ai-agent-infrastructure, /services/agent-orchestration, /services/agent-observability
Platform InfrastructureDelivery/edge platforms and runners./services/managed-git-server, /services/managed-kubernetes, /guides/services/managed-runners, /guides/runners, /guides/infrastructure/managed-git-servers
Data InfrastructureDatastores, observability, data operations./services/managed-postgresql, /services/managed-mysql, /services/managed-mongodb, /services/managed-kafka, /services/managed-opensearch, /services/managed-prometheus, /services/data-as-a-service
ResourcesContent/company routes, not propositions./blog, /docs, /case-studies, /about, /community

The global menu repeats the main retainer, AI, Kubernetes, runner, managed data, and security/audit categories. It additionally exposes /services/emergency, /services/cloud-account-management, /services/disaster-recovery-planning, /services/managed-git-server, /pricing, and /contact-us.

Docs guide proposition map#

Services index (/guides/services)#

Core service lines:

  • DevOps as a Service — /guides/services/devops-as-a-service.
  • SRE as a Service — /guides/services/sre-as-a-service.
  • Managed Kubernetes — /guides/services/managed-kubernetes.
  • Cloud Infrastructure — /guides/services/cloud-infrastructure.
  • Cloud Operations / Cloud Account Management — /guides/services/cloud-account-management.
  • Plans and Pricing — /guides/services/pricing.

Buying-scenario boundaries:

  • Delivery capacity without hiring: DevOps as a Service.
  • Fewer incidents / production ownership: SRE as a Service.
  • Kubernetes platform: Managed Kubernetes.
  • Cloud foundation / migration / modernization: Cloud Infrastructure.
  • Monthly cloud hygiene: Cloud Account Management.
  • Evidence-based assessment: Infrastructure Audit.
  • Pipeline review: CI/CD Audit.
  • Security review: Security Audit.

Package boundaries:

  • Focused audits: Infrastructure Audit, Security Audit, CI/CD Audit.
  • Implementation projects: Managed Kubernetes, Kubernetes Support, Cloud Infrastructure, GitOps.
  • Ongoing plans: XS, S, M, Custom flat/custom monthly support plans.

Managed infrastructure index (/guides/infrastructure/managed-infrastructure)#

Managed products:

  • Managed PostgreSQL — /guides/infrastructure/managed-postgresql.
  • Managed MySQL — /guides/infrastructure/managed-mysql.
  • Managed MongoDB — /guides/infrastructure/managed-mongodb.
  • Managed Redis — /guides/infrastructure/managed-redis.
  • Managed Kafka — /guides/infrastructure/managed-kafka.
  • Managed OpenSearch — /guides/infrastructure/managed-opensearch.
  • Managed Prometheus — /guides/infrastructure/managed-prometheus.
  • Managed Artifactory — /guides/infrastructure/managed-docker-registry.
  • Managed Artifact Repositories — /guides/infrastructure/managed-artifact-repos.

Deployment model boundaries:

  • Assistance-operated physical servers for development, CI/CD dependencies, predictable internal platforms, and steady-state workloads.
  • Customer cloud account for production systems in AWS, Azure, GCP, or Oracle Cloud tenancy.
  • Assistance-managed cloud tenancy when Assistance owns more platform/operations surface.
  • Hybrid development on Assistance physical servers with production in customer cloud.

Generated /services/[slug] inventory#

The marketing site currently generates detail pages for every docs service or infrastructure guide with an index.mdx under the configured content directories:

  • Service docs slugs: agent-observability, agent-orchestration, ai-agent-infrastructure, ai-as-a-service, aws-graviton-migration, aws-marketplace-onboarding, cicd-audit, cloud-account-management, cloud-infrastructure, cloud-management, cloud-migration, cost-optimization, data-as-a-service, devops-as-a-service, devops-trainings, devsecops-as-a-service, disaster-recovery-planning, emergency, finops, generative-ai-engineering, gitops, google-apps-management, infrastructure-audit, kubernetes, kubernetes-migration, kubernetes-support, managed-bitwarden, managed-git-server, managed-kubernetes, managed-mcp-servers, managed-runners, managed-saleor, office365-management, paas-solution, pricing, security-audit, security-compliance, solution-for-paas, solution-for-saas, sovereign-cloud, sovereign-productivity-suite, sre-as-a-service, technology-consulting, vmware-migration.
  • Infrastructure docs slugs also rendered as services: managed-artifact-repos, managed-certificates, managed-dns, managed-docker-registry (Managed Artifactory), managed-git-servers, managed-infrastructure, managed-kafka, managed-mongodb, managed-mysql, managed-opensearch, managed-postgresql, managed-prometheus, managed-redis. Platform-specific GitLab, Gerrit, Gitea, and Forgejo pages remain option runbooks under the Managed Git Server guide, not separate service propositions.
  • Standalone bespoke service routes outside [slug]: /services/managed-cdn and /services/managed-load-balancing.

Obvious drift to resolve downstream#

  1. Cloud migration split: /services routes the Cloud migration card to /services/cloud-infrastructure, while navigation and docs expose /services/cloud-migration / /guides/services/cloud-migration as a distinct proposition.
  2. Disaster recovery split: /services routes Disaster recovery planning to /services/sre-as-a-service, while navigation and docs expose /services/disaster-recovery-planning as a distinct scoped proposition.
  3. DevSecOps/security naming split: /services routes DevSecOps to /services/security-compliance; navigation exposes DevSecOps as /services/devsecops-as-a-service and security assessment as /services/security-audit.
  4. Managed runners URL inconsistency: /infrastructure uses /services/managed-runners, while primary navigation uses /guides/services/managed-runners for the same commercial item.
  5. Docs vs marketing infrastructure product set differs: docs managed infrastructure includes Redis, Artifactory, and Artifact Repositories; /infrastructure omits those and instead includes DNS, Certificates, Managed Git Server, K3s, and runner documentation.
  6. Infrastructure docs rendered under service URLs: [slug] intentionally maps infrastructure guide MDX into /services/<slug> routes, but docs index links remain /guides/infrastructure/<slug>, creating two public URL families for the same propositions.
  7. Managed Git Server canonicalization: the marketed route is /services/managed-git-server; platform-specific GitLab, Gerrit, Gitea, and Forgejo pages should remain option runbooks linked from /guides/infrastructure/managed-git-servers, not separate service propositions.
  8. On-request propositions are mixed with productized propositions: several AI, data, DR, Graviton, marketplace, productivity, SaaS/PaaS, and admin/tooling offers are marked on-request/scoped in pricing metadata but appear alongside ongoing/productized services in navigation or landing-page grids.
  9. CTA route language differs by surface: marketing detail pages default to /get-quote/..., marketing landing pages mostly use contact form triggers or /contact-us, and docs indexes use /contact-sales; downstream alignment should choose whether this is intentional funnel segmentation or drift.