Demo case study
The weekend site-visit push
Six lead sources and one weekend to fill site visits. How a sample developer's leads go from raw rows to a logged call.
This is a demo case study. The setup and every figure are sample data, not results from a customer. Real case studies will replace it as teams go live.
The situation
A mid-size residential project has one weekend to fill site visits. Its leads sit in a partner sheet, a portal export, two forms and two CRMs, and the same people appear in several of them.
What ran
01Capture
Reads all six sources and merges the repeats: 214 rows become 187 unique leads, with 27 duplicates merged.
02Signal
Scores each lead on what it asked and puts the list in order. A. Menon, who asked about a 3 BHK on a higher floor, comes first at 92.
03Engage
Checks the number against the DND registry, places the call in the brand's voice, and saves a summary: connected for 2:14, wants a weekend site visit, brochure by email next.
04Trace
Syncs the outcome to HubSpot and logs each step, from the import at 10:02 to the sync at 10:17.
What it looked like
The trail
Audit log · sample project
Imported 3 sources, merged duplicates
10:02
Scored and ranked 187 leads
10:03
DND check passed, call placed
10:14
Call connected, summary saved
10:16
Outcome synced to CRM
10:17
What to take from it
Nothing here is a result from a customer. It shows the shape of the work: one list, cleaned once, ranked, called after a DND check, and written back with the trail attached.
More demos
Two more worked examples.
Want yours here?
These are demos because VectorStream is still in active build. Join early access and we'll be in touch as it opens.