Most of a real estate agent app is not the listing search.
Ask an agent what fills the day and almost none of it is browsing listings. It is answering a lead before someone else does, confirming a showing, remembering that the sellers on Elm Street want a day of notice, and finding the note dictated in the car. A real estate agent app that only wraps a listing search is solving the part that was already solved. Before you shortlist real estate app builders, get clear on which half of the job you are actually building.
This page covers where listing data really comes from and what it costs you in paperwork, what federal rules say before your app texts a lead, what a showing record has to hold, and where a general CRM stops bending.
Check whether the app can text that leadThe short version
The listing feed is licensed, the rest of the day is yours.
Split the product in two. One half is listing data, which you do not own and cannot get without an agreement with every MLS whose data you want. The other half is what the day is made of: leads, showings, access notes, follow ups, documents. That half has no gatekeeper.
Most agent apps are built around the half you cannot control, then stall in licensing. Build around the half you can, and treat the listing feed as something you add per market once the paperwork clears.
There is no public MLS API you can just call
Take the plain answer to the question everyone asks first. There is no open MLS API a small brokerage can query without an agreement. There is a shared standard, which is a different thing and is regularly mistaken for one.
The standard is the RESO Web API, published by the Real Estate Standards Organization. It is a RESTful, OData based specification that MLSs implement, so field names and endpoints look the same across the MLSs that support it. RESO publishes the specification. RESO does not hold the listings.
Access is granted by each local MLS. Their own guidance is direct about it: you reach the Web API through your local MLS, after agreeing to that MLS data use and licensing policy, and the MLS or its software vendor then issues your credentials. The standard makes several feeds look alike. It does not turn several agreements into one.
For a small brokerage the practical read is: budget paperwork, not code. Expect a licence per MLS, a review of what you intend to display, and display rules you have to implement. One market is one process. Three markets is three processes, and they will not renew on the same day.
What the rules want before a real estate lead app sends anything
An app that fires off the first message by itself is a telemarketing system, whatever you call it internally. The federal rules at 47 CFR 64.1200 apply, and they are specific enough to build a data model from.
Calls and texts to a wireless number that use an automatic telephone dialing system or a prerecorded voice need prior express written consent from the person called. The written agreement has to state clearly that they authorise those calls, and it cannot be made a condition of buying anything. A tick box you cannot reproduce months later is not a record. Store the wording that was shown, the time, and what the person did.
Two more rules shape the schedule. A telephone solicitation to a residential subscriber may not be made before 8 a.m. or after 9 p.m., local time where the called party is. A do not call request has to be recorded within a reasonable time that may not exceed ten business days, and it has to be honoured for five years from when it was made.
So a real estate lead app carries three fields most contact tools treat as optional: a consent record with its own timestamp and wording, a time zone on the contact, and a suppression list that outlives the deal. None of this is hard to build. It is simply never there by default.
47 CFR 64.1200, delivery restrictions on calls and texts
Try it
Can the app send this one on its own
Three stored fields decide it. An app that holds none of them cannot answer the question at all.
Not automatically
- Blocked: Prior express written consent is on file
- Clear: Not on your internal do not call list
- Clear: Local time where they are is 8 a.m. to 9 p.m.
General information, not legal advice. Read the rule and check your state before you automate anything.
A showing is a record, not a calendar entry
The calendar part is the least interesting part. A showing has an address, a requested time, a confirmation state, who confirmed it, access instructions, and feedback that has to go back to the seller. Most of those change after the entry is created, which is why a shared calendar quietly breaks.
Access instructions are the field generic tools have nowhere to put. Lockbox code, gate code, which door, the dog, the neighbour with the spare key, whether the tenant has to be told in writing. Agents text this to each other at eight in the morning. It belongs on the property record, not in a thread.
Confirmation is a loop, not a flag. A request goes out, the listing side answers or does not, and the buyer has to be told either way. Modelling it as a status with a short history costs nothing to build and settles every later argument about who was told what.
Feedback needs an owner and a due date or nobody sends it. One field and one nudge, and the next listing presentation writes itself. A Saturday open house app runs on the same idea: capture the visitor, write down what they said about the kitchen, send the follow up before Monday.
What an agent CRM app holds that a general one does not
A realtor app is a CRM with a property attached to every record. General CRMs model a company, a contact and a deal. This business needs a contact who is a buyer on one file and a seller on another, a property that outlives both, and a transaction with a closing date and documents that expire.
Stages should match how the office already speaks: new lead, contacted, appointment set, agreement signed, active, under contract, closed, lost. The field that earns its keep is not the stage. It is the next action and its date. A pipeline without a next action is just a list with colours.
The property side keeps growing: walkthrough photos, a note about the roof, rough measurements, what the seller was told to fix before listing. That is a property survey app living inside the same product, and it is why agents end up carrying four apps instead of one.
Assume no signal. Basements, lifts, rural lots and concrete stairwells are where the notes actually get written. If saving a photo needs a network round trip, the note does not get written, and the app loses to the camera roll.
What each option actually gives an agent
| Option | Listing data | Consent record for texts | Your own access notes | Works with no signal |
|---|---|---|---|---|
| Notes app and text threads | No | No | in the thread | Yes |
| A general CRM | No | only if you add fields | No | varies |
| A real estate CRM platform | through your MLS feed | Yes | generic fields | varies |
| The member app from your MLS | Yes | No | No | No |
| An app you build | with each MLS agreement | Yes | Yes | Yes |
Building one around how your office actually works
Real estate CRM platforms are priced per seat per month and shaped around the average of a large brokerage. A three person team needs a fraction of that, plus one or two things the platform will not bend to: a referral split that is not a percentage, a seller who has to be called and never emailed, a listing checklist that belongs to your state rather than to the vendor.
Newly is an AI app builder. You describe the app in plain English, including the fields and rules your office actually has, and it writes a real React Native and Expo project you own, running it on a cloud simulator while it builds. Plans start at $25 a month and there is no free plan. iOS builds ship through TestFlight and App Store Connect using your own Apple Developer account, and Android goes to Google Play internal testing from the Deploy tab, or out as a standalone APK. It does not come with MLS data and it will not sign your data licence for you.
Settle one decision before the rest: where the listings and leads live. A lead record that exists on one phone is the same problem as the notes app you are trying to replace.
Questions people ask about real estate agent apps
No. There is no open MLS API you can query without an agreement. The Real Estate Standards Organization publishes the RESO Web API as a standard, but access is granted through each local MLS: you agree to that MLS's data use and licensing policy, and the MLS or its software vendor then issues your credentials. Working three markets means three of those processes.
Describe the week your office actually has
Write down the fields you keep retyping, the follow up nobody chases, and the access note that only exists in a text thread. Build around those three.
Start building