Skip to content
← All client work/Real-estate · AI
Built · later closedReal-estate · AI

AI real-estate deal finder case studyAn AI deal-finder that ran at roughly 75% lower cost than the original approach.

A founder wanted to surface promising real-estate deals from a constant stream of listings — and the early version was expensive to run.

Clientnestper · Bruno Peterle
ProjectAI Real-Estate Deal-Finder Pipeline
My roleSenior developer
StatusBuilt · later closed
Discuss a similar build
Nestper landing page with a field for pasting a property listing URL, above a row of property cards showing price, address, beds and baths.

The real product, shown with demo data.

~75%Lower running cost than the original approach
3Isolated stages: collection, AI scoring, delivery
Rules firstAI reserved only for the judgment calls
HonestLater wound down for business reasons unrelated to the build
In short

A founder wanted to surface promising investment deals automatically, but the early version was expensive to run. I rebuilt it as isolated pipeline stages with a rules-first, AI-second cascade — cutting running costs by roughly 75% while keeping quality high.

01 · The situation

Promising deals, buried in a stream of listings.

A founder wanted to automatically surface promising real-estate investment opportunities from a constant stream of new listings — and the early version was expensive to run.

02 · The challenge

Scale the volume without the AI bill spiralling.

Two things at once: collect large volumes of listing data reliably, and use AI to judge which deals were worth attention — without the AI costs spiralling as volume grew.

03 · What I built

A pipeline of isolated, fault-tolerant stages.

A data pipeline built as isolated stages — collection, AI enrichment/scoring, and delivery — running as independent background workers off a queue, so one stage failing never took the rest down. Screens included a listing analyzer, deal scores, a scenario builder and a subscriber dashboard.

Screens from the real product, captured with demo data. No client or customer data is shown.

04 · How it works

Isolated stages, running off a queue

  1. 01CollectListings from a constant streamDedupCache
  2. 02Rules firstEverything knowable from the data
  3. 03AIAI secondOnly the judgment calls
  4. 04DeliverScored deals, alerts, dashboard
Collection, AI scoring and delivery run as independent background workers. If one stage fails, the others keep going and the failed work is retried.
05 · The hard engineering

Rules first, AI second.

Rules first, AI second — and what it did to the running costRelative running cost
Every incoming listingCollected, deduplicated, cached
Rules: everything knowable from the dataCheap · fast · predictable
AI: only the judgment callsWhere interpretation is needed
Widths are illustrative, not measured volumes.
Original approach100
Rebuilt pipeline~25
~75%lower running cost
01

Rules-first cascade

Deterministic code handled everything knowable from the data; AI was reserved only for the judgment calls.

02

Dedup + caching

Together with the cascade, cut the running cost by roughly 75% while keeping quality high.

03

Fault isolation

Failures were contained and retried cleanly, stage by stage.

06 · Key decisions

The calls that shaped the build

Why rules first, AI second?

Deterministic code is cheap, fast and predictable. Reserving AI for genuine judgment calls — and adding deduplication and caching — is what cut running cost by roughly 75%.

Why isolate each stage?

So one failing stage never takes the rest down. Failures are contained and retried cleanly.

Why is the status “later closed”?

The client later wound the product down for business reasons unrelated to the build. It is shown as engineering work delivered, not an active product.

07 · The outcome

Quality deals, surfaced far more cheaply.

✓ Roughly 75% lower running cost✓ Quality maintained✓ Note: the client later wound the product down for business reasons unrelated to the build
“

Sikandar was an absolute pleasure to work with. He is professional, experienced, and brought valuable insights to the development of my platform. He wasn't afraid to offer constructive feedback and push back when it would improve the project, including steering me away from spending more than necessary. After reviewing the data and pricing, it's clear he understood the challenges long before I did and genuinely cared about my budget. His expertise and collaborative approach made the process smooth and efficient. Highly recommended!

BP
Bruno PeterleFounder, nestper
08 · Stack
PythonFastAPICelery/RedisResilient scrapingAI scoringCost-optimized cascade
Is this like your product?

Any AI product whose running costs grow with volume.

AI-heavy prototypesrules-first design to cut model spend
Data pipelinesisolated stages that fail safely
Deal & lead findersscoring streams of new listings