SHI
Stakeholder Health Index — Sarath MS
A tool I built to solve a real problem
The signals
were always
there. We just
never had a
system to
read them.
SHI reads your inbox every week, scores relationship signals across four stakeholder hierarchies, and generates a Monday briefing — one card, one action at a time.
20
Signals scored
per person
How it works — hover each card
01
Set up once.
Tap or hover →
Setup
Add projects and stakeholders. Each person gets a hierarchy — Client, Execution team, PM chain, or BD — which determines which signals matter and how much weight they carry.
02
Paste everything. AI sorts it.
Tap or hover →
Weekly scan
One bulk dump — client emails, Slack, WhatsApp. Any source, any order, mixed projects. Claude maps each thread to the right stakeholder and scores their signals automatically.
03
One card. One action. Done.
Tap or hover →
Monday briefing
A card deck of the week's most urgent signals — prioritised by severity. Each card names the situation, explains why it matters, and gives one specific action. Under 5 minutes.
04
12 weeks of relationship health. At a glance.
Tap or hover →
Sentiment timeline
Every project has a 12-week health trend line. CSAT scores sit on the same chart. The gap between predicted and actual is where the real PM development conversations begin.
05
The CSAT told you. The signals told you first.
Tap or hover →
CSAT correlation
A CSAT 18 points below signals is not a surprise — it is a question: what were we missing in the check-ins? That question drives better PM practice faster than any annual review.
06
Built on real patterns from real projects.
Tap or hover →
Why it exists
Every alert rule was extracted from a real email thread — HOABL, Nippon India, Geojit, Prismforce. The patterns were already there. This system makes them visible before they become formal problems.
The signal architecture
Four stakeholder hierarchies
Each level carries a different scoring weight
Client (External)
CXO 3×
Decision-maker 2×
Approval 1.5×
SPOC 1×
End user 0.8×
Execution team (Internal)
Manager 2×
Lead 1.8×
Assoc Lead 1.5×
Senior 1.2×
Junior 0.8×
PM chain (Internal)
DM 2×
Program PM 1.8×
Senior PM 1.5×
PM 1.2×
Junior PM 1×
Business / BD (Internal)
BD Director 2×
Account Mgr 1.5×
BD Mgr 1.2×
Sales 1×
Five signal categories
Adapted per hierarchy type
Engagement
Response time
Meeting presence
Proactive outreach
Agenda ownership
Trust
Candour
Feedback quality
Information sharing
Constructive challenge
Decision health
Approval speed
Right person deciding
Decision stability
Risk signals
Escalation direction
Tone shift
Third-party introduction
Momentum
Delivery pace
Scope stability
Energy level
Signals the tool reads that most PMs feel but cannot name
High engagement,
low trust.
They attend every call. They approve everything. Trust signals collapsed three weeks ago. They will escalate at the end — and it will feel sudden.
The tech lead
is now the PM.
The client started directing your tech lead directly. The PM is being cc'd, not leading. Every day this continues, the narrative gets written without them.
Six weeks of
uniform green.
No real project runs perfectly green for six weeks. That is not health — that is safe reporting. The tool flags it and asks for a risk conversation.
Reading the PM index
One project drifting or all of them?
The PM index is a weighted average across all active projects — external and internal stakeholders combined. What it reveals is different from what it measures. A PM with a score of 58 across three projects is in a different situation from a PM with a score of 58 on one project and 80 on the others. The pattern matters more than the number.
One project drifting
Project problem. Investigate that project's specific signals. The pattern is local.
Multiple projects drifting
A pattern forming. Look for common signals across projects — same category, same stakeholder type.
All projects drifting
PM development signal. This is about approach, not individual projects. The pattern is in the PM, not the work.
The CSAT connection
CSAT vs signals
Which PMs predict their CSATs accurately — and which ones miss by 18 points every quarter?
That gap is a PM development conversation, not a delivery conversation. SHI makes it visible, measurable, and tied to something the client already scored.
When signals match
+2
Points gap when the PM is reading the relationship correctly week to week.
When signals miss
−18
Points below what signals showed. The client experienced something the PM did not catch.
Try the tool
Set up your projects, run your first inbox scan, and see your Monday briefing in under 10 minutes.
Open SHI →