An executive assistant in iMessage.
Follow-ups and scheduling consume the gaps between meetings.
Est. deploy 2–4 weeksSee the walkthrough
Executive Assistance · Financial Services
Prepare every advisor meeting from current records.
Advisors switch between systems to build a briefing.
For: Licensed advisors and the team responsible for executive assistance in financial services.
01 · The outcome
What good looks like.
The team has an advisor-reviewed meeting brief, with source evidence and an explicit approval before any external action. Track preparation minutes per meeting against a baseline; do not assume automation improves it.
A connected workflow that uses authorized CRM notes, approved account summaries, and open service tasks to assemble a cited briefing and flag stale balances instead of estimating current values. It produces an advisor-reviewed meeting brief.
Where AI helps, and where a person decides.
AI can assemble a cited briefing and flag stale balances instead of estimating current values. It drafts and organizes; it does not authorize spending, commitments, clinical decisions or customer communication. The licensed advisor verifies the source facts and approves the final action.
Licensed advisor is accountable. People approve customer-facing, sensitive, financial, and legally binding actions.
- Licensed advisor: Capture the source and scope
- Licensed advisor: Review the proposed outcome
- Licensed advisor: Release only the approved version
- Licensed advisor: Check the result and exceptions
A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
02 · The handoffs
How the work moves.
Every handoff has an owner. Select a step to open or close its detail.
Start when: An advisor meeting enters the next-day schedule. Connect only authorized CRM notes, approved account summaries, and open service tasks. The licensed advisor confirms the request is authorized and in scope.
Ready when: The source reference, permissions and accountable owner are recorded.
Use the authorized records to assemble a cited briefing and flag stale balances instead of estimating current values. Preserve the original language alongside the draft and label uncertain fields.
Ready when: Each proposed fact links back to a source, and missing information is visible.
Check an advisor-reviewed meeting brief against the original records and current policy. Correct errors and escalate exceptions to the qualified specialist; do not auto-approve.
Ready when: Licensed advisor has recorded approval or a reason to hold the item.
After explicit approval, save an advisor-reviewed meeting brief in the system of record. Send only approved messages to verified recipients. Record the version and prevent duplicate delivery.
Ready when: The approved record is saved; any delivery is confirmed or placed in the retry queue.
Review preparation minutes per meeting each week, sample completed records for quality, and resolve held items. Change the rules only after reviewing actual errors and staff feedback.
Ready when: Exceptions have owners, the metric has a baseline, and corrective actions are assigned.
Sample record.
$ david run --workflow=finance-meeting-prep
ILLUSTRATIVE RECORD / NOT LIVE CUSTOMER DATA
- Example
- Illustrative only — not a real client record
- Reference
- FINANCE-MEETING-PREP-DEMO-001
- Trigger
- An advisor meeting enters the next-day schedule.
- Owner
- Licensed advisor
- Prepared output
- an advisor-reviewed meeting brief
- Review status
- Awaiting human approval — no external action taken
- Missing information
- Owner to verify source completeness
- Measure
- Preparation minutes per meeting
Start with your tools.
Connect Salesforce, Microsoft 365, Compliance archive through approved APIs or controlled exports. Map record identifiers first; test permissions and field updates in a sandbox. Vendor names describe possible connections, not a guarantee of an available integration or license.
When things go wrong.
- A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
- Use only authorized sources and role-based access. Keep an audit trail of source records, drafts, approvals and delivery status; deduplicate retries.
- If an integration fails, a source is missing or confidence is low, pause the action and assign the original request to the accountable owner.
- For financial or insurance work, a properly licensed professional approves recommendations, coverage, suitability and binding actions. Apply the firm's supervision, retention and advertising rules.
Try this week / no DAVID required
A useful first step.
This week, have your licensed advisor time five examples of this work. Use redacted copies of authorized CRM notes, approved account summaries, and open service tasks to make an advisor-reviewed meeting brief manually, then list which fields required judgment.
What to measure.
- Preparation minutes per meeting
- Minutes of human handling per completed item
- Drafts needing substantive correction
- Exceptions unresolved beyond the agreed review window
Estimate your time back.
20.8
$11,232
03 · More workflows to consider
Related workflows.
Prepare attorneys before the first consult.
Attorneys reread long inquiry threads before meetings.
Est. deploy 4–6 weeksSee the walkthrough
Move reviewed meeting notes into the archive.
Notes and follow-up commitments miss the compliance record.
Est. deploy 4–6 weeksSee the walkthrough
Want this running in your business in 4–6 weeks?
Free 30-minute call. We'll tell you honestly whether AI fits, and where.