It all started with two phone calls to two separate IDX vendors:
Call #1
Eric: Hello. I really like your product and am considering moving from my current IDX vendor over to you.
Vendor #1: Great! Can I send you paperwork?
Eric: Well, there are a few features it’s missing – indexable listings and some conversion features I would like. Is there any way I can pay you guys to add these features for me? I have a decent budget for these features & understand that you would need to roll them out to the entire system, since you don’t provide custom IDX solutions.
Vendor #1: Sorry, we don’t take any customization orders.
Eric: Really? It seems like a win/win, since I get want I want, and you get to charge me to improve your own product.
Vendor #1: Sorry, it’s just something we don’t do.
Eric: hrrrrrm
Call #2:
Eric: Hello. I really like your product and wanted to get some more info.
Vendor #2: Great! What can I tell you?
Eric: Well, I already have a nice website and wanted to see if I could implement your indexable product on my own site.
Vendor #2: No, we have a proprietary system that it integrates with. You would have to move your site over. We charge $125/hour for that.
Eric: Okay…$125/hour is a little high, but I can live with that. I do tinker with code a bit and have some good, local vendors. Is there any way I could get access to just my site, once it’s moved over, in case I want to make my own customizations?
Vendor #2: No. You’ll have to use our developers and work on our schedule for any customizations.
Eric: Are you sure? It’s pretty easy to add directory specific FTP or shell access.
Vendor #2: There’s no way we can allow you to work on the site yourself or use your own vendors.
Eric: hrrrrrm
At this point, I was pretty frustrated. I spoke with a handful of developers in early stages of RETS projects with good, misguided intentions. They saw RETS from the consumer’s perspective, which is fantastic, but they didn’t understand RETS from an agents perspective – namely that Read more