STBM

Relationship + Revenue

CRM Command

People + Follow-Up

Care Flow

Risk + Audit

Trust Desk

Delivery + Coordination

Project Grid

Hosted Vertical Landing Network

One hosted landing system. Many vertical stories.

The platform home now works like a landing network: one public runtime introduces the platform, then hands people into dedicated vertical pages such as LMS, medical, support, and projects operations without switching stacks, domains, or design language.

Explore LMS Explore Medical Ops Explore Support Ops See promoted packs

Live landing aliases: lms.stbm.app, medical.stbm.app, support.stbm.app, and projects.stbm.app

Live Vertical Stories

Start from the platform landing, then go deeper by vertical.

Preview

CRM + Account Ops

Pipeline, accounts, follow-up, renewals, service handoff, partner coordination.

Live page

Helpdesk + Case Flow

Queues, SLAs, escalation, outreach, status-driven dashboards, operator actions.

support.stbm.app or /support

Open support landing

Live page

Medical Operations

Patient/public entry, intake, scheduling, referrals, care coordination, follow-up, and multi-audience medical operations posture.

medical.stbm.app or /medical

Open medical landing

Preview

Compliance + Audit

Controls, reviews, remediation plans, attestations, deadlines, evidence chains.

Live page

Projects + Field Operations

Assignments, milestones, work orders, inspections, task routing, issue review.

projects.stbm.app or /projects

Open projects landing

Live page

LMS + Workshops

Courses, competency evidence, collaborative canvas, gamification, live sessions.

lms.stbm.app or /lms

Open LMS landing

Promoted Pack Discovery

Each live landing can point at a governed vertical pack.

LMS promoted pack

Workspace operator and learner portal experiences publish through the same shared app-experience authority instead of a second LMS microsite stack.

Launch path: `/app/workspace.learning_catalog`

Governance path: `/app/workspace.config_studio`

Preview or publish in Config Studio

Medical operations promoted pack

The config-first starter pack promotes one shared generated workspace for intake, scheduling, referrals, coordination, and follow-up.

Launch path: `/app/workspace.medical_operations_overview`

Governance path: `/app/workspace.config_studio`

Preview or publish in Config Studio

Support and projects are live before pack closure

The hosted landing seam now gives support and projects their own pages while keeping promoted-pack posture honest until the shared managed adoption path is ready.

Medical now tells a public and operator story

The medical landing now carries patient/public entry, intake, scheduling, clinical coordination, and branch-operations framing on the same hosted seam instead of reading like an operator-only teaser.

Same hosted landing seam

Platform home, vertical public pages, and subdomain entry points all stay on one hosted landing runtime with shared domain binding and publish authority.

What This Hero Is Saying

Apps are assembled, not re-invented.

Part-by-part assembly

Every hero icon starts with the same rounded base, then gains meaning as independent parts snap into place. That mirrors the platform: shared shell first, configured packs second.

Center stage is reusable

One app moves aside and stays present while the next one takes the spotlight. The story is not “many separate products.” It is “one core engine presenting many vertical-ready experiences.”

Interaction survives motion

The cards stay tactile on hover and tap, with pieces lifting and brightening to suggest configurable, touchable runtime blocks rather than flat marketing art.