Wexler Gray — Interactive Demo

Exit Readiness Monitor1 escalation open below the escalation threshold

Hollifern Property Software is 20 points below its escalation threshold — execution bandwidth is the strongest theme at 55 against a threshold of 75. 1 escalation is open (1 low), the oldest running 6 weeks. 2 of 3 tracked board actions are complete so far.

55

Highest signal

of 75 threshold

1

Open escalations

1 low

82%

Participation

coverage sufficient

2/3

Board actions

tracked and complete

What needs attention

3 active themes

Execution Bandwidth

17 independent participants · 6 functions

Developing55 / 75↑ Rising 10wView evidence →

Reported by 17 independent participants across 6 functions, persistent for 10 weeks and rising.Escalation open

Leadership Direction Clarity

14 independent participants · 5 functions

Developing46 / 75FlatView evidence →

Reported by 14 independent participants across 5 functions, persistent for 8 weeks.

Talent & Team Stability

10 independent participants · 6 functions

Weak Signal32 / 75↓ EasingView evidence →

Reported by 10 independent participants across 6 functions, persistent for 6 weeks and easing.

Escalations

1 open of 1 →

Execution Bandwidth at Hollifern Property Software: workload persistently ahead of what teams can absorb

Low

Why it matters: Early and above the noise floor. Worth knowing about; not yet worth disrupting the plan for.
What changed: Escalation opened — theme first surfaced above the noise floor. (6 weeks open)
Next step: A board direction covers this. Review tracked actions for progress.

View escalation history

EmergingLowOpenExecution bandwidthtriggered Jul 2, 2026

Signal confidence for a execution bandwidth theme at Hollifern Property Software stands at 55 against a program threshold of 75, reported independently by 17 participants across 4 functions. The pattern is consistent with a known exposure at this company — renewal concentration in a single quarter of the year — which the investment thesis assumes stays contained. Signal will confirm over the coming weeks whether confidence continues to climb.

Beacon lifecycle

Appearing — low coverage, not yet corroborated.

Emerging

Developing

Material

Urgent

Stabilizing

Resolved

Opened as Emerging
auto
Escalation opened — theme first surfaced above the noise floor.
Jun 11

What Signal observed

Confidence for the execution bandwidth theme reached 55 against a threshold of 75, sustained across 6 weeks with reporting from 4 distinct functions (Executive, Engineering, Sales, Customer Success).

Interventions

2/3 complete · 1 in progress

#1

Move reporting-module remediation out of the renewal quarter

The technical debt is real and will be found in diligence, but it need not be repaid in the quarter that produces the retention number.

Owner: CTODone when: Remediation rescheduled outside the renewal window.

Complete

#2

Add contract engineering capacity for the diligence workstream

Rather than reassigning the team that supports renewals.

Owner: CFODone when: Contract capacity engaged and diligence workstream staffed independently.

Complete

#3

Re-check the bandwidth theme four weeks after both changes land

Confidence has fallen since the changes. Signal reports the movement and the sequence; it does not assert that one caused the other, and the four-week re-check is what would distinguish a seasonal peak from a structural constraint.

Owner: CEODone when: Four-week re-check reported; theme confirmed falling or escalation reopened.

In progress

Organizational radar

all 8 themes scored

0

Escalated

2

Developing

Leadership Direction Clarity, Execution Bandwidth

6

Quiet

View all eight themes

Organizational radar

Hollifern Property Software across the eight themes

Every company is scored on the same eight themes, shaded against this program's own escalation threshold — so a quiet row means quiet, not unmeasured.

No signal

Weak

Developing

Escalated

Company

Direction

Bandwidth

Comms

Alignment

Capacity

Talent

Friction

External

Hollifern Property SoftwareExit Readiness Monitor

46

55

·

6

·

32

9

·

Confidence = unique reporters of a theme ÷ active participants over the rolling 4-week window. A cell turns red once it crosses its company's escalation threshold.

Board response

2 of 3 tracked actions complete

1 board direction published for Hollifern Property Software, with 3 tracked actions against it.

“Hollifern put diligence preparation and its heaviest renewal quarter through the same small engineering team.”

View direction and recommendations →

sale preparation · held since November 2021 · Charlotte, NC

Company context

Employees: 340
Signal seats: 38; 11% enrolled
Revenue: $61M ARR
EBITDA margin: 23–26%

Investment thesis

Held five years with net revenue retention above 110%; positioned for a 2027 sponsor-to-sponsor process.

Known exposures

·Renewal concentration in a single quarter of the year
·Technical debt in the reporting module surfaced during vendor diligence prep

Organizational radar

Hollifern Property Software across the eight themes

Every company is scored on the same eight themes, shaded against this program's own escalation threshold — so a quiet row means quiet, not unmeasured.

No signal

Weak

Developing

Escalated

Company

Direction

Bandwidth

Comms

Alignment

Capacity

Talent

Friction

External

Hollifern Property SoftwareExit Readiness Monitor

46

55

·

6

·

32

9

·

Confidence = unique reporters of a theme ÷ active participants over the rolling 4-week window. A cell turns red once it crosses its company's escalation threshold.

Execution Bandwidth

DevelopingRisk55 / 75↑ Rising10 consecutive weeks+7 reporters vs prior window

Confidence

55

/ 75 threshold

Independent participants

17

reporting this theme

Functions

6

distinct

73% to thresholdFirst reported May 2026

Active Beacon escalation

Low

Jump to escalation

Reported by 17 independent participants across 6 functions, persistent for 10 weeks and rising.

How this signal was validated

Signal validation

Why this reads as a signal — and what kind

Signal assessment

67

Coverage

How much of the org is heard

55

Materiality

How much it matters

71

Urgency

How soon to act

Kept separate by design — a signal can be low-confidence yet high-materiality, or well-covered yet not urgent.

Why we trust this

Recurrence100

Repeats week on week

Reach86

Cross-functional breadth

Persistence100

Consecutive-week longevity

Specificity55

Decisiveness of reports

Consistency60

Agreement among reporters

Materiality55

Reported impact magnitude

Independent participants by function

Legal

4reporters · 24%

Customer Success

3reporters · 18%

Executive

3reporters · 18%

Sales

3reporters · 18%

Other functions (2)

4reporters · 24%

Some functions are combined to protect participant anonymity.

Persistence — last 12 weeks

W22

W23

W24

W25

W26

W27

W28

W29

W30

W31

W32

W33

Theme reported this week

Not reported

Leadership Direction Clarity

DevelopingRisk46 / 75→ Stable8 consecutive weeks

Confidence

46

/ 75 threshold

Independent participants

14

reporting this theme

Functions

5

distinct

61% to thresholdFirst reported May 2026

Reported by 14 independent participants across 5 functions, persistent for 8 weeks.

How this signal was validated

Signal validation

Why this reads as a signal — and what kind

Signal assessment

55

Coverage

How much of the org is heard

55

Materiality

How much it matters

57

Urgency

How soon to act

Kept separate by design — a signal can be low-confidence yet high-materiality, or well-covered yet not urgent.

Why we trust this

Recurrence100

Repeats week on week

Reach71

Cross-functional breadth

Persistence100

Consecutive-week longevity

Specificity55

Decisiveness of reports

Consistency60

Agreement among reporters

Materiality55

Reported impact magnitude

Independent participants by function

Customer Success

4reporters · 29%

Legal

4reporters · 29%

Executive

3reporters · 21%

Other functions (2)

3reporters · 21%

Some functions are combined to protect participant anonymity.

Persistence — last 12 weeks

W22

W23

W24

W25

W26

W27

W28

W29

W30

W31

W32

W33

Theme reported this week

Not reported

Talent & Team Stability

Weak SignalStrength32 / 75↓ Falling6 consecutive weeks-2 reporters vs prior window

Confidence

32

/ 75 threshold

Independent participants

10

reporting this theme

Functions

6

distinct

43% to thresholdFirst reported May 2026

Reported by 10 independent participants across 6 functions, persistent for 6 weeks and easing.

How this signal was validated

Signal validation

Why this reads as a signal — and what kind

Signal assessment

54

Coverage

How much of the org is heard

55

Materiality

How much it matters

46

Urgency

How soon to act

Kept separate by design — a signal can be low-confidence yet high-materiality, or well-covered yet not urgent.

Why we trust this

Recurrence100

Repeats week on week

Reach86

Cross-functional breadth

Persistence100

Consecutive-week longevity

Specificity55

Decisiveness of reports

Consistency60

Agreement among reporters

Materiality55

Reported impact magnitude

Independent participants by function

Customer Success

3reporters · 30%

Other functions (5)

7reporters · 70%

Some functions are combined to protect participant anonymity.

Persistence — last 12 weeks

W22

W23

W24

W25

W26

W27

W28

W29

W30

W31

W32

W33

Theme reported this week

Not reported

EmergingLowOpenExecution bandwidthtriggered Jul 2, 2026

Execution Bandwidth at Hollifern Property Software: workload persistently ahead of what teams can absorb

Signal confidence for a execution bandwidth theme at Hollifern Property Software stands at 55 against a program threshold of 75, reported independently by 17 participants across 4 functions. The pattern is consistent with a known exposure at this company — renewal concentration in a single quarter of the year — which the investment thesis assumes stays contained. Signal will confirm over the coming weeks whether confidence continues to climb.

Beacon lifecycle

Appearing — low coverage, not yet corroborated.

Emerging

Developing

Material

Urgent

Stabilizing

Resolved

Opened as Emerging
auto
Escalation opened — theme first surfaced above the noise floor.
Jun 11

What Signal observed

Confidence for the execution bandwidth theme reached 55 against a threshold of 75, sustained across 6 weeks with reporting from 4 distinct functions (Executive, Engineering, Sales, Customer Success).

Interventions

2/3 complete · 1 in progress

#1

Move reporting-module remediation out of the renewal quarter

The technical debt is real and will be found in diligence, but it need not be repaid in the quarter that produces the retention number.

Owner: CTODone when: Remediation rescheduled outside the renewal window.

Complete

#2

Add contract engineering capacity for the diligence workstream

Rather than reassigning the team that supports renewals.

Owner: CFODone when: Contract capacity engaged and diligence workstream staffed independently.

Complete

#3

Re-check the bandwidth theme four weeks after both changes land

Confidence has fallen since the changes. Signal reports the movement and the sequence; it does not assert that one caused the other, and the four-week re-check is what would distinguish a seasonal peak from a structural constraint.

Owner: CEODone when: Four-week re-check reported; theme confirmed falling or escalation reopened.

In progress

PublishedAI-assistedJuly 16, 2026

“Hollifern put diligence preparation and its heaviest renewal quarter through the same small engineering team.”

Execution bandwidth on the Hollifern Exit Readiness Monitor reached 55 across five of seven functions in a business with only thirty-eight enrolled seats. On a programme this small, five functions reporting the same theme is close to the whole company saying it at once.

What Signal knows with confidence: the constraint is real and it is recent. It appeared as two things collided — technical debt in the reporting module surfaced during vendor diligence preparation, and the company's renewal concentration in a single quarter of the year.

What Signal does not know: whether the constraint would have resolved on its own. A small company preparing for a process will run hot; that is not by itself a finding. What distinguishes this from ordinary intensity is that a talent stability theme is falling at 32 while bandwidth rises — people are not leaving, they are absorbing.

The materiality is timing rather than severity. Net revenue retention above 110% is the number the 2027 process will be sold on, and it is produced during the renewal quarter by the same customer success and engineering people preparing the diligence file.

Bearing is issuing this at low severity deliberately. The recommended action is a sequencing decision, and sequencing decisions get cheaper the earlier they are made.

Evidence & inference

What Signal knows, kept separate from what it infers.

What Signal knows

Execution bandwidth reached 55 across five of seven functions on a thirty-eight seat programme.
Talent stability is falling at 32 — the team is absorbing the load, not leaving.
The company reports renewal concentration in a single quarter and reporting-module technical debt surfaced during diligence preparation.
The escalation was raised at low severity and has remained in an emerging state.

What Signal infershypothesis

~The collision of diligence preparation with the renewal quarter is the most likely mechanism, because both draw on the same small group.
~The constraint is probably seasonal rather than structural, though four more weeks of telemetry would be needed to say so.

Alternatives not ruled out

Ordinary pre-process intensity that would have subsided without any change.
A single engineering bottleneck being reported across functions that depend on it.
Diligence preparation revealing pre-existing strain rather than creating it.

Decision options

A

Defer remediation out of the renewal quarter and add contract capacity — protects the retention number, adds cost.

B

Hold the plan and monitor — costs nothing, risks the number the process is sold on.

C

Bring the process forward to avoid the renewal quarter entirely — removes the collision, compresses preparation.

Confidence

Signal is confident the constraint is real and cross-functional relative to programme size. It is not confident the constraint is structural. The four-week re-check in recommendation three is the specific test that would settle it.

Recommendations

01

Move reporting-module remediation out of the renewal quarter. The technical debt is real and will be found in diligence, but it does not have to be repaid in the quarter that produces the retention number.

02

Add contract engineering capacity for the diligence workstream specifically, rather than reassigning the team that supports renewals.

03

Re-check the bandwidth theme four weeks after both changes land. If it has not moved, the constraint is structural rather than seasonal and the exit timeline should be revisited.

Interventions

2/3 complete · 1 in progress

#1

Move reporting-module remediation out of the renewal quarter

The technical debt is real and will be found in diligence, but it need not be repaid in the quarter that produces the retention number.

Owner: CTODone when: Remediation rescheduled outside the renewal window.

Complete

#2

Add contract engineering capacity for the diligence workstream

Rather than reassigning the team that supports renewals.

Owner: CFODone when: Contract capacity engaged and diligence workstream staffed independently.

Complete

#3

Re-check the bandwidth theme four weeks after both changes land

Confidence has fallen since the changes. Signal reports the movement and the sequence; it does not assert that one caused the other, and the four-week re-check is what would distinguish a seasonal peak from a structural constraint.

Owner: CEODone when: Four-week re-check reported; theme confirmed falling or escalation reopened.

In progress

Analysis and recommendations from Bearing.

LiveMonitoring 38 participants177 submissions analyzedWatching 7 functionsRunning 12 weeksUpdated moments ago

Participation health

Are invited slots turning into weekly submissions?

31

Invited

active slots

28

Activated

90% of invited

22

Submitting

71% of invited

3 never started · 6 went quiet — re-share their invite links to lift participation.

Weekly history

last 12 weeks

No Signal

Weak Signal

Developing

Escalated

Click any bar to see that week's themes and reporter breakdown

Monitored functions · 7

ExecutiveEngineeringSalesCustomer SuccessMarketingFinanceLegal

Recent changes

06:4220 new submissions received

This weekExecution Bandwidth accelerating

This weekParticipation at 82%

1 week ago12 new submissions received

2 weeks ago11 new submissions received

6 weeks agoBeacon escalation raised — Execution Bandwidth at Hollifern Property Software: workload persistently ahead of what teams can absorb

The other side of the program

Every number above starts as a 60-second weekly check-in inside the company — no account, no name, just a link.

Preview the participant check-in →