AI Launch Profile
Deck AI chief of staff with a delegated inbox
Deck launched an AI chief of staff with its own inbox, letting a user copy selected email threads, assign follow-up work, and schedule recurring routines without granting full inbox access.
At a glance
Launch Snapshot
- Company
- Deck
- Launch date
- July 21, 2026
- Launch type
- New Product
- Category
- AI Agents, AI Productivity Tools
- Audience
- Founders, Small Business Owners
- Pricing
- The official pricing table lists Free at $0 with up to 20 messages per day and one email address, Pro at $29.99 per month, and custom Enterprise pricing. A 14-day Pro trial is offered without a card.
- Free plan
- Yes
- API
- Not publicly confirmed
- Open weights/source
- Not publicly confirmed
Launch Context
Use these links to move from this record into the broader Launch Intelligence database.
Verification & Sources
- Status
- Verified
- Source links
- 3
- Freshness
- Verified July 25, 2026
- Last verified
- July 25, 2026
- Last updated
- July 25, 2026
Key source checks
Suggest a correction
Creator Coverage Next Steps
This launch has signals that may support demos, reviews, creator education, founder storytelling, or practical product explainers.
Launching an AI product that needs clear demos, creator education, and buyer trust? Sponsor a Kingy AI video or launch feature.
Kingy AI Take
Deck addresses a concrete need: Giving an assistant its own inbox offers a narrower permission model than granting access to an entire mailbox, while still placing the agent inside a familiar workflow used for delegated work. The main limitation is this: Forwarded messages, documents, and calendar context may contain sensitive information even without full-mailbox access.
Who it is for
Small Business Owners, Founders
What feels promising
Giving an assistant its own inbox offers a narrower permission model than granting access to an entire mailbox, while still placing the agent inside a familiar workflow used for delegated work.
What feels unproven
Forwarded messages, documents, and calendar context may contain sensitive information even without full-mailbox access. Users should review permissions and privacy terms, verify drafts before sending, and test whether reminders and routines behave reliably for their workflow.
Source-backed record