Neuruh | DeedSonar | Buyer Demo | 04 Nov 2026

DeedSonar Buyer Demo

Click through what DeedSonar does: lead intake, LANDOS scoring, recipe match, CRM view, and Scan / Dossier outputs. This page is a sales tool, not the product. It runs on synthetic data only and does not connect to the live DeedSonar app.

Ownership: DeedSonar is solely Jeramie Hicks's. Bryan Franklin never signed anything. There is no partner consent gate on a sale.

Synthetic data notice: Every lead on this page is fictional, with invented names, addresses, and phone numbers. No real owner PII appears anywhere on this page.

Document control

Owner
Jeramie Hicks (sole)
Product
DeedSonar
Live site status
deedsonar.com: 503 DEPLOYMENT_PAUSED
Demo data
Synthetic only
Proof job
6071b7ad, 2026-09-16
Contact
cal.com/neuruh

What this demo is

A five-minute, click-through model of the DeedSonar workflow for a prospective buyer. It shows the shape of the product: intake, scoring, recipe match, CRM ranking, and paid outputs. It is not the product, not a live environment, and not connected to any DeedSonar database.

1. What DeedSonar does

DeedSonar is a real-estate CRM and lead intelligence app. Under it sits LANDOS (county parcel ingestion and scoring) and Lead Recipe OS (the signal-to-opportunity kernel). The product surface, verified from the repo on 2026-10-22:

1,744
DeedSonar code files
404
Test files
203
API route files (route.ts)
219
SQL migrations
257
API routes total
50
LANDOS signals

Proof point: hunt job 6071b7ad

On 2026-09-16 a documented hunt job scored 153 leads and synced 153 leads to the CRM, end to end. That run is the recorded evidence that the stack works as a loop: ingest, score, sync, work the lead.

Figure 1. The DeedSonar loop a buyer is buying into: intake, signal scoring, recipe match, CRM work, paid outputs.
1. Lead intakeform + import 2. LANDOS score50 signals 3. Recipe matchR1-R7 4. CRM rankfreshness shown 5. Scan / Dossier$100 / $1,500

Figure 1 reads left to right. The arrow back from step 5 to step 1 is the outcome loop: what a Scan or Dossier learns feeds the next intake.

2. Try-it walkthrough

Step 1 of 5: Load Sample A below (the high-score tax-lien lead) using its loader button.

3. Sample loaders (synthetic)

No sample loaded. Load a sample or fill in the intake form by hand.

4. Lead intake form

Intake

Fill in a lead by hand, or load a sample above. The completeness meter tracks the six fields the intake expects. Nothing leaves this page; there is no server behind this form.

Completeness meter

Completeness: 0% (0 of 6 fields).

Missing fields: owner name, address, APN, county, FIPS, phone.

5. Scoring view: LANDOS, 50 signals

Signal checklist (10 of 50 shown)

LANDOS scores a lead against 50 signals. Ten are shown here so the arithmetic is checkable by hand. Each signal carries a fixed point weight; the score is the sum of the active signals, out of 100. The other 40 signals are not itemized in this demo. Toggle any checkbox and the score, verdict, and bars update.

Score: 0 / 100 NO SIGNALS

Qualification threshold: 55. A lead at 55 or above is QUALIFIED for CRM work. Below 55 is a PASS: keep the record, do not work it now.

Figure 2. Active signal points for the current lead. Bar length equals the signal weight.

SHA-256 provenance receipt (synthetic digest, illustrative only, not computed from live data):
No receipt yet. Load a sample lead.

In the real system, every scored lead carries a SHA-256 receipt binding the source rows and the classification to the score, so a score can be audited back to its evidence.

6. Recipe match view: Lead Recipe OS

Recipe matches for the current lead

A recipe matches when its required signal is active. The why-matched note names the evidence, so a match is never just a label.

RecipeFamilyStatusWhy

R8-R30

Recipes R8 through R30 are listed as Not documented in the sources used for this demo. Nothing is invented for them here. The live registry holds 36 rows including variants and aliases; the canonical catalog is 30 recipe families.

RecipesStatus
R8, R9, R10, R11, R12, R13, R14, R15, R16, R17, R18, R19, R20, R21, R22, R23, R24, R25, R26, R27, R28, R29, R30Not documented in demo sources

Active hunt recipes in the real system: Berrien90+, LIVE_PROVEN tax lien, FLOW_C multi-territory taxsale, FLOW_C probate/estate. Those hunts are named here as product facts; this demo does not run them.

7. CRM list view

Ranked leads

Ranked by score, highest first. Per-field freshness is shown for every row: a field is only as fresh as its last source observation. UNKNOWN is shown as UNKNOWN, never silently filled in. The highlighted row is the current working lead.

RankLead (synthetic)CountyScoreRecipesFreshness by field
Figure 3. The contact ladder: each rung is independent, and the ladder fails closed. A phone number is not the same as permission to call it.
PHONE: accepted phone evidence exists CONTACT RESOLVED: number linked to the right party DNC CLEAR: number clear under scrub rules CONSENT: channel permission satisfied ACTION AUTHORITY: persisted authority decision (max 180 days) A rung that cannot be read is a stop, not a zero. DNC scrubbing is optional in DeedSonar, never an automatic gate.

8. Scan / Dossier outputs

Generate outputs for the current lead

The Scan is the entry product. The Dossier is the deep product. Both are generated from the intake, score, and recipe match above. Prices are the founder's list prices: Scan $100, Dossier $1,500. A free 10-minute qualifying call is at cal.com/neuruh.

No Scan generated yet. Load a sample lead, then press Generate Scan.
No Dossier generated yet. Load a sample lead, then press Generate Dossier.

9. Share link

Share this lead

The current lead is encoded into the URL hash as base64 JSON (#d=...). Nothing is sent to a server. Opening the link restores the lead on load.

10. How it works

This page is a single self-contained file. The sample leads, the 10 shown signals and their weights, and the recipe rules are embedded in the page, so every control runs entirely in your browser. The score is a plain sum of active signal weights. The completeness meter counts six intake fields. The share link encodes only the current lead in the URL hash.

What this is not

Honest gaps and limits

Sources: deedsonar-sale/sale-structure.md and valuation.md (2026-10-22); DeedSonar Forensic System Dossier (2026-09-14); Real Estate Estate Inventory (2026-09-22). Figures are source claims with the dates stated, not re-verified live facts.