The Depth Chart: How I Run a Real Estate Team With No Employees
TLDRThe Depth Chart is how I run a multimillion-dollar real estate business without employees by arranging vendors, AI, VAs, software, lenders, contractors, agents, managers, and advisors around the operator. The goal is not to work alone. It is to protect bandwidth, avoid payroll prison, and build a stronger business.
Table of Contents
- Start With the Map
- Solo Does Not Mean Alone
- The Pyramid Tells You What Matters
- Hire for the Right Reason
- Vendors Beat Employees Most of the Time
- Offloading Is Scaling
- The Support Stack
- Build the Vendor Bench
- Speed, Price, and Quality Are Mostly About You
- FAQ
Start With the Map
I built the Depth Chart Map because this is not one little trick.
This is the visual version of the whole lesson. The article is the written build manual. The map lets you see the pyramid, the vendor roster, the reasons to hire, the support stack, the AI and VA workflows, and the vendor bench in one place.
If you are actually building this, keep the map open while you read.
The map is the practical tool. This article is the explanation behind it.
Solo Does Not Mean Alone
I run a real estate business with no employees. That does not mean I work by myself.
I use contractors, wholesalers, real estate agents, hard money lenders, DSCR lenders, title companies, property managers, insurance agents, CPAs, attorneys, bookkeepers, banks, mobile notaries, inspectors, surveyors, suppliers, engineers, architects, VAs, software, automations, and AI agents.
That is still a team. It is just not payroll.
Most people confuse solopreneur with sole proprietor. A sole proprietor does everything. He answers the phone, writes the scope, picks up materials, chases bids, updates the CRM, handles bookkeeping at night, and calls that entrepreneurship.
That is not entrepreneurship. That is owning a job.
A solopreneur protects bandwidth. He makes money for a living. He sees an opportunity, turns it into profit, and avoids letting the business dump every little support task back onto him.
I have flipped 300-plus houses. I own 150 rentals. I have done the employee version. I had the office, the crews, the payroll, and the internal companies. I also had the day where I fired a pile of people because the math did not work.
I came back to the model I should have respected earlier: vendors, not employees, with me as the asset that keeps getting better.
Common MistakePeople hear “build a great team” and think the team is going to save them. It will not. If your system is broken, the team just spreads the mess faster.
Solo does not mean alone. It means I own the system, not the people.
The Pyramid Tells You What Matters
The Depth Chart starts with the pyramid.
At the bottom is the operating system. Without that, you have nothing to build on. If tasks are scattered across your head, your inbox, your texts, and ten half-used apps, adding people will not fix the problem. It will multiply it.
Above the operating system is the support stack: habits, tools, software, automations, AI, VAs, and eventually support vendors. This is the layer that protects your bandwidth.
Above that are business drivers. These are the people and relationships that directly drive growth:
| Type | Examples | Why They Matter |
|---|---|---|
| Deal flow | Wholesalers, real estate agents, direct mail vendors, marketing vendors | More good opportunities |
| Capital | Hard money lenders, private lenders, DSCR lenders, banks | More deals you can actually close |
| Execution | Contractors, property managers, listing agents | More projects finished and stabilized |
Then come the essentials: CPA, attorney, bookkeeper, insurance agent, bank. You need them, but they should not become the bottleneck. A lot of beginners spend all their energy here because it feels responsible. The problem is you do not have anything to protect until you build something.
Then comes infrastructure: title companies, inspectors, appraisers, surveyors, engineers, architects, suppliers. These usually show up when the road demands them. You hit a title issue. You need a survey. A wall is questionable. You need an engineer. Handle it and keep moving.
At the top are luxuries: staging companies, estimators, money managers, specialty photographers, premium consultants, mobile notaries in some situations. Nice to have. Not the base.
The village analogy is the easiest way to see it. You do not start a village by building the castle walls. You put up tents first. The tents are not permanent. They are not ideal. But they let the village exist. Then, over time, you fortify.
Start with the business drivers. Fortify the pyramid over time.
Hire for the Right Reason
When I say “hire” here, I mean any time someone or something other than you carries work. That could be a contractor, a vendor, a VA, software, or an AI agent.
There are good reasons to hire:
| Reason | What It Means | Example |
|---|---|---|
| Liability | You need a buffer between risk and yourself | Property management, insurance, legal |
| Bandwidth | The task is taking time or mental space from higher-value work | Admin, bookkeeping, document routing |
| Skill upgrade | Someone knows more than you | CPA, engineer, attorney |
| Access | They have a license, permit path, tool, or platform you do not | GC license, title access, lending platform |
| Desire | You can do it, but you hate it enough to pay | Bookkeeping, errands, low-skill admin |
There are also bad reasons:
| Bad Reason | Why It Fails |
|---|---|
| Urgency | Usually means your system was weak before the emergency |
| Fear | You are trying to make the anxiety go away instead of building skill |
| Status | You want to feel like a real company because people work for you |
Fear is a big one. People hire a general contractor because they are scared of managing the job. They hire an assistant because they are scared of the pile on their desk. They hire a CPA, attorney, or bookkeeper before their first dollar because it feels like a business costume.
Sometimes the right answer is to hire. Sometimes the right answer is to learn.
I got my general contractor license because access was limiting me and construction was a business driver. That was worth building into myself. I do not do my own bookkeeping because I hate it, and it is not the highest use of me. That is worth offloading.
The difference matters.
Hire to protect bandwidth, reduce real risk, add real skill, or gain real access. Do not hire to hide from the work you need to understand.
Vendors Beat Employees Most of the Time
I understand the urge to hire employees. I felt it.
There is a pull toward owning the person. You want the office. The crew. The assistant. The project manager. The feeling that you built something real because people are on payroll.
I also believe entrepreneurs should create jobs. That is one of the best things business owners do. But you put your oxygen mask on first. If you hire people before the business can support them, you are not helping them. You are building a payroll problem that eventually lands on everyone.
Employees do have real advantages:
| Employee Advantage | Why It Feels Good |
|---|---|
| Direct control | You can tell them where to be and what to do |
| Dedicated capacity | Someone is available when random work shows up |
| Training asset | In theory, they get better inside your system |
The cons are heavier:
| Employee Problem | What It Costs |
|---|---|
| Payroll prison | You owe money every pay period whether the work is there or not |
| Management weight | You now own their idle time, mistakes, motivation, and drama |
| Tax and benefit drag | Payroll is not just wages |
| You think for them | Employees often push more decisions back to you |
| Exit risk | When they leave, you feel like the business got ripped open |
Vendors are different. They hunt what they eat. They have their own business, their own tools, their own pricing, their own workflows, their own problems. If you manage the relationship correctly, you can make them carry more of the thinking and support work instead of less.
Classification Still Follows the FactsCalling someone a vendor does not make that person an independent contractor. The IRS looks at behavioral control, financial control, and the parties’ relationship, while federal and state labor rules may use different tests. Check the actual working relationship and the rules that apply where you operate.
That is the key.
The best vendor relationships become pull relationships. They follow up. They keep a CRM. They ask you for the missing document because they need the deal to move. Insurance agents and real estate agents often work this way. Contractors usually do not at first. They are push vendors. You have to follow up, make the process easy, and own more of the support work early.
But over time, if you become a real part of their business, some push vendors start pulling. They rely on your work. They plan around you. They care about keeping the relationship.
The goal is not to avoid people. The goal is to build relationships where people carry work without becoming payroll weight.
Offloading Is Scaling
Scaling and offloading are the same move.
Most achievers are not in control of their bandwidth. They just put their head down and work. The problem is that little tasks keep sticking to you.
At first it is fine. You answer one email. You fill out one form. You make one extra call. You put out one sign. You run one errand.
Then it builds up like cholesterol in your veins. One piece of bacon is not the problem. Years of buildup is the problem. Eventually the blood flow constricts and the business has a heart attack.
My job is to keep the business flowing.
That means I work hard to be lazy. Not because I worked hard for 15 years and now coast. I work hard every week to dodge work that should not belong to me, redirect it to the right person, and build systems so it does not come back.
When you protect bandwidth, you get a choice.
You can use the freed-up bandwidth to work less and make the same or more money. More time with your family. More peace. More room to think.
Or you can use the same bandwidth to do ten times as much. More deals. More businesses. More scale.
The move is the same either way: offload the right work, keep the right judgment.
Key ConceptFreedom is not the easy life. Freedom is choosing the obstacles you face. If the business chooses every obstacle for you, you are not free.
Every relationship either takes support work from you or dumps support work onto you. Build toward the first one.
The Support Stack
The support stack sits on top of the operating system.
You cannot hand your mess to AI, a VA, or an assistant and expect it to become clean. If the workflow is vague in your head, it will be worse in someone else’s hands.
There are three types of workflows:
| Workflow | Shape | Best Tool |
|---|---|---|
| Deterministic | A to B to C to D | Software, code, automation |
| Decision | A to B, C, or D based on known rules | AI or VA |
| Judgment | A to question mark | You, or a high-level person with real skill |
Deterministic work is pre-decided. If this happens, do that. Every normal software tool is built on this. Your goal is to turn as much of the business as possible into deterministic workflows because those become assets.
Decision work has controlled variables. The person or AI has to choose, but the choices live inside your rules. AI and VAs are useful here.
Judgment work is different. That is where the path is not carved yet. Too many variables. New problem. Real consequences. That stays close to you unless you have a high-level person who understands your methodology or has a skill you truly do not have.
This is why the operating system comes first. AI and VAs do not replace thinking. They replace support work after you have defined the work.
Some support work is physical. Lockboxes. Signs. Mail. Photos. Material runs. You can hire an errand person. I would rather push that work into vendors when I can. If a contractor is already at the house, I may pay a little extra and have them put on the lockbox or handle the sign.
That is the whole game: keep local physical tasks from turning into a reason to build staff.
AI handles a lot for me now: call and email triage, transcript notes, CRM updates, contract prep, list building, landing pages, bid logging, property management review packets, and company memory.
VAs can handle the things that need human follow-through but not operator judgment.
Support is not someone coming to save you. Support is your operating system with hands.
Build the Vendor Bench
I hate networking.
Not because relationships do not matter. Relationships matter a lot. I hate the fake version where people go stand around at events trying to sound important.
The better way is to know what you want, profile the role, scout deliberately, build a pipeline, lead the relationship, and rate the result.
First, profile.
When I look at a vendor, I care about signals:
| Signal | What I Am Looking For |
|---|---|
| Stage | Hungry, growing, not bloated |
| Owner | Close to the work, not hidden behind layers |
| Craft | Technician at heart |
| Overhead | Not so bloated that I pay for the office furniture |
| Pricing | Can explain numbers clearly |
| Interest | Wants the kind of work I offer |
| Communication | Responds cleanly and follows through |
| Gut check | Something feels aligned or it does not |
Then scout.
For contractors, I am always looking. A work van at a stoplight. A crew at a supply house. A referral from another contractor I trust. For other vendors, I look harder when the role matters or when I know my current player is weak.
Then build the pipeline.
Your depth chart is a CRM. Active, backup, prospect, dead. You need status, notes, contact info, type, and the next action. A list of names is not enough.
Then lead and manage.
Set expectations. Keep accountability clear. Build relationship capital. Make deposits by being clear, paying fast, and not wasting people’s time. Keep one head to chop. If something goes wrong, there should be one person who owns the outcome.
Then rate them.
You are always deciding whether the current starter stays the starter. Sometimes you begin with tents. You use a good-enough vendor because the business has to move. Then you come back and fortify.
The vendor bench is not a list. It is a living pipeline that protects the business from one person becoming load-bearing.
Speed, Price, and Quality Are Mostly About You
People say with vendors you can pick two: speed, price, quality.
That is partly true, but it hides the real lesson.
Speed is often about your deficiencies. If you need something right now, why? Did you buy a thin deal? Did you wait too long? Did you fail to keep a bench? Did your operating system miss the trigger?
Price is often about your understanding. If you do not know what something should cost, you cannot tell the difference between fair pricing and fear tax. Contractors can smell that.
Quality is about expectation alignment. Quality does not always mean premium. Rolled vinyl flooring done exactly to the expected standard can be quality. Hand-finished hardwood in the wrong house can be stupid.
You manage quality by defining expectations and holding the paycheck until the work matches the agreement.
The deeper point is that all three come back to you:
- Better systems improve speed.
- Better knowledge improves price.
- Better expectations improve quality.
That is why I keep coming back to the same point. You are the asset.
Not the employee. Not the contractor. Not the vendor list. Not the AI.
You.
The best depth chart in the world is still only as good as the operator leading it.
FAQ
Do I need employees to scale a real estate business?
No. You need capacity, and capacity can come from vendors, AI, VAs, software, contractors, lenders, agents, and property managers. Employees are one way to add capacity, but they are not the default move.
When should I add the Depth Chart to my business?
Immediately, but start simple. You do not need every vendor on day one. Start with the business drivers: deal flow, capital, contractors, and the path to sell or hold the property.
What is the biggest mistake beginners make with vendors?
They expect vendors to solve problems the operator has not defined. If your scope, expectations, budget, CRM, or operating system is a mess, a vendor usually makes the mess move faster.
Are AI and VAs replacements for an assistant?
In my system, AI handles bounded decision work and VAs handle follow-through after the operating system defines the work. I still keep the judgment work, and physical errands still need someone local.
What if my best contractor, lender, or property manager leaves?
That is exactly why you build a depth chart. If one person leaving can wreck the business, that person was load-bearing. Your job is to build the skill and pipeline to replace them before you need to.