Real Estate Virtual Assistant Rates: Hourly vs Project vs Retainer (What Investors Should Pay in 2026)
- Start hourly if scope changes week to week or you’re still figuring out what you actually need.
- Use a flat project rate when you can define deliverables and “done” in writing (with clear revision limits).
- Move to a retainer once the workload is stable and the VA owns a workflow with simple KPIs.
- If you can’t define “done” or “owned,” don’t lock pricing yet—hourly is the safer default.
Rule of thumb: unclear scope = hourly | defined deliverable = project | stable ownership = retainer.
- Small to mid-size investors budgeting for support (without guessing)
- Operators deciding between hourly vs project pricing
- Teams trying to match pay to scope and accountability
- People looking for VA jobs or “salary” listings
- Teams expecting a VA to fix broken systems for cheap
- Anyone unwilling to define scope, handoffs, and review cadence
- When hourly vs project vs retainer is the right move
- Practical hourly ranges and what they usually include
- How to price common projects without getting burned
- A copy/paste scope + pricing template you can use
The ranges below are budgeting ranges, not promises. Your real number depends on scope clarity, volume, and how independently you need the VA to operate.
The real problem: investors price “a VA,” but they’re actually buying a system
Most pricing confusion happens because investors treat a VA like a commodity: “How much per hour?” But the moment you expect ownership—consistent follow-up, clean CRM data, reliable handoffs—you’re not buying hours. You’re buying throughput and reliability.
The fastest way to overpay is to buy hours with no scope. The fastest way to under-hire is to buy cheap “task help” while expecting an operator.
Hourly vs Project vs Retainer: which structure fits your situation
For small to mid-size investors, the real decision is usually hourly vs project. Retainers make sense later—once scope, volume, and workflow are stable.
| Pricing structure | Best for | What can go wrong | How to make it work |
|---|---|---|---|
| Hourly | Variable workload, ongoing support, testing a hire, mixed task lists | Scope creep, “busy work,” unclear priorities, inconsistent output | Define weekly priorities, track a few KPIs, require clean CRM notes, review weekly |
| Fixed project | One-time builds or cleanups (list cleanup, CRM cleanup, SOP drafting, skip tracing batches) | Vague definitions, rework, endless revisions, hidden edge cases | Lock deliverables, acceptance criteria, revision limits, and handoff format upfront |
| Monthly retainer | Stable recurring workload, coverage needs, workflow ownership with accountability | Paying for “availability” without measurable output, misaligned expectations | Tie retainer to owned workflows, coverage windows, and a monthly KPI scoreboard |
If you can’t describe the work in deliverables or weekly outcomes, you’re not ready for fixed pricing or a retainer. Start hourly, get scope clean, then upgrade the structure.
Typical hourly rates investors budget around (2026)
Hourly pricing works best when you have changing priorities week to week, or you’re still figuring out what you actually need. These ranges are meant to help you budget by scope.
| Scope of work | Typical responsibilities | Common hourly budgeting band |
|---|---|---|
| Task support | Data entry, basic CRM updates, inbox cleanup, list formatting, admin support | $10–$20 per hour |
| Real-estate–specific REVA | Lead follow-up, appointment setting, CRM hygiene, pipeline updates, basic reporting | $15–$35 per hour |
| Workflow owner / senior REVA | End-to-end follow-up ownership, KPI tracking, coordination with acquisitions or agents, light ops responsibility | $25–$45 per hour |
| US-based or premium coverage | Time-zone-aligned support, high reliability, heavier communication load, partial ops or executive-style support | $35–$60+ per hour |
Don’t use these ranges as a negotiation tactic. Use them to sanity-check whether your expectations match the scope you’re buying.
How investors should think about project (flat-rate) pricing
Fixed project pricing is common for small investors because it feels clean: pay for a deliverable, avoid ongoing hourly drift. It works—when the project has tight boundaries.
Where it goes sideways: “Can you clean the CRM?” is not a project. It’s a category of work. A real project is: “Normalize these fields, dedupe contacts, fix stage logic, and deliver a report.”
What must be defined for any project rate
- Deliverables: exact outputs (files, dashboards, SOP docs, cleaned lists, CRM fields)
- Acceptance criteria: what “done” means (examples, required fields, formatting rules)
- Inputs you provide: access, exports, naming conventions, lead stage definitions
- Revision limits: what counts as a revision vs a new request
- Handoff format: where everything lives and how you’ll verify completion
If you can’t define acceptance criteria in writing, keep it hourly until you can.
Examples of projects that price cleanly
- List cleanup + import prep: standardize columns, remove duplicates, validate phone fields, output a clean CSV
- CRM hygiene reset: dedupe rules, fix lead stages, normalize tags, create a “required fields” checklist
- Cold calling script pack: opening, objections, qualification questions, disposition definitions
- Basic KPI scoreboard: weekly tracking sheet + definitions + sample report format
- Transaction file system setup: folder structure + checklist + handoff rules
When a retainer actually makes sense (and when it doesn’t)
Retainers are for stability. If your week-to-week needs are unpredictable, a retainer often turns into paying for “availability” without clear output.
- You have recurring workload every week
- The VA owns a workflow end-to-end
- You need consistent coverage windows
- You can measure output (even if it’s not “deals closed”)
- Scope changes daily and priorities aren’t clear
- No one reviews performance or QA
- You’re outsourcing decision-making without structure
- You don’t have a defined handoff process
Good retainers are built around owned workflows and reporting—not around “X hours included.” Hours can be a planning number, but outcomes are the anchor.
Day-to-day workflow implications (what you must have in place)
Pricing problems are usually workflow problems. If you want predictable output, you need predictable handoffs. Here are the operator basics that make any pricing structure work.
- Defined lead stages and dispositions: everyone uses the same labels, or reporting is garbage
- Minimum CRM note standard: what gets logged after every touch (and where)
- Handoff rules: what gets escalated, to whom, and how fast
- Weekly review cadence: 15–30 minutes to review KPIs, blockers, and next week’s priorities
KPIs that support pricing decisions (activity vs outcome)
You can’t judge value if you only track hours. Track a few leading indicators that tell you whether the workflow is healthy. Split them into activity (inputs) and outcomes (results of those inputs).
- Touches completed (calls, texts, emails) by list segment
- CRM notes completeness (required fields filled)
- Speed-to-lead (time from lead to first touch, if applicable)
- List coverage (how many leads were actually worked)
- Contact rate (for outbound roles)
- Appointments set / kept (show rate)
- Qualified lead handoffs accepted by acquisitions
- Follow-up compliance (leads not going stale)
Don’t pay a workflow owner rate while tracking only “hours worked.” If you want ownership, measure ownership.
Tools and stack: keep it boring and consistent
You don’t need a fancy stack to price a VA correctly. You need consistency: one CRM source of truth, one place for tasks, one reporting format.
- CRM: a single system where stages, dispositions, and notes live
- Task tracking: basic board or checklist for weekly priorities
- Reporting: a weekly KPI snapshot (simple is fine)
- Documentation: SOPs for repeating processes and handoffs
Common failure modes (and what they look like)
- Scope drift: “just one more thing” turns hourly into chaos or breaks fixed pricing
- Undefined “done”: projects never finish because acceptance criteria were never written
- CRM decay: notes are inconsistent, stages are wrong, follow-up becomes random
- Unowned handoffs: VA flags leads, acquisitions ignores them, everyone blames everyone
- No review cadence: problems become “performance issues” because no one caught them early
Implementation template: scope + pricing sheet (copy/paste)
Use this template to decide whether a task should be hourly, project, or retainer. It forces scope clarity and prevents pricing arguments later.
| Work item | Type (hourly / project / retainer) | Definition of done (acceptance criteria) | Inputs required from investor | Check-in cadence |
|---|---|---|---|---|
| Example: CRM cleanup | Project (if defined) or hourly (if exploratory) | Duplicates removed, lead stages standardized, required fields enforced, export report delivered | CRM access, stage definitions, sample “good” record | Midpoint review + final acceptance |
| Example: Lead follow-up | Hourly (early) → retainer (once stable) | All new leads touched within agreed window, notes logged, appointments handed off cleanly | Scripts, dispositions, escalation rules | Weekly KPI review |
If you can define “done,” project pricing becomes fair. If you can define “owned,” retainers become fair.
Want to sanity-check scope against real roles?
Live job postings reveal what teams actually expect at different price points and responsibility levels.
FAQ
Investors usually budget in bands based on scope: task support runs lower, real-estate–specific REVA support sits in a mid range, and workflow owners or premium coverage cost more. The key is matching rate to responsibility and expected independence.
Use hourly when scope is still evolving or priorities change weekly. Use a project rate when you can define deliverables and “done” in writing (including revision limits and handoff format).
Retainers make sense once workload is stable and the VA owns a workflow end-to-end with measurable outputs and a clear review cadence. If scope changes daily, start hourly.
Lock deliverables, acceptance criteria, inputs required from you, revision limits, and handoff format upfront. If you can’t define “done,” keep it hourly until you can.
Track a few leading indicators that reflect workflow health: CRM note completeness, list coverage, speed-to-lead (when applicable), follow-up compliance, and qualified handoffs accepted by acquisitions.
Post a role with clear scope and pricing expectations
Fewer mismatches, cleaner interviews, faster onboarding.
Post a job