Module 12: Adapting Across Verticals

The 85/15 rule 85% of the platform transfers unchanged across verticals. 15% is the true adaptation layer: catalog schema, marketplace adapters, compliance architecture, design palette. The second vertical launched in weeks, not months.

This module closes the curriculum. It covers what changes per vertical, why clients never share infrastructure, the regulatory landscape you need to understand before building the lead-capture layer, and the six scoping questions that determine what gets built and in what order.

The 4 lessons

The last lesson closes with the scoping conversation and a direct consultation CTA. The others are architecture documentation.

Lesson 12.1

What Stays the Same vs What Gets Customized: The 85/15 Rule

System-by-system breakdown of what transfers unchanged (CRM schema, email engine, portal architecture, hosting stack) vs what requires adaptation work (catalog schema, marketplace adapters, compliance layer, design palette).

Lesson 12.2

The Three-Firewall Doctrine: Why Verticals Never Share Infrastructure

Separate database per client. Separate SMTP domain. Separate Cloudflare zone. Named sub-processors in the DPA. The compliance case, the blast-radius case, and the operational case for isolation — plus the concrete implementation at the code and infrastructure layer.

Lesson 12.3

Compliance Layers Per Vertical

The operator's working knowledge of TCPA, RESPA, Fair Housing, CCPA, HIPAA adjacency, and the FTC one-to-one consent rule (effective 2025). Built into the platform architecture from day one — not bolted on after the fact.

Lesson 12.4

How to Scope a Build for Your Category: The Questions That Matter

Six questions — in order — that surface the real requirements without manufacturing scope. Catalog complexity, marketplace targets, lead-to-close journey, compliance constraints, current tech stack, and 12-month vision. Closes with the consultation CTA.