Ask HN: Building tech stack for a dozen Realtor franchises - advice please

4 pointsby albahk13 anni fa4 comments

I have been asked by a trusted contact to implement a complete technology solution for over 15 real estate agency franchises he is acquiring. They all run on their own ad-hoc systems at the moment so they are basically 15 different systems. The goal is to get up and running with a robust platform that can cover the following and expand as and when new offices open:

- managing all customer data (crm functionality)

- storing all documentation centrally and securely (contracts, documents etc for each office plus shared documents provided by the master franchiser)

- email with calendars, blackberry support etc (I think hosted Exchange?)

- managing property listings, photos, floorplans, data sheets, flyers etc

- a shared collaboration space like MS sharepoint but I personally don't think SP is useable for the target audience, likewise wiki might be too technical

- conference calls, video conference (is Skype viable for business use?)

This is a lot more low tech than the usual HN startup but I wonder if the good people of HN could share their thoughts or recommendations. Thanks.

4 comments

gadders13 anni fa

I think for 80-90% of that you could use BaseCamp etc from 37 Signals. I'd custom build as little as possible.

skram13 anni fa

Sounds like you need a consultant with experience rather than just some free advice, IMHO.

lsiunsuex13 anni fa

This doesn't sound like a big deal to me. It's a lot of work for sure, but assuming your getting paid for this work, it's doable.

A Rackspace cloud server or 2; a CDN for the documents; I prefer to use Google Apps for email / calendar but thats me.

You could try BigBlueButton for the conference call / video or take parts of it and modify it to fit your needs.

Probably looking at 3-6 months of work if you have a decent plan put together and your not waiting on much from the client.

davismwfl13 anni fa

My advice, is just tackle one problem at a time and move through them pretty quickly. Accepting that as they begin to use it new use cases will emerge and you'll have to make adjustments. This doesn't mean just don't care what you select, it is just that in my experience this user base will have a hard time articulating their needs. And even if you have a ton of experience they will still change requirements as they start using it. So it is the start fast, adapt as needed methodology. And I would just communicate it to the client that you are going to solve one need at a time, and expect that you will need to revisit them over 2-3 months as people begin using each solution. The advantage to this, is some of that is really low hanging fruit that you could show him immediate benefits from, and have low risk to change. Like moving all email/calendar to Google Apps, or pick your cloud solution there.

Also, I personally feel this approach is being realistic and respectful to the staff that it is hard to articulate all the needs until a user gets their hands dirty with the solution. I also try not to use the word requirements with non-technical clients, instead opting for "Needs", "Wants", "Dreams" or something along those lines.

None of the project sounds hard technically, but it will take time and have some frustrations I imagine.

But I could easily see a Salesforce + Google (email, gdrive, calendar) + FreeConferenceCall (or something similar) + Skype. Most of that is low hanging. If they don't want to use the Cloud providers though, then you have a much larger and tougher task, not to mention way more expensive.