Six surfaces. One shared brain.

Free for qualified prospects

Capture a Lead, drop the scope conversation, and Vertikals ships a hosted prototype the prospect can open during a sales meeting. Same SDLC cycle a contracted build runs — feedback, plan, build, release — committed to a real repo from minute one. No code on the prospect’s side.

• Lead intake from the marketing site or directly in the platform
• AI-assisted prototype generation against the prospect’s actual context
• Hosted URL + summary versioned per project
• LinkedIn post draft generator on each prototype card

CRM that outlives the deal

ContextDocs at three scopes — Project, Client, Company. Every dump runs an AI extraction pass that proposes context updates at all three levels. Append-style updates auto-apply; replacements stage as proposals you accept, edit, or reject.

• Decision-makers, budget cycle, regulatory constraints captured per Client
• Cross-project Company memory survives team churn and project graduations
• Propose-then-confirm workflow keeps humans in the loop on destructive edits
• Compiles to .context/knowledge/ subtrees in every connected repo

Every locked plan, in one place

Operators see every project currently LOCKED or BUILDING across every client. Flip CC↔MANUAL mid-flight, retry stuck builds, abort safely. OBFUSCATED-trust franchisees see “Submit for release” and a status pill — no internals.

• Cross-tenant view for Vertikals; scoped-to-own for FULL franchisees
• Mode toggle blocked while BUILDING (server + client guard)
• Retry re-pushes [vertikals:plan-ready] so Command Center re-ingests
• Abort pushes [vertikals:plan-unlocked] and resets to DRAFTING

Cited Q&A, no embedding index

Ask anything across your in-scope context. Whole-context retrieval — claude reads your dumps + plans + builds + prototypes + memory in a single 120K-token prompt. Citations are inline tags that resolve to clickable links pointing at the originating record.

• Scope selector: Company (Vertikals only), Client, or Project
• Sources cited inline; chips link to dump, plan, build, or context doc
• Refuses out-of-scope questions (a franchisee can’t query someone else’s data)
• No vector DB, no chunking strategy to tune

Trust levels per partner

Two franchisee types (BUSINESS, TECHNICAL) and two trust levels (FULL, OBFUSCATED). The platform shows different surfaces to each — full SDLC for trusted partners, three-step cycle for relationship-led franchisees. Tenant boundaries enforced server-side.

• BUSINESS: relationship-led, opener role, OBFUSCATED by default
• TECHNICAL: outsourcing shop or solo founder, often FULL trust
• Every read/write endpoint scope-checks against franchiseeId
• Audit trail on client reassignments

You own the code, day one

Every build commits to your repo with a tagged message. Mark Contracted provisions a fresh GitHub repo (under your account or org) and pushes the v3 .context/ tree before any code lands. No platform lock-in — if you walk away, the repo keeps shipping.

• [vertikals:plan-ready] / [vertikals:plan-unlocked] / [vertikals:build-complete] commit-tag protocol
• .context/memory/ + .context/knowledge/ subtrees synced from the platform
• Connected repos discoverable per project; multi-repo per project supported
• Repo provisioning via GitHub Contents API (org or personal)