work / case study
bestyeghomes.com — a website that runs itself every night

Most websites are brochures that age. This one is 15 engines working on a schedule: the market comes in every night, pages are rebuilt from data, search engines are told what changed, compliance is proven against the live site, and every enquiry becomes a drafted reply in under a minute. One person runs it, part-time. Here is the machine.
the engine room
What runs, and when
Every box is a real job, and its state is read from that job’s own record on the day this page was built — stamped 2026-10-28. Select any engine to see what it does and what keeps it honest. Then scroll the night.
Data in · nightly · ran today
Listing feed sync
Pulls every active listing in the province from the national listing data feed and removes the ones taken off the market.
guard a watcher confirms the sync and the removals actually happened
feeds Page registry, Cache warm + instant indexing
3 am
The market comes in
Every active listing in the province is pulled fresh from the national feed; anything taken off the market overnight is removed before anyone can see it.
3 am
Pages re-rendered, search engines told
The busiest pages are rebuilt against the new data — 470 of them on 7 October — and search engines are told exactly which pages changed, so fresh listings are found in hours, not weeks.
4 am
Watching the doors
Bulk copying of listings is spotted and sorted into challenge or block, as the data licence requires; every always-on service is checked to be running the code that is actually on disk.
5 am
Compliance, proven against the live site
A script visits the site as an anonymous stranger and proves that no members-only figure leaks — then proves the enquiry path still works end to end.
6 am
Google's numbers, read back
Clicks, impressions and indexing come back from Search Console and redraw the plan board — demand decides what gets built next.
all day
An enquiry becomes a reply in under a minute
Forms, sign-ups and portal lead emails are checked every sixty seconds. A personal reply is drafted and on the agent's phone within a minute — and nothing is ever sent without a person.
every build
Pages are data
Every page is a row in a registry; a page reaches search engines only once it has enough real listings to be worth a visit; mandatory legal texts are checked word for word on every change.
monthly
The month, published
Sold-data exports are registered and checked for coverage; the monthly market report is computed by code from the board's statistics and waits for a person to approve the preview.
the result
Search that compounds
0 → 173
monthly clicks from Google, June to October — average position 21.3 → 13.8, 590 of 647 pages indexed
basis: Google Search Console — calendar months for Jun and Jul, rolling 28-day windows after; read 2026-10-07; indexing 2026-10-05
The numbers
| Window ending | Clicks | Impressions |
|---|---|---|
| 2026-06-30 | 0 | 44 |
| 2026-07-31 | 24 | 2,383 |
| 2026-08-09 | 31 | 3,834 |
| 2026-08-27 | 40 | 6,777 |
| 2026-09-07 | 93 | 10,564 |
| 2026-09-20 | 133 | 15,016 |
| 2026-10-05 | 173 | 17,937 |
No ads have run. The curve is the engine doing its job — about 28,600 active listings and about 76,000 sold records turned into hundreds of pages that answer what people actually search, each refreshed the night the market moves.
speed to lead
An enquiry becomes a reply in under a minute
The first business to answer an enquiry usually wins it. Every website form, sign-up and portal lead email is checked every sixty seconds; the enquiry is classified, a personal reply is drafted with links that are checked to work, and the draft lands on the agent’s phone.
43s median, 12–61s across all 13 website enquiries
The rule that makes it safe: it never sends. A person reads, edits and sends every reply, and follow-ups at one, three and seven days are drafted the same way. The system can’t contact anyone on its own — that is enforced in code and checked every day, not promised. Put one on your enquiries.
pages are data
Adding a page means adding a row
Every page the site should have lives in a registry. One row like this (simplified) becomes a crawlable page for every area that has the listings to support it:
{ slug: "condos-under-300k",
title: "Condos under $300K in {area}",
filter: { type: "condo", maxPrice: 300_000 },
minListings: 3 }A page reaches search engines only once it has enough real listings to be worth a visit, so the site grows without thin pages. Search Console’s own numbers come back every morning and decide which rows get written next.

compliance
Rules run as tests, not promises
- Every night — a script visits the live site as an anonymous stranger and proves no members-only figure leaks.
- Every change — the board’s mandatory legal texts are compared word for word against the source documents; the build fails if one drifts.
- Every night — bulk copying of listings is detected and tiered into challenge or block, as the data licence requires.
- Every refresh — listing data is never served older than the licence allows, and listings taken off the market are removed the same night.
Regulated data is where most automation stops. Here the rules are code, so the site runs unattended without anyone hoping it stays compliant.
the cost
Cash was never the cost
Scope like this is usually quoted at team scale: most of a year, budgets in the hundreds of thousands. The cash line here was small — on the order of $2–3K in subscriptions and hosting, from the founder’s own ledger. The real cost was a person: years of foundations and judgment applied at every gate, working with frontier AI as tireless, capable hands. That combination is what an engagement moves into your business.
the pattern
Nothing here is specific to real estate
Swap the listing feed for your catalogue, price list or service area, and the machine is the same: data in every night, pages generated from a registry, search engines told what changed, rules run as tests, enquiries answered in under a minute. Real estate was the proving ground because it is hard — regulated, data-heavy and competitive.
where it stands
Scope and the next test
The engines above are running today. Search traffic is growing; turning that traffic into enquiries is the stage now being built — listing alerts are built and waiting to be switched on. That conversion stage is the next test, and it is scoped separately for every client too.