4C Group.

What Josh actually cares about.

Josh cares about the client experience. That's it. He calls it the "luxury client experience," and the way he describes it is pretty simple: when a client moves into their home, everything is exactly what they were promised. No surprises on cost. No surprises on the schedule. No surprises on the quality.

He's not chasing AI because AI is cool. He's looking for something that helps his team deliver on that promise more reliably as the company keeps growing.

So when we're on the call, anything we suggest needs to come back to one of three things: cost, schedule, or quality. That's how Josh thinks about ROI.

What 4C does.

4C is one of the few companies in their market that does architecture, interior design, and construction all under one roof. That's their thing. It's also their hardest problem, because they're managing three really different disciplines that all need to work together for one client.

Their market is Park City luxury. Ski houses, second homes, generational family properties. They have a 5-person leadership team and around 50 people total, including field managers, construction managers, designers, architects, and the operations team.

Where they are today.

4C is early. Not clueless, just early. Most of the AI work so far has been Bryce (Josh's son, BYU student) tinkering on his own. He's smart and he can build basic stuff, but he's not a developer.

Here's what's actually happening:

• Rebuilding their TeamBoard tool in-house. They've been paying for an outside tool that handles their org chart and who's in the office. Bryce is rebuilding it himself with AI-assisted code.
• An assistant for Construction Managers. Bryce is trying to build a tool that tracks client selections, approvals, to-do lists, vendor sign-offs, and scope of work. It's not in production. It's a prototype.
• An assistant for Field Managers. Same idea, but for the people on job sites. Schedule tracking, site walk checklists, automatic client updates. Also still a prototype.
• Gemini for meeting notes. They use Google Meet, so Gemini takes notes for them. It was running during our call.
• Some light ChatGPT and Claude use. Nothing systematic yet.

And the line that sums up the whole opportunity:

What Josh actually wants AI to do.

Almost everything Josh wants comes back to the same problem: clients don't make decisions fast enough, and when they finally do, the information doesn't get to vendors cleanly. That breaks the schedule, blows the budget, and ruins the experience he's trying to deliver.

Here's the list of what he wants AI to help with, roughly in priority order:

• Get clients to make decisions on time. Selections, change orders, sign-offs. He says this is one of their biggest struggles right now.
• Translate client decisions into clean scope of work for vendors. Right now it's manual and there are too many places where things fall through the cracks.
• Keep everyone accountable to the order of operations. Josh wants something that knows what should be happening when, and tells someone when it isn't.
• Get into BuilderTrend. All their project data is in BuilderTrend, but it doesn't have a real API. Josh's exact words: "If a tool like this could access that... have a meeting with the Bivens, go get me all the latest data, schedule, costs, quality, notes... that would be powerful." This is high on his list. It's currently out of scope on my piece, so it really belongs in your engagement.
• Take Bryce's prototypes and turn them into something real. The Field Manager and Construction Manager assistants need to go from "Bryce is messing with this" to something the team actually uses every day.
• Help the team get comfortable with AI. Right now Bryce is the only one really using it. They want broader adoption.
• Build it around their EOS framework. They run the company on EOS (Level 10s, rocks, scorecards). They want AI that speaks their internal language.

The people you'll be talking to.

Their tech stack.

• BuilderTrend. This is where all their project data lives. The catch: there's no real API, so you can't pull data out of it programmatically. That's their biggest technical roadblock and also their biggest unlock if you can solve it.
• Team Board. Their org chart and availability tool. Bryce is replacing it.
• Google Workspace. Including Gemini for meeting notes.
• EOS. The internal operating language of the company.
• Some ChatGPT and Claude use. Nothing in production.

What Josh has already said about budget and when he wants to move.

That number came up after I told him your typical project range. He didn't flinch. The thing he keeps coming back to is "as long as it saves us money on the back side." So everything we propose should tie to ROI, and we should be able to show our work.

• Who decides: Josh decides. Chris has to approve.
• Timing: As soon as Chris is available. No artificial pressure.
• What he's expecting: Two things. A proposal from me on the Chief of Staff install (already sent), and a scope from you on the implementation side. He wants both before he decides.
• Heads up on my piece: Earliest install date is May 5. I travel Thursday, Friday, and Saturday only.

Stuff that doesn't fit anywhere else but matters.

• No baggage from past AI consultants. They've never hired one before. Nothing went wrong, because nothing's been tried at scale. This is greenfield.
• The family thing is healthy. Josh has Bryce running real AI work for the company, not protecting him from it. The dynamic on the call was collaborative, not weird.
• Chris is the relationship to manage. Josh said twice that Chris is hesitant about AI. The next call is partly a sales call, partly a "let's get Chris comfortable" call. Talk to him directly when he's in the room.
• EOS is a way to connect. If you can speak fluent EOS (rocks, Level 10s, scorecards, accountability chart), you'll sound like one of them.
• The quote that should be the headline of the call: "I'm not bashful about $20K to $150K as long as it equates to a commensurate level of savings on the back side. How do we do it? Let's go." That's a real quote. He really said it.

What's already been positioned with Josh.

Josh has a $5,000 in-person Chief of Staff install proposal from me. One day on site for the leadership team. That install is the rhythm and language layer. It captures how 4C thinks, makes decisions, and operates, and gives each leader a personal AI Chief of Staff that knows them and the business.

Your engagement is the heavy implementation underneath that. Productionizing the assistants, getting into BuilderTrend, building real role-specific AI employees, training the team. Mine is the operating system. Yours is the software that runs inside it.

Josh already understands this. He asked for both pieces in writing before he decides.

A few thoughts on what'll land.

• Start with the bottleneck. Client decisions on time, cost, schedule, quality. Use his words before you bring in technical stuff.
• Have an answer for BuilderTrend. If Connor can lay out a real path to getting at BuilderTrend data, even without an API (browser automation, partner-tier access, screen agents, whatever), that alone will probably get a yes.
• Show the ROI math. Chris is going to be in the room for this exact reason. Talk in dollars saved or hours back.
• Treat Bryce as a peer. He's going to be your day-to-day contact. He needs to feel like he's part of the team, not getting replaced.
• Don't soften the price. Josh already gave the number. Match his energy and let the work do the selling.

Where this came from

• Discovery transcript: 06-defense/transcripts/2026-04-23_NataleeJosh-4C-and-AI.txt
• Fathom call: fathom.video/calls/649155562
• Proposal sent to Josh: 4c.trailblazers.ai
• Project folder: 04-sales/projects/4c-group-proposal/