AI SYSTEMS · CHARLESTON, SC
Software should move your data. Your people should decide.
I build AI systems for businesses where the work gets stuck between tools — real estate teams, brokerages, and property managers first. Every one of them is built so nothing sends, files, books, or spends without a person saying yes.
THE ARGUMENT
Your people are the integration layer.
Count your software. Most teams I talk to are running six to ten separate products, and every one of them was bought to solve a real problem. None of that is a mistake. The mistake is assuming they connect.
They do not, so a person does it. A lead comes in by voice — a call, a voicemail, a conversation in somebody’s driveway. It gets written on a notepad. Then it has to reach the CRM, the follow-up sequence, the transaction file, and eventually the broker. Four hops, every one of them a human retyping something that already existed in digital form thirty seconds earlier.
That person is your integration layer. They cost forty to eighty dollars an hour loaded, they are slower than software by three orders of magnitude, they make transcription errors, and when they are on vacation the data simply stops moving. You have built your business on the most expensive and least reliable connector available.
Here is the swap. Software becomes the layer that moves things between systems — reading, extracting, formatting, pushing. Your people become the layer that decides — is this right, should this go out, do I approve. That is not a smaller job for your team. It is the only part of the job that was ever worth their salary.
CAPABILITIES
Nine things, and an honest label on each.
Every capability below is tagged with where it has actually been built and what state it is in. If something says prototype, it means it works and has never run in production. I am not going to blur that line.
AI agents that do a whole job
Not a chatbot. A process that runs start to finish — research a prospect, draft the outreach, log it, and stop for approval. Seven of them run my own company.
Dashboards that show the work
What is waiting, what is stuck, what shipped. Not vanity charts. Includes a read-only money view that cannot move a dollar.
Human approval workflows
One inbox holding everything the system wants to do. Nothing leaves it without a click. This is a structural rule, not a setting.
Workflow automation
Tiered follow-up cadences that respect quiet hours and stop the moment a human replies. Built and tested; never run against live contacts.
CRM integration
Structured records pushed into the CRM you already pay for. Verified against a real Monday.com board, re-runnable without creating duplicates.
Document intelligence
Reads the contract, stages the transaction file, and generates the missing-documents punch list. Payloads verified against a live Dotloop account — but the button itself errors right now, because the API credentials are not registered yet.
Voice interfaces
Talk into your phone or browser. Transcribed locally on the machine, so that audio does not go to a transcription vendor. Claude turns it into structured fields.
Compliance guardrails
Blocking fair-housing phrase checks, a per-contact per-channel consent ledger, and permission gating written against SC license law. Blocking means it will not let the message through, not that it warns you.
Audit trails
Append-only. Nothing can be edited after the fact. Exports as a one-file printable dossier per lead.
WHAT I HAVE NOT BUILT
The list nobody else on this page will show you.
- MLS and Spark integration — not built at all. If your project depends on live MLS data, that is new work and I would scope it as such.
- E-signature — not built. I would integrate an existing provider rather than build it.
- Showing scheduling — not built.
- Anything with usage metrics — the real estate system has never run in production, so there are no adoption numbers, no time-saved numbers, and no error rates. Anyone quoting you those from a prototype is quoting you a guess.
- A paid implementation for an outside client — has not happened yet. The first three are founding engagements.
WHO THIS IS FOR
Real estate first, because that is where it hurts most.
Real estate teams, 5–30 agents
Leads arrive by voice and die in the gap between the phone and the CRM. You have got a coordinator whose actual job title should be “retyper.”
Brokerages
You need a broker review queue that is not a shared inbox, permission gating that matches SC license law, and an audit trail that survives a complaint.
Property management, 100–1,000+ units
Maintenance requests, renewals, rent comps, and owner reporting, spread across a property management platform that does not speak to anything else.
Small businesses outside real estate
The handoff problem is not a real estate problem, it is a multiple-software problem. If you are a professional services firm or an operator with the same symptoms, say so on the call — I do this work too.
HOW IT RUNS
Four steps. You can stop after any of them.
STEP 01
Assessment — $750, two weeks
On-site, interviews with the people doing the work, a look at your actual tools. Ends with the AI Opportunity Map: every workflow, ranked by hours returned, with build effort and what to leave alone.
STEP 02
Build one thing — from $10,000, four to eight weeks
We take the single highest-hours item off the Map and ship only that. Milestone-based, so you can stop between milestones. A working system in front of your team before you commit to a second one.
STEP 03
Handoff — included
You get the code, the documentation, the runbook, and the credentials. I train the people who will use it. If you never speak to me again, it keeps running.
STEP 04
Managed AI Operations — from $2,500/month, optional
I watch the approval queue, fix what breaks, and change the system when your business changes. Month to month. Only offered after something has actually shipped.
Step 2 says “build one thing” on purpose. The most common way an AI project fails is building six things at once, none of which get used. I would rather ship one workflow your team actually opens on Monday than a platform they log into twice.
THE RULE
The one rule I do not build around.
Nothing I build sends, publishes, books, files, or spends money on its own. Every one of those actions produces something waiting for a person to approve. That is enforced in the structure of the system, not a checkbox somebody can turn off during a busy week. It is the reason I can put a compliance guardrail in front of a real estate team and mean it.
Start with the Map, not the build.
Two weeks, $750, and a written plan you could hand to any competent developer — including one who is not me.
See what is in the Assessment →