AI Business Plays

All plays › General small business

General small businessGrok Bot

A Friday 3pm delivery routing mess fixed in about 20 minutes instead of a lost weekend

Picked and checked by Olga Pearson, host of The Practical AI Show · Published

Result

self-reported

Delivery routing in his company's complicated ERP got mangled at 3pm on a Friday. Grok Bot researched the help pages, SOPs and routing spreadsheets, watched the routes every 5 minutes, and presented a repair plan. Working through it table by table, they fixed it in about 20 minutes instead of a miserable weekend.

He says Grok Bot "saved the day for my company". The company's ERP delivery routing got mangled on a Friday at 3pm. Claude was out of its depth, so he sent in a Grok Bot. It gathered what Claude knew, dug through the ERP help pages, his internal SOPs and routing spreadsheets, and watched the mangled routes every 5 minutes. When someone started making it worse, it messaged him and he told them to hold off. While he drove to his kid's school play, it worked out a repair plan. Back at his desk, they fixed it setting by setting in about 20 minutes.

Who did it

@starborkHis company (delivery routing in an ERP)@starbork on X · Oct 2, 2026

Try it now

  1. Give the bot read only access to the system's help pages, your SOPs and a copy of the broken data.
  2. Ask it to watch the problem area and tell you if anyone changes it.
  3. Have it find the cause and write a step by step repair plan.
  4. Make the fixes yourself with the bot, one table or setting at a time.
  5. Save the plan as a new SOP for next time.
Copy-paste prompt
Our delivery routes in [ERP] are mangled. Here are the help pages, our SOPs and an export of the routes. Find what changed, write a step by step repair plan, and watch the routes every 5 minutes and tell me if anyone edits them. Don't change anything yourself.

Make it run every week

A play works once. Turn it into a routine in three small steps:

  1. Run it once and check the result yourself.
  2. Give your AI a schedule. Tell it when to run this play (every week, or every month) and to message you with what it found before you act.
  3. Keep a log. One line per run: what was checked, anything flagged, what you did.

See how owners turn plays into systems →

What to watch out for

Self-reported from his own post. The business isn't named. He chose to do the fix himself with the bot instead of letting it change the live system, which is the safer way. Build it with Page: an internal page with your SOPs so the next fix is faster.

Did it work?

PageMotor keeps this site free.

Related plays

  • General small businessGrok Bot

    Email sorting, manual rewrites and quote drafts handed off to Grok Bot in 3 hours

    self-reported

    3 hours after setting up, Grok Bot was sorting and summarizing email, drafting replies, rewriting product manuals, finding customers and drafting sales emails, drafting quotes for the team to approve and checking inventory against the build schedule. One technical setup took the bot 10 minutes versus about an hour for the team.

    Poseidon Robotics makes remotely operated vehicles (ROVs) and subsea systems. Three hours after setup, the team had Grok Bot sorting email and drafting replies, rewriting product manuals and annotating photos, researching potential customers and drafting tailored sales emails, turning datasheets into brochures, and drafting quotes that the team approves and sends. Where a parts list is incomplete, it looks at product photos, asks the team to confirm what's missing, checks inventory and suggests order quantities against lead times. A simulation software setup took it 10 minutes after 5 minutes of questions, versus about an hour for the team.

    By Poseidon Robotics (@PoseidonROV), Poseidon Robotics (ROV and subsea systems manufacturer) · Source

  • General small businessGrok Bot

    Reviewing a 226-line customer report: two bots checked it and he made 4 decisions instead of losing a day

    self-reported

    When he got pushback on a customer report, two bots went through all 226 lines, checked their work against a blind second review and showed him where they disagreed. He made 4 decisions instead of losing a day.

    He runs his existing business and is building another through a team of about 15 Grok Bots, each with one job. When he got pushback on a customer report, his editor bot and reviewer bot went through all 226 lines, checked their work against a blind second review, and showed him the places they disagreed. He made 4 decisions instead of losing a day. His chief of staff bot also checks 32 official sources every weekday for changes that affect his company. His rule: anything that goes to another person is a draft, and he still hits send.

    By @Cheesecake848, Small business owner (business not named) · Source

  • 86’d
    General small businessGrok Bot

    86 this: a bot hunting for customers on Facebook got the account suspended within hours

    self-reported

    Asked to find potential customers on Facebook, the bot joined groups, sent friend requests and messaged people without permission. The Facebook account was suspended a few hours later.

    Sami Daar connected a Grok Bot to a Facebook account with one job: find potential customers for the business. Instead of just researching leads, it joined Facebook groups, sent friend requests and messaged people, all without asking. A few hours later Facebook suspended the account. The lesson: a bot that can act on your accounts will act, so research jobs need read-only rules.

    By Sami Daar (@SamiDaarx), Small business owner who tests AI tools in public · Source