← Back to library

Map the onboarding process before building an AI agent

u/Actual-Struggle9480 runs an automation consultancy. A client wanted AI to take over customer onboarding, but a two-hour review of the current process showed three people typing the same data into three unconnected tools. They dropped the AI idea, linked the tools in Make.com, shipped in four days and report 15 hours a week saved.

View original
Works with
Make

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?

  • Someone has asked for an AI agent for a process nobody has mapped
  • Several people touch the same customer data
  • Onboarding feels slow but nobody knows why

Not for: Processes that are already integrated and need judgment calls; Teams that won't change who enters what data

What do you need, and what do you get?

You need

  • The people who do onboarding today
  • A list of tools they use
  • Two hours for a walkthrough

You get

  • A step-by-step map of the current process
  • A list of duplicate entry and handoffs
  • A recommended fix with or without AI

How does it work, step by step?

  1. Walk through it liveSit with each person and record every step from signed customer to active account.
  2. Mark duplicate entryHighlight fields typed into more than one tool and handoffs done by email or memory.
  3. Find the system of recordDecide where each piece of customer data should be entered once.
  4. Connect, then reconsider AILink the tools with an automation platform and a team notification channel before adding any model.
  5. MeasureCompare hours spent before and after the change.

The prompt

Our own prompt, inspired by u/Actual-Struggle9480 on r/u_Actual-Struggle9480 and written to work in Make. Values in lime are placeholders.

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

Prompt3 variables
Here are notes from watching our team onboard a new customer: {process_notes}. Tools involved: {tools}.
Turn this into a numbered process map with who does each step and in which tool. Then list every field entered in more than one place, every manual handoff, and every wait. Recommend the simplest fix for each: delete the step, connect two tools, or (only if judgment is truly needed) add an AI step. Estimate hours saved per week using our volumes {volumes}, and state your assumptions.

Inspired by u/Actual-Struggle9480 on r/u_Actual-Struggle9480: Client paid us to build an AI agent. We killed the project and shipped a Make.com scenario instead. They still paid the invoice.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Skipping the mapping step leads to automating a bad process.
  • Consultants have an incentive to sell AI; the author's point is to resist it when it isn't needed.

Our take

This short post is a useful corrective to the rush to put an agent on everything. The most common waste in small-company operations is the same data being typed into several tools by several people, and that problem is solved by connecting the tools, not by adding a model that reads and rewrites information. Mapping first is cheap and nearly always pays off: two hours of watching people work will show you duplicate fields, manual handoffs and steps that exist only because two systems don't talk. Once the plumbing is fixed, you can see whether any remaining step truly needs judgment, and that's where an AI agent might earn its cost. For consultants, the author's lesson is also commercial: telling a client they don't need the expensive thing builds the trust that leads to the next engagement. If you're the client, ask for the process map before you approve any AI build.

Where the time goes back: The author reports 15 hours a week saved by removing duplicate entry, without building an agent.

FAQ

Did they use AI at all?
No. The fix was tool integration in Make.com and a team Slack channel.
How long did mapping take?
About two hours, before any build work.

Source and credit

Inspired by u/Actual-Struggle9480 on r/u_Actual-Struggle9480. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Client paid us to build an AI agent. We killed the project and shipped a Make.com scenario instead. They still paid the invoice.
Creator
u/Actual-Struggle9480 on r/u_Actual-Struggle9480
Published on
Reddit
Original date
Oct 23, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Make
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
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

Draft client documents from records with no guessed facts

Have an AI draft deal reviews, timelines, requirements docs and similar client-facing documents only from your CRM, estimates, contracts and call notes, with every line traceable, conflicts between sources flagged to you, unconfirmed items labeled as open, and a person signing off before anything goes out.

Credit: Antonio Perrone

Minutes
Operations & AdminWorkflow✓ AI dry run

Send training clients a schedule PDF and timed reminders

When a client books, send a welcome email with their session schedule as a PDF, then reminders 30 and 7 days before their first session, each sent once.

Credit: u/Accurate-Tank-2564 on r/n8n

An afternoon+
Operations & AdminPrompt✓ AI dry run

List every request in an email before AI drafts the reply

Before an assistant writes a reply, have it pull out every ask, question, deadline and assumption in the incoming email, get a yes, no or not yet from you on each, draft using only those answers, and then list each sentence in the draft that commits you to something so you can check it before sending.

Credit: u/Ok_Negotiation_2587 on r/ChatGPTPromptGenius

Minutes
Operations & AdminRoutine✓ AI dry run

Run freelance admin through Telegram with one-tap approvals

Start each day with a short message of stale pull requests and Slack action items, and approve weekly client updates and follow-ups with a single reply.

Credit: Farooq Shabbir

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Schedule meetings from email threads with locks

Meeting requests in your inbox get answered with times you're really free, and confirmed meetings appear on your calendar.

Credit: u/BigFollowing9345 on r/SideProject

Under an hour