AI Weekly Malaysia

OpenAI published a customer story where startup Model ML uses GPT-5.6 Sol to generate editable PowerPoint and Excel files for finance workflows, reporting 21% fewer tokens per deck than Fable 5, 36% fewer tokens per Excel workbook than Opus 5, and a tearsheet build time drop from ~1 hour to 5 minutes.

Why: This is a vendor case study, not independent benchmarking. The only actionable signal is that GPT-5.6 Sol is being positioned for structured-document generation (PowerPoint/Excel) with token-efficiency claims against named competitors—founders building finance or reporting automation could test those specific token-cost claims in their own pipelines before committing.

OpenAI published a customer story where Zapier's enterprise marketing team, led by Angela Ferrante, uses ChatGPT Work to automate funnel optimization, QA thousands of inbound leads per month, and build campaign assets. The story claims '7+ figures of pipeline value' and reduced manual effort in lead processing.

Why: This is a vendor-published case study with no technical detail on how the automation was built, what prompts or workflows were used, or what the failure modes were. Builders should not change anything based on this; it is marketing for ChatGPT Work enterprise adoption. The only actionable signal is that Zapier found enough value in autonomous lead QA to report 7-figure pipeline impact, which may justify a pilot for SaaS founders with high inbound lead volumes and drop-off problems.

OpenAI published a customer story describing how RingCentral rolled out ChatGPT Work and Codex company-wide via an 'AI-Native Challenge' sponsored by the Office of the CEO, aiming to let non-engineering staff build product features and infrastructure. RingCentral reports $2.6B annual revenue and claims AI tools compress the distance between idea and shipped feature across its Agentic Voice AI portfolio (AIR, AVA, ACE).

Why: This is a vendor case study with no technical detail, metrics, or lessons beyond 'give everyone AI tools.' There is nothing concrete to copy or decide on—no architecture, no cost data, no failure modes. Builders should not change anything based on this alone.