Turning Valon's One-in-Six Claim Into a Watchlist

Valon claims ValonOS is under contract for one in six outstanding U.S. mortgages. That number earns a watchlist line, but it should not carry a multiple until rollout dates and realized ARR make the claim testable.

Valon Technologies raised $150 million in a Series D at a $2.3 billion valuation. Ribbit Capital entered as a new investor, Andreessen Horowitz participated again, and the round doubled the company's earlier valuation. The financing makes the claim visible; it does not prove the software is already running on the loans behind the claim.

A share claim becomes testable when it is tied to contracts

For a B2B infrastructure startup, the useful question is whether a signed contract has become a live system and then recognized revenue. The checklist below turns a headline into a dated watchlist rule.

• Record the claim as a contract. Treat the one-in-six coverage as signed loan coverage, not projected adoption. Keep a separate note for loans under contract and loans still to be migrated.
• Convert the claim into contracted ARR. ValonOS has more than $200 million in contracted annual recurring revenue. Divide that figure by the implied loan count behind the share claim to see whether the revenue matches the coverage.
• Name the rollout dates. If the company has not published go-live dates, migration windows, or a revenue-recognition trigger, mark the item unverified. A dated calendar with those windows and the point at which revenue starts is the minimum.
• Verify the customer base. ValonOS is used by two of the ten largest U.S. servicers, Carrington Mortgage Services and ServiceMac, with ServiceMac as the fourth-largest residential subservicer. Carrington's purchase of Valon Mortgage added roughly 810,000 loans to its servicing book and moved the total toward 2 million. Valon was founded in 2019, first used the platform for its own mortgage servicing, and later sold ValonOS to outside customers. The list should show named customers, loan counts, and the path from internal use to outside sales.
• Test realized revenue after rollout. Keep the multiple on hold until usage and billing show that the contracted ARR is becoming realized ARR. A second note should hold contracted ARR, realized ARR, and the gap between them.
• Set the multiple trigger. Put a one-line condition in the entry, such as a target realized-ARR level or a named customer expansion. The rule should tell you when to move from monitoring to valuation.

The common error is to treat a large contracted share as proof that the software is already running on those loans. Contracts can be signed, delayed, renegotiated, or underused. The watchlist exists to catch that gap.

A watchlist entry needs a date, a customer check, and a revenue test

A watchlist entry should be small enough to update without a full diligence memo. It needs a claim, a revenue figure, a customer check, a date, and a trigger. If a field is missing, the entry should say what is missing.

The investor's job is to separate three states: signed, running, and billed. A contract can exist before the software is live. A live system can exist before revenue is recognized. A recognized revenue figure can still be lower than the contracted amount. The watchlist should name which state the company is in.

When a company claims a large share of a market, start with the system, not the headline. Ask whether the share is attached to a system that is already processing the work. Then ask whether the revenue follows the system. Finally ask whether the multiple should wait for that follow-through.

Update the assessment when relevant revenue or customer details change. If the company stays silent, record the silence as a data point. A missing date is a reason to keep the multiple low.

Assign the multiple only after the realized-revenue test clears.