How I Use AI and VAs to Run My House Flipping Business
TLDRAI and VAs do not fix a disorganized business. Build the operating system first, use AI or VAs for defined decisions and support work, and keep new judgment with the owner.
Table of Contents
- AI and VAs Do Not Fix a Mess
- The Three Kinds of Work
- Move Work Down the Ladder
- Where AI Actually Fits
- Where VAs Actually Fit
- The Real Jobs I Give AI
- Keep Judgment With the Operator
- FAQ
AI and VAs Do Not Fix a Mess
Most people think an assistant, an AI agent, or a VA is going to make their problems go away.
It will not.
If your business is sloppy, adding help usually makes the slop move faster. The inbox is still messy. The CRM is still unclear. The project notes are still scattered. The difference is now somebody else is asking questions about your mess, and you are paying for the privilege.
I run a multimillion-dollar real estate business with no payroll prison. I have flipped 300-plus houses. I own 150 rental units. I use vendors, agentic ai, VAs, automations, and software. But all of that sits on top of the operating system.
The support stack exists to handle the little pieces of cholesterol that build up in the business: mail, CRMs, bookkeeping, reports, emails, tax payments, calls, notes, follow-ups, property lookups, and project admin.
Common MistakeHiring help before defining the work. If you cannot explain the task, the person or tool receiving it cannot rescue you.
The Three Kinds of Work
I sort support work into three buckets.
| Type | What It Means | Best Fit |
|---|---|---|
| Deterministic workflow | A to B to C, same way every time | Automation, code, scripts |
| Decision workflow | A goes to B, C, or D based on rules | AI, VAs, assistants |
| Judgment workflow | A new thing shows up and someone has to think | Owner, high-level operator |
A deterministic workflow is like code. This happens, then that happens, then that happens. Same way every time.
A decision workflow has a choice inside a box you already built. If the invoice matches the bid and the photos show the work is done, approve it. If not, flag it.
A judgment workflow is different. Something you have not seen before shows up. There are too many variables. Somebody has to think.
That somebody is usually me.
Could you eventually hire a high-level person to make judgment calls? Sure. But most small real estate businesses cannot support a six-figure operator who thinks like the owner. So the owner stays at the top of the pyramid.
The goal is to turn judgment into decisions, and decisions into repeatable workflows whenever you can.
Move Work Down the Ladder
Every time a weird task shows up, I try to understand it well enough to move it down the ladder.
Ross names the delegation gradient this way: bounded decision, managed judgment, owner judgment. The closer the work gets to owner judgment, the less safely it can be handed off.
At first it may require my judgment. Then I notice the pattern. Then I turn it into a decision workflow. Then maybe it becomes deterministic.
That is the game.
A task that starts as “Ross needs to think about this” might become “AI can gather the context and ask Ross for approval.” Later it might become “AI can approve this inside a narrow set of rules.” Later it might become pure automation.
This is why your systems become assets. The written workflow, the checklist, the rule, the skill file, the database structure, the way you think through the work, all of it gets better over time.
I have the AI help improve its own instructions when it messes up. It runs a workflow, something breaks, and I do not just get mad. Well, sometimes I get mad first. Then I update the workflow so the same mistake is less likely next time.
Pro TipDo not ask AI to be smarter than your system. Ask it to run the system you already made clear.
The asset is not the tool. The asset is the workflow you keep improving.
Where AI Actually Fits
AI sits best in the space between deterministic work and bounded decisions.
It can read files. It can search a database. It can draft emails. It can compare a contractor bill against a bid. It can look through old notes and tell me if this waterline problem has happened before.
But it needs context.
I have a system I call Omega. It has my Google Drive, calls, texts, YouTube videos, documents, and years of business context chunked up so the AI can retrieve it. That does not make the AI magic. It gives the AI better raw material.
If I keep the task in the right lane, it works. If I push too far and ask it to make a judgment it could not possibly know, it gives me something stupid. Then I remember: it is a robot.
The clean uses are real:
- run comps inside my rules
- look up properties for easements or odd issues
- skip trace owners
- build marketing lists
- track foreclosures and auctions
- send mail and email campaigns
- update the deals CRM
- draft contracts
- pull permits or prep permit workflows
- build scopes from voice notes
- log contractor bids and bills
- update project plans from meeting transcripts
- draft vendor emails and project updates
- triage calls, texts, and email
- review property management reports
That is a lot of work. But each item only works because I already decided what good looks like.
Ross also said he records calls and uses the transcripts because doing so was legal for him in Tennessee. That was a jurisdiction-specific aside, not a rule for every reader. Confirm the current consent requirements that apply before recording any call.
AI is not the brain of the business. It is a worker inside the business.
Where VAs Actually Fit
VAs are useful when the work needs a human but does not need me sitting in the chair.
That might be administrative inbox items. Vendor follow-up. Title company and lender follow-up. Tax payments. CRM upkeep that is still too fuzzy for AI. There are plenty of tasks where a human can read the situation, make a bounded decision, and keep the business moving.
This used to be the classic assistant role. I have had assistants before. I do not need one right now because of how I use the support stack.
A VA still needs management. You meet with them. You review what was delegated last week. You hand over the next batch. You explain the rule when something goes sideways.
A VA will not define a missing workflow for you. If the work is unclear, the VA has to keep asking what you mean.
There are also local errands. A VA in another country cannot put a lockbox on a door. For those, I usually add the task to the right local vendor. A contractor might put the lockbox on while he is already at the property. A sign might get handled by somebody who is already driving that way.
Use VAs for bounded human work. Use local vendors for local hands. Keep owner judgment with the owner.
The Real Jobs I Give AI
The real estate business has three big divisions for me: deals, jobs, and ops.
In deals, AI helps with comps, property lookups, skip tracing, list building, foreclosure and auction tracking, mail campaigns, cold email, CRM updates, contracts, websites, and landing pages.
In jobs, AI helps with permits, inspection scheduling, scope of work creation, contractor bid and bill logging, project planning, meeting notes, vendor emails, and project memory.
In ops, AI helps with call, text, and email triage, email drafts, call notes, CRM updates, property management review, financial discrepancies, maintenance approvals, lease expirations, and asset management notes.
One of my favorite examples is project memory. A property management issue came up around a waterline. The AI searched the old context and found a phone call from four years earlier about what looked like the same issue. That did not solve the whole problem, but it put the right memory in front of me.
That is the point. I do not need AI to be brilliant. I need it to bring me the right stuff, follow the rules, and take small support work off the plate.
Key ConceptAI works best when it narrows the decision for me. It gathers context, checks the rules, and asks for approval when approval still belongs with me.
The support stack handles small tasks so I can scan the information and make the decisions that still belong with me.
Keep Judgment With the Operator
The top of the pyramid is still judgment.
I decide the buy box. I decide whether a contractor is worth building around. I decide whether a weird property problem matters. I decide whether the business should take a certain risk.
AI and VAs can help get the information in front of me. They can keep the machine organized. They can run tasks that used to steal hours. But they do not get to replace the hard thinking.
This is why I tell people to build the operating system first. If you are disorganized, you will not find the uses for AI and VAs because you have not done the work of understanding your own business.
Once you do, the opportunities are everywhere.
And yes, I think you should get on the train. I know that phrase sounds a little goofy. But this is not going away. You are not going to hate it away. It is too useful.
If AI can take your job, you need to get better. It should not be able to take your judgment.
FAQ
Should I hire a VA before building AI workflows?
Maybe, but only if the work is clear enough to delegate. A VA can handle bounded human decisions better than AI in some cases. But if your operating system is a mess, the VA will spend most of their time asking you what to do.
What real tasks did Ross give AI?
The source names CRM updates, property lookups, meeting-note extraction, email triage, bid logging, comps, list building, scopes, project updates, and property-management review. The task still needs a defined workflow and the right level of human approval.
Can AI replace an assistant?
It can replace pieces of what an assistant used to do. It can also make a VA or assistant much more useful. But it will not replace owner judgment unless you are asking it to make decisions it should not be making.
What if I am not technical?
Ross’s requirement is not that every operator write software. It is that the operator understand the process well enough to define the judgment, decisions, and repeatable steps before handing them to a tool or person.
Is this really worth learning right now?
Yes. The tools are getting better fast, and the cost is low compared with payroll. The mistake is thinking the tool is the opportunity. The real opportunity is making your business clear enough that the tool can run pieces of it.