SP
SOLIDPROFESSOR
Core Platform Team
SP Foundation

How SolidProfessor Grows

We need to move faster—without cutting corners on what makes people trust our products: security, quality, accessibility, reliability, privacy, and how we use AI.

Summary

We're building SP Foundation—one shared system for how we build, ship, and run our products. It holds our standards (security, quality, accessibility, reliability, privacy, responsible AI) and SP Accelerators: ready-made building blocks that make hitting those standards the fast way, not the slow way. Teams still own their outcomes—they just stop rebuilding the same basics.

Security and compliance should be built in, not checked at the end. Accessibility should be the default. Reliable releases, useful monitoring, solid quality, responsible AI—that should just be how we work.

Security Quality Accessibility Reliability Privacy Responsible AI

Standards Need Working Parts

A standard tells you what good looks like. It doesn't help you get there faster. That's what SP Accelerators are for: pipelines, scaffolds, design components, test patterns, monitoring setups, security controls, data integrations, AI agents, workflows. You pick one up, and the right practices come with it.

The System

SP Foundation

Shared standards, guardrails, services, and supported Accelerators for trustworthy delivery.

The Working Parts

SP Accelerators →

Pipelines, scaffolds, components, controls, workflows—the pieces teams pick up and use.

The Model

Leadership Ambition

Grow organizational capability and create more customer value.

SP Foundation

Standards, guardrails, services, and reusable Accelerators teams adopt in daily work.

Product Outcomes

Less time rebuilding basics. More time solving customer problems.

Teams still answer for their customer outcomes—the Foundation just makes delivering them less painful.

Current State

12 active Accelerators

Shipped and supported across Delivery, Quality, Security, and AI.

~40% faster deploys

Teams on ECS Accelerator vs. legacy deployment patterns.

3 environments → 1

V1, V2, V3 consolidating to single governed AWS foundation.

Timeline

Q1–Q2 2026

Foundation launch. Core Accelerators shipped. V3 infrastructure live.

Q3–Q4 2026

V2 downsized. Full team adoption. Data Accelerators ship.

Q1 2027

Legacy off. Optimized run rate. Foundation is default.

Ownership

Core Platform Team owns SP Foundation: standards, Accelerators, AWS infrastructure, and adoption support. Product teams own their outcomes—Foundation provides the shared capabilities.

Foundation

Core Platform Team

Accelerators

Each Accelerator has a named owner in the catalog.

AWS Migration

Core Platform Team, reporting monthly to Finance.

Adoption Support

Core Platform Team

Success Metrics

Compliance: Built in

SOC 2, GDPR, WCAG controls embedded in Accelerators.

Reduced duplication

Teams stop rebuilding shared infrastructure and patterns.

Faster onboarding

New projects start with Foundation defaults, not from scratch.

The Goal

The right way to build should also be the easiest way to build.