Get paid faster. Lose less work between the systems you already pay for.

KeyStrawAI is a veteran-owned consulting practice that closes the follow-up, data, and after-hours gaps a business still handles by hand. Fixed scope, measured before and after, running in accounts you own and keep.

built for businesses that run on jobs, schedules & invoices · deepest in hvac, plumbing & electrical · based in cobb county, ga · delivered remotely nationwide

start-intake → see where the money leaks ↓

zsh ~/practice/ops · 9:08pm · sample run

~/practice/ops # 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"  }
  ]
}
$

// start here

Start with money you have already earned.

revenue-recovery-sprint
We baseline what you are owed, clean the data that breaks follow-up, switch on the reminders your software already includes, and build only the exception handling Jobber and QuickBooks cannot cover. Same scorecard again at 30, 60, and 90 days. ar baseline · data cleanup · native config · escalation layer · 30/60/90 scorecard
1-2w · $4-9k

We don’t rebuild the reminders Jobber and QuickBooks already send. We switch all of them on, then build the layer neither tool can have: the part that reads both systems, knows who is in dispute, and treats a net-60 commercial account differently from a $300 repair. The gap analysis comes before the quote, and “you don’t need a build” is a real answer we give, usually a $1,500–4,000 cleanup instead of a $4,000–9,000 one.

how the sprint works →

// services.ts

Five modules. Most businesses start with one.

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

read all five modules in detail →

// who we serve

Built for businesses with phones that ring, calendars that fill, and invoices that age.

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

HVAC, plumbing, and electrical are where the work runs deepest, and where most engagements start. Adjacent trades and other job-based businesses are welcome. If your day looks like dispatch, jobs, invoices, and the phone after-hours: start the intake, wherever you are.

Two weeks of looking. Then we build.

approach.py Python 19 lines · main

def approach(shop):
    """
    Week 01 · Sit at the counter or screen-share
        Half-day at your counter or on a screen-share.
        Watch the day. Read the messages. Ride along.
        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 →