Commercial Land Sourcing Engine with SDR shadowing/email support and CRM maintenance and research

Ops Lead — Land Sourcing Engine (CRM + Data/Scraping + Market Intel + SDR QA) | Australia hours

One-line summary

Build and run the backend machine for commercial property development land-sourcing platform: agent list-building (scraping/manual), CRM architecture + QA, comms stack integration, market intel reporting, and SDR shadowing/email inbox management in AEST.

Your Responsibilities

A) Agent List-Building + Scraping / Market Mapping
• Build and maintain clean lists of industrial/commercial agents by target city/catchment
• Use RealCommercial.com.au primarily as a directory to identify agents/agencies (plus other directories as needed)
• Data hygiene: de-dupe, standardize agency names, ensure correct phone/email, tag by city/corridor
• Maintain “A-list / B-list” and rainmaker tagging (who actually controls off-market)

Deliverable: a structured master agent list ready for SDR outreach and cadence.

B) CRM Architecture + Implementation (Pipedrive preferred)
• Implement CRM as two linked databases:
1. Agents/Agencies (Contacts) = relationship owner, cadence, tags, notes
2. Land Opportunities (Deals/Parcels) = each site as its own record, linked to agent
• Add required custom fields + tags (zoning, site area, frontage, exposure, access, services, constraints, timing, price guide $/sqm, comps mentioned, follow-up date, etc.)
• Build pipelines/stages, views/filters, and dashboards for weekly decision-making
• Implement “non-negotiable logging” rules: no missing minimum fields

Deliverable: CRM live with schema, stages, required fields, and QA rules.

C) Comms Stack Integration (Dialpad / Shared inbox / Logging)
• Integrate Dialpad (or other agreed VoIP) with CRM for call logging (and SMS logging if supported)
• Set up shared mailbox / email logging into CRM so all contact touches are captured
• Set up basic automations: follow-up tasks, reminders, cadence triggers

Deliverable: end-to-end workflow where calls/emails log correctly and tasks are generated.

D) SDR Shadowing + QA + Cadence Enforcement (AEST overlap required) + Communal Email/SMS Inbox Management
• Shadow the SDR during early call blocks (AEST)
• Ensure each call outcome is logged correctly and follow-ups scheduled
• Maintain cadence rules:
• A-list: touch every 2–4 weeks
• B-list: touch every 4–8 weeks
• Provide coaching feedback via QA, not vibes (completeness, outcomes, speed-to-log)
• Shared inbox management (deal responses + routing)

Monitor the communal email inbox and:
• Respond to agent emails same day where possible (templates provided; personalize lightly).
• Request missing documents (plan/IM, services info, zoning, timing, price guide).
• Log the interaction into CRM (contact + deal).
• Escalate “maybe yes” opportunities to the principal quickly with a short summary and any relevant info

Deliverable: SDR runs smoothly with high-quality logging and consistent follow-up. No inbound deal gets lost; every inbound is logged + actioned.

E) Weekly Reporting + Market Intel (this is not optional)
• Weekly report covering:
• outreach volume + connects
• database additions
• opportunities received (count + quality)
• follow-ups due next week
• data completeness/QA pass rate
• Market intel captured systematically:
• corridor pricing $/sqm (arterial exposure industrial/commercial)
• upcoming releases / who controls them
• which agencies consistently have off-market stock
• qualitative notes that improve agent credibility and hit-rate

Deliverable: one-page weekly report + updated intel log.

⸻

Working Hours (Non-negotiable)
• Must overlap Australian Eastern time (AEST) for SDR shadowing/training
• Minimum: 2–3 hours overlap on agreed SDR blocks (e.g., 9:30–11:30am AEST) at least 4 days/week

⸻

Required Experience (Must-have)
• Real estate cold calling operations experience (commercial/industrial preferred)
• You don’t need to be the caller, but you must understand the workflow and QA it
• CRM build + administration experience (Pipedrive strongly preferred)
• Scraping/manual list-building experience (directories, agent pages, de-dupe, enrichment)
• Strong process discipline: checklists, QA, “hard standards,” and reporting
• Comfortable being accountable for backend continuity (the machine must not depend on one SDR)