Produce a unit economics model: COGS/BOM, cloud cost per user, CAC/LTV by region, and budget guardrails with variance alerts.
Draft role scorecards (frontend, backend, firmware, test) with skills relevant to TW/US stacks, bilingual collaboration, and sample structured interviews.
Create TW/US-aligned OKRs for Marketing, Product, Eng, and Ops. Include weekly check-in format and red/amber recovery plans.
Define a structured handoff from Sales to CS: discovery doc, admin setup, kickoff agenda, health scores, and expansion play triggers by region.
Write a runbook: naming conventions, asset library, translation workflow, approval matrix, and backup owners for TW/US holidays.
Provide vendor scorecards for agencies/factories/cloud: quality, cost, delivery, responsiveness, and security. Include escalation ladders.
Generate a 20-test backlog split by TW/US with hypotheses for landing pages, paywalls, and creative. Include sample size calculator and guardrails.
Create SLO targets per region, on-call rotations spanning TW/US, incident severity ladder, customer comms templates, and postmortem format.
Set up a cross-functional product council with TW/US representation: agenda, decision log, RICE/ICE scoring, and roadmap comms pack.
Define TW/US beta pilots: eligibility, NDAs, telemetry, survey cadence, and success criteria. Include de-risking plan for public GA.
Provide accessibility guidelines: WCAG for software, color/contrast, captions; hardware tactile feedback and labeling; cultural sensitivity notes for EN/zh-TW.
Create a research plan: recruit TW and US panels, consent forms, bilingual scripts, and synthesis templates. Include incentives and privacy handling.
