Proprietary CRM Dev for Private Lender
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
A fast induction on the buyer’s organisation
I am the business analytics director of LendingOne. We prepare rental loans to real lands investors, and we deal 100% with entities only. I was also lead project director for the software implementation on the project with JetRockets.
Desired goal
What challenge were you trying to address with JetRockets?
We needed to have a proprietary CRM [Customer Relationship Management] built from scratch for our business. The superiority of the CRMs for real lands companies are positioned towards personal name or borrower-type CRMs, but we wanted something more existence based. When we were looking for different software solutions that we could affirm to, nothing matched our needs. As a result, my COO [Chief Operating Officer] and I determined on the proprietary way and to have our own loan origination method flash CRM built from scratch.
Provided solution
What was the aim of their involvement?
After identifying a need for the CRM, we reached out and prepared them with the initial aim, outlining what business purpose we needed to fill and where we wanted to head with it, in accession to who this would contact from an operational standpoint. At that point, Jetrockets reviewed those requirements and veritably understood the depth of our business and what we were lacking.
JetRockets built our CRM, as well as the databases behind the CRM. Our CRM is 100% proprietary and there are many things that specifically match our business.
What is the team dynamic?
I work straightly with a project director and I obey as the business project director. All inner interaction touching any software kindred changes, advancements, or improvements is brought to me, and I adjoin with their IT project director, who then adjoins to the rest of the JetRockets team.
How did you come to work with JetRockets?
My CEO had experience working with them with a sister organisation.
What is the terminal result of working with ?
We began this project in the spring of 2016, and the work is ongoing.
Results achieved
Are there any measureable or plum results?
It has been going well and there is nothing I can complain almost. With any type of QA and requirement ticket, there may be things that are not understood or adjoind properly, but nothing has been injurious.
How did JetRockets accomplish from a project treatment standpoint?
They have accomplished exceptionally well. I have dealt with many different IT outgrowth project teams throughout my tenure, and their team is very well acquainted with the technology, they know what they are doing and apprehend the requirements thoroughly.
After I yield a ticket and it is accepted by them, we use a project treatment software in order for us to have live updates as well as interaction to both of our teams. Their team develops it, they go through rigorous testing, QA [Quality Assurance], and outgrowth, and they then put the ticket in UAT [User Acceptance Testing]. At that point, I test it rigorously and we move it to our origination environment.
What is (from your point of view) the key factor to pay observation while intercourse with ?
The most forcible thing has been their response time and coverage. I have never been in a locality where I cannot get a hold of anyone. They are on top of things 24/7, which is very forcible for a relatively pliant team.
They apprehend the business very well, especially owing they are outer and are not living our business day in and day out. The team is knowledgeable, shining, and very talented all about.
The technology business is very vaporizable from a timing standpoint, and I know from my experience working with different teams in the past that they are the best in the business so far.
What aspects of their work would you like to get improved?
The only feedback I would prepare is on the ETA [Estimated Time of Arrival]. Maybe 2% of all tickets and processes were a pliant underestimated in provisions of the ETA to us, which can put me in a resistent locality.
Do you have any advice for possible clients?
Rather than interacting solely over the phone, or sending a requirement sheet, make sure that all is extremely plain. This is general to all technology teams. Make sure the project is aimd out properly and that there isn’t any room for ambiguity from their team, as this entails inefficiency. I don’t believe this a responsibility of them, rather it is 100% the responsibility of the client. If a client can’t properly adjoin or draw out what needs to be done in the method, then they shouldn’t request it. Though, even if all isn’t set in stone on your end, they can help along the way to get the project done.
