Units live in a spreadsheet
Prices and statuses sit in a file everyone edits their own way. Someone is working from last week’s copy and sells a unit that is already reserved.
One database, one availability grid, one audit entry per change.
For agencies and developersWorks inside amoCRM
Every unit, every price, always current
Elystex holds your whole inventory — from developer down to the individual unit: availability grid, prices, payment plans, floor plans, reservations and client showcases. Deals stay in the CRM your team already uses. We come to it; we do not take it over.
- Edit straight in the grid, in bulk
- Reserve a unit from the CRM deal card
- Discounts and payment plans with scopes
What you get on day one
Why this exists
Three places where your inventory drifts from reality
The CRM knows nothing about units
An agent keeps two windows open and retypes the price by hand. The typo surfaces at signing, not while it can still be fixed.
The unit arrives in the amoCRM deal card with its price and status.
Shortlists are assembled by hand
Floor plan screenshots in a messenger and a PDF price list that is stale by evening. The buyer calls about a unit sold yesterday.
One link to a showcase in your colours, always at today’s price.
Every developer sends a different price list
One in a spreadsheet, one in a PDF, one as a link that changed yesterday. Somebody has to merge them, and that somebody does it by hand every week.
One catalogue across all developers, one format, one place to change a price.
Your agent finds out it is sold from the buyer
The unit went at the developer three days ago. Your price list still shows it, the buyer has already picked it, and the conversation starts with an apology.
Status and price live in one base — what your agent sees is what is true.
Terms per developer live in someone’s head
Commission, payment plans, which promotion applies to which building. The person who knows is on holiday, and the deal waits.
Payment plans and promotions described once, by scope, and applied by themselves.
The price list is a spreadsheet with versions
Sales works from one copy, marketing from another, the agency network from a third. Three answers to one question about one unit.
One base. The price you set is the price everyone reads, including the buyer.
A promotion has to be reassigned by hand
You set “minus 5% on floors 5 to 8”, the next building goes on sale, and somebody has to remember to extend it. Somebody does not.
The promotion is a scope, not a list. New matching units fall under it by themselves.
Payment plans are counted on a calculator
Every manager rounds differently, and the difference surfaces at signing rather than while it can still be fixed.
Terms are set once; the schedule unfolds from them and the buyer sees the same numbers.
Where to start
Five days from contract to your team working in it
Send us one of the price lists you actually work with. We will load it and show you the same units in a grid, with your branding on the client link. The demo takes 30–40 minutes.
Capabilities
A tool, not a shelf of tools
Every module sits on one database. A price calculated in pricing reaches the availability grid, the deal card and the link the buyer opened. There is nowhere for them to diverge.
Availability grid
The whole building on one screen: floors, cores, statuses, prices.
Details →Market analytics
Price per m², trends, comparison between projects, map.
Details →unique to us
Payment plans and discounts with scopes
Set the condition once; it decides for itself what it applies to.
Details →Reservations
Expiry, automatic release, history, and an answer to “what runs out today”.
Details →Client links and showcase
A shortlist for one buyer, in one link, in your colours.
Details →Floor plans
One drawing across many units, with clickable zones.
Details →amoCRM integration
Units inside the deal card, without switching windows.
Details →Currencies
USD, GEL, AED and more, converted at rate and labelled as such.
Details →What sets us apart
Four things teams usually do by hand
Payment plans and discounts with scopes
A condition is described by a scope — project, building, floor range, unit type, available only — and picks up new units by itself. Systems built around hand-kept lists cannot do this: there, a promotion is reassigned by hand every time the base grows.
A separate instance per agency
Your base is yours: its own subdomain, its own storage, no sharing a table with someone else’s data.
Data export written into the contract
A full export in a machine-readable format on request is an obligation — not an extra you pay for and not a favour at parting.
No meter on every action
Buyers who open your showcase are not users. You pay for staff, not for a client having looked at a unit.
Try it
This is not a picture. Click around
The same availability grid your sales floor works in: two buildings, statuses, layouts and price. The filters run right here — before any demo and without writing to us.
Showing 36 of 36
No unit matches these filters. Drop one of them or press “Reset”.
Click a unit to open its card
Pricing
Half the price of comparable systems
Buyers who open your showcase from a link are not users and are never billed. You pay for your staff.
Start
One agency, up to 5 staff
$ 149per month
Full pricingTeam
A sales team on amoCRM
$ 349per month
Full pricingMaximum
A developer or a network of offices
$ 740per month
Full pricingHow it flows
One unit, end to end — never typed twice
On the left is that unit in the availability grid, on the right is the deal card in your CRM. Nobody retypes anything in between.
Deal card · amoCRM
UnitBuilding 3 · apt. 27 · 61.7 m²
Price$ 145 900
Statusavailablereserved
Reserved for 2 more days
- The unit appears in the databaseYou load the developer’s price list and the building assembles into a grid. The unit is available.
- An agent reserves itOne click in the grid. A reservation with an expiry, not a colour in a shared file.
- The deal card fills itself inNumber, area, floor and price land in amoCRM. The agent typed not one character.
- The reservation expires — the unit is back on saleThe term ran out and the cell returned to available. Nobody had to remember it.
Who it is for
Three ways this gets used
An agency resells someone else’s units and lives on someone else’s price lists. A developer sets the price. A solo agent gets something else entirely — not a system but a channel: our database, our developer contracts and a share of every deal.
For agencies
Every developer you sell, in one database
An agency lives on someone else’s price lists. They arrive by email, each in its own format, and go stale the same week. Elystex holds every developer you work with in one catalogue — with an availability grid per building, live prices and reservations your agents can make without leaving the deal card.
Read on →For developersYour whole project, priced and sold from one screen
A developer sets the price rather than reads it. Elystex holds the project the way you sell it: an availability grid per building, promotions and payment plans described by scope, reservations with an expiry, and a catalogue you can embed on your own site.
Read on →For solo agentsSell new builds from our database and keep 85%
The database and the developer contracts are ours, and the developer pays the commission. The client is yours, 85% is yours — and there is no access fee.
Read on →
What changes
A workday without double entry
Your team stops retyping. Every number below is about work that disappears, measured on a live deployment.
1system a unit gets entered into, instead of two
11deal fields filled automatically
0manual price transfers between systems
