For larger text, use “Read or print.”
For larger text, use “Read or print.”
Product updates
This is the agent’s deck as it came out: 6 slides, unedited. The company and numbers are fictional; the request was written the way people send them, with the notes pasted in.
“my bi-weekly update to my director is due tomorrow and it's bad news.”
ugh. my bi-weekly update to my director is due tomorrow and it's bad news. the new scheduling calendar launch slipped and beta usage is below what we promised. i don't know how to frame this without it sounding like excuses. help Notes: - We committed to general availability of the scheduling calendar on Sept 15. New date: Oct 13 at the earliest. - Why: in beta, sync with Google and Outlook calendars double-books about 3% of appointments. We won't launch until it's under 0.5%. Google sync is now at 0.4%; Outlook is still at 3%. - Beta: 40 customer accounts. We promised 60% would use it weekly by the end of beta. Actual: 35% (14 of 40). - Accounts using it weekly book 22% more jobs than before they had it (only 14 accounts and 6 weeks of data). - Of the 26 accounts not using it, 11 told customer success they're waiting for the Outlook fix. We haven't heard from the other 15. - Sales has promised the calendar to 2 prospects closing in October, about $95k ARR combined. Don't know which calendar they use. - Options I see: (a) launch Oct 13 with Google sync only, Outlook when it's fixed; (b) hold everything until both work, probably early November. - I lean (a) but haven't asked sales yet.
In our blind test, the reviewer would send this deck as it is and flagged nothing. Guide to decision and update decks.
In Claude Code or Codex, install the free skill instead: npx skills add arunai30/super-document-skills --agent claude-code --skill create-html-presentation --copy