Broday
Broday

Your day. Your market. Your next move.

Broday is market intelligence for real-estate brokers and agencies. A deterministic core turns listings, recorded transactions and building registers into one verified model of the market. A guarded AI layer explains it in plain language.

In production on live market data Daily market run, fully automatic AI layer live, with guardrails First broker pilot next
Recorded property transactions
334,000+
The state register of real sales, linked to buildings. Around 24,000 sales a year; history goes back to 1998.
≈ 24,000sales a year
28years of history
16,675in 2026, register to September
94%
Active listings tied to a real building
9,974 live today · 13,555 more kept as history
Data-quality checks168
Every day, before anything reaches a broker.
Buildings with identity24,900+
Cadastre, energy certificates, cadastral values and construction files joined to each one.

Live counts from the production database, 15 October 2026. Hover the bars for each year.

The problem

The hard part is not generating text. It is knowing what is true.

A broker's market lives in a dozen places at once: listings on several portals, real sales in state registers, buildings in cadastre, clients in messengers. Before anything can be explained, these facts have to be reconciled.

One flat, many identities

The same apartment appears on several portals at different prices. Sales sit separately, under a cadastral number instead of an address.

A price without a reference

An asking price says little until it is compared with what the building actually sold for, on enough evidence to say it out loud.

Opportunities get lost

A fitting object appears, and the client who wanted it is forgotten. Value exists only when the signal reaches the broker in time.

The system

Everything flows into one core. Out comes the next move.

Public registers, market listings and the broker's own clients go in. The core resolves identity, checks every number and produces concrete actions. Every day, without anyone running it.

In
Listing portalsSale, rent and new projects. Refreshed every hour.
Recorded transactionsThe state register of real sales, the market's ground truth.
Building and address registersCadastre, coordinates, energy certificates, cadastral values, construction files.
Public auctionsOfficial notices of property sales at auction.
Clients and requestsBudget, rooms, area, districts, timing. Several requests per client.
The Broday coreDeterministic
  1. One object behind every duplicate. The same flat on three portals becomes one object, by a strict key.
  2. Building identity. Address and cadastral number tie each listing and each sale to a real building.
  3. Price compared twice. Against recorded sales in the building or district, and against asking prices.
  4. A reason in numbers. How much cheaper, against what, on how much evidence. Silence when evidence is thin.
  5. Listing traps caught. Offices posing as flats, developer stock, multi-unit lots, read from the text by the AI guard.
  6. Freshness. Stale and withdrawn listings recognised; history never lost.
  7. 168 data-quality checks. Every day, before anything reaches the broker.
  8. Requests re-checked every 10 minutes. Every client request against the whole market.
Out
Morning briefUp to eight opportunities a day, each with its reason.
Matches for each clientWhen nothing fits: why, and how to widen the request.
Object and building passportPast sales, construction history, energy class. Every number with its evidence.
Seller signalsWithdrawn, returned, price cut, gone to auction.
Market analytics and reportsSlices, dynamics, price arguments for buyer and seller.
Client pagesA personal page sent via WhatsApp, Telegram or email; the client answers from it.

Diagram of the system, not a product screen.

The AI layer

The core decides. The model explains, and is checked.

Broday is not a wrapper around a chat model. The language model sits on top of verified results, sees only what it needs and cannot put a number on screen that the core did not compute.

How one explanation is made

  1. The core computesPrice reference, evidence depth, match fit, computed before any model is involved.
  2. A whitelist projectionOnly allowed fields leave the core. Client names never reach the model.
  3. The model writesOffline, in the daily run, never on the request path, so screens never wait for it.
  4. Every number is verifiedA text with a figure that is not in the facts is rejected and logged.
  5. A text twin always existsIf the provider fails or is switched off, a plain template from the same facts is shown. The product never stops.

Live in production today

  • AI guard over the top of the rankingReads listing text and flags traps with a quoted piece of evidence; 580+ listings judged so far. A word list reached 24% precision on the same task; the guard reads meaning.
  • 4,900+ model-written explanationsWhy this object, what changed, morning brief, match and digest. District and next-move texts run on templates for now.
  • 1,100+ texts rejected by the checksEach one replaced by its template twin and logged with the reason. Nothing unverified reached a screen.
  • Two providers with automatic failoverProvider-agnostic transport; a failing key moves work to the second provider and back.
  • Every call meteredTokens and cost recorded per call against a price table, so unit economics are measured, not guessed.
AI guard · listings judged
One in four listings at the top of the ranking hides a trap that a price filter cannot see. Each verdict carries a quote from the listing text.
Model texts · checked before showing
6,145texts written by the model
4,969 passed every check1,176 rejected
Why this object
2,395
What changed
1,304
Morning brief
809
Match
431
Digest
41
Passed texts by kind. A text is rejected when it fails a check (for example, a number the core did not compute), and the broker sees the template twin instead.
Level 1 · now

Explain what the core knows

Briefs, reasons and summaries from computed facts. Cheap per broker, cached, with a template twin.

Level 2 · next

Requests in plain language

"Two rooms, quiet street, within budget" becomes validated request criteria, by text or by voice, confirmed by the broker.

Level 3 · after the pilot

Prepared actions

Follow-ups, client messages and reports drafted by the model, sent only after the broker approves them.

Engineering evidence

Built so that every number can be trusted.

These are signals of engineering maturity, not of market traction. They show that the system is ready to carry real users.

Automated tests per release
11,800+
server ≈ 9,300interface ≈ 2,500
Every change runs all of them. Only a fully green build reaches production.
Browser scenarios every night
127
A real browser walks the product as brokers would, every night.
Rebuild from an empty machine
30:19
Minutes from a blank server to a working product, measured in a full rehearsal. The ring is one hour.
Pipeline heartbeat · last 30 days
≈ 285 runs a day
No day missed

Every number is provable

Each figure has a source and a way to recompute it. Where evidence is thin, the system stays silent and says why.

Client data is encrypted

Personal data is stored encrypted, and every time it is shown is written to an access journal.

Workspaces are isolated

One agency never sees another's clients. A table that could leak across workspaces turns the build red.

Runs by itself

The daily market run is automatic, catches up if it misses a slot, and a missing run is visible without anyone checking.

Watched around the clock

An outside monitor checks the system continuously, and no signal counts as a failure. Only a fully green build reaches production.

A market is a package

Sources, geography, thresholds and language live in a market package, not in code. A blocking build check keeps the core market-free.

Who it is for

Brokers first. Then the whole agency.

Brokers work their own clients; the agency sees the whole picture and keeps its knowledge when people change.

Available today

Broker and agency workspace

  • 1
    Roles checked by the serverBroker and agency administrator, each with exactly the access they need.
  • 2
    A shared agency baseThe administrator sees all clients and deals; each broker sees their own.
  • 3
    Coordinated seller workColleagues' actions on a seller lead are visible, so nobody calls twice.
  • 4
    Knowledge stays with the agencyWhen a broker leaves, their clients stay.
Stage and roadmap

Engineering first. Market proof next.

Broday is pre-revenue. The product runs in production on live market data; the next milestone is repeated use by real brokers. Every step ends with something measurable.

Now

Working core

Data foundation, decision engines, broker workspace and Level 1 AI in production.

Reliable daily run
0–3 months

Broker pilot

A small group of brokers on the full product, with explanations measured for usefulness and cost.

Weekly active use, cost per broker
3–6 months

Plain-language requests

Level 2: text and voice into validated criteria, compared against the classic workflow.

Task completion and trust
6–12 months

Second market package

The same core with a new package of sources, geography and language.

Repeatable expansion
For partners

What we are looking for.

Grant programmes, model providers and investors who want to back a working system rather than a slide deck.

What support pays for

  • API credits for the broker pilot Level 1 and 2 for every pilot broker, with cost measured per call.
  • Model and evaluation partnership grounded multilingual output, refusal on thin evidence, safety of prepared actions.
  • Funding for the pilot and the second market people on the ground, data access and a second package.

What a partner gets

  • A real domain with hard data identity resolution and evidence, not toy prompts.
  • Inspectable seams source → computation → projection → model → check → fallback.
  • Honest measurement usefulness, cost and fallback rate reported from production logs.
Fact sheet

Broday in one table.

Product
Market intelligence and daily workspace for real-estate brokers and agencies.
Category
Decision support and market analytics. Not a listing portal and not a CRM replacement.
Stage
In production on live market data · pre-revenue · first broker pilot next.
Data
334,000+ recorded transactions since 1998, 24,900+ buildings, 23,500+ listings, energy certificates, cadastral values and construction files.
Core
Deterministic: identity resolution, price references, evidence depth, matching, 168 data-quality checks a day.
AI
Live: AI guard over the ranking, 4,900+ model-written explanations, 1,100+ rejected by number checks. Whitelisted input, number verification, template fallback, two providers, metered cost.
Engineering
11,800+ automated tests, 127 nightly browser scenarios, 30-minute rebuild from an empty machine, encrypted personal data with an access journal.
Platform
Market-specific rules live in a package; the core carries none. A second market is a package, not a rewrite.
Looking for
API credits, model partnership, grant or investment for the pilot and the second market.
Contact

See it working.

A live walkthrough of the product on real market data, for programmes, partners and investors.

hello@broday.io