I'm especially interested to know the features and pricing.

Please do not do exclusively do some MSFT technology (i.e. c#, .net, VB...).  Otherwise everyone like me will be locked out.

Thanks
Jay

Thanks
Jay

Thanks!

Sean

I agree... to a point.

For instance, our corporate office has an online system (tied to accounting) into which we have to re-key basic loan data.  This is really annoying and wastes a lot of time.  I'm going to write a tool to log in and enter information for me.  If the SDK/API can make "borrower objects" readable through Java, then creating the tool would be much easier for me.  Otherwise, I'll have to find my own way to parse borrower files.

On the other hand, if the "objects" in point were accessible through VBA, I could do some powerful/amazing things.  For example, almost every system at least has Excel installed and I create many spreadsheets for customers.  If I can access point data with VBA, then I could make a "cash flow" sheet with one table showing a borrower's bills before refinancing and another table showing the bills after paying certain debts and lowering their interest rate.  Plus, I can pop in a couple charts and very visually show them the value of refinancing today.  Further, just by using income, liabilities, previous and new PITI, I could plot the data out 10 years in the future and show how much better off they'll be.  Through VBA and the SDK, I can write one program that automatically generates these excel spreadsheets for any borrower and instantly emails them--all with one button click.

As another example, I could pull all borrower data into access.  Then I can querry all closed loans that have interest-only terms expiring in the next 12 months.  From this set, I could make customized Word form letters with the details of their loan and property.  Then I could pass this into Outlook and automatically email each customer their individualized form letter reminding them it's time to re-fi.  Again, all done just by clicking a "notify I/O borrowers" button.

These are off the top of my head but the point is, there are endless uses to having Point data exposed and accessible to multiple programming languages.  One potentially simple solution would be to export basic XML objects since nearly all major languages have XML parsers.  There could be a "loan" object that has all the basic fields.  A "originator" object could have information relating to an originator's pipeline and production.  A "cardex" object could expose database information.

Alternatively, to keep things really simple, basic XML objects could be created that just contain the fields of each "page" in point.  There are only so many key pages that accept user input.  There could be a "borrower information" object a "page 1" object a "page 2" object, etc.  It's not very elegant but it's straight-forward and easy to use and create.   Whatever the GUI pulls its values from can likely just be made into an XML object with very little effort.

Having JUST that much, is enough for me to improve my own productivity two or three fold!  I would no longer care what EnCompass can do (I've been trying to decide whether to switch) because I know I could build anything I need with point's SDK or find useful mods/plugins/extensions on-line.