Independent reviews. IonBin has no partnerships with the tools on this page and was not paid for these listings. Our evaluations are our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Need

I need to decide what AI should do before I hire for a role

Verified Oct 17, 2026 Review by Apr 15, 2027 1 source
Short answer

Don't treat the role as one unit. List the four to ten outputs the hire would produce, then mark each one: AI does it, AI drafts and a person approves, or a person owns it. Hire for what's left, and write SOPs for the rest. You get a sharper job description and a realistic view of what AI can carry. Not legal or HR advice.

What it is

A short audit to run before opening a role, or when someone leaves. It turns “should AI replace this job?” into a list of concrete outputs. Alex Hormozi describes the idea in a March 2026 video: write down the four to ten things a hire would actually do, and ask whether each could live inside a workflow instead of headcount.

How it works

  1. List the outputs, not the duties: “weekly pipeline report”, “first reply to inbound leads”, “invoice follow-ups”.
  2. Mark each one: automate, assist (AI drafts, a person approves) or human (judgment, relationships, accountability).
  3. Check each AI step for data and access. Can the AI reach what it needs safely?
  4. Pilot the automate and assist items for two weeks with a named reviewer.
  5. Write the job description around what remains, and turn the rest into SOPs.

Benefits

  • Clearer hiring. The role is defined by work AI can’t do well.
  • Faster onboarding. The SOPs you wrote become the new hire’s manual and the AI’s instructions.

Limits and risks

  • Pilots lie when baselines are guessed. Time the current way first; don’t estimate the “before” number.
  • Hidden work. Roles include relationship and judgment work that doesn’t show on a task list. Ask the person doing it.
  • Employment law. Restructuring or removing roles can carry legal duties. Get advice before acting on an audit.

This page is about planning work, not employment decisions. It isn’t legal or HR advice; changing or removing roles can carry legal duties, so check the rules that apply to you.

Checked specs

Snapshot from official sources on Oct 17, 2026.

Practitioner method (video transcript)For every hire you are considering, write down the four to ten things the person actually does, then ask whether each could live inside a workflow instead of headcount [1]

Best-fit stacks

Stack 06

Ops & admin automation

Hand repeat admin (receipts, logs, notices, handoffs) to workflows your agent can trigger.

Agent compatibility

Tool in this entryHow agents connect
Claude Agent platform API/CLIBulk import
ClickUp MCPAPI/CLIBulk import
Notion MCPAPI/CLIBulk import

Levels come from each tool's recorded, sourced compatibility. How the levels work.

Sources

  1. How to Win With AI in 2026, role-to-workflow section (from 4:42) · Alex Hormozi, 2026-03-31Practitioner view accessed Oct 17, 2026

Practitioner views are restated in our words and labeled as views, not measured results. Product facts come from official sources dated above.

Suggest an edit

IonBin's wiki isn't user-edited. Corrections go to our Directory Curator, who checks them against primary sources before anything changes. Spot something wrong or out of date on “I need to decide what AI should do before I hire for a role”? Email us with a link to a primary source.

Suggest an edit by email or write to [email protected]