I build AI agents and automation for general contractors and specialty trades — the back office, not the jobsite: estimating, submittals, field data, and AR, wired into whatever already runs your jobs. Based in Charlotte, working with contractors across North Carolina. Every engagement starts the same way: a one-week, $4,500 operations audit that maps where your back office leaks hours and hands you a build roadmap ranked by ROI. The fee is credited toward the first build — and if the audit doesn't surface savings worth more than its cost, you don't pay.
Charlotte, NC · On-site across the state or remote
Estimating assistants that draft takeoffs from plans, agents that route submittals and RFIs instead of letting them age, field-capture that lands in your office systems without re-typing, and AR chasers that never forget.
These aren't dashboards someone has to remember to check. Each one is an AI agent wired into the systems you already run — it does the re-keying, the routing, and the reminding, and your people approve the judgment calls.
Estimating eats your most senior people's evenings
An assistant reads the plan set and drafts the takeoff — counts, quantities, the assemblies you always price the same way. Your estimator starts from a draft instead of a blank sheet and spends the evening pricing risk, not counting fixtures. For a specialty trade bidding twenty jobs a month, that's the difference between chasing the work you want and bidding whatever there was time for.
Submittals, RFIs, and change orders get re-keyed at every hop
An agent watches the inbox and the PM system, logs every submittal and RFI once, routes each to the right person, and flags the ones aging past your response window. Change orders ride the same rail — captured once, priced, tracked to a signature. Nothing gets re-keyed, and nothing dies in a project engineer's inbox over a long weekend.
Field data — photos, T&M tickets, daily logs — dies in text threads
Crews keep doing what they already do: snap the photo, text the T&M ticket, dictate the daily log. The system reads each one, files it to the right job, pulls out the hours and materials, and lands it in your office systems the same day. When a dispute surfaces eight months later, the record is already organized — job by job, day by day.
AR follow-up happens when someone remembers
The agent knows every open invoice, its age, and its retainage terms — and follows up on schedule, polite at 30 days, firmer at 60. It drafts, a human approves, and nothing slips because the office was buried in payroll week. Pay-app deadlines get the same treatment.
More people means more roofs, more upfits, more service calls — and the same five people processing the paperwork. Construction automation in North Carolina isn't about robots on the jobsite; the near-term money is in the office. The contractors who automate the back office bid faster and collect faster than the ones trying to hire their way through it.
of contractors have actually changed a workflow with AI — 87% say it will reshape the work
Raleigh ranks among the top U.S. metros for new home construction; Charlotte's pipeline is just as full.
Read those two numbers together: the pipeline is full, almost nobody has actually changed a workflow yet, and nearly everyone knows it's coming. That gap is the opening.
14 field and back-office applications built for a multi-brand field-services group — finance automation alone recovered 18 hrs/week.
For a mid-market reverse logistics-tech company, I built the MCP server and agent tooling their internal teams use every day — Python on Google Cloud, wired into live inventory and truckload workflows, supporting 50+ internal users.
Different industries, same shape: crews in the field generating photos, tickets, and logs — and an office drowning in them. You own everything I build: code, infrastructure, and documentation.
Run a plant or a practice instead? I build for North Carolina manufacturers and independent medical practices too.
Every engagement starts with a $4,500 operations audit — fixed price, one week, credited toward your first build. If it doesn't surface savings worth more than its cost, you don't pay. Build sprints are fixed-scope from $45,000, and ongoing work runs from $8,500/month, month to month. The audit tells you which number matters before you spend it.
Whatever runs your jobs. Named tools with APIs — Procore, Buildertrend, Sage, QuickBooks — get wired in directly; if your jobs run on spreadsheets, I automate the spreadsheets themselves. Nothing gets ripped out — the automation sits on top of what your team already knows.
You do. Code, infrastructure, and documentation are yours at handoff, and your team gets trained on running it. Support is available without being mandatory — nothing is held hostage to a retainer.
It depends on the size of the leak, not the headcount. A ten-person specialty trade re-keying every T&M ticket can lose more each week than a fifty-person GC with clean systems. That's what the audit measures — and if the savings aren't there, I'll tell you not to build.
Yes. I'm based in Charlotte, and audits run on-site or remote anywhere in the state. For contractors, on-site is usually worth it — the gap between what the field does and what the office system says is easier to see from inside the office.
One week, $4,500, on-site or remote. I map where your back office leaks — estimating, submittals, field data, AR — and hand you a roadmap ranked by ROI. If it doesn't surface savings worth more than its cost, you don't pay.