AI automation for small business · Nashville, Tennessee

I'm not a developer. I automated an entire concrete company anyway.

I spent a year running the back office at a commercial concrete company — invoices, payroll, budgets, vendor statements. Then I taught AI to do it, one job at a time. Now I help other small business owners get their weeks back, and I'm teaching everything I learned along the way.

Work with me Join the course waitlist

One week in the back office — before & after TriStar Concrete · real production numbers

Back-office job	It used to take	Now it runs
Vendor invoices filed, coded & entered read from email, matched to jobs, posted to QuickBooks	Hours, every single week	Daily · 8:00 AM
Weekly crew payroll 44 checks, $93,207.25 — posted print-ready in one run	A full afternoon	Weekly · overnight
Vendor statements cross-checked against the books every line matched, mismatches flagged for a human	Honestly? Rarely got done	Same day, every time
Weekly cash & budget reporting to the owner project budgets, stuck invoices, financial snapshot	Whenever there was time	Every Monday · 7:00 AM

24 automations run this business today — and one more patrols all the others and emails at 5 PM if anything breaks.

The story

Two years ago, "AI" meant occasionally asking ChatGPT a question.

I'm Sophie. My husband Blake runs a commercial concrete company outside Nashville, and I ran its back office — accounts payable, payroll, budget spreadsheets, the pile of vendor statements nobody wants to reconcile. I have never written code. I'm a mom before I'm anything on this page.

What I had was a very clear picture of the repetitive work eating my week, and a willingness to sit with an AI tool until it did that work correctly. Not a chatbot — an AI agent that reads the actual emails, opens the actual PDFs, and posts to the actual QuickBooks. I built the first automation to file vendor invoices. Then payroll. Then statement matching, budget sync, the owner's weekly financial report. Each one ran in test mode until I trusted it, then it ran for real.

If someone who ran the back office of a concrete company can automate the whole thing, your business can be automated too. That's not a slogan — it's a ledger.

Now I do this for other small businesses: find the work that repeats, build the automation on the tools you already use, and hand it to you running — with alarms that tell you if it ever stops.

Work with me

How an engagement goes

Step 1 — Audit

We sit with your week

One working session. We walk through what you (or your office manager) actually do, and I mark every task that repeats. You leave with a written list of what's automatable, in plain English, ranked by hours saved.

Step 2 — Build

I build it on your tools

No new software to learn. The automations run on what you already have — QuickBooks, email, spreadsheets, your calendar. Everything runs in test mode first; nothing touches real money until you've approved it.

Step 3 — Handoff

It runs itself, you own it

Each automation runs on a schedule, emails you its results, and raises its hand when something looks wrong. You own the system outright — I'm a call away, not a subscription.

The course

Or learn to build it yourself

Automate Your Back Office — for owners, not developers

Blake and I are turning everything we built at the concrete company into a step-by-step video course. Small lessons, one real automation at a time, on your own laptop before anything runs unattended.

Set up the AI tools from zero — no coding background assumed
Connect QuickBooks, email, and your calendar safely
Build your first real automation and watch it run
Test-mode habits, review gates, and what not to automate
Make it run every day — even when your computer is off

Waitlist · Filming now

We're filming the first modules right now. Get on the list and you'll hear from me — a real person — when it opens.

Join the waitlist

About

A back office that proved it

Everything on this page ran (and runs) in a real company with real money — not a demo account. That's the standard for client work too: an automation isn't done when it works once, it's done when it has run unattended for weeks and told you about its own mistakes.

When I'm not building automations, I'm raising a daughter, running a Nashville mom community, and sharing the becoming-of-it-all at @becomingsoph.

Based in: Bellevue · Nashville, TN
Proving ground: TriStar Concrete's back office
Automations in production: 24 and counting
Runs on: QuickBooks, email, spreadsheets — your existing tools
Code you'll need to write: None