Higher State Enterprise
Your strategy isn’t the bottleneck. Inconsistent human execution is.
A measured 90-day pilot that installs Higher State OS in one revenue team, transfers the cadence to managers, and shows leadership what the evidence does—and does not—support.
Pilot facts
One revenue team
90 days
Manager-led reinforcement
Baseline and executive readout
Designed for an organization with 10–250 revenue producers in the target population, a focused pilot team, an executive sponsor, and enough data to define success responsibly.
Adrian Provost leads the engagement and delivers the live sessions. If additional facilitators or analysts are required for the scope of a given pilot, they are named in the order form before the pilot begins.
The problem
The execution gap
You can have a defined sales process, a capable enablement team, and managers who care—and still see a different standard in every room. One rep discovers the real decision criteria. Another jumps to the demo. One manager coaches behavior. Another reviews only the number after the fact.
A Higher State Enterprise pilot gives participants a common baseline, a practical preparation protocol, a tested language architecture, realistic rehearsal, and a manager cadence. The goal is not a short-lived performance spike. It is an operating system the organization can use after the pilot ends.
Symptoms the pilot addresses
- Sales cycles lengthen because decision criteria and next steps remain unclear.
- Discovery varies by rep, manager, region, or office.
- Discounting begins before value and risk have been framed clearly.
- Coaching depends on a few strong managers and cannot be reproduced.
- Reps understand the process in training but abandon it under pressure.
- Pipeline reviews describe activity without identifying the behavior behind the movement.
- Top performers carry too much of the result while the middle remains inconsistent.
- Enablement produces content, but managers lack a cadence for rehearsal and reinforcement.
Fit
Who it is for
The strongest fit is an organization that:
- Has 10–250 revenue producers in the target population and can define one focused pilot team.
- Uses a complex, high-consideration, high-trust, consultative, enterprise, channel, franchise, or brokerage sales motion.
- Has an executive sponsor with authority to align managers, approve access, remove barriers, and attend the readout.
- Sees a specific execution problem such as uneven discovery, unclear decision criteria, early discounting, long cycles, inconsistent preparation, manager-dependent coaching, or weak pipeline integrity.
- Already has a sales process or enablement investment but sees uneven adoption in real conversations.
- Can provide participating managers and a designated internal project owner.
- Can provide enough approved evidence to establish a baseline: interviews, CRM reports, call samples, scorecards, enablement materials, or other agreed inputs.
- Is willing to define success, attribution limits, access, privacy, retention, and an expansion decision before delivery begins.
- Wants managers to own the reinforcement cadence after the pilot rather than remain dependent on an outside coach.
Typical sponsors include CROs, VPs of Sales, founder-CEOs, brokerage owners, franchise executives, business-unit leaders, and sales-enablement leaders.
Who it is not for
- A team seeking a one-time motivational event with no baseline, practice, manager follow-through, or readout.
- An organization requiring a guaranteed revenue or conversion result.
- A team without an executive sponsor, participating managers, or an internal project owner.
- A request for covert employee monitoring, undisclosed recording, automated employment decisions, personality profiling, or individual health assessment.
- A performance-remediation substitute for HR, legal, clinical, or employee-assistance processes.
- A group that cannot lawfully share or approve the data required for the agreed pilot.
- A need that spans many teams, geographies, or business units but has not been reduced to one testable pilot.
- Individual-development needs should route to Accelerator unless complexity justifies a scoped exception.
- An organization seeking ownership of Higher State OS, unrestricted source materials, or the right to deliver the method with its own facilitators.
Prerequisites
Before delivery begins
- Named executive sponsor and internal project owner.
- One defined pilot team; larger target populations require phased delivery.
- At least one participating manager for every practical coaching group.
- A bounded performance problem and one preliminary business question.
- Agreement to a 90-day schedule and manager reinforcement expectations.
- Access to sufficient approved baseline evidence. Call recordings are optional, not mandatory.
- Completion of legal, privacy, information-security, procurement, recording-consent, and data-processing review before protected or production data is transferred.
- A signed statement of work, commercial terms, data responsibilities, and measurement brief.
- Participant communication that explains purpose, expected time, data use, who sees what, and how to raise a concern.
- Explicit permission for any recording, transcript, or personally identifiable content used.
- No request to collect medical information or use the Index for employment selection, diagnosis, or automated personnel decisions.
- Calendar access for sponsor, managers, pilot participants, and required subject-matter owners.
Evidence
Baseline and data inputs
The first decision is what evidence is both useful and appropriate. The pilot does not require every possible data source. It requires enough to define the leak and observe movement responsibly.
Potential inputs
- Higher State Index responses from participating employees, with clear consent and use terms.
- Sponsor, manager, and participant interviews.
- Existing stage conversion, cycle, next-step, discount, forecast, or retention data.
- A permissioned sample of call recordings, transcripts, scorecards, or meeting notes.
- Existing sales-process, onboarding, enablement, and coaching materials.
- Manager observations tied to agreed behaviors.
- Participation, rehearsal, and coaching-adoption data generated during the pilot.
Before launch, both parties approve a measurement brief identifying the baseline window, target population, definitions, source systems, access, owners, comparison approach, and limitations.
The plan
The 90-day schedule
Weeks 1–2 — Measure
Purpose
Find the priority execution leak and establish the baseline.
Work
Sponsor alignment; participant communication and consent; Higher State Index; manager and stakeholder interviews; selected call, pipeline, and process review; definition of behavior and business indicators.
Output
Baseline report, priority leak, pilot scorecard, participant segments, measurement plan, and a signed definition of success.
Weeks 3–6 — Regulate + Reframe
Purpose
Improve readiness and the language used at the moments that matter.
Work
Personal pre-performance protocols; live workshops; discovery and framing review; objection and negotiation language; manager coaching practice; field application between sessions.
Output
Pre-performance protocol, first version of the language architecture, participant practice plan, manager coaching prompts, and early usage data.
Weeks 7–10 — Rehearse
Purpose
Make the behavior durable enough for real calls and meetings.
Work
Role-play, permissioned call teardown, AI-supported practice using approved scenarios, peer review, manager feedback, and repeated application to current opportunities.
Output
Scenario library, competency scorecard, revised language architecture, adoption report, and documented coaching actions.
Weeks 11–12 — Scale + readout
Purpose
Transfer ownership and make an evidence-based expansion decision.
Work
Manager handoff, playbook finalization, adoption report review, participant and sponsor feedback, baseline comparison, limitations review, and 90-day readout.
Output
Team playbook, manager cadence, final adoption report, business-indicator readout, recommendations, and an expansion/no-expansion decision brief.
Curriculum
Full curriculum / modules
The standard pilot uses 12 program weeks within a 90-day contract window. Contracting, security, and data access begin before Week 1.
| Week | Title | Learning objective | Output / deliverable |
|---|---|---|---|
| 1 | Measure I: Charter the pilot | Align the business question, human behavior, scope, ownership, and evidence before training begins. | Signed Pilot Charter, RACI, Measurement Brief v1, Data Plan, and participant communication. |
| 2 | Measure II: Establish the baseline | Identify the priority execution leak without collecting unnecessary information. | Baseline Report, aggregate Index view, priority leak, participant segments, Pilot Scorecard, and signed definition of success. |
| 3 | Regulate I: Design the preparation standard | Give participants a practical routine for the actual moment in which execution changes. | Personal Pre-Performance Protocol v1, role-based Preparation Card, and usage plan. |
| 4 | Regulate II: Test under disruption | Make the preparation standard usable when time, ambiguity, or pressure changes the plan. | Protocol v2, first rehearsal scores, field-use log, and manager coaching actions. |
| 5 | Reframe I: Discovery and decision criteria | Build shared language for understanding how the customer or stakeholder will decide. | Team Room Map, opening standards, discovery question set, and Language Architecture v1. |
| 6 | Reframe II: Friction, trade-offs, and next steps | Clarify objections and negotiation issues before defending or discounting. | Objection and negotiation framework, next-step standard, Language Architecture v2, and midpoint decision log. |
| 7 | Rehearse I: Build the scenario system | Turn recurring high-stakes moments into safe, repeatable practice. | Scenario Library v1, Competency Scorecard, Feedback Guide, and baseline rehearsal data. |
| 8 | Rehearse II: Practice the weakest moment | Improve consistency through repetition focused on the lowest-scoring behavior. | Individual practice records, Scenario Library v2, competency trend, and calibration notes. |
| 9 | Rehearse III: Review live work | Transfer practice into current calls and meetings while protecting permission and privacy. | Call-Teardown set, revised Language Architecture v3, and documented coaching actions. |
| 10 | Rehearse IV: Install manager ownership | Make the practice and feedback cadence runnable without the external facilitator. | Manager-led session record, Adoption Report, final coaching cadence, and ownership map. |
| 11 | Scale I: Compare and hand off | Prepare an honest comparison of baseline, adoption, behavior, and available business indicators. | Team Playbook, Manager Handoff Package, Final Adoption Report draft, and Business-Indicator Readout draft. |
| 12 | Scale II: Read out and decide | Give leadership enough evidence to sustain, change, stop, or expand the work. | Final Readout, Expansion/No-Expansion Decision Brief, Quarterly Review Agenda, and data closeout plan. |
Experience
Participant and manager experience
The participant experience
- A short baseline reflection and onboarding session.
- A personal pre-performance protocol.
- Focused workshops on language and decision moments.
- Weekly practice using current, relevant scenarios.
- Selected peer, manager, or facilitator feedback.
- A final reflection on adoption, usefulness, and next actions.
The manager experience
Managers are not observers. They are the transfer mechanism.
- A briefing on the baseline and target behaviors.
- A simple call-review and coaching rubric.
- Weekly prompts for one behavior-focused coaching conversation.
- Calibration sessions to make scoring more consistent.
- A role-appropriate view of the adoption report.
- A handoff package and quarterly review agenda.
Format & logistics
How the pilot runs
- Delivery format: Blended remote pilot by default. On-site delivery is available only when scoped.
- Contract window: 90 days, with 12 program weeks. Pre-launch procurement/security work may precede Day 1.
- Pilot population: One revenue team. Broader populations or multiple regions require a phased or custom scope.
- Manager ratio: Defined in the SOW; plan for one participating manager per practical coaching group.
- Live participant delivery: One kickoff, four 90-minute workshops, and four 60-minute rehearsal labs in the core schedule.
- Manager delivery: Three 60-minute calibration sessions plus brief weekly reinforcement.
- Sponsor cadence: 90-minute design session, 45-minute midpoint review, and 90-minute final readout.
- Internal-owner cadence: 30 minutes weekly.
- Practice rooms are kept small enough for active facilitation. Larger pilot populations are split into parallel rooms.
- Access window: Participant course materials are available for 180 days from kickoff unless the SOW says otherwise.
- Tooling is agreed with the customer during onboarding and documented in the SOW.
- Security: No production or personal data is transferred until the agreed security and privacy controls are complete.
- Travel: On-site travel, lodging, venue, and related expenses are either included in the selected tier or approved in writing at cost, as stated in the SOW.
- Accessibility: Participant communication, captions, transcripts, accessible files, remote access, accommodation route, and venue requirements are agreed before launch.
Deliverables
What's included
- Executive baseline report and priority-leak analysis.
- Pilot charter, measurement brief, and success scorecard.
- Participant-level pre-performance protocol template.
- Team language architecture for discovery, framing, objections, negotiation, and next steps.
- Live workshop and rehearsal sessions defined in the statement of work.
- Permissioned scenario library and call-teardown rubric.
- Manager coaching cadence and calibration guide.
- Adoption report with agreed role-based views.
- Higher State OS team playbook.
- 90-day executive readout with results, limitations, and recommendations.
- Quarterly review framework for teams that continue.
Outcomes
What you achieve
- A documented baseline and one priority execution leak.
- Clear separation among self-reported readiness, observable behavior, adoption, and business indicators.
- A shared preparation protocol for selected high-stakes moments.
- A tested team language architecture for discovery, framing, friction, negotiation, and next steps.
- A permissioned scenario and rehearsal system.
- A behavior-based coaching rubric and calibrated manager cadence.
- A role-appropriate adoption report.
- A team playbook and ownership map.
- A 90-day readout with sources, time periods, limitations, and other plausible contributors.
- A reasoned decision to sustain, adjust, stop, or expand.
Adoption indicators may include
- Participant completion of the baseline and core practice sequence.
- Use of the pre-performance protocol.
- Rehearsal and feedback frequency.
- Manager coaching completion and rubric use.
- Demonstrated competency on agreed scenarios.
- Continued use at weeks 8 and 12.
Business indicators may include
- Qualified next-step rate.
- Stage conversion.
- Sales-cycle movement.
- Discount frequency or depth.
- Forecast accuracy.
- Onboarding ramp or manager-coaching consistency.
- Customer-defined indicators tied to the pilot problem.
The SOW must define each metric, data source, owner, time window, comparison, and limitation. A successful pilot does not require every metric to move. It requires responsible delivery, enough adoption to evaluate the method, honest measurement, and a clear next decision. No revenue result or causal conclusion is guaranteed.
Scope and cancellation terms
Scope outside the pilot
- A pilot population requiring parallel delivery.
- Multiple separate teams or business units.
- Translation, interpretation, or substantial localization.
- Custom software, SSO, CRM integration, data engineering, or a bespoke AI system.
- Formal facilitator certification, enterprise license, or broad content rights.
- Travel beyond included on-site days.
- Work requiring regulatory, legal, HR, or clinical expertise.
Refund and cancellation principles
- The reservation may be canceled until the earlier of (a) 10 calendar days after signature or (b) the first completed design/discovery session, less approved non-cancelable third-party costs.
- Once discovery begins, completed work and reserved capacity are non-refundable.
- If the client terminates for convenience, the client pays for delivered work, committed capacity, and approved non-cancelable expenses through the effective termination date, as defined in the SOW.
- If the provider terminates without client breach and cannot provide a reasonable substitute, refund prepaid amounts for undelivered services.
- Approved travel or third-party costs not yet incurred are refundable; incurred costs are not.
- A material scope or calendar change requires a signed change order.
Governance
Expansion options
Expansion is earned at the readout, not assumed at kickoff.
- Team expansion: Extend the playbook and manager cadence to adjacent teams.
- Regional or office rollout: Adapt scenarios while preserving the common measurement standard.
- Quarterly reinforcement: Continue measurement, calibration, rehearsal, and executive review.
- Executive or event activation: Use a leadership session or keynote to align a wider audience before rollout.
Acceptance criteria
- One bounded pilot team.
- Executive sponsor and internal owner.
- Participating managers.
- Defined problem that can be connected to observable work behavior.
- Sufficient appropriate evidence or a credible plan to establish it.
- Feasible legal/security/procurement path.
- Mutual acceptance of data, confidentiality, IP, measurement, and no-guarantee terms.
- Budget within the approved scope.
Privacy and security
Security and data questions
The pilot is designed around data minimization, transparency, and role-appropriate access.
- Collect only the data required for the agreed measurement plan.
- Explain what is collected, why it is used, who can see it, and how long it is retained.
- Obtain appropriate consent before storing individual Index responses or using recorded material.
- Use aggregate reporting for executive readouts unless individual-level access is explicitly necessary, lawful, and disclosed.
- Do not collect medical information or use the Index as a medical, psychological, or employment diagnostic.
- Do not use undisclosed monitoring or automated employment decisions.
- Use approved systems, access controls, and deletion procedures defined in the agreement.
- Define how AI-supported rehearsal works, what content it can access, and where human review remains required.
- Complete the customer's security, legal, privacy, and procurement review before production data is transferred.
Security documentation — including the current security overview, the subprocessor list, the data retention schedule, and the incident-response contact — is provided during procurement review, before any production data is transferred. Request it through the contact form.
FAQ
Frequently asked questions
Why start with one team?
A focused pilot makes the problem, participants, managers, evidence, and decision point clear. It creates a responsible way to learn before asking the organization to scale.
Why 90 days?
The window is long enough to establish a baseline, teach and rehearse the behavior, observe early adoption, transfer the cadence to managers, and complete a readout. It is not presented as enough time to prove every downstream business effect.
What team size is the best fit?
A pilot usually includes one team. Broader populations or multiple teams require a phased or custom scope.
Do we need call recordings?
No. Permissioned recordings can improve behavioral review, but the pilot can use transcripts, manager observations, meeting notes, scorecards, reconstructed scenarios, and operating data. The measurement brief states what the evidence can support.
Is the Higher State Index an employee assessment?
It is a performance reflection tool, not a medical, psychological, personality, or employment-selection diagnostic. It should not be used for hiring, firing, promotion, compensation, or automated personnel decisions.
Who can see individual results?
The data plan defines role-based access before launch. Executive reporting is aggregate by default. Individual information is shared only when necessary, lawful, disclosed, and appropriate to the agreed coaching purpose.
How much time does the pilot require?
Participants typically spend 60–150 minutes in active weeks. Managers typically spend 45–90 minutes in active weeks, plus brief reinforcement. The sponsor joins design, midpoint, and final decision sessions. The SOW gives the exact calendar.
Can the pilot be delivered remotely?
Yes. Remote is the default. Standard and Complex tiers may include on-site days or equivalent remote blocks. The SOW states delivery mode, travel, accessibility, and recording terms.
Will Adrian personally deliver the program?
Adrian Provost leads the engagement and delivers the live sessions.
Do you guarantee revenue or conversion improvement?
No. The pilot measures agreed adoption, behavior, and available business indicators, but many factors influence commercial results. The readout distinguishes observation from causation and states limitations.
What happens if the business indicators do not move?
The readout asks whether the behavior was adopted, whether the measure was appropriate, whether the time window was sufficient, and what other factors changed. Leadership may stop, adjust, reinforce, or run a narrower next test. Expansion is not automatic.
What are the cancellation and refund terms?
The SOW controls. The recommended structure allows an early refund of the reservation payment before discovery begins, less non-cancelable costs. After work and capacity are committed, the client pays for delivered work, reserved capacity, and approved expenses. Prepaid undelivered services are refunded if the provider terminates without client breach and cannot provide a substitute.
Request a diagnostic
Is a 90-day pilot the right next step?
Share enough context for a useful first review. A diagnostic request is not a commitment to buy. Adrian will assess fit, identify missing information, and recommend the next step.
Prove the system in one team before you scale it.
Start with one bounded performance problem, a responsible baseline, and a 90-day decision point.