Export Manual for Super Agent

[
  {
    "sectionId": "introduction",
    "sectionTitle": "Introduction & Overview",
    "pageId": "process-overview",
    "title": "Our Process, Start to Finish",
    "url": "/introduction/process-overview",
    "content": "# Our Process, Start to Finish\n\n  \n    💡\n\n    \n      When to Use This\n\n      Not part of the standard discovery call. Use it when a customer asks *\"What exactly happens after I sign?\"* or *\"What are we paying for?\"* Walk through the steps naturally — you don't need the internal stage codes.\n\n    \n\n  \n\n\n  \n    \nCustomer-facing — they are involved at this stage\n\n    \nInternal production — we handle it, customer not directly involved\n\n  \n\n\n  \n    Step\n1\n\n\n    ProposalProposal & Contract Review\n▼\nWhat Happens\nWe send you a proposal that outlines exactly what's included, what's not included, and the scope of work we discussed. The proposal is also your contract.\n\nWe can schedule a call to walk through it together — most clients find that helpful before signing.\n\n\nSay on the Call\n\"We're going to send you a proposal. It outlines what's included, what's not, and the scope of work we just talked about. Would you like to set a time for me to review it with you?\"\n\n\n    A001\n2\n\n\n    A001Preliminary Research & Constraint Intake\n▼\nWhat Happens\nOnce you sign and pay the deposit, we immediately begin research on your property — pulling records, researching your jurisdiction's requirements, identifying zoning constraints, setbacks, overlay zones, and any special conditions.\n\nThis is the stage where \"every property has a story\" can come into play. If we discover something unusual, we bring it to you before any further work happens.\n\n\n**Note:** This is professional work that cannot be done before you sign. It is the first deliverable of your project.\n\nSay on the Call\n\"The moment you sign and pay the deposit, our team starts pulling records on your property — zoning, constraints, any special overlays. If anything unusual comes up, we call you immediately before doing anything else.\"\n\n\n    A002\n3\n\n\n    A002Existing Conditions Capture\n▼\nWhat Happens\nIf your project involves existing construction — a house, garage, or commercial space — our site tech reaches out to schedule a visit. We use a Matterport scanner to precisely measure the existing buildings on your site.\n\nThose measurements are input into our Revit model so our designers work from accurate as-built conditions, not assumptions or old records.\n\n\n**Note:** Projects on vacant lots or with no existing construction may skip or abbreviate this stage.\n\nSay on the Call\n\"If there's existing construction on the site, our site tech will reach out to schedule a visit. We use a Matterport scanner to measure everything precisely so our designers aren't working off assumptions.\"\n\n\n    A003\n4\n\n\n    A003Design Development & Kickoff✓ Customer Approval Point\n▼\nWhat Happens\nWe schedule a kickoff call with you, your project manager, and your designer. Even if you've told us what you want in sales, we start fresh with the designer — we want you to tell them directly, in your own words.\n\nThe designer develops proposed layouts in Revit and presents them to you for review and approval. You see the design before anything gets engineered.\n\n\n⚠ Primary approval point. Once you approve the design, production begins. Changes after this point ripple through architectural, structural, and Title 24 — and significantly expand scope.\n\nSay on the Call\n\"After the site visit, your project manager sets up a kickoff call with you and your designer — as if you've never talked to us before. We want you to tell the designer directly what you're looking for.\"\n\"The designer presents layouts to you for approval before anything gets engineered. Once you approve the design, that's when production starts.\"\n\n\n    \n\n**Customer handoff.** After design approval, the customer's next significant touchpoint is the permitting kickoff. Everything between A003 and submittal is internal production — we manage it.\n\n\n    A004–6\n5\n\n\n    A004 – A006Construction DocumentsInternal\n▼\nWhat Happens — Internal\n**A004** — The schematic designer from A003 formally defines exactly what goes on the construction document drawings.\n\n**A005/A006** — Our CD designer produces the fully annotated, code-compliant architectural plan set: floor plans, elevations, sections, details, code notes, construction notes, and material specifications.\n\nOnce complete, structural engineering and Title 24 run from this package in parallel.\n\n\nSay on the Call\n\"Once you've approved the design, we move into construction documents. That's an internal phase — our team builds out the full plan set with all the code notes and specifications the city needs to see. You don't need to be involved in that. We manage it.\"\n\n\n    \n\n▼ Structuralruns simultaneously with▼ Title 24— both working from the completed architectural CDs\n\n\n    S+T24\n6\n\n\n    Structural + Title 24Engineering & Energy ComplianceInternal\n▼\nWhat Happens — Internal\nTwo workstreams run simultaneously from the completed architectural CDs:\n\n**Structural Engineering** — Stamped structural drawings and calculations: shear walls, posts, footings, beams, lateral and gravity systems.\n\n**Title 24 Energy Compliance** — The energy compliance report based on the building configuration, envelope, water heater, HVAC, and mechanical systems.\n\n\n⚠ No turning back. Shear walls, posts, footings, beams, building envelope, water heater, HVAC — all fixed for the first city submission.\n\nSay on the Call\n\"At this stage the plans go to structural and Title 24 simultaneously. Our structural engineer stamps the structural drawings, our energy consultant does the Title 24 compliance. Both come back and get incorporated into the architectural plans. We coordinate all of that internally.\"\n\"This is the same process any architecture firm runs with outside consultants. We just do it in-house.\"\n\n\n    \n\n↓ Architectural plans + Structural drawings + Title 24 report combined into one submittal package, with any minor coordination adjustments reconciled across all three disciplines.\n\n\n    A007\n7\n\n\n    A007Pre-Submittal Coordination & Package AssemblyInternal\n▼\nWhat Happens — Internal\nThe full package goes through a coordination review before it goes to the city — every sheet checked against every other sheet across all three disciplines for consistency. The package is only ready to submit when this review passes.\n\n\n    Permit\n8\n\n\n    PermittingSubmittal, Plan Check & Permit Issuance\n▼\nWhat Happens\nIf you've included permit processing, our permitting team does a kickoff call with you before we submit — walking you through what to expect.\n\nWe submit to the city on your behalf. The city's plan reviewers come back with comments. This is completely normal — our founder has done over a thousand projects and has had maybe three approved on the first submission.\n\nGenerally the city needs to see the plans twice. First submission: they tell you what they want to see differently. Second submission: you show it that way, they're satisfied. Once satisfied — typically after two submissions — a building permit is issued.\n\n\nSay on the Call\n\"If we're handling permitting, our permitting team does a kickoff call before we submit — so you know exactly what the city is going to ask you for and what to expect.\"\n\"After we submit, the city comes back with comments. That's completely normal — our founder has done over a thousand projects and has had maybe three approved on the first submission. Generally the city needs to see it twice. We manage that whole process.\"\n**Permit processing is optional** — billed time & material. If the client handles their own permitting, skip this in your explanation.\n\n\n  \n\n\n  \n    \n### City Fees — Always Clarify These\nPaid directly by the client to the city — not part of Pacific Sands's contract\n\n\n    \n      Fee 1\nPlan Check Fee\nPaid at submission. Pays the city's plan reviewers to review your project.\n\n\n      Fee 2\nPermit / Inspection Fee\nPaid when you pull the permit. Pays the city's building inspectors who visit your site during construction.\n\n\n    \n\n    Fees vary by jurisdiction and project size. We can give you a ballpark, but exact amounts are set by the city. Both are separate from Pacific Sands's fees.\n\n  \n\n\n  \n    \"You talk to the designer directly — as if you've never talked to us.\"\n\n\n    Every project has a kickoff. Every kickoff starts fresh. That's how we make sure the design reflects what you actually want."
  },
  {
    "sectionId": "introduction",
    "sectionTitle": "Introduction & Overview",
    "pageId": "project-process-pipeline",
    "title": "Project Process Pipeline (A001–A007)",
    "url": "/introduction/project-process-pipeline",
    "content": "# Project Process Pipeline\nA001 through A007 — What each stage does, doesn't do, and hands off\n\n\n  \n    \nPhase 1 — Discovery & Constraints\n\n\n    A001\n\n\n## Preliminary Research & Constraint Intake\n\n\"What rules and limits does this project operate under?\"\nDoes\n- Identify zoning & code frameworks\n- Establish site & jurisdictional constraints\n- Flag ambiguous or high-risk code areas\n- Translate code into design-relevant limits\n- Record constraints in Project Storyline\n\nDoes Not\n- Decide building layout or massing\n- Resolve design tradeoffs\n- Declare assemblies\n- Write CRC / CBC notes\n- Interpret proprietary systems\n\n\nA001 defines the box. It does not design what goes inside it.\n\n\n    ▼ Constraints documented → Risks flagged → Designer understands flexibility\n\n    A002\n\n\n## Existing Conditions Capture\n\n\"What exists today?\"\nDoes\n- Import & model existing conditions\n- Verify dimensional accuracy\n- Clearly depict existing construction\n- Provide reliable base model for design\n\nDoes Not\n- Interpret zoning or code\n- Make design decisions\n- Propose solutions or layouts\n- Declare assemblies\n\n\nA002 records reality. It does not interpret it.\n\n\n  \n\n  \n    \nPhase 2 — Design & Decisions\n\n\n    A003\n\n\n## Design Development & Decision Capture\n\n\"What is this building?\"\nDoes\n- Develop proposed building design\n- Resolve spatial layout, massing & form\n- Make design decisions to move forward\n- Identify tradeoffs (code / client / budget)\n- Capture decisions in Project Storyline\n\nDoes Not\n- Write CRC / CBC code notes\n- Define wall, roof, or floor assemblies\n- Select ESR numbers or manufacturers\n- Resolve proprietary system requirements\n\n\nA003 decides what the building is. A004 declares what systems exist.\n\n\n  \n\n  \n    \nPhase 3 — Design Freeze\n\n\n    A004\n\n\n## Assembly Identification & Declaration\n\n\"What systems does this building use?\" — Last freeze point before CDs\nDoes\n- Declare all roof, wall & floor assemblies\n- Assign assembly IDs & descriptions\n- Identify ESR-dependent components\n- Confirm client alignment on assemblies\n\nDoes Not\n- Define materials or thicknesses\n- Include CRC / CBC language\n- Perform code analysis\n- Create details\n\n\nIf the assembly does not exist in A004, it does not exist in the project.\n\n\n  \n\n  \n    \nPhase 4 — Construction Documents\n\n\n    A005\n\n\n## Annotate & Document Plans\n\n\"Show it on the drawings.\" — Documents declared assemblies on plans\nDoes\n- Tag wall, roof & floor assembly IDs\n- Show assemblies on plans, elevations, sections\n- Reference A006 definitions\n- Remove all TBD / placeholder text\n\nDoes Not\n- Decide design intent\n- Create or modify assemblies\n- Define code language\n- Introduce new scope\n\n\nA005 documents decisions. It does not make them.\n\n\n    ▼ Assembly IDs shown on drawings → Definitions live in A006\n\n    A006\n\n\n## Assembly & Code Definition\n\n\"Define it technically.\" — The only place assemblies are formally defined\nDoes\n- Define each assembly (materials, layers, specs)\n- Write all CRC / CBC code notes\n- Provide ESR numbers & listed systems\n- Create consolidated general notes sheet\n\nDoes Not\n- Decide design intent\n- Change assemblies\n- Interpret municipal amendments\n- Coordinate drawings\n\n\nIf an assembly is not defined in A006, it cannot be built.\n\n\n  \n\n  \n    \nPhase 5 — Quality Gate\n\n\n    A007\n\n\n## Coordination & Consistency (Pre-Submittal)\n\n\"Does everything match?\" — Final verification before permit submittal\nVerifies\n- Drawings match approved design intent\n- Assembly IDs match across A004 → A005 → A006\n- No silent post-A004 design changes\n- CRC/CBC notes appear only on A006 sheets\n- All ESR components defined & referenced\n\nDoes Not\n- Respond to city comments\n- Redesign assemblies\n- Add new details\n- Modify scope\n- Create new content\n\n\nA007 proves the set is coherent. If it isn't, it doesn't ship.\n\n\n  \n\n  Each stage answers one question. No stage does another stage's job.\n\nClear constraints upstream prevent expensive redesign downstream · Control is not friction — control is scale"
  }
]