One day at your office in Park City. Five people. A working AI Chief of Staff installed, trained on your business context, and in use before we say goodnight.
Your brand promise is simple and uncompromising: set and manage expectations around cost, schedule, and quality. Delivering that across architecture, interior design, and construction, with the client at the table, requires one thing more than any other — the right information in the right hands at the right moment.
Your biggest bottleneck is not software. It is the business knowledge living inside your senior people. Every decision, every standard, every judgment call you have built over 20+ years of luxury residential work sits inside the heads of the people in the room. That is where the AI Chief of Staff changes the shape of the problem.
By the end of this day, each of the five people in the room has their own AI Chief of Staff grounded in 4C's context, principles, and brand promise. A second brain. A thought partner. The person who never forgets what you decided last month, never misses the follow-up, and never loses track of what matters. Every attendee leaves with two working skills they built themselves, a clear operating rhythm for daily use, and a roadmap for what comes next.
This is: A focused one-day install that gives each of your senior people a personal AI Chief of Staff they can actually use Monday morning. Built in front of them, with them, on top of their real work.
This is not: Enterprise software deployment, BuilderTrend integration, custom engineering, or a rollout to your broader staff. Those are separate engagements. We will surface exactly what belongs in each lane before we wrap.
8:00 – 8:30 AM · Orientation (30 min)
8:30 – 9:30 AM · AI OS Setup (60 min)
Install Claude Code, load the AI OS framework, and populate every attendee's system with the context their AI needs to be useful.
9:30 – 9:45 AM · Break (15 min)
9:45 – 11:00 AM · Skill Build #1: Daily Morning Brief (75 min)
Meet the Agent that Builds Agents. Using the /brainstorm and /explore skills, each attendee sits with their AI to design their own daily morning brief — the one ritual that tells them what matters before they start the day.
11:00 – 11:30 AM · Lunch (30 min)
11:30 AM – 1:00 PM · Skill Build #2: Each Person's Signature Skill (90 min)
Every person in the room does different work. So every person builds a different second skill — the one that removes the biggest friction from their week.
1:00 – 1:15 PM · Break (15 min)
1:15 – 2:45 PM · Persistent Memory and the Defense System (90 min)
This is what turns a chatbot into a Chief of Staff. We install and demo the two systems that make the AI trustworthy over time.
2:45 – 4:15 PM · Daily Operating Rhythm + Workflow Roadmap (90 min)
Lock in how each person uses this Monday through Friday, and surface what comes next.
4:15 – 5:00 PM · Q&A and Commit (45 min)
Open floor. Whatever is still fuzzy, we clear. Whatever is still broken, we fix. And each person writes down the one thing they will do with their AI Chief of Staff tomorrow morning.
CEO. Vision, client relationships, brand integrity. His AI focuses on client briefings, team leadership, and strategic decisions.
Chief Visionary Officer, architect. His AI focuses on design decisions, client-facing proposals, and the translation between vision and execution.
COO/CFO. His AI focuses on financial, operational, and scheduling visibility. The weekly pulse on what is on track and what is at risk.
Strategic Leadership Partners. His AI focuses on his mentoring work with Josh and the team — context, themes, and follow-through.
Operations and resident AI builder. His AI focuses on turning spoken ideas into scoped builds he can execute, and acts as the bridge between the team's needs and what gets built next.
We operate inside Claude Code. The AI Chief of Staff is built on Claude Code, which is safe, powerful, and private, and has limits on which external tools it can connect to without custom engineering. Those limits are known and will be respected.
BuilderTrend and similar closed platforms are out of scope. Systems without public APIs require a separate technical engagement. We will capture every integration you want and route it to the right lane (internal build, Bryce's capacity, or an enterprise partner like Scott's team).
Claude Code is evolving week by week. By the time we land in Park City, there will almost certainly be additional capabilities available that are not listed here. We will use whatever serves you best on the day.
This is a working install, not a demonstration. Expect to hit walls. Expect to work around them. Expect to leave the day with a system you will actually use — not a polished prototype that lives on a shelf.