Phase 7 teaches you how to deliver Brava in a way that scales without breaking quality. You’ll learn what must be live, what can be async, how to choose the right format per situation, and how to install communication boundaries so you’re never “on-call” while still being deeply effective.
What you’ll be able to do
Choose the right mix of live + async • protect capacity • deliver consistent outcomes across remote and in-person clients.
Why this matters
If delivery isn’t structured, you become a 24/7 helper. Boundaries aren’t optional—they’re the system that makes Brava profitable.
14) Virtual vs In-Person Execution
Delivery
Brava is not “in-person only” and it’s not “remote only.” It’s a delivery system. You decide what must be live, what can be handled async, and when presence matters because it changes behavior—not because it feels nicer.
What must be live (non-negotiable moments)
Live
Live time is reserved for moments where trust, alignment, or behavior change requires real-time presence. If it doesn’t require presence, it becomes async.
Employee check-ins (most of them): structured async pulses that identify signals quickly.
Follow-up proof-of-done: quick verification prompts + screenshots + “is this now standard?”
Async rule
If it can be answered once and reused, it becomes an async template.
When presence matters (decision filter)
Filter
Presence matters when it changes behavior and reduces misinterpretation. Use this filter to decide live vs async.
High risk: misalignment could cost revenue, retention, or execution this month.
High emotion: tone matters and text would inflate conflict or confusion.
New install: first-time behavior shifts are easier when you model it live once.
Low trust: if the relationship is new or fragile, do it live to stabilize.
Fast question
“If I handle this async, does it increase misinterpretation or reduce follow-through?” If yes → go live.
Remote scale model (simple operating lanes)
Scale
Remote delivery works when lanes are clear. This model keeps you present enough to create outcomes, without creating dependency.
REMOTE DELIVERY MODEL (repeatable) Weekly: • 1 leadership touchpoint (live or async voice note) • 2–4 employee check-ins (mostly async) • 1 follow-up lane (proof-of-done checks) • 1–2 async response windows (batch) Monthly: • 1 owner report walkthrough (live) • 1 priority reset + next installs (live or live+async) Quarterly (optional): • 1 “stability audit” session (live)
Why this scales
Live time is limited to moments that change behavior. Everything else becomes standardized and repeatable.
Mini drill (delivery decision)
Take one messy business situation and decide: what is live vs async? Then write the smallest lane-based plan.
Situation: Must be live because: Can be async because: This week’s lanes: - Leadership touchpoint: - Check-ins: - Follow-ups: - Async windows:
Mastercoach (locked)
Enter code to reveal trainer cues, tests, and what to look for.
Incorrect code. Try again.
Mastercoach cues: Virtual vs In-Person Execution
The failure modes: (1) “meeting addiction” (everything becomes live), (2) “ghost consulting” (everything becomes async and trust drops), and (3) “on-call dependency” (clients train them to respond instantly). Train the filter: presence only when it changes behavior.
Pass test: give 5 scenarios → they must choose live vs async and justify using the presence filter (risk/emotion/new install/trust).
Watch for: “Let’s hop on a call” as default. Require the question: “Does live reduce misinterpretation or increase follow-through?”
Watch for: too little live time early (trust not installed). Require a strong onboarding + monthly owner walkthrough live.
Scoring: 1–5 on: decision quality, lane clarity, scale readiness, boundary language, outcomes focus.
Correction phrase
“Live is for alignment + behavior change. Async is for scale. If everything is live, you won’t scale.”
15) Communication Boundaries
Boundaries
This section protects strategist capacity. Boundaries are not a “personal preference”—they are part of the Brava operating system. You will set availability without being on call, install async norms, define owner access rules, and create team access clarity.
Availability without being on call (the standard)
Standard
Brava delivery requires you to be responsive, not constantly available. You must set response windows so the business learns the system.
Response windows: “I respond in 1–2 windows per day. This protects speed and quality.”
Emergency definition: “Emergency means operational stoppage or customer harm—not stress.”
Escalation lane: “If urgent, send it to the owner lane. If not, it goes in the async queue.”
Batching protects outcomes: constant pings create shallow work and lower quality.
Boundary rule
The moment they train you to respond instantly, your capacity collapses and quality drops.
Async norms (how you make remote delivery clean)
Norms
Async only works when the business knows how to use it. You must install norms that reduce back-and-forth, prevent vagueness,
and keep accountability clean.
One-thread rule: one topic per message thread (prevents chaos and missed decisions).
Structured asks: “Context → the ask → deadline → what success looks like.”
Proof-of-done standard: screenshot, photo, or copy/paste of the updated system (no “we did it” claims).
Decision capture: decisions are summarized and pinned as “new standard” (prevents re-arguing).
Async clarity rule
If they can’t state the ask clearly, it’s not ready for your time yet.
Owner access rules (protect the strategist lane)
Owner
Owners can unintentionally collapse the system by bypassing lanes. You set owner access rules so you’re not used as a venting line
and not pulled into daily noise.
Owner lane only: owner messages go in a dedicated channel (not mixed with staff team chat).
Access by category: owner can message about priorities, risk, and decisions—not day-to-day frustrations.
Time windows: “Owner messages are reviewed during response windows unless it’s a defined emergency.”
Monthly reset meeting: issues that aren’t urgent get parked for the monthly walkthrough.
Owner rule
Owners get clarity, not constant access. Constant access creates dependency and chaos.
Team access clarity (prevent “strategist-as-HR”)
Team
Team access is limited and structured. If the team uses you as a therapist, vent line, or complaint collector, Brava collapses into
“HR escalation.” You define what team access is for.
Check-ins are structured: you collect signals, not stories (you’re not doing therapy).
No triangulation: you do not carry messages between employees and leaders.
Confidentiality scope: you protect privacy, but you escalate risk signals to the owner (without naming gossip).
Lane language: “Bring me signals. We solve systems. If it’s personal conflict, we route it properly.”
Team rule
You’re a safe signal holder—not an HR replacement and not a therapist.
Scripts you will memorize (boundary language that doesn’t offend)
These phrases keep you firm without sounding cold. Use them early so the business learns the Brava system.
BOUNDARY SCRIPTS
Response windows:
• “I respond in 1–2 windows per day so I can protect speed and quality.”
Emergency definition:
• “Emergency means operational stoppage or customer harm — not stress.”
Owner lane:
• “Owner messages go in the owner lane so we keep decisions clean and auditable.”
Team access:
• “I collect signals and patterns, not stories. We fix systems, not vent loops.”
Escalation:
• “If it can’t be acted on this week, we park it for the monthly walkthrough.”
Mastercoach (locked)
Enter code to reveal trainer cues, tests, and what to look for.
Incorrect code. Try again.
Mastercoach cues: Communication Boundaries
The failure modes: (1) they feel guilty and over-respond, (2) they let owners dump daily noise into the strategist lane,
(3) they become a venting line for employees, and (4) they avoid boundaries until the client “trained” them into on-call behavior.
Train: boundaries are part of delivery, not personality.
Pass test: role-play 3 boundary moments (owner dumping, employee venting, “urgent” text) → they must respond calmly using scripts.
Watch for: “I’ll just answer real quick” reflex. Correct: “If it’s not a defined emergency, it sits until response window.”
Watch for: “triangulation.” If they carry messages between people, they become HR. Require lane clarity and escalation rules.
Scoring: 1–5 on: calm authority, script accuracy, escalation clarity, lane enforcement, guilt resistance.
Correction phrase
“Boundaries aren’t personal. They’re how Brava stays fast, clear, and profitable.”
16) Choosing the Right Model Per Client
Fit
Not every business needs the same delivery model. Your job is to choose the format that matches their reality:
leadership maturity, stability level, urgency, and how much structure they can actually follow through on right now.
The 4 delivery models (pick one as default)
Models
Brava can be delivered in multiple formats. But you pick ONE default per business so the system is stable.
THE 4 BRAVA DELIVERY MODELS
1) Remote Standard (Scale)
• Weekly async lanes + monthly owner walkthrough live
• Best for stable teams + owners who follow process
2) Remote Intensive (Stabilize)
• More frequent leadership touchpoints (live or voice note)
• Best for messy businesses that need fast structure installs
3) Hybrid Local (High leverage)
• Remote lanes + 1 in-person presence day/month
• Best when “presence” changes leader behavior and follow-through
4) In-Person Embedded (Rare / premium)
• Regular on-site presence
• Best for extreme dysfunction or high-stakes turnaround (price accordingly)
Client readiness indicators (how you choose)
Signals
Use these indicators to choose the model based on reality—not preference.
Leadership maturity: can they handle accountability without defensiveness?
Stability level: is the business calm enough to follow lanes—or constantly on fire?
Urgency: are they losing staff/revenue right now (requires more intensity)?
Owner bandwidth: do they actually show up for decisions and installs?
Delivery model isn’t permanent. You adjust based on compliance and stability—but you do it with rules, not emotions.
Upgrade to intensive if: priorities aren’t executed for 2 weeks OR risk signals spike.
Downgrade to standard if: lanes are followed consistently for 30 days and fires decrease.
Hybrid presence if: in-person changes leader behavior (not because they “prefer it”).
Embedded only if: turnaround is required AND priced to match the reality of the work.
Important
Never punish a client with intensity. You upgrade because outcomes require it.
Mini drill (pick a delivery model in 60 seconds)
Drill
This quick drill keeps you from guessing. Use it during onboarding or right after the first evaluation.
60-SECOND MODEL PICK
1) Stability level (calm / medium / on fire):
2) Owner follow-through (high / medium / low):
3) Leadership maturity (high / medium / low):
4) Urgency (high / medium / low):
Default model:
Why this model fits reality:
One rule we install immediately (lanes/boundaries):
Rule
Pick the model that the business can follow today—then upgrade as they become stable.
Mastercoach (locked)
Enter code to reveal trainer cues, tests, and what to look for.
Incorrect code. Try again.
Mastercoach cues: Choosing the Right Model
The failure mode is “one model for everyone.” That creates either overwork (too intensive) or weak outcomes (too light).
Train them to pick based on: stability, follow-through, leadership maturity, urgency. Make them defend the model in business terms.
Pass test: present 3 client profiles → they must choose a model + justify using the 4 indicators + set lanes/boundaries.
Watch for: “they want in-person” bias. Correct: “presence is chosen only if it changes behavior and follow-through.”
Watch for: under-servicing a chaotic business. Require “intensive first” until stability improves.
Scoring: 1–5 on: reality-based selection, lane clarity, boundary installs, upgrade/downgrade rules, outcome focus.
Correction phrase
“We choose the model that matches reality today, then we upgrade as stability increases.”
