Let AI Share the Life Admin: “One Assistant per Job” or “One for Everything”?

On this page

What Happened

@RampCapitalLLC shared a lineup of 15 assistants, each handling one job1: a gift assistant tracks a budget for each friend and relative and sends a ping when it spots a good price; a travel assistant compares flights and rental cars; a maintenance assistant digs through emails and receipts to build the car’s service history; a weekend assistant lists nearby events before each weekend, with a separate list for the kids; and one is dedicated to reading emails from teachers, adding events to the calendar, and sending a reminder every evening about the next day.

Big tech has followed. Google’s family agent lets multiple family members share calendars, lists, and a daily summary14, and Meta, OpenAI, and startups have all launched personal agents that can make reservations and change itineraries11.

Common Approaches

1. One assistant per job. Each assistant owns a single topic1. Splitting things this way keeps instructions short and debugging easy, and turning one off doesn’t affect the others. The initial setup period nearly used up the entire allowance2.

2. One coordinator plus a daily briefing. The alternative is one assistant connected to email, calendar, and to-dos that delivers a daily summary; a leaner version does only a daily news digest plus a weekly competitor report4. A family version can be broken into a few jobs—family calendar, weekly meal plan, school emails, activity planning, restocking, sign-up deadlines, and a Sunday family briefing—starting with just one5. Each family member can also message the same assistant to add events, reserve library books, or flag who needs a ride, with the youngest kid messaging from an iPad23.

3. Capture information first, automate later. Complexity has to prove it’s worth it: start by dropping to-dos in via a phone shortcut and let the AI learn your preferences by observing6. After setting up assistants for a group of non-technical users such as lawyers and business owners, voice input did the most to boost usage, and the fewer the steps, the more reliable the workflow12. A comparison of several leading memory architectures concluded that personal use doesn’t need a complex memory system—Markdown files are enough15.

4. Prepare, but don’t pull the trigger. For reservations, quotes, and payments, the assistant only goes as far as “organized and waiting for your confirmation.” In one example from an independent garage-door installation business, the phone voice assistant only confirms the service area, collects details, and quotes a pre-approved price range—it doesn’t book jobs directly13.

Our Recommendations

  • Start with the one or two most annoying jobs, run them for two weeks, then add more.
  • Stop and ask a human before paying, signing anything, or messaging anyone outside.
  • Store data somewhere you can see it (a spreadsheet or document), not only in the chat.

Disagreements

  • Is the convenience worth the privacy? When a family assistant was open-sourced, the question that drew the most attention was security: it can access the whole family’s locations, the entire inbox, the kids’ photos, and classmates’ schedules7. A family trip planned with a personal agent came to a halt at the point of entering a credit card, because it wasn’t clear where the data would be stored9. Terms of service are a problem too: an agent can accept third-party terms on your behalf that bind you, the provider’s liability is capped at just $100, and if it buys the wrong thing you have to sort it out with the merchant yourself8.
  • Should these chores be handed off at all? Errands like grocery shopping can be kept deliberately, as part of life10; on the other hand, within a single week an agent can hire a gardener, schedule preschool tours, and book restaurants10.
  • One or many? Running several AIs to manage your life may end with needing yet another AI to manage them11.
  • How much does it cost? “How much does running all of this cost per month?” is the most practical question3.

What to Do

  1. Write down the 3 most annoying jobs of your week, and pick just 1 to start.
  2. Use the prompt below to create an assistant, spelling out what it’s responsible for, where its data lives, and when it must ask you.
  3. Connect only the accounts this job needs. An assistant that reads school emails doesn’t need your bank account.
  4. Put fixed-time jobs (such as the weekend events list) on a schedule.
  5. Check after two weeks: Does it really save time? Has it made mistakes? Turn off anything that isn’t useful.

General-Purpose Prompt

Single-topic life assistant · 11 lines
You are my [topic, e.g., gifts / family calendar / car maintenance] assistant.
Scope: [one-sentence description]. For anything outside this scope, just let me know; don't handle it yourself.
Sources: [email label / calendar / the list I paste to you].
Where to record: keep all records in [spreadsheet or document name], and date every update.
Recurring task: every [Thursday evening], put together [what you'll give me], at most [10] items, with source links.

Rules:
- Before ordering, paying, entering payment details, or accepting any terms, stop and show me the total price and the cancellation/change policy.
- Never message or email anyone without asking me first.
- Mark uncertain information as "unconfirmed"; don't guess.
- At the end of each run, tell me: what you did, what you're still waiting on, and what might go wrong.

Replace the [ ] parts with your own details

How Tools Differ

  • Can it run on a schedule? Grok Bot’s Routines can be triggered on a schedule or by incoming email, webhooks, or Slack messages, and every run consumes usage17; Claude Cowork also has scheduled tasks, and new tasks on Pro and Max run in the cloud20. For tools without scheduling, paste the prompt manually at a fixed time.
  • How many accounts can it connect? Grok Bot’s Gmail plugin connects one mailbox at a time and can read, draft, send, and label18. Handle family and work mailboxes separately.
  • One or many? Each Grok Bot bot has separate memory21, and several bots can be put in a group chat19, which suits “one per job”; tools with only a single conversation are better suited to “one coordinator.”
  • Plans: Grok Bot is included in X Subscription’s Premium, Super, and Ultra, but not Free or Plus16; Cowork is available only on paid plans22.

References

  1. @RampCapitalLLC: The original post on 15 life assistants ↩ a b
  2. @RampCapitalLLC reply: Nearly used up the allowance during first-week setup ↩
  3. @CheeseCapitalCo: Asks what it costs per month ↩
  4. @gacjr1: Daily news digest and weekly competitor report ↩
  5. @Michael_Fenech_: Seven jobs for the family version ↩
  6. Hilary Gridley (YouTube): An anti-system approach to life management ↩
  7. r/ClaudeAI: Open-source family assistant and security criticism ↩
  8. Instinct tutorial video (YouTube): Comments summarizing the terms of service ↩
  9. Erica Layer (LinkedIn): Privacy concerns from planning a family trip with a personal agent ↩
  10. LinkedIn post (ariellerjackson): Wanting to keep some chores; comments list a week of errands ↩ a b
  11. Will McTighe (LinkedIn): Comparing three personal agents; comment: “need a fourth AI” ↩ a b
  12. r/n8n: Lessons from setting up assistants for a dozen non-technical users ↩
  13. r/AI_Agents: Voice assistant prepares but doesn’t book jobs directly ↩
  14. Joseph Michael (LinkedIn): Google’s family agent, up to six family members ↩
  15. r/AI_Agents: Markdown files are enough for personal use ↩
  16. Grok Bot Help: Plans ↩
  17. Grok Bot Help: Routines ↩
  18. Grok Bot Help: Connect plugins ↩
  19. Grok Bot Help: Group chats ↩
  20. Claude Help: Use Cowork on web, desktop, and mobile ↩
  21. Grok Bot docs ↩
  22. Claude Help: Get started with Cowork ↩
  23. @m1kehouston reply: The whole family talks to one assistant via iMessage, kids on an iPad ↩