Services

Opsfleet Portfolio Extension


Opsfleet portfolio extension research

Date: 2026-06-22

Scope#

This is a research artifact only. It does not change Assistance product UI, routes, navigation, service content, pricing, or quote behavior.

Public Opsfleet sources consulted#

Assistance implementation inspected#

  • apps/www/app/(pages)/services/page.tsx
  • apps/www/app/(pages)/services/ServicesContent.tsx
  • apps/www/app/(pages)/services/[slug]/page.tsx
  • apps/www/app/(pages)/services/[slug]/ServicePage.tsx
  • apps/www/app/(pages)/services/_compatServicePage.tsx
  • apps/www/app/(pages)/services/managed-cdn/page.tsx
  • apps/www/app/(pages)/services/managed-load-balancing/page.tsx
  • apps/docs/content/guides/services/
  • apps/docs/content/guides/infrastructure/
  • packages/navigation/navigation.json
  • apps/www/lib/service-pricing-data.ts
  • apps/www/lib/service-quote-mapping.ts
  • apps/www/lib/service-highlights.ts
  • apps/www/lib/managed-infra-pricing.ts

Portfolio mapping#

Opsfleet service / offerCurrent Assistance equivalent or gapRecommended Assistance slug / titleImplementation notes
DevOps as a Service / Fractional DevOpsStrong equivalent: /services/devops-as-a-service; Services overview already positions an ongoing retainer with CI/CD, IaC, Kubernetes, and Slack access.Keep devops-as-a-service / DevOps as a ServiceNo new slug required. If positioning is expanded later, emphasize embedded/fractional team, roadmap ownership, sprint participation, and packaging/on-site-installation support in the existing MDX/frontmatter.
AI as a ServicePartial equivalent: /services/ai-agent-infrastructure, /services/agent-orchestration, and /services/agent-observability. Gap: broader AI discovery, RAG, fine-tuning, responsible AI/governance, hybrid/on-prem AI deployment, and production support as one buyer-facing offer.ai-as-a-service / AI as a ServiceAdd content under apps/docs/content/guides/services/ai-as-a-service/index.mdx if this becomes a real offer. Add quote category mapping in service-quote-mapping.ts; likely mark on-request in service-pricing-data.ts unless productized. Navigation can group under a future AI/platform section rather than managed infrastructure.
Data as a ServicePartial infrastructure equivalent through managed PostgreSQL/MySQL/MongoDB/Redis/Kafka/OpenSearch and cloud infrastructure. Gap: analytics warehouse, behavioral data pipelines, semantic layer, dashboards, natural-language query, and business insight delivery.data-platform-engineering / Data Platform Engineering or data-as-a-service / Data as a ServicePrefer Data Platform Engineering if Assistance should stay infrastructure-oriented and avoid BI/consumer analytics promises. Would need a new services MDX page, quote mapping, on-request pricing, and navigation placement outside managed databases.
Cloud MigrationStrong partial equivalent: /services/cloud-infrastructure includes migration and modernization; /services/kubernetes-migration, /services/vmware-migration, and /services/cloud-account-management cover adjacent cases.cloud-migration / Cloud MigrationNew campaign-style slug could wrap existing cloud infrastructure migration content. Implement as docs-backed service MDX and add navigation only if migration deserves a first-class buyer journey. Quote category should be infrastructure or consulting.
Kubernetes Adoption / Kubernetes ImplementationStrong equivalent: /services/managed-kubernetes, /services/kubernetes, /services/kubernetes-migration, and /services/kubernetes-support.Keep existing slugs; optional kubernetes-adoption / Kubernetes Adoption campaign pageNo gap in capability. A new page would mostly consolidate existing Kubernetes implementation, migration, K3s deployment options, support, GitOps, observability, and security proof points. Avoid duplicating existing service pages unless SEO/campaign needs justify it.
Shift to GravitonPartial equivalent: /services/cost-optimization, /services/cloud-infrastructure/aws, and Kubernetes/cloud operations can cover AWS compute right-sizing. Gap: explicit AWS Graviton assessment and migration execution.aws-graviton-migration / AWS Graviton MigrationTreat as a focused cost/performance modernization project, not a core nav item. Add on-request service description and consulting quote mapping if added. Content should cover assessment, dependency compatibility, test rollout, EKS node groups, production cutover, and savings validation.
DevSecOps as a ServicePartial equivalent: /services/security-audit, /services/security-compliance, /services/cicd-audit, and DevOps/SRE retainers. Gap: ongoing DevSecOps execution retainer for CISOs/security roadmaps.devsecops-as-a-service / DevSecOps as a ServiceAdd docs-backed service page if Assistance wants an execution retainer distinct from audits. Map quote category to consulting; add on-request pricing or hourly retainer config. Navigation fit: Security & Compliance group.
AWS Marketplace Provisioning & OnboardingWeak equivalent: /services/technology-consulting, /services/solution-for-saas, /services/solution-for-paas, and managed artifact/container delivery pages are adjacent. Gap: AWS Marketplace SaaS packaging, onboarding, deployment automation, and go-to-market support.aws-marketplace-onboarding / AWS Marketplace OnboardingSpecialist offer; keep on request. If implemented, content should avoid broad business-development claims and focus on technical packaging, deployment automation, metering/provisioning integration, Marketplace constraints, and handoff. Quote category: consulting.
DRP as a Service / Disaster Recovery Plan implementationPartial equivalent: /services/sre-as-a-service, /services/cloud-infrastructure, managed data services, and incident response. Gap: dedicated DR assessment, RTO/RPO planning, automated failover, DR testing, validation, and ongoing readiness.disaster-recovery-planning / Disaster Recovery PlanningGood fit for Assistance portfolio. Add service MDX and map to infrastructure or consulting. Could reuse SRE/cloud implementation patterns and mark pricing on request. Navigation fit: Managed Kubernetes or Consulting, depending on whether positioned as implementation or advisory.
Site-level AI portfolio: multi-agent AI systems, AI operational excellence, AI governance and controlPartial equivalent: agent infrastructure/orchestration/observability pages. Gap: AI governance/control and operational-excellence layer beyond infrastructure hosting.ai-governance / AI Governance or extend ai-as-a-serviceIf Assistance pursues AI services, add one umbrella AI service first, then split governance only after there is enough distinct content. Quote mapping and pricing should remain on request.

Existing implementation pattern to use later#

Assistance service pages are mostly content-backed: apps/www/app/(pages)/services/[slug]/page.tsx resolves apps/docs/content/guides/services/<slug>/index.mdx and apps/docs/content/guides/infrastructure/<slug>/index.mdx. Adding a normal service generally requires:

  1. Create the MDX page with frontmatter and highlights.
  2. Add the route to packages/navigation/navigation.json if it should appear in menus.
  3. Add quote routing in apps/www/lib/service-quote-mapping.ts.
  4. Add pricing or on-request copy in apps/www/lib/service-pricing-data.ts.
  5. Add managed-infrastructure calculator data in apps/www/lib/managed-infra-pricing.ts only for calculator-style infrastructure components.

managed-cdn and managed-load-balancing are exceptions implemented as direct compatibility pages under apps/www/app/(pages)/services/; new services should prefer the docs-backed MDX pattern unless there is a specific reason to use a direct page.