Advisory OS Project Architecture

Takes matrix output → updates Ruben's living master plan. GPS, themes, constraints, conversations, team context. Shared in session (shown, not handed over). Updated weekly after every matrix run. One job: keep the master plan current and accurate.

Takes master plan updates → updates the active project plan. Currently: Accounting Manager OS. Matrix banner, GPS alignment, 5 builds, stakeholders, coaching notes. Advisor only — client never sees. One job: keep the project plan reflecting current reality.

Takes project plan updates → updates the client-facing blueprint. Builds, timeline, outcomes. No diagnostic language, no advisor-only details. Client receives this. Crulliance branded. One job: keep the blueprint clean and client-appropriate.

Produces the actual deliverables for the active constraint solve — SOPs, templates, tools, workflows. Team-facing documents in Crulliance branding. This is where the work product gets built. Separate from the Build Agent (which designs the deployment system). One job: produce constraint-specific deliverables.

Pulls thought leadership ideas from client work — constraint solves, session insights, methodology moments, patterns across clients. Input: session recaps, constraint briefs, matrix outputs, your own notes. Output: a ranked list of thought leadership angles with the "so what" for your audience. One job: find the ideas worth building campaigns around.

Takes the chosen idea → develops the full campaign strategy for the week. Sales goal, angle, target audience segment, constraint it addresses, which offer it connects to, CTA, narrative arc. This is the strategic brief that ALL downstream projects reference. One job: define what this week's campaign is about and why.

Takes campaign brief → produces the interactive HTML/React thought leadership piece. Full storytelling arc, production-grade, Advisory OS branded. This is the anchor content for the week. Everything else references it. One job: build the thought leadership piece to published quality.

Takes the thought leadership piece → builds 2 micro-tools that complement it. Each tool makes the TL piece's insight actionable. Format rotates: calculator, revelation tool, diagnostic, comparison, swipe file. ~80–95 min per tool. These are the hand-raiser magnets. One job: build the micro-tools.

Takes thought leadership piece + micro-tools → produces all distribution content. LinkedIn posts (TL piece post + 2 hand-raiser posts), Lead Shark DMs for asset delivery, GetSales follow-up DMs, conversation starters, and weekly email to list (TL piece + tools + briefing invite). One job: produce all the distribution content for the campaign.

Takes the full campaign → produces the briefing video assets. The briefing is a 10–15 min screen-shared recording, time-gated to Sunday midnight, with a fallback version after expiry and an evergreen mini-site version. Output: briefing script + screen-share document (the visual you record over). One job: produce the briefing package.

The living design system. Referenced by all production projects. When you need a new design configuration (workshop instead of briefing, new asset type), you pull the design system into a chat, describe what you need, iterate, prove it, and then extract a skill document for the new component. The Design System grows as you prove new patterns.

Designs the deployment system for a constraint solve — BEFORE anything gets built. This is the strategic layer: given this constraint, what's the deployment package? (Which SOPs, templates, tools, workflows are needed? In what order? Who uses each piece?) The SOP/Build project in the Ruben line then executes the deployment design. Separate from SOP production.

Creates custom proposals for prospects and existing client extensions. Straddles My Business (new prospects) and Client Delivery (extending engagements). For you right now; potentially deployable to clients later.

Complete system: interview protocol → extraction → agent build (V1 + V2 anonymized) → QC → delivery. 11 files. Rob Foncannon golden examples. Also a $497 offer. This one is done — just needs to be set up in a fresh project with all 11 files loaded.

Full design system for building client authority websites. Connects to Website Evaluation Tool. Also built Advisory OS website. Being used actively with Jen Bar right now.

Jen stays as one project for now. Her constraints aren't defined enough for the assembly line structure. You're solving constraint-by-constraint in small weekly bites. Authority website is nearly done. When her engagement matures to where Ruben's is, mirror the Tier 2 structure. For now: one project, her reference data, her brand, and whatever's active.

Group program. Momentum Monday, Thursday co-working, monthly 1:1s. Existing workflow is clean — constraint brief across the group → Friday email → Monday session → recap. Potentially sunsetting. Do not over-rotate. Just set up a fresh project with the existing instructions and keep running it.

Where you improve how master plans, SOPs, blueprints, and project plans work in general — before pushing updates to Tier 2 projects. This is where methodology changes get tested before they hit live client projects. Not urgent. Build this when you have a methodology change to test.

Onboarding workflow: brand kit creation, reference data population, first constraint identification, first deployment plan. Duplicate Tier 2 structure and load client-specific files. Build this from the pattern that emerges from Ruben + Jen. Not urgent until your next client signs.

Builds front offer pages. Used for your own business and clients (Linda's $2,500 service sprint). Set up fresh when you need it next.