Developer Admin

Registry, unit grid, price lists, feeds, reservations and deals — in one window. One that doesn't lie.

Connect your company

Built
for sales teams
tired of cross-checking

The unit grid, the website, batumi.estate and the contract show one price. Always.

▶ Play

Not just
a building.

Behind this facade — 1,248 units. Each with a price, a status and a history.

Live registry

Building 2 · 7 floors

Floor 05

6 apartments

Available0
Reserved0
Contract0
Sold0

from$ 34,500

* Updates faster
than the head of sales
can ask for a summary

Available
Reserved
Contract
Sold

* Figures are illustrative.

One window, instead of four^*

01 / 06Units, buildings, statuses

Registry
and unit grid

apt. 124 · 2-room · 58.4 m²available

One tableThe unit grid comes from it too
02 / 06Price, author and date

Price lists
with history

~~$ 74,900~~ $ 76,400 Price list #14 · head of sales · 01.09

Increases in wavesDraft in advance
- batumi.estate148 unitsok
- Website148 unitsok
03 / 06batumi.estate and your website

Feed
to batumi.estate

Export building 2 to batumi.estate
04 / 06Takes the unit off listings

Reservations
with a deadline

Warning Reservation on apt. 57 expires in 02:59:59 Then the unit goes back on listings by itself
05 / 06Schedules and payments

Deals
and contracts
- Payment 115.07paid
- Payment 215.09paid
- Payment 315.11due
06 / 06Five roles, one log

Roles
and log
- 14:02Head of salesprice, apt. 57
- 14:05Marketerfeed to batumi.estate
- 14:11Managerreservation, apt. 12
Quarter in reviewSales team edition

RECAP

Issue #12131415

0mismatches
this quarter

Friday
is free.Cross-checking with the website cancelled as unnecessary

#1

Developer AdminRegistry, price lists, feeds, reservations and deals in one window

* An Excel price list, an Excel unit grid, a platform dashboard and a “who cancelled the reservation” chat

The system: one set of data, you can see where units sit unsold, one price everywhere

One system

Registry, price lists, feeds, reservations and deals run on the same data. Change a price and it changes everywhere — not in three files out of five.

Nothing left
to cross-check

Where units sit unsold

Status history remembers how many days each unit has been on sale. Colour the unit grid floors by it — and you see what sells and what sits. No summaries, no Friday export.

Days on sale
by floor

Everything adds up

One price — in the unit grid, on batumi.estate and in the contract. The price list remembers who set it and when, and a feed without a price simply won't go out to batumi.estate.

One price.
Everywhere

ONE

One window for the whole sales team

A five-minute break

Customer pipeline
to the keys

Customers travel down the pipeline to the keys. The pipeline wears out, the foreman runs out of steam, and competitor rats are already waiting at the holes. Press the button.

deals: 0 · stolen: 0

In real life, the system presses the button

A lead arrives linked to a unit and a source, and a reservation takes the unit off listings by itself. No holes in the pipeline.

Connect your company

100% of your data

Move in a day

no Excel

You send an export — we load it.
We check the unit grid together.
Excel — thanks for everything.

Moving
one complex

≈ a day. Units, prices and reservations move together.

One registry
instead of a folder of files

Reservations that
expire by themselves

A reservation takes the unit off listings and puts it back on sale on time by itself. No “until Monday” sticky note on the monitor.

Export
back to Excel

Any time, all of it — the data is yours. In case you miss it.

How it sounds
at the stand-up

No names or logos — only roles. Recognise anyone?

[ 01 / 05 ] Head of salesruns the stand-up at 9:30

“The reservations summary took two hours to put together — from three Excel files, a chat and ‘I think I put it in’. Now I come to the stand-up and it's already done.”
Mon · 09:31 · stand-up

Reservations summary

before2 h3 files + chat

after0 minbuilds itself
[ 02 / 05 ] Commercial directorsigns off price lists

“Raising prices used to be our Friday ritual: the whole team, late into the night, with a calculator. Now the draft price list is calculated in advance, and Friday is just Friday again.”
Fri · 18:47 · price list

Price increase

beforeFridayuntil 23:10

afterdraftready on Tuesday
[ 03 / 05 ] Manageron the phone from 9:00 to 21:00

“‘Is 412 still available?’ I used to say ‘let me check’ and walk across the whole office. Now I look at the unit grid while the customer is still finishing the question.”
Tue · 11:05 · call

Is 412 available?

before“let me check”and across the office

afterunit gridfloor 4, available
[ 04 / 05 ] Marketerin charge of feeds

“A platform kept rejecting the feed because of a unit without a layout, and we found out from customers. Now a unit like that simply won't pass the check and won't go anywhere.”
Wed · 10:12 · export

Feed rejected

before14units per export

after0checked before sending
[ 05 / 05 ] Financelikes it when things add up

“The payment schedule lived in an Excel file that had four ‘final’ versions. Now it lives in the deal card. In one version.”
Thu · 16:20 · reconciliation

Payment schedule

beforein Excelfinal_v4(2).xlsx

afterin the dealcontract · schedule · payments

We export where people search

batumi.
estate

01 · feed on schedule

Units, prices and layouts —
straight from the registry

<offer id="k2-412">
  <rooms>2</rooms>
  <floor>4</floor>
  <area>54.2</area>
  <price>…</price>
  <image>412-plan.webp</image>
  <status>available</status>
</offer>

Your own
XML

02 · and JSON for your website

24/7

03 · exports — no days off

Sat · 03:00 · feed sent

You sleep — batumi.estate
gets fresh prices

0rejected

04

A unit without a layout or a price —
the check won't let it into the feed

Choose your scale

1 building

One building, one sales team, one truth. The unit grid, price list and feeds are built from the registry — nothing left to cross-check.

Residential complex

Several buildings under one roof. Prices go up in waves from a draft price list, everyone has their own role, and the log remembers who changed what.

Group of companies

Several complexes and legal entities in one system. Company data never mixes, each company has its own roles and log. XML/JSON feeds and Excel export — any time.

Pricing is calculated at the demo for your inventory and number of users

Unit grid and unit registry
Price list with history, feeds on schedule
Pricing by inventory and number of users

Several buildings in one registry
Price increases in waves
Roles and change log

Several complexes and legal entities
Company data isolation
XML/JSON feeds and Excel export

What's inside

Unit registry and unit grid

Price lists with history

Feed to batumi.estate

Your own XML/JSON feed for the website

Leads linked to a unit and a source

Reservations that expire by themselves

Increase waves · draft price list

Roles and a log of every change

Several buildings in one registry

Several complexes and legal entities, data isolation

Export back to Excel

Moving off Excel

≈ a day

≈ a day per complex

Pricing depends on inventory and number of users. We'll calculate it at the demo — 30 minutes on your data.

Request a demo

Open format

XML-FEED-1

Abstract

We present XML-feed-1, an open format for exporting units that is built from the registry rather than from a spreadsheet someone forgot to update. The feed reproduces the key properties of a unit — building, floor, area, price and layout — and goes out on schedule to batumi.estate and your website. Units without a price or a layout are stopped by the check before the feed; every export produces a report. Limitations: the format does not know what was agreed in the smoking area and does not guess a price nobody entered.

Acknowledgements

To Excel, for years of service. Special thanks to the “Prices_final_v7_really” tab, which held on to the very end.

Review

“We used to build the feed by hand on Fridays. Now it builds itself, and on Fridays we argue about other things.”

— Head of sales, a developer's sales team

Example

realty-feed.xml · snippet

<?xml version="1.0" encoding="UTF-8"?>
<realty-feed>
  <generation-date>2026-09-13T06:00:00+04:00</generation-date>
  <offer internal-id="412">
    <type>sale</type>
    <category>apartment</category>
    <building-section>Building 2</building-section>
    <floor>4</floor> <rooms>2</rooms>
    <area><value>54.2</value><unit>sq. m</unit></area>
    <price>
      <value>70500</value>
      <currency>USD</currency>
    </price>
    <image tag="plan">plans/412.webp</image>
  </offer>
</realty-feed>

A unit without <price> or <image tag="plan"> won't make it into this file.

Reviewers' questions

We'll show you on your own inventory. In 30 minutes, no slides.

Connect your company

Built for sales teams tired of cross-checking

Sharewith your head of sales

Moving one complex off Excel

≈ 1 day

Developer Admin

Not justa building.

Live registry*

One window, instead of four*

Registryand unit grid

Price listswith history

Feedto batumi.estate

Reservationswith a deadline

Dealsand contracts

Rolesand log

The system: one set of data, you can see where units sit unsold, one price everywhere

Nothing leftto cross-check

Days on saleby floor

One price.Everywhere

no Excel

Movingone complex

Reservations thatexpire by themselves

Exportback to Excel

How it soundsat the stand-up

We export where people search

batumi.estate

Your ownXML

24/7

0rejected

Choose your scale

1 building

Residential complex

Group of companies

XML-FEED-1

Abstract

Acknowledgements

Review

Example

Reviewers' questions

We'll show you on your own inventory. In 30 minutes, no slides.

Not just
a building.

Live registry

One window, instead of four^*

Registry
and unit grid

Price lists
with history

Feed
to batumi.estate

Reservations
with a deadline

Deals
and contracts

Roles
and log

Nothing left
to cross-check

Days on sale
by floor

One price.
Everywhere

Moving
one complex

Reservations that
expire by themselves

Export
back to Excel

How it sounds
at the stand-up

batumi.
estate

Your own
XML