An MLS is the source, per market
There is no single national feed in the United States. Each MLS licenses its own, so a product covering several markets maps the same field more than once.
Most property software problems are modelling problems, not interface problems: a tenancy stored as one row with an end date, a rent roll derived from the ledger it is meant to check, a listing feed mapped once and never versioned. We build the parts that are expensive to undo.
Tell us what you are building
Real estate software development builds the systems that run a tenancy: a versioned lease record, a rent roll that reconciles to the ledger, client money held apart from trading cash, and listing data exchanged in a standard shape. Most projects fail on the data model, not the interface.
Our work
We have no landlord, managing agent or developer among our clients, and saying so now is cheaper than you finding out later. What we have built is the parts a property system is made of, so judge the three below on whether that transfers.
Listing data
This is the layer where integrations fail, because a feed gets treated as a file rather than a versioned standard. Every version and date below was read on RESO's own sites, and each card carries the date it was last read.
There is no single national feed in the United States. Each MLS licenses its own, so a product covering several markets maps the same field more than once.
Internet Data Exchange is what lets a brokerage show a market's inventory on its own site. The display terms travel with the data, so they belong in the model.
RESO's dictionary site shows 2.1 ratified at 43 resources and 2,139 fields, against 1.7 at 26 and 1,333, and 2.0 at 41 and 1,745. A feed two versions back maps differently. Read 13 November 2026.
RESO's Transport list carries Core at v2.1.0, dated December 2023, with $filter, $select, $orderby, $expand, pagination and metadata. Build to that, not to a bespoke REST shape. Read 17 November 2026.
RESO's certification page says it certifies Web API Core 2.0.0, Data Dictionary 2.0 and RESO Common Format, and that NAR MLS policy requires compliance with RESO's most recent standards. Read 17 November 2026.
RESO retired the RETS workgroup on 23 June 2017 and stopped certifying RETS in 2018, while saying at the time that RETS was not dead. The switch off is per MLS: on RESO's transition leaderboard, read 14 November 2026, three MLSs publish a date and 110 read TBD.
Scope
Eight pieces of work. Most engagements are three or four of them, and the first one decides what the rest cost.
Charges generated from the terms, so a review settled in November and effective from March produces its own backdated adjustment.
A per landlord and per property position for any past date, not a pooled bank balance that agrees today.
Billed on account, reconciled against actual spend, with apportionment held as a dated schedule rather than a percentage column.
A feed mapped to the Data Dictionary version it was issued against, with the listing record kept apart from the tenancy record.
Demands keyed to certified milestones rather than dates, and receipting that separates drawable from non drawable money as it lands.
Failure modes
Six failures seen often enough to name, with the practice that prevents each one.
It answers today and nothing else. Version it in the first sprint: effective dating under a live ledger is the costliest change here.
Deriving one from the other makes them agree by construction. Compute the roll from the lease terms, so an unbilled review shows up.
A pooled figure says the bank agrees, and nothing about whose money it is. Keep a per landlord position for any past date.
One percentage per tenant cannot survive a unit split or a gross up provision. Hold it as a dated schedule instead.
GOV.UK publishes two bands and a ceiling, so five weeks is one branch. Drive the check from the annual rent, as configuration.
Matching the rent roll total proves the sum, not the schedule under it. Replay a past year charge by charge: compensating errors agree.
By operation
There is no single best one, and a page that names one is usually selling it. Real estate is one phrase for several businesses, each with a different core object.
GOV.UK's landlord overview of the Renters' Rights Act, in effect since 1 May 2026, says a tenancy agreement cannot carry an end date.
The listing is the product, arriving on an MLS feed or going out through IDX. Pipeline is the core object, not tenancy.
Money arrives before the building exists, which makes it regulated. India and Dubai both route it to a project account.
Voting weight usually follows share of the common parts, not one vote per unit, and it changes when a unit is subdivided.
Which version of your core they have integrated, who holds the listing feed licence, and whether they replay a past year before go live.
System types
Four families of system, and the constraint that decides the plan in each. A property management system, a lettings CRM and a client accounting package are three products, not one.
| System family | What it is | The constraint that decides the plan |
|---|---|---|
| Enterprise portfolio and asset management | Yardi Voyager, MRI Software, RealPage and SAP RE-FX. Where large portfolios consolidate. | Which extension points your installed version exposes, not the ones described for the current release. |
| Mid market lettings and management | AppFolio, Entrata, Buildium, Propertyware, Arthur, Reapit and Alto. Usually bundling client accounting with property management. | Whether the accounting module can produce a per landlord position at a past date, or only today. |
| Listing, distribution and brokerage CRM | An MLS feed per market in the United States, IDX display on brokerage sites, portal feeds elsewhere, and a CRM in front. | Which Data Dictionary version each feed is issued against, and who holds the licence for the markets you want. |
| India, the Gulf and the association layer | Sell.Do and Anarock on developer sales, MyGate, ADDA and NoBrokerHood on the society side, with Tally and Zoho underneath. | Which system is authoritative for the charge. The integration question here is rarely the API. |
Which system is authoritative for a charge decides more of this build than the choice of product. See what moves the number on a property management software build.
Compliance
Not a badge wall. These are the instruments that change the data model or the delivery date. Every row was read at its own primary source and carries the date it was last read. The regional ones move.
| Instrument | What it forces the software to do | When |
|---|---|---|
| Renters' Rights Act 2025, England | GOV.UK's landlord overview says existing assured shorthold tenancies become assured periodic, and that a tenancy agreement cannot carry an end date. Section 21 is gone: possession runs on section 8 grounds. | In effect 1 May 2026. Read 13 November 2026. |
| Register your rental property service, England | GOV.UK's guidance of 29 October 2026 puts the landlord and each let property on a register, issues a rental property number, and gives 28 days to complete the record with gas, electrical and EPC evidence. | Region by region from 15 December 2026. Read 13 November 2026. |
| Tenant Fees Act 2019, deposit caps | GOV.UK's fee guidance caps the deposit at 5 weeks' rent below £50,000 annual rent and 6 weeks between £50,000 and £100,000, leaves rents above £100,000 outside the Act, and caps a holding deposit at 1 week. | Guidance updated 12 November 2026. Read 13 November 2026. |
| Domestic minimum energy efficiency standard | GOV.UK's landlord guidance says F and G cannot be let on a new tenancy since 1 April 2018, and since 1 April 2020 cannot continue to be let, unless an exemption is registered. The EPC band gates the tenancy. | 1 April 2018, then 1 April 2020. Read 17 November 2026. |
| Client money protection, England | Scheme membership is mandatory under the 2019 regulations, per GOV.UK's enforcement guidance. Store the membership and its certificate, surface it where a client sees it, and raise a task when it changes. | In force 1 April 2019. Read 13 November 2026. |
| Dubai Law No. (8) of 2007, escrow accounts | Dubai's own legislation text opens the account in the project's name and dedicates it to that project, at Articles 7 and 9. Article 14 has the escrow agent retain five percent of each account once the completion certificate is obtained, released a year after units are registered. | Issued 6 May 2007. Read 13 November 2026. |
| Dubai Law No. (26) of 2007, tenancy registration | Article 4 requires a written lease contract with named terms, and says every lease contract is registered with RERA, with no authority hearing a dispute on an unregistered one. Ejari is the registration system; RERA is the requirement. | Issued 26 November 2007. Read 13 November 2026. |
| Real Estate (Regulation and Development) Act, 2016, India | The regime for project registration and project escrow: registration before marketing or sale, and money from allottees held in a separate project account for construction and land cost. We keep the percentage as configuration read from the statute, never a constant. | Act of 2016. Read 13 November 2026. |
We hold no certifications. Not ISO 27001, and not SOC 2, which is an attestation examination rather than a certificate. For GDPR and PCI DSS the scope statement matters more than the badge: whether tenant, applicant and client account data sit inside the boundary. We do not hold client money, we are not a credit reference agency, and we do not file with a regulator for you.
Transparency
We publish the hours: seven modules with their ranges, and the arithmetic. A fixed price follows discovery.
Phase one
1,380 hours
The worked example, seven modules, each one inside its own range above.
Typical timeline
16 to 24 weeks
As a squad. A statutory date inside the window compresses scope rather than the calendar.
Module span
1,140 to 1,980
Every module at its minimum, through to every module at its maximum.
| Driver | Hours |
|---|---|
| How many charge types, and how variableA monthly rent with an uplift is a different engine from stepped, indexed and reviewed commercial terms. | High impact |
| Whether the tenancy model already versionsIf it does, this is integration work. If not, effective dating goes in under a live rent ledger, the costliest thing to add late. | The largest swing |
| Whether service charge is in scopeApportionment schedules, base years, expense stops and gross up provisions are a second model, not a report. | Adds real scope |
| How many listing feeds, and at which versionsTwo feeds on one Data Dictionary version share most of the mapping. Two versions apart do not. | Per feed, not once |
| Which core you keep, and what it exposesVendor API surface at your specific version, not the one in the current documentation. | 80 to 200 each |
| How client money is currently heldBuilding a per landlord position is bounded work. Reconstructing one out of a pooled history is not. | 180 to 300 |
| How many live tenancies migrateReplay testing scales with the variety of the terms, not the number of tenancies. | Rarely small |
| Module | Hours |
|---|---|
| Tenancy and lease model with versioning and effective dating | 200 to 340 |
| Charge schedule, indexation and rent review engine | 160 to 280 |
| Client money ledger and reconciliation | 180 to 300 |
| Service charge budgeting and annual reconciliation | 160 to 280 |
| Arrears, notices and possession workflow | 120 to 220 |
| Integrations: accounting core, payments, referencing, portals | 180 to 320 |
| Portals, reporting and the audit trail | 140 to 240 |
Delivery
Five phases, each named by the artifact it produces rather than by a stage in a generic waterfall.
Phase 01
How the tenancy handles time, written down before anything is built on it. What is versioned, what is not, and why. Every later argument resolves against it.
Phase 02
Every charge type your agreements can produce, with its trigger, its arithmetic and its backdating behaviour. Written before the engine, because it is the engine's test suite.
Phase 03
Each feed mapped to the standard version it was issued against, with your local fields kept out of the standard ones. A second market then reuses the mapping.
Phase 04
Where money sits at each step, whom it belongs to, and how a per landlord position is proved at a past date. Agreed with whoever signs your accounts.
Phase 05
A full past year replayed per tenancy against the new model, compared charge by charge, with differences explained rather than netted off. Totals are not the test.
Four families: property management systems with client accounting, brokerage and agency CRM, listing distribution over an MLS feed or IDX, and the portals and field apps on top. Yardi, MRI, AppFolio, Entrata and Buildium sit in the first. Most businesses run three and assume one covers the others.
There is no single best one. If you are letting, it is a property management system whose client accounting can produce a per landlord position for a past date. If you are leasing commercially, it is a system holding the lease terms as a schedule. If you are developing, it is sales and escrow receipting keyed to certified milestones.
We will not rank them, because that ranking changes with who paid for the list. The deciding question is integration: whether the CRM can hand a signed deal to the system holding the tenancy without a person retyping it, and whether its feed licence covers your markets.
It is the standard way to read listing data from an MLS, and you need it if you take an MLS feed. RESO's Transport list carries Web API Core at 2.1.0, dated December 2023, speaking OData 4.01. RESO's certification page says it certifies Web API Core 2.0.0 and Data Dictionary 2.0 today, and that NAR MLS policy requires compliance with RESO's most recent standards.
16 to 24 weeks as a squad. The worked example above is 1,380 hours across seven modules, and the module ranges sum to 1,140 hours at every minimum and 1,980 at every maximum. A statutory date inside the window compresses scope rather than the calendar.
You do, or your protection scheme does. We do not hold client money at any point. We build the ledger, the per landlord position and the reconciliation, and integrate to an established accounting core rather than replacing it, because client money is a regulated ledger with audit expectations.
Yes, and that is the more common shape of this work. Yardi, MRI, AppFolio, Entrata and Buildium are configurable rather than programmable, so the first question is which extension points your version exposes. Vendor documentation describes the current release and you may not be on it.
Four steps with a shape attached to each, so booking a call is a known quantity.
Bring how your tenancy record handles time, and one arrears figure you had to defend. Those two answers size the project faster than an hour of description.
We establish whether your tenancy record can reproduce a past state, and what it costs you when it cannot. That usually explains the symptoms you called about.
Module by module against the hour ranges on this page, with anything excluded named as excluded. If your core already does most of it, the document says so.
You choose whether we build it, your team does, or your incumbent extends. The document is useful in all three cases and it is yours either way.
Bring your current tenancy record and one arrears figure you had to defend. Thirty minutes on those two usually tells both of us whether this is a fit, and you leave with the hours either way.
Real feedback from the people we've proudly partnered with.
Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.
We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.
Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.
Explore further
The versioned tenancy store and the charge ledger
Tenant, owner and landlord portals
Inspection, works and resident apps
Lease abstraction and document control
Arrears chasing and works routing
Listings and marketplace, the other side of this line
Client money rules and the billing behind them
Service charge, submetering and recharge
Every sector we build for, in one place
Tenancy, lease and service charge in one system
Where a ledger helps and where it does not
Portals for landlords, tenants and agents
Tenancy, document and automation writing that applies directly to property systems.