Your requirements. Our implementation. Your lending platform.
Every lender operates differently. Your products, credit policies, approval authorities, workflows, documents, integrations, verification requirements and downstream systems are your own.
appTRAKER is designed around that reality. LAUNCHER.SOLUTIONS translates your products, policies, workflows, documents, integrations and operating requirements into a working appTRAKER environment.
The implementation may be highly customized behind the scenes. From your team’s perspective, it is turnkey.
Custom configuration, delivered turnkey
Launcher works with your team to understand how you lend, then translates those requirements into a working appTRAKER environment. An implementation can include:
You define the lending requirements. We build the lending environment.
Your credit policy. Implemented.
Your team participates at the level that fits its skills, ownership model and plans for post-launch administration. Launcher translates lender-defined policy into appTRAKER rules and workflows covering:
The policy is yours. What Launcher supplies is the work of expressing it as rules, programs, calculations and workflows inside the platform — and the lending experience to know which of those a given requirement actually belongs in.
One platform, different products
Configure each lending product with its own application, policy, workflow, documents and handoff on one platform.
Application → Credit → Underwriting → Decision → Verification → Documents → eSign → Funding
The path above is shared. What differs is how each product is configured within it — the programs, calculations, approvals, documents and workflows appropriate to the transaction. The same environment can carry personal loans, indirect automotive, credit cards, leasing and home equity without any of them being forced into another product’s shape.
Applications through funding
Launcher can configure the complete origination experience around your operating model, from the first application screen a borrower or dealer sees through to the systems that receive the funded loan.
Applicant and dealer experiences
myLOAN, Dealer Portal and other supported application channels are configured as part of the implementation and tested with the end-to-end workflow.
myLOAN + Dealer Portal + Other supported channels
Branding, product selection, application requirements, disclosures, documents and the workflow behind each channel are all lender-defined. Borrower and dealer messaging runs through CONNECT, and dealer relationships, agreements and hierarchies through myDEALER.
Underwriting and operations
Behind the application, the working environment your credit and operations teams use every day is configured to your process:
Automated credit rules and scorecards are implemented through autoBOUGHT, and loan structuring, payment and term calculations through autoBUILT. Where a requirement is better served by a queue and a human reviewer than by a rule, it is built that way.
Documents and eSign
Document work is one of the most lender-specific parts of an implementation, and one of the least appealing to hand to an internal team. appTRAKER DOCS & FORMS supports lender and third-party forms, Form Packs assembled by product and program, configured disclosures and supported eSign workflows.
Launcher performs the form mapping, data population, conditional logic and packet assembly so that the documents produced at decision, at signing and at funding are the ones your compliance team approved.
Integrations
appTRAKER connects to the systems your lending operation already depends on. Supported integrations can include lender-selected:
Launcher can manage the technical analysis, data mapping, development, configuration, testing and deployment required for supported integrations.
Analysis → Data mapping → Development → Configuration → Testing → Deployment
See the integration partners already connected to appTRAKER, and the API and data exchange options available for proprietary systems.
From requirements to production
Implementation runs as a managed process with a defined role for your team at every stage.
A typical implementation reaches go-live in under 60 days. Scope, the number of integrations and your team’s availability move that in either direction, and the schedule is agreed during Define rather than assumed.
Define → Design → Implement → Test and refine → Launch
Define the requirement. Review the solution. Test the result. Launcher handles the implementation.
As hands-on as you want to be
Your team can collaborate through requirements, configuration, testing, training and launch at the level it chooses.
Some lenders want Launcher to manage nearly the entire implementation while their team defines requirements, reviews results and performs acceptance testing. Others have experienced lending-technology, operations or IT teams that want to participate closely. Both approaches work.
Depending on your internal resources, your team can:
For organizations that want greater post-implementation independence, the implementation itself can become part of the knowledge-transfer process, building the understanding needed to administer the environment after launch.
Launcher makes configuration decisions and operating knowledge visible to the lender team.
Turnkey across different lending models
The same implementation model supports very different lending operations, including:
Some of those have solution pages of their own — auto lending, credit unions, powersports, marine and RV, utility, farm and golf carts and refinance among them — and each was implemented the same way: requirements first, configuration second. LAUNCHER assembles and configures the platform so the lender receives a working origination operation.
Why Launcher for turnkey implementations?
Configurable platform. Turnkey delivery.
appTRAKER gives lenders the flexibility to support highly specialized products, policies, workflows and integrations. Launcher makes that flexibility practical.
Your products. Your credit policy. Your workflows. Your technology ecosystem. Implemented by Launcher.
appTRAKER is configured around the lender’s products, credit policy, teams and downstream environment, and delivered as a working lending process.
appTRAKER
Configurable, scalable loan origination built around your products, channels and credit policy.
Explore →myDEALER
Dealer relationship management, built into the origination workflow.
Explore →myLOAN
A branded online application experience that feeds straight into appTRAKER.
Explore →autoBOUGHT
Your virtual underwriter — automated, 24/7 credit decisioning.
Explore →launchPAD
Essential origination tools for startup lenders and new programs.
Explore →Fraud Intelligence
Identity, phone, location, address, and bureau signal intelligence at the point of decision.
Explore →Dealer Portal
Give your dealer network one connected place to submit, work, and close deals with your lending team.
Explore →CONNECT
Two-way SMS and email between your lending team and applicants, tied to the loan.
Explore →autoBUILT
Configurable workflow automation for your origination process.
Explore →appTRAKER DOCS & FORMS
Document management, form generation, Form Packs and eSign — built into the LOS.
Explore →Frequently asked questions
How long does an implementation take?
A typical implementation reaches go-live in under 60 days.
Scope, the number of integrations and your team’s availability move that in either direction. The schedule is agreed during Define, at the start of the implementation, rather than assumed.
What does turnkey implementation mean?
Launcher configures and implements appTRAKER around the lender’s agreed business requirements rather than requiring the lender to perform the platform setup itself.
The implementation can still be highly customized. Turnkey describes who does the work, not how standardized the result is.
Is appTRAKER an off-the-shelf implementation?
No. appTRAKER is configurable around each lender’s products, credit policy, workflows, documents, integrations and operational requirements.
How involved can our team be?
As involved as you want. Some lenders primarily define requirements, review the implementation and perform acceptance testing. Others participate closely in configuration, rules, workflows, integrations, forms and testing.
The appropriate level of involvement can reflect your internal technical resources and how much appTRAKER administration you intend to manage after launch.
Can our team learn the system during implementation?
Yes. Teams that expect to administer more of appTRAKER internally can observe and participate in the implementation process, providing practical knowledge transfer before go-live.
Does our team have to configure appTRAKER?
No. Launcher performs the implementation and configuration associated with the agreed requirements. Your team provides and approves the business policies, requirements, documents, vendor information, access and other necessary inputs.
Can Launcher implement our underwriting rules?
Yes. Credit rules, programs, pricing, conditions, stipulations, approval authorities, calculations and other lender-defined decisioning requirements can be configured as part of the implementation.
Will Launcher implement integrations?
Yes. Launcher can investigate, design, configure, develop, map, test and deploy supported integrations according to lender requirements and applicable third-party specifications.
Can different products have different workflows?
Yes. Different products, finance types, divisions, application channels and lending programs can maintain distinct requirements while operating on the same appTRAKER platform.
Can Launcher configure our documents and forms?
Yes. Lender and third-party forms can be mapped, Form Packs assembled, disclosures configured and supported eSign workflows incorporated as part of the implementation.
Are the borrower and dealer application channels configured too?
Yes. myLOAN, Dealer Portal and other supported application channels are configured around your branding, products, application requirements, disclosures, documents and workflows.
What does our team need to provide?
The lending policies, products, processes, documents, integration details and business requirements that define how you lend, plus review and approval as the implementation is built and tested.