Credit Acceptance: CAPS Technology Challenges
Former Software Engineer at Credit Acceptance
inpractise.com/articles/credit-acceptance-tech-stack-challenges
Former Software Engineer at Credit Acceptance
Interview Transcript
This is a snippet of the transcript, sign up to read more.
Yes, perhaps start with the history, the objectives, and why it didn't work out.
The aim was to replace CAPS, but it didn't work out. It was a huge project with many people involved. There were several reasons for its failure, primarily budget issues. It went so over budget that they didn't see the return on investment they expected.
This is a snippet of the transcript, sign up to read more.
Related Content
Credit Acceptance: Hurdles to Loan Volume Growth
Former Director of Sales at Credit Acceptance
Credit Acceptance: CAPS vs DealerCenter Loan Application Workflow
Independent Car Dealer in the US
Credit Acceptance: CAPS Workflow Challenges
Finance Manager at Richfield Bloomington Honda
Credit Acceptance vs Westlake: Loan Origination Process
Copyright Notice
This document may not be reproduced, distributed, or transmitted in any form or by any means including resale of any part, unauthorised distribution to a third party or other electronic methods, without the prior written permission of IP 1 Ltd.
IP 1 Ltd, trading as In Practise (herein referred to as "IP") is a company registered in England and Wales and is not a registered investment advisor or broker-dealer, and is not licensed nor qualified to provide investment advice.
In Practise reserves all copyright, intellectual and other property rights in the Content. The information published in this transcript (“Content”) is for information purposes only and should not be used as the sole basis for making any investment decision. Information provided by IP is to be used as an educational tool and nothing in this Content shall be construed as an offer, recommendation or solicitation regarding any financial product, service or management of investments or securities. The views of the executive expressed in the Content are those of the expert and they are not endorsed by, nor do they represent the opinion of In Practise. In Practise makes no representations and accepts no liability for the Content or for any errors, omissions, or inaccuracies will in no way be held liable for any potential or actual violations of laws, including without limitation any securities laws, based on Information sent to you by In Practise.
© 2024 IP 1 Ltd. All rights reserved.