Claude AI Design System + Deployment Lead

##SITUATION We are a boutique, family owned SEC registered RIA serving high net worth families. About 15 people. We run Salesforce Financial Services Cloud, Microsoft 365. I already build with Claude daily: custom skills, projects, MCP connectors, and generated deliverables. What I do not have is a governed system. Brand tokens live in three places. Document output quality depends on who prompted it. Nothing is versioned. Nobody else at the firm can produce a client ready artifact without routing it through me. You will design that system, build the first production version of it, and train me to own and extend it after you leave. If your plan requires you to stay forever, you are not the right fit. ##SCOPE 1. Firm wide Claude design system Condense and build a single governed source of brand truth that every Claude output pulls from. - Brand token file (colors, type scale, spacing, logo rules, chart palettes) structured so it can be consumed by document generation, HTML, and Salesforce components - Skill and project architecture: what belongs in a skill, what belongs in a project, what belongs in a shared reference file, and how they call each other - Naming, versioning, and backup conventions - A written standard I can hand to a new hire 2. Training and handoff on schema and structure - Live sessions (recorded) teaching me how to add, update, and retire skills and reference files without breaking downstream output - A maintenance runbook: what to review monthly, what breaks first, how to test a change before it goes firm wide - Debug patterns for when generated output drifts off brand 3. Document generation pipelines Repeatable, prompt driven production of: -Simple one page formatted outputs (client summaries, meeting recaps, one page briefs) -Complex 20 to 30 page client reports with cover pages, section dividers, running headers, table of contents, charts, and disclosure pages -Excel styles and templates (formatting standards, conditional formatting rules, chart theming, reusable model shells) - Fillable PDF and word docs Each pipeline needs a defined input, a defined output file format, and consistent formatting across runs. Show me how you handle page breaks, chart theming, and long document assembly, because that is where most of these builds fall apart. 4. HTML and LWC component system - Branded HTML component library for microsites, forms, and email friendly layouts - Lightning Web Component patterns for Salesforce Financial Services Cloud that inherit the same tokens, respect SLDS, and pass a Salesforce code review - Documented so Claude can generate new components on pattern rather than improvising 5. Account Engagement email template and block library Salesforce Account Engagement (formerly Pardot) is our marketing automation platform. We need a branded, reusable email system inside it. - Master email template set: newsletter, event invitation, client announcement, advisor introduction, drip and nurture, plain text style personal send - A block or region library our team can assemble without touching code: hero, headline plus body, two column, advisor bio card, event details, CTA button, disclosure footer, social footer - Email safe HTML that renders correctly in Outlook desktop, Outlook web, Apple Mail, Gmail, and mobile, including dark mode behavior - Merge field and dynamic content handling, correct unsubscribe and preference center links, and required disclosure blocks -Tokens inherited from the same brand source as every other output, so a color change happens once - A Claude pipeline that turns a draft or a content brief into a populated, ready to load template Tell me which Account Engagement email builder version you have built in and how you handle testing across clients. We have an existing internal process that converts .eml files into Account Engagement ready HTML. You may extend it or replace it, but say which and why. 6. Voice and positioning system for text generation Codified tone rules by scenario, with examples and counterexamples: - Client email replies - Internal updates and status notes -Client proposals and pitch material - Marketing and newsletter copy - Compliance sensitive language and phrases we never use Deliverable is a voice reference plus the prompt structure that enforces it, not a style essay. 7. Deployment and administration on a Claude Team plan Rollout plan across roles: advisors, planning, operations, service Seat structure, org level feature toggles, and connector policy Adoption plan with training material by role Documented guidance on what can and cannot be restricted at the Team tier, and a recommendation on whether Enterprise is justified for us Compliance context We are SEC registered. Anything client facing is subject to books and records retention and the SEC Marketing Rule. Your build needs to account for review before distribution, source citation in generated reports, and clear rules on what client data may enter a prompt. Prior experience in financial services, legal, healthcare, or another regulated industry is a strong plus. Deliverables checklist Brand token source file plus consumption pattern for each output type Skill and project architecture map with naming and version standards Four or more production document pipelines (one page, long form report, Excel template set, and one of your recommendation) HTML component library plus LWC component patterns with sample code Account Engagement master templates plus a reusable block library, render tested across major clients Voice and positioning reference with scenario prompts Team plan rollout plan, permission configuration, and role based training material Recorded training sessions plus a written maintenance runbook A 30 day and 90 day extension roadmap You are a fit if you have Shipped production Claude skills, projects, or agent systems for an organization, not just personal use Built document generation pipelines that produce polished, repeatable, multi page files Strong design system fundamentals: tokens, components, documentation Working knowledge of Salesforce Lightning Web Components and SLDS Production email HTML experience, including Outlook rendering, dark mode, and marketing automation template systems Comfort writing documentation and teaching a technical but non engineer operator Opinions. I want someone who tells me when my structure is wrong ##Bonus points Financial services or RIA experience Salesforce Financial Services Cloud specifically Salesforce Account Engagement or Pardot template development Excel or Word template engineering at a high level of polish Experience administering a Claude Team or Enterprise deployment