AI & automation, ranked by what actually moves money.

KeyStrawAI is a veteran-owned consulting practice for local businesses in Cobb County, Georgia. We sit at your counter, pick three automations worth building, ship the highest-ROI one first, and keep the report short enough that you'll actually read it.

start-intake → see what we build ↓

zsh ~/practice/local-business · 9:08pm · sample run

~/practice/local-business # 9:08pm, after closing
$ keystraw inspect --shop "your-business" --rank-by roi
→ analyzing 14 days of inbound, ops, and reporting...
→ done in 3.2s
 
{
  "ranked_opportunities": [
    { "id": "after_hours_ai",    "hours_saved": 11.5, "build": "2 weeks" },
    { "id": "missed_appt_recover", "hours_saved": 6.0,  "build": "1 week"  },
    { "id": "weekly_owner_digest", "hours_saved": 3.5,  "build": "3 days"  }
  ]
}
$

// services.ts

Each one is a real project. Mix and match per shop.

phone-desk
The phone keeps ringing after you close. We answer, qualify, book. after-hours chat · sms · review reply · phone agents · lead intake
module · 2-4w
schedule-keeper
The invisible tax on small businesses. Reschedule logic, dispatch, no-show recovery. booking · reminders · routing · customer records
module · 1-3w
friday-digest
The Friday email you never get around to writing, generated from systems you already pay for. weekly read · owner dashboards · pos / quickbooks / stripe
module · 3-7d
invoice-chaser
The overdue invoice you hate chasing, followed up in your voice until it's paid. escalating nudges · sms / email · payment-plan offer · stops when paid
module · 1-2w
estimate-drafts
Drafts in your voice, built from your own historical examples. Proposals, invoices, marketing. proposal/invoice · reminder email · marketing post
module · 1-2w

read all five modules in detail →

// shops we serve

Built for Cobb County service shops with phones that ring and calendars that fill.

hvac
plumbing
electrical
solar
roofing
auto-repair
glass
appliance-repair
pest
garage-door

Adjacent verticals welcome. If your day looks like dispatch, jobs, invoices, and the phone after-hours — start the intake.

Two weeks of looking. Then we build.

approach.py Python 19 lines · main

def approach(shop):
    """
    Week 01 · Sit at the counter
        Half-day on site. Watch the day. Read the messages.
        Ride along with whoever is actually doing the work.
        Output: a notebook of friction, not a slide deck.

    Week 02 · Three opportunities, ranked
        Each opportunity has a number next to it:
            hours_saved_per_week, dollars_recovered_per_month,
            build_cost, run_cost.
        Output: one short doc, three line items.

    Week 03+ · Build, pilot, cut over
        Highest ROI first. Ship into production, run a
        one-week pilot, cut over, then hand off in your name.
        Output: revenue or hours, your accountant recognizes both.
    """
    return three_concrete_things

read the full approach →

// ethos

We don't have a quota of AI automations sold per quarter. So we won't sell you something you don't need.

keystrawai · how we engage

// leak-check

What does the phone ringing after close actually cost?

Two numbers from your week. The math runs right here, in your browser, nothing is sent, saved, or followed up on.

javascript is off, so the calculator is too. the method, by hand: missed after-hours calls per week × 4.33 weeks × your average ticket, then assume 15 to 35% of those callers were real jobs that booked elsewhere. that range is the monthly leak; × 12 for the year. preliminary either way: the real number comes from two weeks of looking.

leak-check ~/your-shop · runs locally

# preliminary math · your numbers, stated assumptions · not a quote

$ keystraw leak-check --missed-calls/wk _ --avg-ticket _
# enter two numbers above. the math runs here, nothing leaves this page.

start-intake → how we verify the number →