Aishah Mohd Yusof · Co-founder/CEO · Retail / E-commerce · SMB · 22 employees
Petalwise's biggest readiness gaps are visibility and workflow evidence: the lead record shows a 22-person SMB with a founder-led AI-in-retail post today, but no engineering contact, no product/tech stack, no AI licence or usage data, and no PR/testing/guardrail signal. That makes Day 1 stack fit and Day 2 workflow integration unverifiable. The highest-leverage 90-day move is to use the 4pm founder call to identify the engineering lead and run a pre-workshop baseline audit (licences, MCP/IDE rules, secrets, daily AI usage, cycle time, PR/deploy frequency, defect/escaped-bug rate), then deliver one 2-day cohort sized to the 22-person org and a 30-day adoption/guardrail follow-up. Measure success as named engineering owner, baseline dashboard live, ≥80% of attendees using shared Cursor/Claude Code rules, and one repo enforcing AI-PR guardrails within 90 days.
No editor/agent stack is named in the lead record; the only firm facts are 22 employees and a founder-led retail/e-commerce deal at 10% probability. With no Cursor/Claude Code/Copilot licences, MCP servers, IDE rules, or secrets-handling detail supplied, Day 1 cannot be assumed to land without a pre-workshop stack audit; score stays critical.
The record contains no engineering contact, no product list, and no evidence of AI in PR review, testing, code-gen, prompt hygiene, or agent guardrails. Because Day 2 depends on existing AI-assisted workflows to retrofit, the absence of any observable practice signal makes the dimension critical rather than merely unknown.
The one positive signal is the co-founder/CEO posting about AI in retail today, which suggests top-down curiosity; however there is no engineering-leadership posture, no stated willingness to change workflows, and no blast-radius tolerance for autonomous agents. That founder-only signal supports at_risk, not healthy.
No cycle time, PRs/dev/week, time-to-merge, or deploy-frequency baseline is supplied; the lead is still at 10% probability with a 4pm next step. Without a throughput baseline the workshop cannot quantify the gap it closes, so velocity scores critical.
No daily/weekly AI usage, licence utilization, or sub-team distribution is disclosed for the 22-person org. The only activity is a founder-level AI-in-retail post today, not engineer usage, so adoption cannot be scored above critical.
No defect rate, escaped bugs, time-to-feature, dev satisfaction, or retention data appears in the lead record. With no product list and no engineering contact, there is no observable output-quality baseline; outcomes remain critical until measured.
No proposals yet. The AI writes one from the readiness check.