Champion Mindset Playbook: Caliche Roofing
Why this matters here. At 4.2M with three crews and two estimators still needing the owner to close insurance jobs, the thing holding everything up is not hours, it is whether the team responds to hard moments by solving or by explaining. Growing without Ray in every estimate requires people who own their outcomes on a normal Tuesday, not just when the owner is watching.
The Definition Card
A Champion at Caliche is someone who owns the outcome the moment they see a problem and brings a proposed fix and keeps the client informed before the client has to ask.
We notice our Champions every day when they:
- An estimator finds a scope gap on an insurance job and calls the adjuster themselves before telling Marco it is a problem
- A crew lead notices a material shortage at 7am and has a solution in hand when they call Luis, not just the news
- Dana catches a billing error and corrects it and tells the client before the client calls about it
- An estimator loses a job and comes to the Monday pipeline review with one specific thing they would do differently next time
- A crew member sees a safety issue on a neighbor's property mid-job and flags it to the crew lead the same day
- Someone gets a negative Google review and drafts a response for Marco or Ray to approve rather than waiting to be asked
- A team member disagrees with a call and says so directly in the room, then executes the decision once it is made
Victim behavior here is when someone blames the adjuster or the weather or the client for a missed close or a blown schedule or an overrun cost.
We notice victim behavior when someone:
- Starts the explanation of a missed job with "the adjuster was impossible" or "the client already had someone" before saying what they tried
- Brings a problem to Luis or Marco with no proposed next step, just the news
- Lets a client find out about a delay by calling us rather than us calling them
- Misses a schedule date and the first sentence is about materials arriving late, not about what they are doing about it now
- Goes quiet on a hard job instead of escalating early
- Talks about what another crew or another estimator is doing wrong without having said it to that person first
- Presents the week as fine in a check-in when it is not, because it feels safer to look good than to ask for help
How we call it without shaming. "That sounds like a window sentence. Give me the mirror version, what is the one thing you could have done differently?"
The litmus question. "Am I starting with what they did, or am I starting with what I am going to do about it?"
Story Bank
| Title | The story | Impact (how it felt, what it produced) | Behavior it shows |
|---|---|---|---|
| The Helotes Scope Call | Sam was running an insurance estimate in Helotes. The adjuster's initial scope came back short. Instead of flagging it to Marco or waiting for Ray to step in, Sam called the adjuster directly, walked the line items, and got a revised scope approved. Marco found out the job was done when the customer mentioned it. Sam never made it a moment; he just handled it. | The crew started on time, the margin held, and Ray never had to touch it. Marco felt what it looks like when an estimator owns the whole job, not just the measurement. It set the standard for what independent looks like on an insurance job. | Owns the outcome, brings a proposed fix, does not wait for permission |
| The 7am Materials Call (example to replace) | A crew lead noticed at 7:05am that shingles for the day's job were not on the truck. He had already called the supplier, confirmed a noon delivery, and called Luis with a question: did Luis want to shift the crew to the gutter job next door first. Luis said yes. The crew lost no billable hours that day. | No crew standing around, no client call about a delay, no cost overrun. Luis felt like he had a crew lead, not a crew. | Brings a solution, not just the problem |
| The Honest Pipeline Review (example to replace) | At the Monday pipeline review, one estimator said out loud that he had let two retail jobs age past 10 days without a follow-up call because he had been focused on insurance jobs. He named the two jobs, said he would call both that afternoon, and asked Marco if there was a follow-up script he should be using. Both jobs closed that week. | Marco had real information to coach from. The estimator closed jobs that were about to go cold. The team saw that honesty in the review room produces help, not a lecture. | Looks in the mirror first, asks before assuming, trusts the process |
| Waiting for the Adjuster to Blink (example to replace, anonymized) | On a mid-size insurance job, the scope came back low. The person handling it decided to wait and see if the adjuster would revise it rather than making the call. Two weeks passed. The client called Ray directly, frustrated that nothing was moving. Ray had to step back into a job he had handed off, spend two hours on the phone with the adjuster, and delay two other jobs to do it. | The client nearly walked. Ray lost half a day. The crew's schedule shifted. The cost of waiting was three times the cost of one uncomfortable phone call. The lesson is not about the person; it is about what silence costs when a hard call is sitting in front of you. | Victim behavior: goes quiet on a hard job, lets the client find out first |
The Helotes Scope Call
The story: Sam was running an insurance estimate in Helotes. The adjuster's initial scope came back short. Instead of flagging it to Marco or waiting for Ray to step in, Sam called the adjuster directly, walked the line items, and got a revised scope approved. Marco found out the job was done when the customer mentioned it. Sam never made it a moment; he just handled it.
Impact (how it felt, what it produced): The crew started on time, the margin held, and Ray never had to touch it. Marco felt what it looks like when an estimator owns the whole job, not just the measurement. It set the standard for what independent looks like on an insurance job.
Behavior it shows: Owns the outcome, brings a proposed fix, does not wait for permission
The 7am Materials Call (example to replace)
The story: A crew lead noticed at 7:05am that shingles for the day's job were not on the truck. He had already called the supplier, confirmed a noon delivery, and called Luis with a question: did Luis want to shift the crew to the gutter job next door first. Luis said yes. The crew lost no billable hours that day.
Impact (how it felt, what it produced): No crew standing around, no client call about a delay, no cost overrun. Luis felt like he had a crew lead, not a crew.
Behavior it shows: Brings a solution, not just the problem
The Honest Pipeline Review (example to replace)
The story: At the Monday pipeline review, one estimator said out loud that he had let two retail jobs age past 10 days without a follow-up call because he had been focused on insurance jobs. He named the two jobs, said he would call both that afternoon, and asked Marco if there was a follow-up script he should be using. Both jobs closed that week.
Impact (how it felt, what it produced): Marco had real information to coach from. The estimator closed jobs that were about to go cold. The team saw that honesty in the review room produces help, not a lecture.
Behavior it shows: Looks in the mirror first, asks before assuming, trusts the process
Waiting for the Adjuster to Blink (example to replace, anonymized)
The story: On a mid-size insurance job, the scope came back low. The person handling it decided to wait and see if the adjuster would revise it rather than making the call. Two weeks passed. The client called Ray directly, frustrated that nothing was moving. Ray had to step back into a job he had handed off, spend two hours on the phone with the adjuster, and delay two other jobs to do it.
Impact (how it felt, what it produced): The client nearly walked. Ray lost half a day. The crew's schedule shifted. The cost of waiting was three times the cost of one uncomfortable phone call. The lesson is not about the person; it is about what silence costs when a hard call is sitting in front of you.
Behavior it shows: Victim behavior: goes quiet on a hard job, lets the client find out first
Observation Rituals
| Ritual | Lives in | Who runs it | Cadence | The rule |
|---|---|---|---|---|
| Weekly champion story | Friday tailgate meeting (parking lot, before crews roll out) and Monday sales huddle | Luis runs it at the tailgate; Marco runs it in the sales huddle | Every week, rotating who tells the story | 60 seconds max. The person telling it names the specific behavior, how it felt, and what it produced. Not a ceremony. If no one has a story, the runner tells one from the story bank. |
| Weekly victim-behavior lesson | Friday tailgate meeting | Luis runs it for crew; Marco runs it in the sales huddle | Every week | Anonymized or self-nominated. Self-nomination is the goal: it proves the mirror is working. The runner names the behavior and the cost, never the person. If someone self-nominates, the team thanks them, no pile-on. Ray runs both for the first 8 weeks to model that the owner is not exempt, then hands to Luis and Marco. |
| Kudos wall | Dedicated group text thread, created and managed by Dana | Dana manages the thread; Marco and Luis post to it; anyone on the team can post | Posts happen as they happen; Dana reads two kudos aloud at the Friday tailgate | A kudo must name the specific behavior, not just the person. "Great job this week" does not go in the thread. "Called the adjuster before escalating and got the scope revised same day" does. |
Weekly champion story
Lives in: Friday tailgate meeting (parking lot, before crews roll out) and Monday sales huddle
Who runs it: Luis runs it at the tailgate; Marco runs it in the sales huddle
Cadence: Every week, rotating who tells the story
The rule: 60 seconds max. The person telling it names the specific behavior, how it felt, and what it produced. Not a ceremony. If no one has a story, the runner tells one from the story bank.
Weekly victim-behavior lesson
Lives in: Friday tailgate meeting
Who runs it: Luis runs it for crew; Marco runs it in the sales huddle
Cadence: Every week
The rule: Anonymized or self-nominated. Self-nomination is the goal: it proves the mirror is working. The runner names the behavior and the cost, never the person. If someone self-nominates, the team thanks them, no pile-on. Ray runs both for the first 8 weeks to model that the owner is not exempt, then hands to Luis and Marco.
Kudos wall
Lives in: Dedicated group text thread, created and managed by Dana
Who runs it: Dana manages the thread; Marco and Luis post to it; anyone on the team can post
Cadence: Posts happen as they happen; Dana reads two kudos aloud at the Friday tailgate
The rule: A kudo must name the specific behavior, not just the person. "Great job this week" does not go in the thread. "Called the adjuster before escalating and got the scope revised same day" does.
Who runs it. Ray runs the champion story and the victim-behavior lesson for the first 8 weeks to model that the owner goes first and is not exempt. After week 8, Luis owns both at the Friday tailgate and Marco owns both in the Monday sales huddle. Dana owns the kudos thread from day one.
Reinforcement Plan
| Who | What | When | |
|---|---|---|---|
| Feedback | Marco (for estimators), Luis (for crew leads), Dana (for office) | Name the specific behavior in the moment, in behavior language: "You called the adjuster before it became my problem, that is exactly what we mean by owning it." Managers go first and are the fastest mirrors in the building. | Within 24 hours of the behavior. Positive feedback same day if possible. Corrective feedback before the next shift or next workday. |
| Reinforcing content | Ray | One short example per month: a real story from Caliche, a short article, or a 2-minute clip that connects to the definition card. Ray shares it verbally at the Friday tailgate or sends it to the team group text. | First Friday of each month. Ray selects it and delivers it himself. |
| Rewards | Marco and Luis nominate; Ray approves | A $50 gift card or equivalent, given publicly at the Friday tailgate, for a specific champion behavior that had a measurable business outcome. The behavior is named out loud when the reward is given. | Once per month per team (sales, crew). Reward the behavior, not just the result: an estimator who handled a hard adjuster call well but did not close the job is still eligible. |
Feedback
Who: Marco (for estimators), Luis (for crew leads), Dana (for office)
What: Name the specific behavior in the moment, in behavior language: "You called the adjuster before it became my problem, that is exactly what we mean by owning it." Managers go first and are the fastest mirrors in the building.
When: Within 24 hours of the behavior. Positive feedback same day if possible. Corrective feedback before the next shift or next workday.
Reinforcing content
Who: Ray
What: One short example per month: a real story from Caliche, a short article, or a 2-minute clip that connects to the definition card. Ray shares it verbally at the Friday tailgate or sends it to the team group text.
When: First Friday of each month. Ray selects it and delivers it himself.
Rewards
Who: Marco and Luis nominate; Ray approves
What: A $50 gift card or equivalent, given publicly at the Friday tailgate, for a specific champion behavior that had a measurable business outcome. The behavior is named out loud when the reward is given.
When: Once per month per team (sales, crew). Reward the behavior, not just the result: an estimator who handled a hard adjuster call well but did not close the job is still eligible.
Expansion Queue
| Concept | When or trigger | Owner |
|---|---|---|
| Growth versus Fixed Mindset | After the first 8 weeks of the champion card are running without Ray at the tailgate | Marco (sales), Luis (crew) |
| Event plus Response equals Outcome | After the victim-behavior lesson has run at least 6 times and the team is self-nominating | Ray introduces it, then hands the framework to Marco and Luis |
Growth versus Fixed Mindset
When or trigger: After the first 8 weeks of the champion card are running without Ray at the tailgate
Owner: Marco (sales), Luis (crew)
Event plus Response equals Outcome
When or trigger: After the victim-behavior lesson has run at least 6 times and the team is self-nominating
Owner: Ray introduces it, then hands the framework to Marco and Luis
How to run a new concept. First, define it in Caliche's words with observable behaviors the team would actually see on a job site or in the office. Second, teach it using a real story from Caliche's own history, not a textbook example. Third, observe it inside the rituals already running: the weekly story, the lesson, the kudos thread. Fourth, nourish it with feedback in behavior language, one piece of reinforcing content, and a reward tied to a specific behavior that showed the concept in action.
Definition of Done
The team uses the mirror and window language unprompted in check-ins and on job sites. The weekly story, the victim-behavior lesson and the kudos thread run without Ray in the room. When a hard moment happens, someone on the team names the behavior out loud before Ray does.
What to Check First
- Two stories are still examples. The 7am materials call and the honest pipeline review are placeholders. If you have real moments from Luis's crews or from a sales huddle, tell me and I will rewrite them with the actual details.
- The victim story is also a placeholder. If there is a real anonymized moment where going quiet on a hard job cost the business time or a client, that story will land harder than a composite. You do not need to name anyone.
- The $50 reward amount. Confirm this is the right size for Caliche. It should feel meaningful without being a budget line that gets cut the first slow month.