← Back to library

Pick your first agent job with a one-day friction audit

James Camp (@JamesonCamp), a founder who has spent heavily on AI tools, advises starting agents with a one-day friction log. Write down every repetitive or draining task, sort it into data entry, research or communication, and score how often it happens and how much you dislike it. Hand the top scorer to one bot with one job for a week.

  • OutcomeFor one workday, log each task that irritates you, sort by type, score by frequency and dread, and hand the top one to a single narrow bot.
  • SetupMinutes
  • LevelStarter
  • CreditJames Camp πŸ› ,πŸ›  (@JamesonCamp)
View original
Works with
Grok Bot

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You are new to agents
  • You do not know what to automate
  • You want a quick win

Not for: Teams with a mapped process already; Tasks needing judgment calls each time

What do you need, and what do you get?

You need

  • A notebook or note app
  • One workday
  • A bot account

You get

  • Ranked friction list
  • A first bot with one job
  • A one-week review

How does it work, step by step?

  1. Log a dayWrite down every repetitive or annoying task as it happens.
  2. SortPut each into data entry, research or communication.
  3. ScoreRate frequency and how much you dread it.
  4. Hand off oneGive the top item to one narrowly named bot.
  5. Review after a weekWiden its scope only if the week went well.

The prompt

Our own prompt, inspired by James Camp πŸ› ,πŸ›  (@JamesonCamp) and written to work in Grok Bot. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt1 variable
Here is my friction log from today: {friction_log}.
Sort each item into data entry, research or communication, and score frequency (daily, weekly, rarely) and dread (1 to 5).
Rank them and propose one narrowly named bot for the top item, with its instructions, the access it needs, and what it must ask me before doing.

Inspired by James Camp πŸ› ,πŸ›  (@JamesonCamp): I Spent Tens of Thousands on AI Tools. Grok Bot Is the First Agent I’d Recommend to My Mom.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • All bots under one account use the same files and sessions, so they do not isolate access.
  • Do not start with five bots at once.
  • Measure hours back and tasks no longer dreaded.

Our take

James Camp's friction audit is the cleanest starting method we have seen for people who keep hearing about agents and never begin. Logging tasks as they drain you beats brainstorming a list later, because the dull jobs you avoid are the ones you forget when asked what to automate. Scoring by frequency and dread surfaces work that is both common and unpleasant, which is where an agent pays off quickly. One bot, one job, one week is the right pace: you learn whether the handoff actually helps before building a fleet. After the week, decide with evidence: did it save time, did you trust its output, what broke. His caveat about shared computers and sessions under one account matters when you connect email or files; give access deliberately and start with the lowest-stakes job on your list. Prefer tasks with clear inputs and a reviewable output, such as a draft or a sorted folder, over anything that sends messages or spends money on day one.

Where the time goes back: You start where the payoff is highest instead of automating something that barely matters.

FAQ

How many bots does he run?
Five narrow ones across messaging, Notion, Stripe, content and analytics.
When should you build custom?
Only once an off-the-shelf tool clearly falls short, he says.

Source and credit

Inspired by James Camp πŸ› ,πŸ›  (@JamesonCamp). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
I Spent Tens of Thousands on AI Tools. Grok Bot Is the First Agent I’d Recommend to My Mom.
Creator
James Camp πŸ› ,πŸ›  (@JamesonCamp)
Published on
X
Original date
Aug 24, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Grok Bot
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks β†’

Related playbooks

Operations & AdminPromptβœ“ AI dry run

Audit how you manage your agent team, not only the agents

Have your chief-of-staff agent review the last 30 days of how you delegated, clarified, interrupted, corrected, assigned, approved and followed up across your agent team, score eight management areas with evidence, list your three biggest weaknesses, and draft a seven-day improvement plan, without changing any bot, routine or instructions until you approve.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminPromptβœ“ AI dry run

Brief an agent with nine fields, not a how-to

Before you hand a job to an agent, fill in nine short fields that name the result, the sources it may use, the deadline, what it may do alone, what needs your say-so, what it must never do, how to prove the work is finished, what to do when it gets stuck, and where to put the deliverable, then add a line that tells it to pick the simplest reliable method.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminPromptβœ“ AI dry run

Brief your agent on the outcome, not every step

Hand a new job to your lead agent by describing the finished result instead of the steps, and have it confirm what success looks like, ask only for context it cannot find itself, pick the simplest dependable approach, state what it will do alone and what needs your approval, and check the result against your goal before calling it done.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminRoutineβœ“ AI dry run

Make key agent routines leave a receipt that gets checked

Pick the scheduled agent jobs you cannot afford to miss, have each one record a receipt with its run time, outcome and what it produced, let a separate checker compare expected runs against receipts on a schedule, and get alerted only for missing receipts, failures or odd results, after testing all four cases with harmless examples.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminWorkflowβœ“ AI dry run

Trial an agent team for a week before replacing help

Before an agent team takes over a human assistant's work, run it for a week on real tasks and log approvals that expired, forgotten tasks, duplicate sends and cost.

Credit: u/Bubbly_Sort849 on r/cursor

Under an hour