Suresh Kumar Pillai · COO · Property / Marketplace · SMB · 80 employees
PropSimplify is a 51/100: the two biggest gaps are the absence of any evidenced AI editor/agent stack and the absence of any engineering throughput or AI-in-PR telemetry in the deal record. The CRM holds commercials (RM 77,000, negotiation stage, COO verbal today) and one decisive constraint — a cost-sensitive CEO — but no licence count, repo host, PR tool or cycle-time baseline. That means Day 1 hands-on would run on borrowed seats and Day 2 PR-review and agent-guardrail labs would have nothing to anchor to. The highest-leverage 90-day move is a single sequenced play: run a 30-minute stack audit this week, capture a pre-cohort baseline (cycle time, PRs/dev/week, deploy frequency), then deliver cohort 1 with a shared CLAUDE.md/cursorrules plus a CEO-facing ROI one-pager that converts licence spend into reclaimed cycle time before Friday 9:00am.
No licence count, editor standard, MCP server or secrets-handling posture appears anywhere in the deal record for this 80-person org — the only tooling signal is the 'Cost-sensitive CEO' tag, which caps per-seat spend tolerance. Day 1 assumes Claude Code/Cursor seats and MCP wiring already exist, so the score lands at 48 until a stack audit confirms what is actually installed.
There is zero evidence AI touches PR review, testing or code-gen: the account has no products list and no engineering workflow data, so Day 2's agentic-dev and guardrail modules cannot be shown as an upgrade to an existing practice. At 42, Day 2 is currently greenfield teaching rather than tuning, which is the single biggest reason the workshop may feel generic to their team.
Leadership intent is the strongest signal in the account: the COO personally confirmed verbally today and a concrete next step is booked for Friday 9:00am, which reads as real sponsorship rather than curiosity. It stays at 66 rather than healthy because the 'Cost-sensitive CEO' tag means blast-radius tolerance and workflow-change appetite are untested above the COO — approval for autonomous agents has not been probed.
No throughput baseline exists in the record — no cycle time, no PRs/dev/week, no time-to-merge, no deploy frequency. The score sits at 52 because the workshop's entire value narrative is 'close the gap', and right now the gap is unquantified for a property-marketplace SMB where release cadence is typically ad hoc. Without a pre-cohort snapshot, impact cannot be proven at the 30-day mark.
Adoption cannot be measured from this record — no licence utilisation, no daily/weekly usage split, no distribution across sub-teams. The one usable signal is headcount: 80 employees against a ~35-participant cohort cap means full engineering coverage needs two or more cohorts at RM 3,500 per head, a multiplication the cost-sensitive CEO will notice immediately.
The only quality-adjacent number on the account is CRM health 70, which scores the sales relationship, not engineering output — there is no defect rate, escaped-bug count, time-to-feature or dev satisfaction data. At 52 the dimension is effectively unmeasured, so any Day 2 claim about defect reduction would be unfalsifiable to this buyer and is the weakest part of the pitch.