Tools & Systems

Purpose: One page that says what every tool in the Summit stack is for, who owns it, and how much the Hermes agent is allowed to touch it. When someone asks "where does that live?" or "who do I ask about X system?", the…

Purpose: The rules that make GHL trustworthy. A CRM is only useful if everyone believes what's in it, and everyone only believes what's in it if the stages mean the same thing every time. Rosa enforces these rules;…

Purpose: How Summit books time so estimates happen on schedule, crews aren't double-committed, and nobody promises a customer a slot that doesn't exist. Rosa owns the calendars; Tara and Pete own their own availability…

Purpose: Where files live at Summit, how they're named, and who can see what. Two systems only: Google Drive for documents, CompanyCam for job-site photos. Anything saved anywhere else (desktop, personal Drive, phone…

Purpose: Which channel Summit uses for what, so customer messages are trackable, internal messages reach the right person, and nothing important dies in a personal text thread. The rule underneath all of it:…

Purpose: How Summit's paid channels are set up, who touches them, and what Summit itself is responsible for versus the outside agency. Jenna owns the agency relationship; nobody at Summit edits campaigns directly. The…

Purpose: The ranked list of automations Summit should build next, with what each one needs before it can go live. This is the working backlog Dave and Rosa review monthly. Ranking weighs revenue leakage stopped against…

Purpose: The principles that decide who gets access to what at Summit, and the process for granting, reviewing, and removing it. This document deliberately contains no credentials, no keys, and no account identifiers;…