4C Group Prepared for 4C Group

AI Chief of Staff
In-Person Install

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.

Duration   8 hours (8 AM – 5 PM) Location   4C Group office, Park City, UT Investment   $5,000 Earliest date   May 5, 2026 or later

Summary

You've built 4C to deliver something most of your industry cannot: architecture, interior design, and construction under one roof with the client at the table. The promise is cost, schedule, and quality expectations set and managed. The challenge is that the integration that makes 4C valuable is also the hardest thing to run.

You're looking for how AI can actually make that easier, for you, for your clients, and for the way 4C operates. The real question underneath is what 4C looks like when every person on your team is AI-enabled. This day is the first answer: each of you walks out with your own personal AI Chief of Staff, and a direct experience of what you're capable of when you have one.

Next step: let's schedule a success alignment call.
Book 30 Minutes

What You Are Getting

The Executive AI Operating System, installed on each laptop.

This is not an app. It is a structured system that makes Claude Code act like a Chief of Staff with a full executive team of AI agents who can help run your business. Here is what gets built.

Hover and click to explore. Full view: open in a new tab.

Investment

$5,000
One-time. All inclusive.
  • I cover my own flight, hotel, and ground transportation
  • A full day at your office, 8 AM to 5 PM
  • Up to 5 of your people in the room
  • Three short prep calls before I fly out — alignment with you, 10 minutes with each attendee, tech readiness with Bryce
  • A working AI Chief of Staff set up on each person's laptop
  • A written Success Plan handed to you before I leave at 5 PM
  • A 30-minute check-in call 30 days after install
Purchase
Redirects to secure checkout. Install date booked after purchase.

What this is, and is not.

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.

Before Install Day

Three short conversations that make sure the day delivers.

Install day is only as useful as the prep that leads into it. Three focused calls happen on the runway — none of them replace the eight hours, all of them make those eight hours sharper.

1. Success alignment call with Josh — 30 minutes, before we book the date

Before you commit to the date, you and I get on a call and define what success looks like together. Not a sales call. An alignment call.

What we cover:

  • What you personally want to be able to say on the Monday after install
  • What each of your four team members needs most from their AI
  • The one or two things that, if they happen, make this day worth every dollar
  • The one or two things that are out of scope for this day and belong in a different lane

At the end of the call we both know exactly what "done" means. No surprises on install day, no shifting goalposts.

2. A 10-minute chat with each attendee — after commitment, before install

Five short conversations. Phone or Zoom. Ten minutes each. I'm not sending a form. I want to hear each person in their own voice.

What I ask each person:

  • What does your week actually look like, not what your job title says
  • What are the three things that eat the most attention in your week
  • If your AI could do one thing perfectly by end of install day, what would it be
  • How do you want it to sound when it writes for you
  • Anything the AI should never do

By the time I fly out, I know each person in the room before I shake their hand.

3. Tech readiness call with Bryce — 30 minutes, 5 to 7 days before install

So we start the day building instead of troubleshooting, Bryce and I get on a short working call about a week out. This is not technical setup for your team — that is on Bryce. It is a coordination call between Bryce and me to confirm the room is ready.

What we cover:

  • Your current tech stack — what 4C already uses daily
  • What Bryce has already built so we don't duplicate work
  • Laptop inventory — Mac or PC per attendee, model, admin rights
  • Claude Code installed and signed in on each laptop before install day
  • Active Claude Max subscription confirmed for each of the 5 attendees
  • Wi-Fi, casting method to the TV, and whiteboard availability confirmed
  • Any firewall, VPN, or IT constraints I need to know about

By the time I land in Park City, the room is set up, the software is live, every attendee has signed into Claude Code, and we start at 8:00 AM building — not at 10:30 AM still installing.

Agenda

Click to view agenda (subject to change).

Start   8:00 AM End   5:00 PM Working hours   7 Breaks   2 × 15 min + 30 min lunch

8:00 – 8:30 AM  ·  Orientation (30 min)

  • Ground rules for the day — what to expect
  • How the AI Chief of Staff thinks — departments, agents, skills, memory
  • The anti-chaos principle — why this reduces overwhelm instead of adding to it
  • How context compounds over time — the system gets smarter the more you use it

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.

  • Claude Code installed on each of the 5 laptops
  • AI OS scaffolded — departments, agents, skills, memory, defense
  • Business context loaded — 4C's brand promise, client types, values, integrated delivery model
  • User context loaded — each attendee's role, responsibilities, voice, decision rights
  • Department principles seeded — how you think about cost, schedule, quality, client communication
  • Goals set for the business and for each individual

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.

  • /brainstorm: the AI interviews each person to surface the information they need every morning
  • /explore: take the idea and expand it — what it pulls from, how often, what it looks like
  • Build and test live — everyone runs their own brief before we break for lunch
  • Each version is tailored: Josh's brief looks different from Chris's, which looks different from Solim's

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.

  • Josh (CEO): Client briefing skill that prepares him before he meets with an owner — context, history, decisions pending, tone to hold
  • Solim (Chief Visionary, architect): Design decision summarizer that turns conversations with subs and vendors into clean client-facing proposals
  • Chris (COO/CFO): Weekly financial and operations pulse — what moved, what is at risk, what needs a decision
  • Peter (mentor): Leadership check-in doc that prepares him for his sessions with Josh and the team
  • Bryce (operations): Workflow handoff skill — turns a spoken idea into a scoped build request he can execute on later

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.

  • Persistent memory: every conversation, decision, and document your AI has seen is remembered and can be referenced. No more re-explaining yourself every Monday.
  • The defense system: scheduled checks that keep the system accurate, up to date, and on rails. Daily, weekly, monthly cadences. The anti-chaos layer.
  • What the system does automatically versus what needs human input
  • How context improves decision quality over 30, 60, 90 days of use

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.

  • Morning, midday, end-of-day rhythms tailored to each role
  • Weekly and monthly rituals that keep the system sharp
  • Identify the next 5 to 10 workflows 4C wants to build, grouped into three lanes:
  •     — Self-serve: things the AI Chief of Staff can help you build yourself
  •     — Bryce's lane: builds that fit within his skill set and capacity
  •     — Technical lane: anything requiring deeper engineering (e.g., BuilderTrend integration) — captured and routed to the right partner (Scott's team or equivalent)

4:15 – 5:00 PM  ·  Q&A, Success Plan, and Commit (45 min)

Open floor — whatever is still fuzzy, we clear. Whatever is still broken, we fix. I hand each of you your written Success Plan before I walk out the door. Each person writes down the one thing they will do with their AI Chief of Staff tomorrow morning.

What Makes This Different

Six features that turn a folder structure into an operating system.

Executive Team

A full AI C-suite, one per person on your team.

Defense Department

Self-cleaning system. Catches drift before you do.

Persistent Memory

The AI never forgets. Context compounds every session.

Get Smarter

Ingests any video, book, or doc. Trains itself overnight.

Agent That Builds Agents

Describe a workflow. The AI builds it with you, same day.

Principles-Based Thinking

Your frameworks, your voice, your standards — every time.

Who's in the Room

Five people. Five different jobs. Five custom AI Chiefs of Staff by end of day.

Co-Founder & CEO

Josh Phillips

Vision, client relationships, brand integrity. His AI focuses on client briefings, team leadership, and strategic decisions.

Co-Founder & Chief Visionary Officer

Solim Gasparik

Architect. His AI focuses on design decisions, client-facing proposals, and the translation between vision and execution.

COO & CFO

Chris Phillips

Financial and operational leadership. 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

Peter Foss

Mentor. His AI focuses on his coaching work with Josh and the team — context, themes, and follow-through.

Operations

Bryce Phillips

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.

Logistics

What We Provide

  • Eight hours of focused, hands-on facilitation
  • Claude Code installation on each of the 5 laptops
  • AI OS framework, agents, skills, and defense system
  • Two built-and-tested skills per person by end of day
  • Daily operating rhythm tailored per role
  • Post-install workflow roadmap for next 90 days
  • Travel, flight, lodging, and ground transport

What 4C Provides

  • Location: your Park City office
  • One laptop per attendee (5 total) — Mac or PC, with admin install rights
  • An active Claude Max subscription for each attendee (set up by Bryce before install day)
  • Claude Code installed and signed in on each laptop before the day starts
  • Fast, reliable Wi-Fi
  • A TV or large monitor we can cast to (preferred)
  • A whiteboard (preferred)
  • Lunch and snacks for the day
  • All 5 attendees present for the full 8 hours
  • 30-minute tech readiness call with Bryce, 5 to 7 days before install

Out of Scope

What this day is, and what it is not.

The goal of this day is to install a working AI Chief of Staff for each person in the room — a thought partner trained on how 4C runs. The goal is not to build custom software, integrate closed platforms, or hack around tool limitations in one sitting. Naming what sits outside this engagement protects both the day itself and the work that rightly belongs elsewhere.

Explicitly out of scope

Custom software development. Building assistants that read and write directly to BuilderTrend, automated construction-manager workflows, or custom integrations into closed project-management platforms. This work is valuable and routes separately — to Bryce's capacity or a technical partner like Scott Duffy's team. We surface every candidate and send you out with a roadmap.

Tools without MCP support. We operate inside Claude Code and use tools it can connect to natively via MCP (Model Context Protocol) — Gmail, Google Calendar, Airtable, Notion, and a growing list. Tools that do not yet have MCP support (BuilderTrend, Fathom, and others) are named honestly and routed, not retrofitted on the fly.

Claude Max subscriptions. Each of the 5 attendees needs an active Claude Max subscription on their laptop before install day. Set up by Bryce on the tech readiness call. Not included in the $5,000.

Ongoing implementation support. Beyond the 30-day check-in built into this engagement (see next section), continued work is a separate engagement discussed if mutually desired.

What this day is. A working install — not a demonstration. Expect to hit walls. Expect to work around them. Expect to leave with a system the five of you actually use, not a polished prototype that lives on a shelf.

After Install Day

Two deliverables that protect what we built.

The system is only worth what each of you does with it on Monday morning. These two deliverables are built into the engagement to make sure Monday morning actually happens.

Success Plan — handed to you before I leave at 5 PM

A written document you walk out of the day with in your hand. It is the manual you refer back to when you sit at your desk on Tuesday morning and think, "wait, how did she set this up?"

What's in it, per person:

  • The skills you built on install day, with the exact commands to use them
  • Your daily rhythm — how to open the morning, how to close the day
  • A week-by-week plan for the first 30 days so you build the habit without being overwhelmed
  • Your top future workflow ideas, pre-sorted into lanes: self-serve, Bryce's capacity, or technical partner

Plus a team-level section: the prioritized 90-day roadmap for what gets built next, and how to re-engage when you are ready.

30-Day Check-In — 30 minutes, virtual

Included in the engagement. Scheduled at the end of install day, held approximately 30 days later. Not a "how's it going" check-in — a focused working session.

What we cover:

  • What each person is actually using, and what is gathering dust
  • Sharpening anything that needs tuning based on real-world use
  • Confirming or revising the 90-day roadmap

Next Steps

Three steps to locking your install.

1

30-min alignment call

You and I get on a call and define exactly what success looks like for install day. No commitment required to have this conversation.

2

Secure your date

Once aligned, complete the secure checkout. The confirmation page walks you through the next steps the moment payment clears.

3

Prep runway

10-minute chats with each attendee, and a 30-minute tech readiness call with Bryce. Then I'm on a flight to Park City.

Ready when you are.

Purchase — $5,000