WREA FY27 Growth Strategy & Implementation Plan

Version 1.3 · refined 27 July 2026 · FY27 = July 2026 – June 2027 · Prepared for Thomas (CEO)

Thesis: grow gross profit ~60% in a market whose turnover is forecast to shrink ~20% — by owning the "what's my home worth" moment, weaponising WREA's proprietary agent-performance data, monetising the dormant CRM database, converting more of the leads we already buy, and making every paid dollar bid against real gross profit. Growth from share capture and yield, not from buying more of a shrinking tide.

Evidence base: 12-week CRM source economics (pulled live 2026-07-02), three weekly growth-operator reports (8–28 June), paid-media governance rules, staff-meeting market brief, the agent-data platform docs, both July build specs (email nurture, property estimate tool), competitor teardowns, and independently verified market/competitor research (RBA, Westpac, Cotality, competitor filings, US/UK marketplace playbooks). Draft v1.0 was adversarially reviewed by two independent passes (numbers reconciliation + cold board-advisor read); v1.1 incorporates the fixes.

The year on one page

1. Where the business actually is

From the live 12-week CRM pull (6 Apr – 28 Jun 2026): 3,295 leads → 908 intros, $361k ad spend, $398 blended cost/intro, $732 revenue/intro, $334 GP/intro. Annualised: roughly a $2.9M revenue run-rate with ~$1.3M/yr contribution after ad cost (staff and other opex sit below this line — every "GP" figure in this document means contribution after ad cost only). Intro mix: 86% paid (Google ~70%, Microsoft ~16%), 14% organic.

908
Intros / 12 weeks (~76/wk)
$398
Blended cost per intro
$732
Revenue per intro
28%
Lead → intro conversion (12wk avg)
~$715–895
GP per organic intro (zero ad cost)
0
Nurture emails sent to 14k emailable contacts

Six structural facts the strategy is built on

  1. The paid engine is fragile, not just expensive. Weekly GP margin swung +87% → −3.8% → +66% across three June weeks. Google weekly cost/intro ranged $410–$692 in June; in the worst week (15–21 June) the Google channel netted $16 GP per intro ($708 revenue − $692 cost). Serving budget exposure is $39.2k/week against a $25k cap (open P0, two weeks running), and 30 unlogged account changes hit in one week. This engine funds the company and it is one bad month from funding nothing.
  2. Organic intros are worth ~2× paid intros and cost nothing — but organic is small and softening. ~10–13 intros/week at $715–895 GP each; organic lead CVR slid 1.5% → 1.4% and organic form-completion (Clarity SubmitForm) is 2.04% vs 5.07% on paid landing pages. A single WREA page (/australian-house-prices-graph…) gets ~880 organic users/week and produces zero leads.
  3. Lead→intro conversion moves 26–39% week to week, and nobody is managing it as a number. WREA has 573k call-log rows and 173k call recordings (no transcripts) — the raw material for a sales-conversion system exists and is untouched. A 5-point lift on ~3,300 leads/yr is ~165 intros — as big as the entire email opportunity.
  4. WREA is sitting on an unmonetised proprietary data asset none of the competitors can cheaply copy: the agent-intelligence platform — ~17.2k suburbs, 42k agents, 599k listings, ~1.05M sold-history rows, per-agent sold counts / median price / days-on-market, with a public-safe rankings API already feeding WordPress/Laravel. RateMyAgent built an 85k-visit organic machine from agent pages with weaker per-visit economics; WREA has the data and ~9k visits.
  5. The database is dormant. ~30.5k property-owner contacts (14k emailable), zero nurture sends, while OpenAgent runs a 160-thread suburb-personalised email machine against the same sellers. Both build specs to fix this (nurture OS + estimate tool as capture engine) were completed this week — the plans exist; FY27 is execution.
  6. The team is small and named: Thomas (CEO), David (paid media), Felix (dev), Mark, sales + support. Everything below is sequenced for one dev plus AI-operator leverage (the weekly growth pack, Codex/Claude lanes) — with a pre-declared descope order when Q1 gets tight (§7).

2. FY27 market reality — and the one-off opportunity inside it

Fact (verified July 2026)Strategic consequence
RBA cash rate back at 4.35% after three 2026 hikes; big-four consensus: no cuts in FY27 (Westpac sees two more hikes).No rate-cut demand wave is coming to save lead volume. Plan for flat-to-down seller demand.
May 2026 Budget: negative-gearing quarantine on new established-property investments + CGT discount replaced by indexation from July 2027 (existing holdings grandfathered). Westpac: investor activity −34%, total turnover −20%.The addressable pool of transactions shrinks ~20%. Growth must come from share and yield. But grandfathering creates a time-boxed investor sell-decision wave before July 2027 — a genuine one-off demand spike in H2 FY27.
WREA already ranks with zero competitor presence on: capital gains tax calculator (9,900/mo), determine capital gains (5,400), ATO clearance certificate (5,400).WREA is — accidentally — the best-positioned player in the country for investor-exit search demand. Nobody else owns this cluster. This is the single cheapest large campaign available in FY27 (§6, Lever 5a).
Divergent capitals: Perth +13%, Brisbane +9%, Adelaide +7% forecast; Sydney −3%, Melbourne −4%; clearance ~50%.Two seller psychologies to serve: hot-market sellers (WA/QLD/SA — speed and yield) and anxious-market sellers (NSW/VIC — exactly the "which agent can defend my price?" positioning). Geographic budget and content weighting follows this split.
AI Overviews: informational queries lose 35–64% of clicks; transactional/local real-estate queries are among the least affected; being cited inside AIOs lifts CTR.Doubles the case for tools + local/transactional pages over generic articles, and for structured, citable first-party data (fee ranges, agent stats, suburb medians) that AI engines quote — with WREA's name on it.
Spring selling season: September–November 2026.Hard deadline: every FY27 asset that touches seller acquisition must be live by 1 September 2026. Q1 is a build quarter with a date, not a vibe.

3. Competitor read

CompetitorWhat they actually are (verified)FY27 posture toward them
OpenAgentThe real full-funnel competitor: 924 suburb pages, OpenEstimates (valuation volume growing 28.5k→34.5k in June alone), paid valuation ads, 160-thread suburb-personalised email machine. A$23.6M raised; ~2.1M visits/yr; no visible 2025–26 product news (possibly consolidating).Copy the system (local page → valuation capture → nurture → comparison CTA), beat them on data specificity and fee/strategy honesty. Their sitemap added zero new URLs in late June — they are not sprinting; the window to close the suburb/valuation gap is open.
LocalAgentFinderPaid-heavy (Semrush-estimated ~$28k/mo — directional), disciplined conversion funnel, strong property-value page (~89k sampled vol), bought a conveyancer (2024) — monetisation deepening. ~49 staff.Their valuation tool is the benchmark to beat on credibility (the V3 tool spec already does). Their conveyancing move validates Lever 5's ancillary-revenue path.
RateMyAgent (ASX:RMY)85k organic visits from 12k agent-directory pages, but a subscale, loss-making review/awards business (FY25 rev A$21.5M, FY26 forecast cut; market cap ~A$20M). Not a direct seller-lead competitor.Proof-of-demand, not a threat: their traffic shows agent-evidence pages are the biggest organic pool in the category. WREA has better per-agent data economics (each visit can become a $732 intro, not an ad impression). Take their traffic playbook, attach it to a referral P&L.
Global patternHomeLight → embedded finance (equity unlock via 40+ lenders, then AI closing agent); Clever → white-label agent-matching for mortgage servicers; LAF → conveyancing. The funded winners all deepened revenue per seller rather than buying more top-of-funnel.FY27 pilots ancillary monetisation (broker/conveyancer referrals) small and late (Q3–Q4), after the core levers are live. Direction, not distraction.

4. The strategy: six levers

One sentence: stop renting all your demand from a volatile auction — convert WREA's four dormant assets (the valuation moment, the agent-performance data, the CRM database, and the leads you already pay for but under-convert) into owned demand and higher yield, while re-plumbing paid to bid on gross profit instead of leads.

Lever 1Own the "what's my home worth?" moment. Ship the property estimate tool as the acquisition anchor (spec done), build the /property-value hub, and take the 49.5k+/mo valuation cluster where WREA is currently absent. The single biggest demand pool adjacent to the business, both competitors are farming it, and the AIO shift favours tools over articles.
Lever 2Weaponise the agent-evidence data (the moat). Turn the 42k-agent / 1.05M-sold-row intelligence platform into public agent-evidence and suburb-market pages, sales scripts, and estimate-tool proof. This is RateMyAgent's traffic engine attached to WREA's referral economics — and the "confidence-building" thesis from your own staff brief made concrete.
Lever 3Monetise the database. Execute the nurture operating system (spec done): rescue lane for the ~137/month stalling leads (SMS decision for the two-thirds without email), then value-refresh and local-market utility lanes across the 14k emailable contacts. OpenAgent proves the category; WREA's current send volume is zero.
Lever 4Re-plumb paid to bid on gross profit. Value-based bidding with CRM GP uploaded as offline conversion values, automated budget-exposure guardrails, change-log discipline, weekly leak-kills. Not uncontrolled spend — keep the same ~$30k conditional weekly boundary working harder and no longer able to silently lose money.
Lever 5Deepen yield per seller. (a) The investor-exit campaign riding the pre-July-2027 CGT deadline through WREA's unopposed CGT/ATO content; (b) route intros to agents that actually convert (yield routing from own data); (c) pilot broker/conveyancer referral revenue. The proven global pathway, sized for a small team.
Lever 6Convert more of what we already have. Sales-floor speed-to-lead (SLA measurement, attempt cadence, AI mining of the 173k call recordings) plus a monthly CRO experiment cadence on the site (organic form completion 2.04% vs paid 5.07% — the gap is fixable). Lead→intro from 28% toward 33%+. The cheapest intros in the company are the ones already paid for.

5. FY27 targets, decomposition, and the GP bridge

5.1 Headline targets (phased H1 / H2 — most levers are H2-weighted; don't misread October as failure)

MetricFY26 exit run-rateDec 2026 exitJun 2027 exit (FY27 target)Note
Intros / year (run-rate)~3,935~4,400~5,400 (+37%)Decomposition in §5.2 — against a −20% market ⇒ implied share ~+70%
Contribution after ad cost~$1.31M~$1.55M~$2.1M plan / ~$1.8M baseThe number the year is judged on
Owned-channel intro share (organic + email + tool)~14%~20%25–30%The fragility fix — compounds into FY28
Lead → intro conversion28%30%≥33%Lever 6; measured weekly in the pack
Blended cost / intro$398$370≤$330Mix shift + value bidding, not spend cuts
Revenue / intro$732$750≥$790Yield routing + hot-market coverage
Emailable, consented contacts~14,050~15,500≥18,000Tool capture ramp: 150/mo (Q2) → 350–500/mo (Q3–Q4)

5.2 Intro decomposition — where +1,450 intros actually come from

SourceFY26 run-rateFY27 planHow
Paid (Google + Microsoft)~3,385~3,780 (+12%)Flat budget; value bidding + estimate-tool landing CVR + leak-kills + geographic re-weighting. Deliberately modest — the auction is not the growth story.
Organic (existing + new pages)~550~800Agent-evidence + suburb pages + /property-value hub + CRO lifting organic CVR 2.0% → 3.0% (that CVR lift alone ≈ +40–60 intros/yr on current traffic).
Estimate tool (direct + paid-assisted, net of cannibalisation)0~350–450Ramp: 2k sessions/mo by Dec → 4k+/mo by Jun; ~8% contact capture; ~30% lead→intro. H2-weighted.
Email/nurture (lift vs holdout)0~150–250Rescue (~137/mo qualified) + value-refresh + utility lanes; every claim holdout-measured.
Investor-exit campaign0~100–150H2 only; content + email + modest exact-match paid on an unopposed cluster.
Total~3,935~5,200–5,400Owned share lands 25–30% depending on tool/SEO ramp

Sales-conversion lift (Lever 6) is embedded in the per-source rates above rather than double-counted as a separate line: +5pts lead→intro on ~3,300 paid+organic leads is worth ~165 intros and is the main mechanism behind the paid and organic lines improving without extra spend.

5.3 GP bridge (annualised contribution after ad cost)

ComponentGP impactBasis
Market headwind on baseline−$130k to −$250kWestpac −20% turnover scenario, partially offset by hot WA/QLD/SA markets and the investor wave
L4 Paid efficiency (value bidding + leak-kills + guardrails)+$150k to +$250kOffline-value bidding typically improves CPA/value 15–30% (treat as industry heuristic, not a promise); June's named leaks (−$858, −$1,165 ad groups) show the recoverable floor
L6 Sales speed-to-lead + site CRO+$100k to +$180k+5pts lead→intro ≈ 165 intros × ~$700; organic CVR 2→3% ≈ +40–60 intros
L3 Email/nurture (lift vs holdout)+$110k to +$180k150–250 incremental intros at ~$700+ GP; assumes ~1.5–2.5% annual intro conversion of the emailable base — OpenAgent's program implies the category supports this
L1 Estimate tool+$150k to +$300k§5.2 ramp math; both competitors pay for this intent today, which prices the demand as real
L2 Agent-evidence + suburb pages (H2-weighted)+$80k to +$200k~250 incremental organic intros at ~2× GP; SEO lag is why the low end is low
L5 Investor-exit + yield routing + partner pilot+$80k to +$150kTime-boxed CGT wave + revenue/intro $732→$790 from routing
Component span$1.85M – $2.6M (sum on baseline $1.31M)Plan = $2.1M (below midpoint); base case = $1.8M if SEO and tool ramp slowly. Be honest that the ranges are planning judgment, not arithmetic certainty — the weekly pack exists precisely to correct course monthly.

Every component is measured in the existing weekly pack (CRM source economics is the truth layer); email and investor-campaign components carry mandatory holdouts so lift is real, not attributed noise. If GP tracks below ~$1.55M run-rate at the December gate, §10's cash rule applies.

6. Lever detail and plays

Lever 1 Own the valuation moment

Lever 2 Weaponise the agent-evidence data

Lever 3 Monetise the database

Lever 4 Re-plumb paid to bid on gross profit

Lever 5 Deepen yield per seller

Lever 6 Convert more of what we already have

6.7 Data confidence and public-evidence dependencies

Added 2 Jul 2026. The levers above lean on WREA's proprietary data being right and defensible. Several in-flight data projects are therefore explicit FY27 dependencies with owners and gates — not background evidence. Each appears on the execution board with the ID shown.

DependencyFY27 operating ruleGates / feedsBoard
Self-serve agent shortlist and source filteringSelf-serve is the next major customer-facing launch, but only as a controlled cohort. The displayed agent shortlist must pass an agreed accuracy check; no agent, agency or data unique to REA can be exposed; and current scraper/data-confidence evidence must be accepted. Total scraper-backlog completion is not required when the launch cohort itself is covered by accepted evidence.Controls whether the existing self-serve journey can move from built to safely live; depends on the L2-6 evidence lane without waiting for every lower-priority backlog itemL2-8
RMA public evidence (RateMyAgent sitemaps)A strong positive-only public-evidence source — but only when driven by fresh sitemap snapshots with the sold-date guard (sold sitemap ≈ 507k rows rolling ~12 months; 81% coverage of recent REA sold). The stale legacy rma_listings table must not be consulted. Absence is never proof; individual RMA pages are DataDome-protected — sitemaps only.Defensibility of listing-status claims behind L2 agent-evidence pages and sales conversationsL2-7
REA listing-status reconciliation (ListingReconciler)REA sold PDP sitemap = sold-candidate/public evidence. REA buy PDP sitemap = discovery/change detection only — presence ≠ live, absence ≠ withdrawn. Status corrections require GraphQL/agent-profile or exact-page proof, applied only through the existing safe ListingReconciler path (measure → verify → correct; no-write report first; Thomas-approved incl. legal coverage).Hard gate for L2-2 (public agent pages must show reconciled counts) and for L5b yield routing (routing on wrong counts routes wrong)L2-6
OnTheHouse / ODIN valuation fallbackA cautious licensed/cache fallback: OTH suburb market-trends cache sits below the REA cache and above broad suburb/state defaults in the fallback order; it must never live-block a lead form; consumer-facing display approval (the DR2-style legal/commercial check) remains a standing gate. Thin-data suburbs (AVM medians with zero recent sales) never trigger "market moved" claims.L1 estimate-tool fallback tier (N1 "fail useful") and L3 value-refresh email honestyL1-8
CloakBrowser / sidecar reliabilityAn execution and data-freshness dependency, not an afterthought: direct production reads have proved strong, but /fetch validation must become page-aware/adaptive before the sidecar is relied on as a broad verification path (reconciliation Step-2 checks, OTH warming). Until then, sidecar-verified corrections stay sample-gated.Freshness of everything in L1/L2; reconciliation verify stepOPS-4
CRM agent search / recommended-agent qualityTreated as part of sales conversion and trust (Lever 6), not a technical bug category: consultants sell from these surfaces and sellers see their output. Search/recommendation defects get triaged with the same weekly visibility as funnel metrics.L6 lead→intro target; consultant trust in the data the whole strategy sellsL6-6

Principle: no proprietary data point goes public-facing (pages, tool, emails, routing) ahead of its confidence gate. The board makes these gates visible in the weekly review, so "data not ready" is a named blocker, never a silent assumption.

7. Quarterly implementation plan

Q1 · Jul–Sep 2026 Build the machine before spring (hard deadline: 1 September)

Felix's quarter, sequenced honestly (≈9 working weeks): the immediate customer-facing release is a controlled self-serve agent-connection cohort using the journey already built, after the L2-8 shortlist, source-filtering and scraper/data-confidence gates pass. The other committed lanes remain: guardrails + dead-traffic CTAs + speed-to-lead reporting; nurture P0 + P1 rescue; estimate tool P0 + P1; then beta hardening + agent-evidence template wiring. Agent-evidence page generation runs on the content/AI lane, not Felix. Offline-upload build is Felix (small), validation and bidding migration is David. Pre-declared descope order if the quarter slips: agent-evidence pages → tool P2 (emailed report, it's Q2 anyway) → utility email lanes. Rescue lane and tool P0/P1 do not slip; 1 September does not move.

LeverDeliverablesOwner
L4 (first!)Close the budget-exposure P0 (July, week 1). Pause the ended-but-enabled campaign. Change-log discipline live. Offline GP-value conversion upload built and validating. Weekly leak-kill ritual in the Monday pack.David + Felix + Thomas
L6First-contact-time + attempt-count metrics remain a reporting improvement; JS-error form fixes remain small hygiene work. General call-attempt optimisation is not the main Q1 launch. The Property Value Form 2.6% conversion readout moves into the Q2 Property Value Hub / paid-scale checklist.Thomas + sales, Felix (metrics)
L1Estimate tool P0 rails + P1 controlled beta (per spec); DR1 listings verification (Thomas) and ODIN tier check closed; public launch 1 Sep. Dead-traffic conversion: house-prices-graph + calculators pages get tool CTAs (wk 1–2, near-zero dev).Felix + Thomas
L3Nurture P0 (defuse workflow, suppression, eligibility, preview) + P1 rescue pilot with holdout (per spec).Felix
L2Self-serve agent connection first: close the shortlist, source-filtering and scraper/data-confidence gates, then run a controlled production cohort. Continue the agent-evidence template v2 and top-100 suburb-page lane for 1 Sep, with public counts still gated by reconciled evidence.Felix + Thomas (self-serve); Felix (template) + content
GateQ1 exit review: self-serve controlled cohort live with measurable selection-to-intro outcomes; tool public; rescue sending; agent pages live; value upload feeding Google; exposure P0 closed; speed-to-lead on the Monday page. Anything not live gets a named blocker and a date.Thomas

Q2 · Oct–Dec 2026 Spring harvest

LeverDeliverablesOwner
L4tROAS live on Agent (National) once signal floor met; scale Microsoft within cap; shift marginal budget to WA/QLD/SA and exact-match winners. Paid landing traffic progressively pointed at the estimate tool (A/B vs standard funnel).David
L1/L2/property-value hub live; suburb-market pages 50–100 (spring cohort); estimate-tool embeds on suburb + calculator pages; first Agent Market Index story (October, Thomas + AI-drafted) with PR push.Felix + content + Thomas
L3Nurture P2: value-refresh lane (stage-branched) + VIC local utility monthly send; emailed estimate report + magic-link verification live (tool P2). SMS rescue decision after email-rescue readout.Felix, Thomas (SMS call)
L6AI call-transcript pilot (sample of 173k recordings) → script/objection readout; CRO experiment cadence running (1/month); organic CVR trending toward 2.5%.Thomas + AI lane
GateQ2 exit review: owned-channel intro share ≥20%; tool ≥2k sessions/mo, ≥150 verified captures/mo; lead→intro ≥30%; no negative-GP Google week since tROAS; suburb pages showing Search Console traction (else pause expansion). GP run-rate check vs $1.55M (§10 cash rule).Thomas

Q3 · Jan–Mar 2027 The investor-exit wave

LeverDeliverablesOwner
L5aInvestor-exit campaign launch (January): hub + net-proceeds calculator chain, investor email lane (CRM investor segment, holdout-measured), exact-match paid layer, February Index story angled on investor selling. The quarter's headline swing.Thomas + all
L5bYield routing v1: agent conversion scorecard from own data; routing rules with sales team; hot-market coverage gap-fill (recruit agents where intros go unserved).Thomas + sales
L2/L3Suburb pages → 300 where proven; NSW/QLD utility email expansion; market-event email capability (rate decisions) live behind preview gate.Felix + content
L5cPartner pilot: 2–3 conveyancer/broker referral agreements on existing flow.Thomas
GateQ3 exit review: investor campaign CPL/intro economics vs core funnel; routing lift on revenue/intro; lead→intro ≥32%; partner pilot go/kill.Thomas

Q4 · Apr–Jun 2027 Compound and decide

8. Operating rhythm and scorecard

9. What we are deliberately NOT doing

10. Risks and pre-agreed responses

RiskPre-agreed response
Turnover falls harder than −20% (Westpac hike path materialises)Verdict system already handles it: cash-protection mode, paid floor at proven exact-match winners, levers 1–3+6 continue (cheap and compounding). The investor-exit wave is counter-cyclical to this risk.
Cash rule (the base-case trigger): GP run-rate below ~$1.55M annualised at the December gateFreeze all H2 discretionary spend (partner pilot, Index PR, suburb expansion beyond 100), hold paid at winners-only, and re-plan H2 around the two levers with the best measured GP-per-effort. No new builds start until the run-rate recovers.
Google volatility / AIO expansion into local queriesOwned-share target is the hedge; tools + first-party data + structured citations are the AIO-resilient assets. If organic informational clicks fall, tool and agent-evidence pages (transactional) hold.
Paid engine has another negative-GP month before value bidding landsGuardrails-as-code in July; weekly leak-kill; the ~$30k conditional weekly boundary is real — a breach without a logged decision is an incident, not a surprise.
Execution capacity (one dev)Sequenced plan, both Q1 builds fully specced, gates kill scope, and the Q1 descope order is pre-declared in §7 (agent pages slip first; rescue + tool P0/P1 never slip). If Felix is blocked >2 weeks, the descope order executes automatically — no re-litigating.
Key-person risk: David (paid) and Felix (dev)Paid: change-log + guardrails-as-code turn tribal knowledge into system state (Q1 week 1); the weekly pack already lets Thomas read the account cold. Dev: both build specs are written to be executable by any competent Laravel dev — that's deliberate redundancy.
ODIN/data dependency + data rightsHandled in the estimate-tool spec (DR1/DR2 owner gates — DR1 = Thomas verifying sold-listings data is public-domain before comparables ship; DR2 = ODIN paid-tier display check; budget breaker, suburb-tier fallback, swappable source interface).
Investor wave doesn't materialiseCampaign is content + email + modest exact-match paid — low sunk cost; the CGT content assets retain evergreen value regardless.

11. Decisions needed from you now

  1. Adopt the FY27 targets (§5) — including the explicit plan-vs-base framing — or adjust before Q1 locks.
  2. Confirm 1 September as the hard spring deadline and ratify the Q1 descope order in §7 (this is the real decision — what slips first when something slips).
  3. Capacity: approve in principle one content/AI-operator contractor if the Q1 gate shows page/content production (not dev) is the bottleneck — pre-approving the trigger avoids losing a month to the decision in October.
  4. Cash rule: ratify the December trigger (§10) — below ~$1.55M GP run-rate, H2 discretionary spend freezes automatically.
  5. DR1/DR2 closure (sold-listings public-domain verification; ODIN tier display check) — both are yours and gate the estimate tool's comparables and launch.
  6. Approve the paid re-plumb (offline GP-value upload + guardrails + change-log) with David — it changes his weekly workflow, and §10 makes his account state system-readable.
  7. Sales SLA: agree the speed-to-lead standard with the sales floor (Lever 6) — the metric ships in July either way; the standard needs your authority.
  8. Investor-exit campaign: green-light the January launch so content and the CRM investor-segment work can be scheduled in Q2.
  9. Partner pilot appetite: yes/no to spending your own time on 2–3 conveyancer/broker conversations in Q3.

12. Appendix: evidence and sources

Strategy authored by Claude (Fable 5) on 2026-07-02 for Thomas Roberts, from live CRM economics, four weekly growth reports, the July 2026 build specs, WREA's internal platform documentation, and independently verified market/competitor research. v1.1 — revised after two independent adversarial review passes (numbers reconciliation; cold board-advisor read). v1.2 (2 Jul) — added §6.7 data-confidence and public-evidence dependencies (RMA snapshots, REA reconciliation, OTH/ODIN fallback, sidecar reliability, CRM agent-search quality) with board IDs. v1.3 (27 Jul) — refined the current execution order: self-serve agent connection is the next controlled customer launch; its shortlist, source-filtering and scraper/data-confidence gates are explicit; Property Value Form call-depth analysis moved to the later Property Value Hub rollout checklist.