• Real Estate Consulting Rooted in Real Experience

Posts By :

Brian Kinash

Why Most MLSs Are Sitting on a Data Problem They Haven’t Named Yet

 150 150 Brian Kinash
By:
0

Most MLSs have a data problem. It’s not always obvious — the listings are flowing, the IDX feeds are running, and the members aren’t complaining loudly. But underneath the surface, the gaps are growing.

The issue isn’t usually the data itself. It’s the lack of a deliberate strategy around it. What data do you own? What’s being shared, and with whom? What governance policies actually exist versus what’s assumed? And critically — what happens when a vendor, a merger, or a regulatory change forces the issue?

What a Data Strategy Actually Looks Like

A data strategy for an MLS doesn’t have to be a 200-page document. At its core, it answers a few fundamental questions: What data do we collect? How is it stored and maintained? Who has access to it, under what terms? How does it align with RESO standards? And what’s the plan when any of those answers need to change?

Most MLSs can’t answer all of those clearly. That’s the starting point — not a failure, just an opportunity.

Where to Start

Begin with an audit of your current data flows. Map what’s coming in, what’s going out, and what sits in the middle. From there, you can start identifying where the real risks and opportunities live.

If you’d like to talk through what this looks like for your organization, let’s connect.

AI in the Brokerage: What’s Actually Useful vs. What’s Just Noise

 150 150 Brian Kinash
By:
0

Every brokerage leader is hearing about AI. Tools, platforms, and vendors are promising transformation. Most of it is noise. Some of it is genuinely useful. The challenge is knowing the difference.

The most effective AI applications in brokerages right now aren’t the flashy ones — they’re the quiet productivity improvements that save agents 20 minutes a day. Drafting listing descriptions. Summarizing showing feedback. Responding to routine inquiries. Researching comparable properties faster.

Where AI Actually Delivers

The highest-value AI use cases in real estate brokerage fall into three buckets: content and communication (faster, better written output), research and analysis (data synthesis that used to take hours), and administrative triage (routing, summarizing, and organizing information so agents focus on clients).

What to Ignore for Now

Anything that promises to “replace” your agents’ judgment isn’t ready. AI is a tool, not a strategy. Brokerages that treat it as a competitive advantage treat it the same way they treat any other tool — they train their people on it, build workflows around it, and measure whether it’s actually helping.

Want to talk about where AI fits in your brokerage’s operations? Start here.

RESO Web API: What It Is, Why It Matters, and What Most People Get Wrong

 150 150 Brian Kinash
By:
0

RESO — the Real Estate Standards Organization — has been working for years to standardize how real estate data is structured, accessed, and shared. The RESO Web API is the most important output of that work for MLSs and technology providers today.

What It Actually Is

The RESO Web API is a standardized protocol for accessing MLS data. Instead of every MLS and vendor building custom integrations, the Web API provides a common language — based on OData — that allows data to be consumed consistently regardless of the platform.

Why It Matters Now

Vendors are increasingly requiring RESO Web API compliance. MLSs that haven’t made this transition are creating friction for their members and limiting what technology partners can offer. The good news: most MLS platforms now support it. The work is in configuration, validation, and ensuring your data dictionary is aligned.

What People Get Wrong

The most common mistake is treating RESO compliance as a checkbox exercise. Real compliance means your data is consistently mapped, your fields make sense, and the API actually works the way vendors expect. That requires more than turning on a feature.

If your MLS is working through RESO alignment, let’s talk.

Getting More Out of Matrix: Features Most Agents Have Never Touched

 150 150 Brian Kinash
By:
0

Matrix is the most widely used MLS platform in North America — and most agents are using about 30% of what it can do. That’s not a criticism. It’s an opportunity.

The Features Worth Learning

Beyond the basics of running searches and pulling CMAs, Matrix has powerful tools that most agents discover by accident — if at all. Custom hotsheets that alert you to activity in specific neighborhoods. Speed bar shortcuts that cut search time significantly. Market condition reports that give clients context, not just data. Auto-email setups that keep prospects engaged without manual follow-up.

The Training Gap

Most agents learned Matrix from a 45-minute session when they joined their board. The platform has evolved significantly since then, and training hasn’t kept up. That’s where real productivity gains live — not in a new app, but in the one already sitting in front of them.

If your brokerage or board is interested in Matrix training that actually changes how agents work, reach out.

The Hidden Cost of Inconsistent MLS Data

 150 150 Brian Kinash
By:
0

When people talk about MLS data problems, they usually mean obvious things — wrong listing statuses, missing fields, duplicate records. But the real cost of inconsistent data is much harder to see, and far more expensive than most organizations realize.

What Inconsistency Actually Looks Like

It’s rarely catastrophic. It’s the agent who submits a listing with a square footage that’s technically required but never validated. It’s the vendor who’s been working around a mapping issue in your feed for two years because nobody flagged it. It’s the report your staff pulls for the board that everyone privately knows isn’t reliable.

Over time, these small gaps compound. Members lose trust in the data. Vendors build workarounds that become permanent. Staff stop correcting problems because it feels futile. And when a migration, merger, or compliance requirement forces the issue, the debt comes due all at once.

The Real Costs

Inconsistent data costs MLSs in at least four ways: vendor friction (integrations break or behave unpredictably), member complaints (agents lose confidence in search results and reporting), staff time (data cleanup is invisible but constant), and governance risk (when policies aren’t enforced consistently, enforcement becomes arbitrary).

Where to Start

The first step isn’t a technology fix — it’s a data audit. Map what fields you require, what you actually receive, and how consistently the two align. That gap is your starting point. From there, you can build validation rules, update your data entry policies, and establish a regular review cadence.

It doesn’t have to be done all at once. But it does have to be started deliberately.

If you’d like help scoping a data audit for your MLS, reach out here.

Prompting for Real Estate: How to Get Better Output from AI Tools

 150 150 Brian Kinash
By:
0

Most real estate professionals who are disappointed with AI tools are actually disappointed with their prompts. The tool isn’t the problem — the input is. And the good news is that prompting is a learnable skill, and even small improvements make a significant difference in output quality.

The Core Principle: Specificity Wins

Vague prompts produce vague output. “Write a listing description” gets you something generic. “Write a listing description for a 3-bedroom, 2-bathroom rancher in a quiet cul-de-sac, recently renovated kitchen, backing onto a greenbelt, targeting move-up buyers with school-age children” gets you something you can actually use.

The more context you give, the better the output. Property details, target buyer, tone, length, what to emphasize — all of it helps.

Useful Prompt Patterns for Real Estate

A few patterns that work well in practice:

Role + Task: “Act as an experienced buyer’s agent. Write a follow-up email to a client who attended three showings this weekend and hasn’t responded yet.”

Format instructions: “Write this in three short paragraphs. Keep sentences under 20 words. Use a warm but professional tone.”

Constraint framing: “Do not mention price. Focus on lifestyle, not features. Avoid the word ‘stunning’.”

These sound simple, but they dramatically tighten the output and reduce the amount of editing you need to do afterward.

What to Always Review

AI output should always be a first draft, not a final one. Check any statistics or facts it cites. Make sure the tone sounds like you. And watch for filler phrases that sound impressive but say nothing — AI loves those.

The goal isn’t to remove yourself from the process. It’s to let the AI handle the blank-page problem so you can focus on refining.

If you’re interested in a practical AI prompting session for your team or office, reach out — this is one of the most immediately useful trainings we offer.

Tech Stack Audit: How to Know If Your Brokerage Is Overpaying for the Wrong Tools

 150 150 Brian Kinash
By:
0

The average brokerage is paying for more software than it uses — and missing tools it actually needs. This isn’t a criticism; it’s just what happens when technology decisions get made reactively over years. A vendor demo here, an agent request there, a “let’s try it for 30 days” that became permanent.

The result is a tech stack that’s expensive, confusing, and doesn’t really hold together as a system.

What a Tech Stack Audit Actually Involves

A useful audit starts with a simple inventory: what tools are you paying for, who’s using them, and what for? Most brokerages are surprised by the list when they actually write it down. Then comes the harder questions: What overlaps with something else? What do you pay for that agents don’t use? What workflow gaps exist that no current tool addresses?

The goal isn’t necessarily to cut everything. Sometimes the right answer is consolidation. Sometimes it’s replacing one tool with a better one. Sometimes you discover you’re paying for an enterprise tier of something where the basic version would do.

The Overlap Problem

The most common waste pattern I see in brokerage tech stacks is overlapping functionality. A CRM that does transaction management. A transaction management system that does document storage. A document storage solution that also has e-signature. An e-signature tool that also has a CRM.

None of these tools talk to each other, agents use different ones for different tasks, and the brokerage is paying for four tools to do what one well-chosen platform could handle.

Where to Start

Pull your software subscriptions from your credit card and accounting records. You’ll find things you forgot about. Then survey your team — not “do you use X?” but “what do you actually use every day and what’s annoying about it?” The gap between what you’re paying for and what people actually value is where the opportunity is.

If you’d like a structured tech stack review for your brokerage, start the conversation here.

Platform Adoption Isn’t a Training Problem — It’s a Change Management Problem

 150 150 Brian Kinash
By:
0

You rolled out a new platform. You ran training sessions. You sent the emails. And six months later, half your members or agents are still doing things the old way — or not using the new system at all.

The instinct is to schedule more training. That’s usually the wrong instinct.

Why Training Alone Doesn’t Work

Training teaches people how to use a tool. It doesn’t answer the questions that actually determine whether someone adopts it: Why should I change what I’m already doing? What’s in it for me? Who do I call when something breaks? Is this going to be here in two years, or will I have to learn something new again?

People don’t resist new systems because they don’t understand them. They resist because change is effortful and the value isn’t obvious enough to justify that effort. Training doesn’t solve that problem. Communication, trust, and early wins do.

What Actually Moves the Needle

The organizations that achieve high platform adoption share a few common practices. They communicate the why early and repeatedly — not just what’s changing, but why this change is good for the people being asked to make it. They identify early adopters and give them a reason to become advocates. They make it easy to get help, and they make asking for help feel normal rather than embarrassing. And they celebrate visible wins — the agent who saved two hours a week, the staff member who found a workflow that cut a recurring headache.

The Long Game

Adoption is not an event. It’s a process that happens over months, and it requires ongoing attention even after the “launch” is behind you. The MLSs and brokerages that treat it as a long-term initiative — rather than a go-live milestone — consistently see better results.

If your organization is struggling with adoption on a current or upcoming platform rollout, let’s talk about what’s actually getting in the way.

Choosing an MLS Platform: What the Sales Demo Won’t Tell You

 150 150 Brian Kinash
By:
0

Every MLS platform looks good in a demo. The interface is clean, the features are well-explained, and the sales team is polished. The experience of actually running your MLS on the platform is a different matter entirely.

Choosing a platform is one of the highest-stakes decisions an MLS makes — it affects every member, every transaction, and every staff interaction for years. Getting it right requires going well beyond the demo.

Questions to Ask That Sales Teams Don’t Love

What does your support ticket resolution time actually look like — not the SLA target, but the real average for issues like ours? Can we speak with three MLSs of our size that you’ve onboarded in the last 18 months — not references you’ve chosen, but ones we identify? What’s your migration process for our historical data, and who owns the risk if something goes wrong? What features on your roadmap are actually committed versus aspirational?

The answers — or the hesitation before the answers — tell you a lot.

What Reference Checks Should Actually Cover

Most reference checks are too polite to be useful. Push past “how’s the platform?” to the specific questions that matter: How long did the migration actually take versus what you were told? What surprised you that you wish you’d known? What’s your biggest ongoing frustration? If you were starting over, what would you do differently?

Real answers come from specific questions. Vague questions get marketing answers.

The Configuration Question

Every MLS has specific workflows, data fields, and member expectations that need to be accommodated in the new platform. Understanding what’s configurable, what requires a custom development request, and what simply isn’t possible is critical before you sign — not after.

Get the configuration requirements in writing. Walk through your current workflows with the vendor’s implementation team, not the sales team. The gap between “yes we can do that” and “here’s how we’d do that” is where surprises live.

If your MLS is evaluating platforms or preparing for a migration, get in touch — navigating this process is exactly what I help organizations do.

RESO Data Dictionary: Why Field Standardization Is Harder Than It Sounds

 150 150 Brian Kinash
By:
0

The RESO Data Dictionary is one of the most important infrastructure investments the real estate industry has made in the last decade. By standardizing what fields exist, what they’re called, and what values they can hold, it creates a common language that makes integration faster, cheaper, and more reliable.

In theory. In practice, adoption is messier than the documentation suggests — and most MLSs are somewhere in the middle.

What the Data Dictionary Actually Does

At its core, the RESO Data Dictionary defines a standard set of field names (like ListPrice, BedroomsTotal, LivingArea) and the lookup values that go with them. Instead of one MLS using “Active” and another using “A” and another using “For Sale,” there’s a defined standard. Vendors building on top of the data don’t have to build separate translation layers for every market they enter.

This matters enormously for portals, analytics tools, and technology vendors who operate across multiple MLSs. It also matters for MLSs themselves — consistent data is easier to govern, validate, and report on.

Where It Gets Complicated

The challenge is that most MLSs have years of legacy configuration that doesn’t align neatly with RESO standards. Custom fields that were built for local needs. Lookup values that members have been using for years and don’t want to change. Platform limitations that make certain mappings technically awkward.

Alignment isn’t impossible — but it requires deliberate mapping work, stakeholder communication, and in many cases, changes to member-facing data entry workflows that will generate pushback.

The Right Approach

Start with a gap analysis between your current field configuration and the RESO Data Dictionary. Prioritize the highest-traffic fields first — the ones vendors actually use and members actually fill in. Work through the mapping systematically, document your decisions, and build a review process so alignment doesn’t drift over time.

RESO certification is a milestone, but the real value is in the ongoing discipline of maintaining standards as your platform and member base evolve.

If you’re working through Data Dictionary alignment and want a structured approach, get in touch.

  • 1
  • 2