How to Choose a Website Vendor for Your REALTOR® Association

You'll do this roughly once every seven years, which means nobody on your staff is experienced at it and the consequences last a long time.

Here's how to think about it. We build one of these platforms, so read accordingly — but everything below is what we'd tell an association that ended up choosing someone else.

---

The four kinds of vendor

Your AMS provider. Convenient, bundled, one contract. Strong on membership data. The website is a secondary product for them and it usually shows. Best fit for small associations where simplicity outweighs polish.

A general web agency. Good design, modern build, no association experience. They'll do beautiful work and learn what NRDS is on your budget. Expect six to nine months. Ask hard about what happens when the project ends and you need to change something.

A specialist association platform. Built for associations, sometimes for REALTOR® associations specifically. Less bespoke design freedom, much less bespoke risk. This is where we sit.

A local developer or a member's nephew. Cheap, fast, and a serious business risk. When they get busy or move on, you own software nobody can maintain. We've replaced several of these.

None of these is universally right. The AMS bundle genuinely is the correct answer for a 400-member board with one staff member, and we'd tell them so.

---

The five questions that actually predict the outcome

Skip the feature checklists. These five tell you more.

1. "Show me the admin."

Not the homepage. The screen your communications director will use every week for the next five years.

Every public site looks good in a demo. Admin interfaces are where the difference between a platform someone enjoys using and one they avoid becomes obvious — and staff avoidance is how websites decay.

If a vendor won't show you the admin before you sign, that is the answer.

2. "Which associations like ours have you done, and can I call two of them?"

Ask for one where something went wrong. Every project has one. A vendor who says otherwise is either inexperienced or not being straight with you, and neither helps.

When you call the reference, ask: what took longer than expected? and what do you wish you'd asked before signing?

3. "What happens when our communications director wants to change something?"

The answer separates platforms from service contracts.

If routine changes require a ticket, a service request, or an hourly rate, you're buying an ongoing dependency. That may be acceptable — but price it over five years, because that's what you're actually signing up for.

4. "Have you connected to our MLS's feed before?"

The single largest technical risk in an association website project, and the one most often discovered late.

Every MLS is different. Three broad standards are in use — RESO Web API, Trestle, and legacy RETS — and the differences are substantial. A vendor who has done yours before can tell you what will be awkward. A vendor who hasn't will find out during your project.

Also ask who obtains the feed credentials and permissions. It's usually a third-party approval, it usually takes longer than anyone expects, and it belongs on the critical path from day one.

5. "What happens to our website if we leave you?"

Ask it plainly. You want to know:

• Do you own your content, and can you export it?
• Is the site built on something another vendor could take over?
• What are the notice terms?

You're not planning to leave. You're testing whether the commercial relationship depends on you being stuck.

---

What to weigh, and how much

A rough weighting that reflects where projects actually succeed or fail:

	Weight	Why
Relevant association experience	30%	The strongest predictor of whether the project lands
Technical fit (MLS, member data, SSO)	25%	Where the risk and the overruns live
Ease of use for staff	20%	Determines whether the site stays current after launch
Total cost over 5 years	15%	Not the build price — the whole thing
Timeline	10%	Matters most if you have a hard trigger

Design is deliberately absent. Not because it doesn't matter, but because it's the thing selection committees over-weight. Every vendor on your shortlist can produce an attractive site. Far fewer can handle your feed or build something your staff will actually maintain.

---

Warning signs

• A quote well below the others. Under-scoped integrations, almost always.
• No named references at similar scale.
• "Yes" to everything. Nothing has trade-offs? They haven't understood the requirement.
• They won't show you the admin.
• The proposal doesn't mention your MLS or member data at all.
• Design-first, data-later. A beautiful site with a broken directory is a failed project.

Good signs

• They ask about your MLS feed and your member data in the first conversation
• They give you a URL mapping plan before you ask about SEO
• They tell you which of your requirements is going to be difficult
• They disqualify themselves from something
• Their references answer the phone

---

A note on timelines

Agencies commonly quote six to nine months for an association site, and industry surveys suggest most redesigns run over on time, budget, or both.

Faster is possible when the association-specific parts are already built rather than being invented for you. One 9,400-member association — full platform — went live in twelve weeks.

Ask any vendor what specifically drives their timeline. If the answer is "it depends", ask what it depends on. The honest answer is usually: how quickly you make decisions, and how long your MLS takes to approve the feed.

---

Related

• Association website redesign RFP template
• What a redesign actually costs in 2026
• AMS vs. website: what your association actually needs