• Welcome to AppraisersForum.com, the premier online  community for the discussion of real estate appraisal. Register a free account to be able to post and unlock additional forums and features.

Quicksourse (alamode) VS Spark

Status
Not open for further replies.
For me, Spark.

I tried QuickSource back in 2017. I liked it. It covered the top half of the grid pretty well. I loved that it snagged the MLS comp photos.

I had some issues, though, and it took a while for their tech support to get back to me. I remember they were nice, but they were not what I was looking for.

I gave Spark a try in 2018 or 19 (I forget). I like it—I don't love it, but I like it a lot.

Here's what it does, and here's how I use it:

First, it imports tons of comps well. This is its main job. It gets well over 50% of what I need. Our MLS (Bright) needs to be re-configured for it to do any better. I import far more comps than I used to b/c so much of the form is completed. I can always cut them later.

Unlike QuickSource, it does not grab MLS photos. It will take them from Google if you set a switch, but Google photos without any editing are typically garbage.

Could I get all of that info from a local import? Mostly, but not everything. Spark is more complete than what I can accomplish alone.

Second, it's linked to Dwelling Cost. I run cost approaches for almost every non-condo report because it's so fast (compared to M&S, which is clunky as sh#t). It's also free, whereas Marshal & Swift charges $50 / month or $17 / report (I think).

Interestingly, it can also generate a PDF version of just a cost approach (much more detailed than page 3 of the URAR). Not often, but once or twice a year, I need that, and that feature comes in handy.

Third, it does do the MC form, market trends, etc. ... all of the market sections. I don't use this most of the time. I prefer to do my own, and I get slightly different results. I'm interested in the previous year as well, so I'm deep into the market section already. I like that it's there to double-check, though.

Spark also wins in the tech support department. They respond to emails and answer the phone. You can also do a Zoom session with the creator during Friday afternoon office hours.

Then there's Synapse. It's cool. It's a work in progress, though, and I don't know how long I'll keep it at $30 / month. I use it for my court cases and more difficult properties.

The biggest problem I have with Spark and Synapse?:

The writing (in the support-for-adjustments' comments and in the cost approach) is pretty bad. I'll post an example in a minute.

Conclusion:

Spark saves me some time, but I use it because it's just more thorough overall, allowing me time for other parts of the form and problem. Synapse increases the amount of time I spend on a report, not saves, but it gives me something useful to talk about, for court or for those times when a reviewer is going to actually read your report.

QuickSource wasn't there for me in full 7 years ago. A lot can happen in 7 years, so it might be worth doing a trial and see if they have figured some things out since then.
 
Bad writing in Synapse... if anyone's listening, now's your chance to make some improvements:

This is just one section (of 20+). This is the one for GLA:

The GLA adjustment was developed at $42 per square foot. To arrive at this adjustment, 17 different adjustment methods were utilized and many of those were calculated on three sets of data. That resulted in a total of 19 different analyses being performed. Of those analyses, a total of four were given weight and consideration. The results (based on those four methods) provide an adjustment range from $0 to $223. Depreciated Cost, Robust Least Median of Squares Regression, Least Median of Squares Regression, and Least Absolute Deviation Regression were the adjustment methods used to develop this adjustment.

vs. me:

The size of a property affects value. The contributory value for GLA is $42 per square foot. This adjustment results from 4 types of analysis, including depreciated cost, robust least median of squares, least median of squares, and least absolute deviation.

What's wrong with Synapse?:

- passive voice all over the place ("was developed at", "were utilized", "were calculated", "being performed", "were given", and then the other verbs are to be or otherwise non-active ... there's one active verb in the whole mess ("provide")...

- mixture of numbers ("17" but also "four") ... yes, I know that follows proper English, but it's confusing as hell. The "four" in this case should really be "4"...

- extra, filler words: "17 different adjustment methods" - what's the difference between that and "17 adjustment methods" .... "a total of four were given weight" ... what's the difference between that and just "four were given weight"

- repeated words: "Adjustment" shows up six times. Wow. Other repeated words: "method", "analysis" ...

- But wait, there's more: Capitalization errors; dangling modifiers, and other stuff ...

Yeah, I know, not many folks read the addendum, anyway, but it's so easy to fix. Spark, if you're listening, please consider handing your comments over to a professional writer (or at least scrubbing it with Grammarly or some other AI writing program).
 
isn't it a little slow, looking back and forth, using your typewriter.
Well, I set my iPad next to my IBM Selectric and it goes pretty quick once I figured how to download from my mobile app.

If they have programs to form fill the comparable sales, why do they need us?
 
If they have programs to form fill the comparable sales, why do they need us?

In Virginia it's because the information in Bright is often wrong:

- The construction materials say "Brick," when in reality it's aluminum with a brick skirt.
- The architectural style says "Colonial" when it's really a split-foyer.
- The estimated size is 2,400 sf when it only has 1,600 sf.
- no deck, patio, balcony, or porch is mentioned
- no basement or garage is mentioned
- no off-street, carport, or other parking is mentioned
- waterfront or water view is noted but there is no unobstructed water anywhere near the listing
- utilities are incorrectly listed (central a/c, gas, well, septic, etc.)
- condition is described glowingly, but it's really a dog

The list goes on ... and that's just the listing. The tax records are often wrong too.

Certain things, however, are usually correct, like number of bathrooms and lot size. Number of fireplaces also seems to always be right (so long as the fireplaces are still working).

The bottom line is that a form filler isn't necessary, but I find it helpful in getting a chunk of the busy-work out of the way while I focus on other stuff that's more important to determining the value. Additionally, I find that when I'm using Spark, I end up importing 7-9 comps and cutting half later. I don't typically do that when it's all manual or my own wimpy import through Total.
 
Bad writing in Synapse... if anyone's listening, now's your chance to make some improvements:

This is just one section (of 20+). This is the one for GLA:

The GLA adjustment was developed at $42 per square foot. To arrive at this adjustment, 17 different adjustment methods were utilized and many of those were calculated on three sets of data. That resulted in a total of 19 different analyses being performed. Of those analyses, a total of four were given weight and consideration. The results (based on those four methods) provide an adjustment range from $0 to $223. Depreciated Cost, Robust Least Median of Squares Regression, Least Median of Squares Regression, and Least Absolute Deviation Regression were the adjustment methods used to develop this adjustment.

vs. me:

The size of a property affects value. The contributory value for GLA is $42 per square foot. This adjustment results from 4 types of analysis, including depreciated cost, robust least median of squares, least median of squares, and least absolute deviation.

What's wrong with Synapse?:

- passive voice all over the place ("was developed at", "were utilized", "were calculated", "being performed", "were given", and then the other verbs are to be or otherwise non-active ... there's one active verb in the whole mess ("provide")...

- mixture of numbers ("17" but also "four") ... yes, I know that follows proper English, but it's confusing as hell. The "four" in this case should really be "4"...

- extra, filler words: "17 different adjustment methods" - what's the difference between that and "17 adjustment methods" .... "a total of four were given weight" ... what's the difference between that and just "four were given weight"

- repeated words: "Adjustment" shows up six times. Wow. Other repeated words: "method", "analysis" ...

- But wait, there's more: Capitalization errors; dangling modifiers, and other stuff ...

Yeah, I know, not many folks read the addendum, anyway, but it's so easy to fix. Spark, if you're listening, please consider handing your comments over to a professional writer (or at least scrubbing it with Grammarly or some other AI writing program).
First of all, I really appreciate ALL of your comments and yes, I’m listening :)
Regarding the commentary I have a few things to say. First, the comment you posted that’s from Synapse is the longest, most detailed we offer but we have variations of comments so I would definitely recommend going for the shorter versions to more closely match the comment you posted that’s your own. When you’re in Synapse, click View Comments at the top right and then you can customize comments for each different feature you’re getting an adjustment for.
I think that will help but you probably won’t be completely happy due to the passive voice. The issue is that commentary is handled very differently by appraisers so it’s difficult to come up with comments everyone will be happy with. The comments you see now are where we landed after feedback from our beta-testers. This was considered the best overall by our users although, of course, everyone would like to make changes here and there.
I disagree with you on the use of “different” being an unnecessary filler word. It’s an important word to use because while there may have been 17 different methods, there may be 34 adjustment methods calculated. For example Least Absolute Deviation and Ordinary Least Square Regression could have each been run twice for a total of four adjustment results but that would be only two different methods (since each was run twice).
I hear you on the 17 and four. I did use “four” instead of “4” since it’s proper to do that but I get why it looks weird. I will have that changed by the end of this week. I’ll try for today or tomorrow but I’m traveling back home from an appraisal conference and am backed up on work so may not be able to get to it right away. Also, I can’t remember how difficult that will be to modify.
Regarding the many uses of adjustment, method, etc I think if you change the settings for comments like I described above that will help a lot. I don’t see the punctuation issues you see so please let me know what you mean. Do you not like that I capitalize the names of the adjustment methods?
Our new tool (called Nova) combines Spark with adjustment support (like Synapse). When we release it, not all features will be there but we are planning on integrating some type of dynamic commentary and I hope to eventually include a way for you to upload your own commentary so it can learn your voice and speak like you do. I don’t know how far in the future that is but it’s definitely doable. Until then we’ll work on refining the comments based on feedback.
Thanks again and happy to hear anything else that could help, especially as we build out Nova so we can make changes before we release it.
Brandon Reich
 
First of all, I really appreciate ALL of your comments and yes, I’m listening :)
Regarding the commentary I have a few things to say. First, the comment you posted that’s from Synapse is the longest, most detailed we offer but we have variations of comments so I would definitely recommend going for the shorter versions to more closely match the comment you posted that’s your own. When you’re in Synapse, click View Comments at the top right and then you can customize comments for each different feature you’re getting an adjustment for.
I think that will help but you probably won’t be completely happy due to the passive voice. The issue is that commentary is handled very differently by appraisers so it’s difficult to come up with comments everyone will be happy with. The comments you see now are where we landed after feedback from our beta-testers. This was considered the best overall by our users although, of course, everyone would like to make changes here and there.
I disagree with you on the use of “different” being an unnecessary filler word. It’s an important word to use because while there may have been 17 different methods, there may be 34 adjustment methods calculated. For example Least Absolute Deviation and Ordinary Least Square Regression could have each been run twice for a total of four adjustment results but that would be only two different methods (since each was run twice).
I hear you on the 17 and four. I did use “four” instead of “4” since it’s proper to do that but I get why it looks weird. I will have that changed by the end of this week. I’ll try for today or tomorrow but I’m traveling back home from an appraisal conference and am backed up on work so may not be able to get to it right away. Also, I can’t remember how difficult that will be to modify.
Regarding the many uses of adjustment, method, etc I think if you change the settings for comments like I described above that will help a lot. I don’t see the punctuation issues you see so please let me know what you mean. Do you not like that I capitalize the names of the adjustment methods?
Our new tool (called Nova) combines Spark with adjustment support (like Synapse). When we release it, not all features will be there but we are planning on integrating some type of dynamic commentary and I hope to eventually include a way for you to upload your own commentary so it can learn your voice and speak like you do. I don’t know how far in the future that is but it’s definitely doable. Until then we’ll work on refining the comments based on feedback.
Thanks again and happy to hear anything else that could help, especially as we build out Nova so we can make changes before we release it.
Brandon Reich

Thanks for taking the time to respond. For what it's worth, your product is better than anything I've tried up to this point. And like some people already pointed out, while it might not always be necessary to have such a high level of support, it sure is helpful for divorce work and other litigation. It's nice to be able to point to another method, another level of support.

Additionally, I love that you hold office hours and otherwise listen to your clients and continue to make your product better.

I shipped a text to your office in Austin earlier today: Effective Report Writing: A Guide for Appraisers and Reviewers. It's short and easy to read. Personally, reading it has made my own writing better. I guarantee you'll get at least one new idea out of it.

The two places where I think it would benefit Spark are in the Cost Approach comments and the Adjustment Support comments, but use it however you wish. I've already got workarounds in place for my stuff, anyway.

Cheers, and keep up the good work!
 
Thanks for taking the time to respond. For what it's worth, your product is better than anything I've tried up to this point. And like some people already pointed out, while it might not always be necessary to have such a high level of support, it sure is helpful for divorce work and other litigation. It's nice to be able to point to another method, another level of support.

Additionally, I love that you hold office hours and otherwise listen to your clients and continue to make your product better.

I shipped a text to your office in Austin earlier today: Effective Report Writing: A Guide for Appraisers and Reviewers. It's short and easy to read. Personally, reading it has made my own writing better. I guarantee you'll get at least one new idea out of it.

The two places where I think it would benefit Spark are in the Cost Approach comments and the Adjustment Support comments, but use it however you wish. I've already got workarounds in place for my stuff, anyway.

Cheers, and keep up the good work!
Wow! Thank you for sending us that and I'll definitely read it. Really appreciate the feedback.
Just an FYI, I'm not personally in most of those Office Hours calls but our Chief Appraiser (Jack Lavoie) is and he gives me a summary of what I need to know to make our products better after the call. In the future I hope to get back on them but I'm WAY behind in building stuff so I had to ask Jack to take over for awhile.
Last, regarding that change I said I would make. I said I would have it done last week but I didn't. However, I made the change in the code and it should be deployed and working in Synapse by tomorrow night.
Again, really appreciate you taking the time to give the feedback and also for sending me that text! Take care!
Brandon Reich
 
Status
Not open for further replies.
Find a Real Estate Appraiser - Enter Zip Code

Copyright © 2000-, AppraisersForum.com, All Rights Reserved
AppraisersForum.com is proudly hosted by the folks at
AppraiserSites.com
Back
Top