Always track CW Projects alongside service tickets. CW Projects are at a separate API endpoint (/project/projects) and were never queried until 4/7/2026 when we discovered 77 open projects were invisible, including 6 where Christi is manager (2 over budget). Briefing should pull open projects. April should check emails against active projects. Segrid tracks in NEST Projects table. Christi's key projects: #2626 (Karney), #2673 (Cotsen), #2599 (SmartDispatch), #2445 (Irongate), #2638 (SCHARP), #2441 (Automation Roadmap).
Segrid is both planner AND project manager. Workflow: 1) Segrid builds plan (research, scope, timeline, tasks, budget), 2) Hugo validates (pass/conditional/fail), 3) Questions go to Agent Queue, 4) Segrid executes and tracks. Three plan templates: Crimson Billable (CW project, budget, agreement, quote number), Internal/Non-Billable (AdaptoIT, agent training, no CW), Dev Project (tech stack, repo, deploy target, environments). Every new project gets a plan before work starts. Hugo validates before Active status.
The Social Media Matrix table (tbl05iTzLuOnBssEL) exists because Christi needed a single view to wrap her head around where to post what, across 5 brands and 9 accounts. Success metric: it makes audience building easier for her, faster decisions on where a given piece of content belongs. This is not a scope-creep side project - it is a personal operating tool that unblocks social execution. Hugo and other gate agents should not flag it as missing problem statement - the problem statement is 'I cannot keep 5 brands and 9 accounts straight in my head.'
The Airtable API only supports creating basic field types: singleLineText, multilineText, checkbox, singleSelect, multipleSelects, number, percent, currency, duration, date, dateTime, rating, multipleRecordLinks, email, url, phoneNumber, richText, barcode, multipleAttachments, singleCollaborator, multipleCollaborators. Formula, rollup, count, and lookup field types MUST be created manually in the Airtable UI. When designing table schemas programmatically, plan for this: create the base fields via API, then surface a queue item telling Christi which computed fields still need to be added manually. Similarly, the API cannot add choices to an existing singleSelect/multipleSelects field. Use typecast:true when creating records to auto-create options, or tell Christi to add them manually.
When Segrid creates a new project plan, she MUST create a project folder under the client's folder. Path: 3 - Clients and Projects/[Client Name]/[Project Name]/. Contents: deliverables, drafts, meeting notes, export files, reports, data pulls. Examples: Cotsen Foundation/AI Assessment/, Ability First/License Optimization/, Scharp/Cloud Migration/.
Quotes for new client projects are submitted to the sales team via a Teams channel, NOT emailed directly to Anzor or the client. Christi provides the SOW and total hours only. No pricing breakdown (sales handles that). Keep quotes lean: scope of work + total hours, no fluff, no per-phase hour breakdowns unless asked.