Ibrahim Hassan · Head of Tech · IIoT / Manufacturing · SMB · 65 employees
The supplied record is thin: Padu Cipta is a 65-person IIoT/manufacturing SMB at Discovery, with one Head of Tech contact, a 40% deal probability, and only a pre-shared workshop outline. The two biggest readiness gaps are unverified AI tooling and no observable workflow/adoption baseline, so neither Day 1 tooling nor Day 2 workflow integration can be assumed to fit. The highest-leverage 90-day move is a 2-day pilot workshop with one squad, paired with a pre/post baseline of licence utilisation, daily AI usage, cycle time, and escaped defects, then a 30-day PR-review guardrail pilot.
The record names only a Head of Tech contact and a pre-shared workshop outline; it supplies no Cursor/Claude Code/Copilot licences, MCP servers, IDE rules, or secrets-handling detail. Tooling scores 55 because Day 1 can probably be scoped, but the stack fit is unverified.
No PR-review, testing, prompt-hygiene, code-gen, or agent-guardrail practice is described in the supplied data. Practices score 45 because Day 2 applicability is unconfirmed, making workflow integration the clearest critical gap.
The record shows a single Head of Tech contact, a 40% deal probability, and a deal not marked hot. Culture scores 60 because leadership interest is implied by the pre-shared outline, but no broader engineering leadership posture or blast-radius tolerance is observable.
The supplied context gives employee count and deal stage but zero engineering throughput data. Velocity scores 50 because there is no cycle-time, PRs/dev/week, time-to-merge, or deploy-frequency baseline to size the workshop gap against.
The record contains no daily/weekly AI usage, licence utilisation, or sub-team distribution data. Adoption scores 40 because the absence of any usage baseline makes it impossible to confirm whether Day 1 will reach a meaningful share of the 65 employees.
No defect-rate, escaped-bug, time-to-feature, satisfaction, or retention data is present in the supplied context. Outcomes score 55 because quality is unmeasured, so the workshop cannot yet target a quantified output gap.
No proposals yet. The AI writes one from the readiness check.