PRG LandTech — Official Team Onboarding SOP
Version 1.0 • Effective Immediately • Owner: Founder / Leadership
1. Objective
- Eliminate onboarding inconsistency • Reduce ramp‑up time • Prevent pipeline stagnation
- Protect system integrity • Ensure cultural alignment • Standardize performance expectations
- You are not joining a course — you are joining an operating system.
2. Role Classification
All members are classified before onboarding. Each role has different KPIs and access. No universal access.
3. Pre‑Onboarding (72h)
Administrative
- Offer agreement & NDA signed
- Compensation structure confirmed
- W‑9 / employment docs • Identity verification • Payment setup
System Access
- Email, CRM, Lead dashboard, Tasks, Communications
- Buyer DB (if applicable) • Shared drive access
Assigned mentor & team lead must be recorded in the onboarding tracker.
4. Day 1 – Structural Orientation (90m)
- Mission alignment: Why PRG • Why structure • Accountability expectations
- System overview with a real deal: entry → tasks → exit
- Behavioral standards: 24‑hour comms • No silent confusion • Document all actions
5. Week 1 – System Immersion
Objective: Understand before acting. Independent offers/negotiations/listings are not allowed until shadowing completes.
6. Week 2 – Controlled Task Execution
Objective: Supervised action; all work is reviewed before going live.
- Acq: price 5 sample leads • draft 3 offers • 3 seller scripts
- Dispo: 3 listings • 10 buyers contacted • follow‑up cadence
- Ops: clean 10 CRM records • audit 5 files • assign corrective tasks
7. Week 3 – Limited Live Pipeline Access
- Acq: pre‑qualified leads; offers/contracts require approval
- Dispo: 1–2 properties; log conversations; daily activity report
- Ops: CRM management • lead triage • task enforcement
- KPIs begin formal tracking
8. Week 4 – Performance Review
- Evaluate execution, documentation, clarity, initiative, culture
- Decision: Advance • Extend 2 weeks • Reassign • Terminate
- Performance only — no emotion.
9. Performance Metrics (Role Specific)
10. Leadership Responsibility
Leadership reviews pipeline weekly, prevents stagnation, supports pricing/dispo strategy, and removes bottlenecks. Leadership is accountable for team output, not just personal deals.
11. Escalation Protocol
If under contract and no buyer activity in 72h, no internal update in 48h, or no task progression in 48h — escalate immediately. No property sits silently.
12. Failure Management
Direct correction → Written reset → 14‑day plan → Re‑evaluation. Clear corrective structure — no vague warnings.
13. Culture Statement
We are a structured execution team. We move together, transparently, with discipline. You are not here to experiment — you are here to operate.