← Back to the atlas
No. 002ProposalSoftware and AI

AI Personal Assistant

Source

The idea

Build an assistant with durable knowledge of a user's work and preferences that can act on email, calendar, and recurring workflows with approval.

Why this is interesting

  • A useful assistant has to retain context and complete recurring work across tools, rather than answer isolated prompts.
  • Permission design is part of the product: users need to understand what the assistant can read, what it can change and when approval is required.
  • A narrow role or workflow may create a stronger starting point than a universal assistant because quality and trust are easier to measure.

Possible starting points

01

Founder operations assistant

Coordinate inbox, calendar, follow-ups and recurring operating tasks with explicit approval boundaries.

02

Role-specific assistant

Own a bounded workflow for sales, recruiting, finance or customer operations.

03

Team memory and follow-through

Turn decisions across meetings and tools into assigned, traceable actions.

Questions to answer

  1. Which repeated workflow is painful enough to delegate but bounded enough to verify?
  2. What should always require approval before the assistant acts?
  3. How will a user inspect, correct and delete the assistant’s retained knowledge?

Useful resources