A three-stage commercial arc, not a SaaS pricing page
SoloFrame is the platform layer. How SVTech monetizes it moves in stages: hand-built vertical flagships, licensed re-skinned deployments for partners, expansion proof builds that test new markets, and eventually a locked-down self-serve Studio. Each stage generates the evidence that de-risks the next.
Custom Vertical
SVTech-built, SVTech-operated. One flagship per category.
SVTech designs, builds, and operates a fully-branded vertical SaaS on the SoloFrame vertical PaaS - starting from a paying pilot customer's real clinical or operational pain point. Engagement includes domain discovery, manifest design, content authoring, deployment, and ongoing operation.
- • License fee + revenue share with the pilot
- • First paying pilot fee paid (Sept 2025)
- • White-glove launch · 30–60 days
- • Target: 1–2 active flagships per category
- • Digital Wellness Academy (healthcare · PHI)
- • GTM-OS (revenue ops · non-PHI)
- • BizFrameHub (AI education · launching today)
- • Colombian Spanish Academy (localized learning · rapid proof build)
Licensed
Same vertical code, re-skinned for a partner. Platform-reviewed manifest. Clinical when needed; reskilling and operator academies when not.
A partner organization - a multi-location psychiatric group, professional association, accelerator, employer training team, or operator community - licenses the engine behind a first-party vertical, rebranded for their audience. Manifests are version-pinned and platform-reviewed.
- • Annual license + per-seat / per-practice
- • Dedicated Dokploy environment per licensee
- • BAA + compliance support for PHI verticals
- • Non-PHI academies skip clinical overhead by manifest
- • Co-developed curriculum and content libraries
- • Psychiatric / behavioral-health networks
- • Employer mental-health benefits providers
- • Professional associations and credentialing bodies
- • Enterprise AI reskilling teams
- • Accelerators and operator communities
Studio
Self-serve sandbox. Locked allowlist. Customer builds a vertical.
A self-serve builder that composes a vertical from a locked allowlist of engines, prompts, assessments, and content modules. Narrower surface than first-party verticals; pre-approved manifests; no custom server code. PLG motion on a proven platform.
- • No customer-uploaded server code
- • No arbitrary webhooks
- • No custom DB schemas
- • No custom domains in MVP
Studio only works after the engine is battle-tested across ≥2 first-party verticals and ≥2 licensed partners. Flywheel gets built bottom-up.
Every tier of a SaaS pricing page assumes the product is done
Ours isn't - and saying otherwise would be a credibility tax. The arc above is a real operational sequence.
Building one flagship for a real paying customer produces the content library, manifest patterns, and regulatory posture that a licensee can adopt. Expansion proofs like BizFrameHub and Colombian Spanish Academy test how quickly that discipline can move into a new buyer or domain.
A handful of licensed partners reveal which parts of the engine are truly reusable vs. flagship-specific. Studio's allowlist is a distilled version of what already worked for licensees.
No engine lands in the shared platform without ≥2 vertical consumers or a third committed use case. This keeps the core small and every abstraction earned.