S
SALES.AI
Sales for vibe-coding workshops
TodayDashboardClientsDealsCalls
Training
TrainingRole playPlaybook
DC
Founder
Founder
Petalwise Sdn Bhd

Readiness check

Aishah Mohd Yusof · Co-founder/CEO · Retail / E-commerce · SMB · 22 employees

34
of 100
Weak
Industry average: 70
-36 pts vs peers

Summary

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.

3 high-risk areas7 recommended actions

By area

Tooling
32

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.

Named editor/agent stackNone supplied
Org size22 employees
Deal probability10%
CRM health52/100
Practices
28

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.

Engineering contact0 named
AI PR-review evidenceNone supplied

Risks

  • High
    No engineering stakeholder named
    Lead record names only the co-founder/CEO; no engineering lead or platform owner is identified, so workshop fit and follow-up ownership are unassigned.
  • High
    No AI licence or stack inventory
    No Cursor/Claude Code/Copilot licences, MCP servers, IDE rules, or secrets-handling detail appears; Day 1 hands-on exercises cannot be pre-configured.
  • High
    No workflow/guardrail evidence
    No PR-review, testing, code-gen, prompt-hygiene, or agent-guardrail practice is described, so Day 2 applicability is unverified.
  • Medium
    No velocity baseline
    Cycle time, PRs/dev/week, time-to-merge, and deploy frequency are absent; the workshop cannot quantify throughput improvement.
  • Medium
    No outcome baseline
    Defect rate, escaped bugs, time-to-feature, dev satisfaction, and retention are absent; success criteria must be instrumented.
  • Medium
    Founder interest not yet translated to engineer adoption
    Only observable AI signal is a founder post today; no engineer daily/weekly usage or licence utilization data is supplied for the 22-person org.

Next steps

  • Run 4pm founder call to name engineering lead and workshop owner
    P0
    Named engineering sponsor and single owner for baseline and cohort scheduling within 7 days. (~1 wk, eng_lead)
  • Pre-workshop stack and secrets audit
    P0
    Inventory of Cursor/Claude Code/Copilot licences, MCP servers, IDE rules, and secrets-handling gaps; Day 1 lab pre-configured for every attendee. (~2 wk, platform)
  • Instrument 30-day readiness baseline
    P0
    Dashboard of daily/weekly AI usage, licence utilization, cycle time, PRs/dev/week, time-to-merge, deploy frequency, defect/escaped-bug rate; baseline ready before Day 1. (~3 wk, platform)
  • Deliver Day 1 shared-rules and prompt-fluency lab
    P1
    ≥80% of attendees commit one shared Cursor/Claude Code rule and one reusable prompt template to the team rules repo by end of Day 1. (~2 wk, individual_devs)
  • Deliver Day 2 AI-PR guardrail clinic
    P1
    One repo enforces AI-generated-code PR checklist, CODEOWNERS, test gate, and blast-radius policy within 30 days; measured by PR template adoption. (~2 wk, eng_lead)
  • 30-day adoption and guardrail follow-up
Test/guardrail evidenceNone supplied
Product listEmpty
Culture
55

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.

Founder AI signal1 post today
Engineering leadership postureNot supplied
Workflow-change willingnessNot supplied
Blast-radius toleranceNot supplied
Velocity
30

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.

Cycle timeNot supplied
PRs/dev/weekNot supplied
Time-to-mergeNot supplied
Deploy frequencyNot supplied
Deal stageNew lead (10%)
Adoption
25

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.

Daily/weekly AI usageNot supplied
Licence utilizationNot supplied
Sub-team distributionNot supplied
Engineering headcountNot supplied
Org employees22
Outcomes
30

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.

Defect rateNot supplied
Escaped bugsNot supplied
Time-to-featureNot supplied
Dev satisfaction/retentionNot supplied
ProductsNone listed
P1
Weekly active AI tool usage and PR cycle time reviewed with managers; target ≥70% weekly active usage and 10% cycle-time reduction by day 90. (~4 wk, managers)

Proposals

No proposals yet. The AI writes one from the readiness check.