The problem
An assistant needs enough context to sort messages, prepare a useful meeting brief and suggest a reply. Reading that context and taking an action are different responsibilities.
The product challenge was to make preparation useful while preserving a deliberate decision at the moment a draft becomes an action.
My contribution
- I defined the personal assistant and CRM product: cross-channel triage, meeting preparation, draft replies and a native iOS front door.
- I chose a Reader / Planner / Executor architecture with device-signed approvals. Preparing a suggested action does not, by itself, authorize the executor to carry it out.
- I directed the TypeScript and SwiftUI implementation and independent review of changes, with internal TestFlight builds for the iOS app.
A design decision
Put an explicit approval between a plan and an action
I separated reading and planning from execution. The product requires each action to be approved and signed on the phone before it can proceed.
A person has to take an extra step before an action runs. In exchange, the assistant can help with preparation while the user retains control over what actually happens.
Read the context
Prepare a draft
Approve on the phone
Execute the action
What changed
- Preparation becomes a reviewable action
- Message triage, meeting briefs and reply drafts are part of one product flow, ending in an action the user can inspect before approving.
- A concrete boundary for automation
- The device-approval requirement separates an AI proposal from permission to act. A native iOS interface makes that approval a first-class part of the product.
- A native app in TestFlight
- The iOS app has reached internal TestFlight testing, providing a native interface for the assistant and its approval workflow.
Interactive walkthrough · mock data
A draft is a proposal until you approve it
Walk through a fictional reply. Edit the sample draft, review the proposed action and simulate phone approval. The demo stays in this browser and sends no messages.
01 / Incoming request
Fictional incoming message
“Can we move our design review to Thursday at 14:00?”
Project teammate · teammate@example.test
This local walkthrough simulates approval. The product requires a device-signed approval on the phone. The draft and recipient here are fictional.