All use cases
Office & Admin

A St. Louis lawn-care owner who can't code runs his company with 10 AI bots — and nothing ships without his OK

Service Autopilot has no API. His bots still reroute Saturday boards, fix a bad fert text to every customer in under 5 minutes, and pull GPS so he can see which crews burn an hour before the first job.

Real storyDone with Grok Bot (team of ~10 bots) working around Service Autopilot
TradesAll trades

What they did

X user @Brettbrownlee22 (Brett Brownlee), 25 years in lawn care in St. Louis, says he "can't code" and now "10 AI bots help run my company: dispatch, time clocks, the customer inbox, review asks. Nothing gets sent and no money gets spent without my yes." Service Autopilot "has no API and charges per user for the app, so only my crew leaders have it." He wrote that Grok Bot "gets me around that." Concrete jobs he described: (1) Saturday rainout — "Crew fell short Friday so the whole board had to be rerouted… Told my Grok bot how I wanted the teams split. It moved the stops and republished the board. I went to my daughter's game." (2) Fert manager mistake — "My fert manager's automated text told customers the wrong step… Grok Bot fixed the form, the text, and the automation, then re-texted every customer with an apology. Under 5 min." (3) Yard bleed — "One crew cost me 110 minutes of paid time yesterday before they reached their first job… Every morning my Grok bot pulls truck GPS from Service Autopilot: ignition, leaving the yard, QuikTrip stops, first arrival. 40 trucks." (4) Inbox — "295 emails down to 33. A rained-out Saturday rerouted from my phone." (5) Leaf pricing — bots "rebuild our leaf removal pricing off decades of our real job history" so he can "measure a lawn, get an estimate that hits our man-hour target." He also one-shotted "a live crew board with AI… It pulls from Service Autopilot so every guy knows who he's with," and built a morning report "Per crew, per client, fuel, revenue" in "about 35 seconds" (he showed fake data; "The real one hits my inbox every morning now").

How it went

He reports the rainout board moved and republished so he could leave for his daughter's game; the fert apology blast went out in under 5 minutes; GPS made yard time visible across ~40 trucks; inbox went from 295 emails to 33 on one pass he posted. He does not publish a full ROI. He is also promoting Grok Bot (free 2-week invites and "$250/hr" "office hours" DMs), so treat the posts as operator + advocate.

Worth knowing

The useful pattern is not "buy 10 bots." It is: pick one stuck workflow your field software won't open (no API, per-seat lock, wrong customer text), give a bot clear rules, and keep send/spend behind a human yes. GPS and inbox triage only help if someone reviews the flags. If an owner is selling the same tool in the same thread, weigh the outcomes against that.

Try it yourself

You are an office assistant for a Wisconsin lawn / landscape company. You draft dispatch, customer texts, and inbox triage. You never send, never spend money, and never change live schedules until I say yes. TASK: Help me fix one stuck office workflow this week. CONTEXT (fill in the [BRACKETS]): - [SHOP]: Example: Oconomowoc Turf & Tree (fictional), ~8 crews, uses Service Autopilot / Jobber - [STUCK WORKFLOW]: pick one — Saturday rainout board, wrong customer blast, morning "who am I with?", leaf/aeration pricing from past jobs, inbox triage - [SOFTWARE LIMIT]: Example: no API / only crew leaders have the app / texts go out from a form we can't easily edit - [WHAT HAPPENED]: paste the facts (wrong text wording, crew shortfall, GPS notes, email subjects). No secrets you wouldn't show your office manager. - [RULE]: Nothing ships without my OK. STEPS: 1. Restate the stuck workflow in plain English and what "done" looks like today. 2. Draft the exact steps a human or bot should take, with a pause before any send or board publish. 3. If this is a customer text: draft the correction + short apology. Keep it under 400 characters when possible. 4. If this is a board/dispatch: propose the crew split as a table I can approve, not a live change. 5. If this is inbox triage: group emails into KEEP / DEFER / DELETE CANDIDATE with one-line reasons. Do not delete. 6. List three spot-checks I should do before approving. RULES: - Never invent a customer, address, price, or schedule. - Never claim a message was sent. - Mark every draft: DRAFT - OWNER MUST APPROVE BEFORE SENDING OR PUBLISHING. - Prefer fixing one workflow over building a 10-bot org chart. OUTPUT FORMAT: Part A: problem. Part B: draft fix. Part C: approval checklist. Part D: what not to automate yet. FOLLOW-UPS TO TRY NEXT: - "Turn last season's leaf jobs into a simple $/man-hour pricing table I can review." - "Draft tomorrow's crew board from this stop list." - "Here are 40 truck GPS first-arrival times. Flag crews over 45 minutes from yard to first job." FILLED-IN EXAMPLE (fictional Wisconsin business): - [SHOP] = Oconomowoc Turf & Tree (fictional) - [STUCK WORKFLOW] = fert text told customers the wrong next step - [SOFTWARE LIMIT] = auto-text form hard to edit on a phone - [WHAT HAPPENED] = wrong step went to active fert customers Saturday morning

Want help getting this working? Rise Systems in Oconomowoc sets these up.

Want this running in your business without the DIY? Rise Systems in Oconomowoc sets these up.

Free 15-minute AI check-up
Read the original

Source: X (Twitter) · October 29, 2026

Related