Working prototype

PropertyScout rental pilot · Bangkok

Prove the lift.Know why.

PropertyScout runs paid acquisition into the Superagent website. The controlled pilot measures whether Superagent then qualifies renters and books appointments better—and by exactly how much.

Start the five-step guideReview launch gates
THB 500kPropertyScout-run media
≈ 4 weekstest window
≈ 300inquiry sample
Live proof lineBase case
Baseline pending
PropertyScoutshared baseline
300Inquiries
138Qualified
26Booked
Superagentdiagnostic path
300Inquiries
162Qualified
113Matchedinternal
46Booked
Modeled result at 300 inquiries+20 booked appointments

PropertyScout is compared only on stages it already measures. Matched remains visible as a Superagent internal diagnostic.

One path to launch

Five steps. No skipped gates.

Work left to right. Each step produces the evidence required by the next one.

Listing contractSuperagent supplies the JSON shape.PropertyScout conforms its feed.No partner-specific adapter.

Step 1 · Approve the basics

Agree the rules before building the pilot.

Confirm the scope, owners, operating boundaries and decision rights. A checked item means its owner can point to the accepted decision.

Basic approvals0%

PropertyScout Engineering remains TBC until a named owner is confirmed and reachable.

Data

What is the real shared baseline?

PropertyScout supplies inquiry, qualification and booked appointment evidence for a comparable cohort.

Operations

Who owns availability and response time?

Listing inventory is not operationally ready without a reachable partner contact.

Decision

What uplift justifies the next phase?

Agree the evidence threshold before observing the results, not after.

Step 2 · Lock in the metrics

Compare shared outcomes. Diagnose the Superagent path.

PropertyScout supplies qualification and booked-appointment benchmarks. Superagent keeps matched in its own path to explain how the lift is created.

Target presets
Shared planning historyNo saved scenario yet
Shared benchmark

PropertyScout today

Illustrative

No matched stage is requested. Replace these two placeholders with the signed pre-pilot baseline.

meets agreed renter criteria
%
books a property appointment
%
Pilot + diagnostics

Superagent target

Base case

Matched is intentionally retained here to reveal where Superagent’s qualification-to-booking performance is created.

shared comparison stage
%
Superagent internal diagnostic
%
shared appointment outcome
%
Booked appointments26→46PropertyScout benchmark → Superagent model
Absolute improvement+6.8ppend-to-end inquiry-to-booking rate
Relative uplift+77%booked appointments versus benchmark
Modeled pilot CPATHB 10,754THB 500,000 ÷ Superagent bookings

Step 2 · Measurement contract

Compare what is shared. Keep the diagnostic that matters.

The experiment decides whether Superagent improves the partner’s qualification and booking outcomes. Its internal match stage explains the mechanism; it is not a PropertyScout requirement.

Shared experimentInquiry → Qualified → Booked
  • Raw counts and conversion rates
  • Median time-to-stage
  • Cost where available
  • Comparable channel, cohort and period
Superagent internalQualified → Matched → Booked
  • Match and shortlist rate
  • Time to first viable match
  • Match-to-booking conversion
  • Used to diagnose, not benchmark PropertyScout
Decision readoutpercentage-point lift+relative uplift+time-to-stage change

Step 3 · Onboarding

Bring the inventory in on our contract.

Stable identity ruleexternal_ref → partner_ref
PropertyScout selection checklist

Promote the agreed Bangkok segment.

PropertyScout Business and Marketing applies these rules before Engineering assembles the JSON feed. Exceptions need joint approval before onboarding.

1 bedroomFrom THB 15,000per month
2 bedroomsUp to THB 70,000per month
How to use thisFeed selection ruleNot new importer rejection logic
Accepted · BTS Sukhumvit Line
N5Ari
E12Udom Suk

Both boundary stations are included.

Accepted · Sathorn–Silom
CBDCentral corridor
S6Saphan Taksin

Saphan Taksin is the inclusive last station before the river crossing.

Accepted · MRT Blue Line
BL25Lumphini
BL20Phra Ram 9

The direct corridor and both boundary stations are included.

1
ScopeMarco

Select the pilot inventory

Apply the agreed bedroom, price and transit-corridor rules before the feed is assembled.

2
ContractRanjit

Share the sample

One clean JSON template, field rules and a stable external reference convention.

3
ProofTBC

Return a representative feed

Enough real listings to expose missing fields, media problems and mapping questions.

4
LoadRanjit

Import the pilot inventory

Use the existing import path, check visible results and retain PropertyScout IDs.

5
OperateMarco

Open the operating route

Confirm availability contacts plus the mailbox, parser and CRM destination for handoffs.

Scope boundaryThis is a one-time pilot onboarding. Real-time sync is deferred. The backend engineer owns import execution; the joint dependency is a clean feed and a verified visible result.
Outside experiment

Step 3 · Operating boundary

Email is the boundary.

Superagent’s responsibility ends after sending the agreed case in a simple structured email. PropertyScout owns everything downstream in its systems.

01 · SuperagentSend structured email

Share the simple format and send it at the agreed ready state.

02 · PropertyScoutParse the message

Own the receiving mailbox, parser and any downstream handling.

03 · PropertyScoutCreate the CRM record

Upload the parsed case and manage CRM-side operations.

No joint template approval.No handoff performance metric or parser result is used to judge the experiment. The format only needs to be simple enough for PropertyScout to parse.
0%launch ready

Step 4 · Readiness checklist

Paid media stays locked.

Check a gate only when the named owner can point to the evidence. Every change is saved with its editor and timestamp.

Step 4 · Owners behind the gates

Four teams. One dependency chain.

Engineering makes the flow possible. Business and operations make the comparison valid.

SuperagentRanjit

Engineering

  1. Send the clean Superagent JSON sample and partner field requirements.
  2. Run the representative, pilot and final imports through the existing workflow.
  3. Confirm listing visibility, media and stable PropertyScout references.
  4. Create and share the simple structured handoff email, then record sends.
  5. Verify attribution and shared funnel events before paid traffic begins.
SuperagentYuriy

Business & operations

  1. Agree pilot inventory scope, commercial terms and operating contacts.
  2. Define shared qualification and appointment stages; keep match internal.
  3. Own the Superagent website, qualification funnel and reporting—not paid-media operation.
  4. Own the four-week runbook, daily exceptions and launch decision.
  5. Report absolute lift, relative uplift and time-to-stage change.
PropertyScoutTBC

Engineering

  1. Build the feed to Superagent’s sample—no custom format or direct API integration.
  2. Provide a representative snapshot, resolve feedback, then deliver the final snapshot.
  3. Keep external listing references stable and media URLs reachable.
  4. Configure the email parser and upload the resulting record into PropertyScout’s CRM.
PropertyScoutMarco

Business & marketing

  1. Run THB 500,000 of paid lead generation toward the Superagent website from a PropertyScout-controlled ad account.
  2. Own campaign setup, creative, audiences, pacing, spend monitoring and emergency pauses.
  3. Share the current qualification and appointment baseline before launch.
  4. Confirm the comparable paid-media cohort, channels, locations and segments.
  5. Nominate availability, receiving-mailbox and CRM owners.
  6. Release each media tranche only after the agreed launch and quality gates clear.

Step 5 · Launch

Record GO. Release carefully. Watch the shared funnel.

Launch is an explicit decision, not the automatic result of finishing an import. After joint GO, PropertyScout Marketing starts the first approved traffic tranche; both teams scale only while the evidence stays healthy.

Release statusLaunch locked

Complete Step 1 and every Step 4 evidence gate before paid traffic begins.

0% overall launch readiness
01Yuriy + Marco

Record GO

Accept the shared baseline, inventory result and launch evidence.

02Marco · PropertyScout Marketing

Release paid traffic

Activate the first approved tranche from PropertyScout’s ad account toward the Superagent website.

03Yuriy

Run the daily scorecard

Review spend, shared funnel results, inventory and availability.

04Named pause owner

Pause on a failed guardrail

Stop affected traffic first; investigate and record the decision second.

Scale rulePropertyScout moves through the approved media tranches toward THB 500,000 only while attribution, inventory freshness, availability and shared funnel quality remain inside the agreed guardrails.

Post-launch · Weekly evidence

See the result before Week 4.

Enter PropertyScout’s comparable pre-pilot counts once. Add Superagent’s inquiry, qualified and booked-appointment counts each week. The monitor recalculates cumulative lift immediately.

Current signalLoading saved metrics…Directional readout begins after the first weekly update
Shared metrics accessChecking access…

Anyone can view the guide and dashboard. Authorized pilot editors sign in here to change shared values—no OpenAI account is required.

Live cumulative readout

Superagent vs PropertyScout

Shared stages only. “Matched” stays in Superagent’s diagnostic funnel and is not required from PropertyScout.

Sample progress0.0%
Cumulative inquiries0across 0 saved weeks
Qualified0awaiting actuals
Booked appointments0awaiting actuals
Appointments vs expected—needs benchmark + actuals
Qualification rate
PropertyScout 0.0%Awaiting Week 1
Appointment rate
PropertyScout 0.0%Awaiting Week 1
Qualified → appointment rate
PropertyScout 0.0%Awaiting Week 1

Qualification lift—

Appointment lift—

Expected appointments—

2 · Weekly update

Add the latest actuals

Yuriy

Use counts for one non-overlapping week. Saving the same date again asks before replacing it.

Save the PropertyScout benchmark first.
3 · Evidence trail

Week-by-week comparison

0 updates
Weekly Superagent actuals compared with the saved PropertyScout benchmark
Week endingInquiriesQualifiedAppointmentsPS expectedCumulative Δ
No weekly actuals yet.Save the benchmark, then add Week 1 to start the early readout.
4 · Audit history

What changed, when and by whom

0 recent events

The first saved benchmark, readiness decision or scenario will start the audit trail.