This article is a work in progress. If you have any questions, thoughts, or corrections, contact us.

Technology and infrastructure

Build vs buy decisions

Build vs buy decisions

Every technology decision in ABF operations involves a build-vs-buy tradeoff. The right answer depends on your scale, asset class, internal capabilities, and timeline. Getting this decision wrong is expensive: building too early wastes capital on systems that don’t match your eventual business, while buying the wrong solution locks you into limitations that constrain growth.

When off-the-shelf works

Use vendor solutions when:

You’re originating a standard asset class. Consumer loans, auto finance, equipment leasing, and mortgage have established vendor ecosystems. Someone has already solved your problem.

Your facility structure is conventional. Standard warehouse or term structures with typical waterfalls and eligibility criteria work well with configurable platforms.

You’re under $500M AUM. Below this scale, the fixed costs of custom builds rarely justify the flexibility gains. Per-loan vendor pricing is usually competitive.

You don’t have dedicated technology staff. Custom systems require ongoing maintenance. Without in-house engineers, you’ll be dependent on contractors who may not be available when you need them.

Time-to-market matters. If you need to be operational in months rather than years, vendor solutions are the only realistic path. Custom builds take 12-18 months minimum for core systems.

When custom builds make sense

Build custom when:

Your asset class is unusual. If no vendor has experience with your loan type, you’ll spend as much time teaching them as you would building it yourself.

Your waterfall logic is complex. Multiple facilities with non-standard triggers, dynamic advance rates, or unusual concentration calculations may exceed what configurable platforms can handle.

Transaction volume is high. At 100K+ loans, per-loan pricing becomes expensive. The math shifts toward platforms with fixed costs.

You have specific integration needs. If you need to connect to counterparties or systems that vendors can’t support, custom development may be required.

You have a dedicated technology team. Engineers who understand your business can build systems that exactly match your operations. But maintaining custom systems requires ongoing investment.

Total cost comparison

The right comparison is total cost of ownership over 3-5 years, including implementation, licensing/maintenance, staff, and opportunity cost.

Example: $200M consumer loan facility

Vendor approach:

ComponentAnnual Cost
LMS (20K loans @ $5/loan/month)$1.2M
Data warehouse (Snowflake)$30K
BI tool (Tableau)$15K
Investor portal (third-party)$40K
Total$1.3M

Illustrative pricing. See pricing disclaimer.

Custom build:

ComponentYear 1Ongoing Annual
LMS build$1M$200K maintenance
Data infrastructure$150K$50K
Reporting build$200K$50K
Staff (2 engineers)$350K$350K
Total$1.7M$650K

Breakeven analysis

Custom builds have higher upfront cost but lower ongoing cost. The breakeven is typically 3-5 years, assuming you execute the build well.

Critical caveats:

  • Most originators underestimate custom build costs by 50% or more
  • Timelines typically slip by 6-12 months
  • Staff turnover creates knowledge gaps
  • Regulatory changes require ongoing adaptation

The payback calculation only works if you have the execution capability to deliver on time and maintain the systems long-term.

Decision framework

Ask these questions in sequence:

1. Does a vendor solution exist for your asset class?

If no vendors serve your asset class, custom build is likely necessary. Search industry directories, ask peers, and consult with technology advisors.

2. Can the vendor handle your specific requirements?

Get detailed answers on:

  • Waterfall calculation capabilities
  • Eligibility criteria flexibility
  • Concentration calculation methods
  • Reporting format customization
  • Integration with your counterparties

If the vendor says “we can configure that,” ask for examples of similar implementations and reference customers.

3. What’s your volume trajectory?

Per-loan pricing makes sense when volume is uncertain. If you’re confident about hitting high volumes, fixed-cost models become attractive.

4. Do you have the team to build and maintain?

Be honest about your capabilities. Building is the easy part; maintaining systems over years while your team evolves is harder.

5. What’s your timeline?

If you need to be operational in 6 months, the decision is made. Vendor solutions are the only path.

Vendor selection criteria

When evaluating vendors, investigate these areas thoroughly:

Asset class experience

Have they worked with your loan type before? Ask for:

  • Number of clients in your asset class
  • Case studies or references
  • Specific feature support for your requirements

Reference clients

Talk to 2-3 current customers of similar size and complexity. Ask about:

  • Implementation experience
  • Ongoing support quality
  • Unexpected limitations discovered after go-live
  • Total cost vs. quoted price

Implementation support

Who helps you configure and go live?

  • Dedicated implementation team or shared resources?
  • Timeline expectations and what causes delays
  • Your responsibilities vs. vendor responsibilities
  • Training and documentation provided

Integration capabilities

Can they connect to your payment processor, banks, counterparties?

  • Native integrations vs. custom development
  • API availability and documentation
  • File format support (NACHA, Metro 2, etc.)
  • Integration cost (included or additional)

Data portability

Can you get your data out if you leave?

  • Export formats available
  • Historical data retention
  • Termination assistance

Important: Get data portability in writing. If your vendor holds your data hostage, switching becomes extremely painful.

Pricing model

Understand the full cost structure:

  • Per-loan vs. flat fee vs. hybrid
  • Implementation fees and what they include
  • Annual increases (capped or uncapped?)
  • Costs for additional modules or features

Contract terms

Read the fine print:

  • Contract length and auto-renewal terms
  • Termination provisions and penalties
  • Price increase limitations
  • Service level agreements and remedies

Vendor landscape overview

Loan management systems

VendorAsset Class FocusScaleNotes
Peach FinanceConsumer, BNPLSMB-MidModern, API-first
LoanProMulti-assetSMB-MidFlexible, configurable
Canopy ServicingConsumerSMB-MidPurpose-built servicing
Applied Business SoftwareAuto, consumerMid-EnterpriseEstablished, comprehensive
Shaw SystemsConsumerMid-EnterpriseLegacy but extensive
Black Knight/ICEMortgageEnterpriseIndustry standard
SagentMortgageMid-EnterpriseModern mortgage platform
OdessaEquipment, leaseMid-EnterpriseComplex structures
defi SOLUTIONSAutoMid-EnterpriseFull lifecycle

Data and analytics platforms

VendorTypeBest For
SnowflakeData warehouseGeneral purpose, easy to use
DatabricksData + analyticsHeavy analytics/ML needs
BigQueryData warehouseCost-sensitive, Google ecosystem
RedshiftData warehouseAWS ecosystem
TableauBI/visualizationDashboards, self-service
LookerBI/visualizationEmbedded analytics
Power BIBI/visualizationMicrosoft ecosystem, cost-effective

Fund administration and portals

VendorServicesScale
Alter DomusFull administration + portalMid-Enterprise
SS&CFull administration + portalEnterprise
CitcoFull administration + portalEnterprise
CSC GlobalDocument + portalSMB-Enterprise

Common decision mistakes

Assuming your needs are unique. Most originators think their requirements are special. They’re usually not. Off-the-shelf solutions handle 90% of needs.

Over-weighting features. More features mean more complexity. Choose a platform appropriate for your current scale with a reasonable upgrade path, not one built for enterprises 10x your size.

Underestimating maintenance burden. Custom systems need ongoing care. Engineers leave, requirements change, dependencies break. Budget 20-30% of initial build cost annually for maintenance.

Ignoring opportunity cost. Time spent managing technology is time not spent on your core business. Factor in management attention, not just dollars.

Making decisions based on price alone. The cheapest option often has hidden costs: limited support, inflexible configuration, poor integration capabilities. Total cost of ownership matters more than sticker price.