Novel assets fail diligence when people underwrite the name of the asset instead of the mechanics underneath it.
By Noah Green CPA CFE, Sheepdog Prosperity Partners LLC
The mistake this article is trying to prevent
The first mistake in Why Emerging Asset Classes Are Hard diligence is that the team assumes the closest conventional asset class provides the right diligence model, even when the cash-flow behavior is materially different. That mistake usually does not look reckless at the beginning. It looks efficient. The file has documents. The model has assumptions. The request list has been answered. The deal vocabulary feels familiar enough for the team to move quickly.
But diligence is not a speed exercise. It is structured doubt. The point is not to distrust every representation. The point is to make the representation carry its own evidentiary weight. A useful diligence process should be able to say, in plain English, what is supposed to happen, why it should happen, who has to perform, what documents prove it, what can interrupt it, and what the capital provider can do when the answer changes.
For this topic, the useful frame is narrow and practical: The difficulty of emerging assets is not novelty itself; it is the temptation to borrow an old framework without proving that the mechanics match. That is the discipline. It keeps the review from drifting into generic commentary and forces the team to build a decision-ready file.
Reduce the topic to mechanics
The mechanics are the gap between the marketing description of the asset and the economic process by which it produces, preserves, and transfers value. If the team cannot describe those mechanics without marketing language, it does not yet have a diligence frame. A label may be helpful shorthand after the work is complete. It should not be the starting point. Labels compress complexity; diligence expands it until the real risk becomes visible.
A mechanics-first review asks what actually has to occur for cash to arrive. It identifies the operational steps, the contractual steps, the data steps, and the human decisions that sit between the asset and the money. It also asks which of those steps are routine only because nobody has applied stress. The best diligence questions are often basic: who sends the bill, who receives the money, who applies the cash, who can issue a credit, who keeps the records, who can change the system, and who notices when the pattern changes?
The answer should be written as a process map, not as a paragraph of comfort. A process map exposes handoffs. Handoffs expose control points. Control points expose failure modes. Once the failure modes are visible, the legal and credit analysis can stop speaking in abstractions.
Separate repayment from recovery
The source of repayment is a payment stream that may be contingent, platform-mediated, behavior-driven, seasonal, contractually subordinated, or dependent on operational execution. That source deserves its own underwriting. The team should test whether it is historical, contractual, behavior-driven, discretionary, recurring, concentrated, seasonal, platform-mediated, or dependent on continued sponsor execution. Each answer changes the diligence scope.
The source of recovery is different. Recovery is what remains when the ordinary-course payment path has been interrupted. It may be the same asset, a lien, a receivable pool, a contract right, a physical asset, a claim to proceeds, a reserve, a guarantee, or a remedy that depends on cooperation from third parties. Recovery should be evaluated under the conditions that created the need for recovery in the first place. That is where many analyses become too optimistic.
A common false comfort is to say that the asset is performing and therefore the collateral is sound. Performance is relevant, but it is not collateral analysis. Collateral analysis asks what the asset is worth, how it can be reached, how quickly it can be converted, and whether the recovery value is independent from the same stress driver that reduced cash flow.
Map control before relying on projections
Control matters because cash flow without control is an expectation, not protection. In this article’s topic, the control points include who can change pricing, enforce customer behavior, move records, redirect cash, modify eligibility, or decide whether the asset continues to exist in economic form. These points should be identified before the team debates the final model. A model that assumes cash dominion, clean reporting, rapid enforcement, or uninterrupted servicing is only reliable if the structure can actually deliver those features.
Control is not limited to bank accounts. It includes data rights, document custody, reporting cadence, approval authority, reserve mechanics, notice procedures, replacement rights, and the ability to verify exceptions. It also includes negative control: who can prevent the capital provider from acting? A borrower, seller, servicer, account bank, customer, court, platform, landlord, utility, insurer, regulator, or contractual counterparty can all become practical gatekeepers.
The cleanest diligence files make control visible. They identify the party, the right, the required notice, the timing, the evidence, and the failure consequence. If a right cannot be exercised quickly when the asset is under stress, it should not be described casually as protection.
Evidence is not the same as a data room
The evidence package should include the records that prove the asset is not merely described but actually created, owned, enforceable, current, and historically convertible into cash. The question is not whether those items were uploaded. The question is whether they reconcile. Management summaries are useful only when they can be tied to source files and cash records. System reports are useful only when the system rules are understood. Contracts are useful only when the team understands how the contract terms appear in the data and cash movements.
A practical evidence review should distinguish four levels of support. First, there is management assertion. Second, there is internal documentation. Third, there is system or transactional evidence. Fourth, there is independent or third-party evidence. Diligence should try to move the most important assumptions as far down that evidence ladder as possible. Not every fact needs third-party confirmation. But every material assumption should have a clearly identified support level.
The team should also look for adverse evidence. Clean diligence is not the absence of exceptions. It is the disciplined treatment of exceptions. If the seller can produce only favorable files, or if exceptions are always explained but never logged, the file is not stronger. It is less testable.
What breaks first
The interruption risks include model drift, platform change, counterparty renegotiation, legal challenge, operational substitution, adverse selection, or a change in the conditions that made the asset look comparable. These are not remote possibilities included for legal completeness. They are the first places the team should look when designing stress cases. A base case usually assumes continuity. Diligence should ask what continuity depends on.
The most useful stress case is not necessarily the most dramatic one. It is the first plausible interruption that would change the decision. A small reporting delay may matter more than an extreme macro shock if the structure depends on fast trigger reporting. A modest increase in dilution may matter more than a catastrophic default if the advance rate has no room for ordinary commercial deductions. A servicing transition may matter more than asset performance if collections depend on daily operational execution.
The goal is to identify the earliest indicator that the thesis is changing. If the team cannot name that indicator, it may know the downside in theory but not in time to act.
Legal structure as practical risk allocation
The relevant legal questions include the difference between a structure copied from a familiar market and a structure tailored to the rights, remedies, and transfer rules of the actual asset. These issues require counsel-led review. The diligence team should not turn legal analysis into casual business advice. But the business team still has to understand what the legal structure is intended to accomplish and what assumptions it depends on.
The business team does not need to replace counsel, but it does need to understand what the documents are supposed to accomplish and where the legal path relies on fragile operating assumptions. Can cash actually be redirected, or is that true only after a notice period that gives leakage time to compound? Can the records be transferred, or does the asset live inside systems that nobody else can run cleanly? Can a replacement party step in, or does the practical remedy still depend on the incumbent continuing to cooperate?
This is where many emerging assets reveal hidden dependence. Transfer language may look complete until anti-assignment, privacy, or platform rules are tested. A reserve may look protective until release mechanics are read closely. A lien may look strong until proceeds are commingled before they ever reach a controlled account. A repurchase promise may look comforting until the repurchaser is under the same stress that created the breach.
Structure manages uncertainty. It does not remove it. The file has to say which rights matter, when they matter, and what has to remain true for them to matter at all.
The pause test
An emerging asset does not deserve rejection because it is unfamiliar. It deserves a pause until the team can explain the mechanism without leaning on analogy.
That pause test is straightforward. Can the file show how cash is earned, how it is controlled, how it is recorded, how it is tested, and what survives when the easy assumption breaks? Can the team identify the first failure path rather than only the final disaster case? Can it distinguish between a risk that can be priced and a dependency that makes the model dishonest?
If yes, the deal may still fail, but it is failing on the merits. If no, the review is still underwriting the name of the asset instead of the machinery underneath it.
Practical diligence checklist
- Ban analogy in the first pass. Describe the asset without naming a familiar asset class.
- Write the earning-to-cash sequence step by step and mark every handoff.
- Identify who controls money, records, exception handling, and notices at each step.
- Separate repayment underwriting from recovery underwriting and test them independently.
- Tie each material assumption to a support level: assertion, internal record, transaction record, or independent evidence.
- Find the first plausible break in the chain, not the most dramatic macro scenario.
- List the legal rights that matter only under stress and note what timing, consent, or cooperation they require.
- Force every issue into a decision bucket: fatal, priceable, mitigable before close, or monitorable after close.
Red flags to escalate
- Management can explain the thesis but cannot reconcile the source data.
- The model assumes a clean sweep, clean report, or clean transfer that the operating chain does not support.
- Definitions in the financing documents do not match the data fields used for reporting.
- Exceptions are handled manually but not logged, aged, and tied back to money movement.
- The recovery case depends on the same party, system, or assumption that powers the base case.
- Legal rights are described as complete while consents, notices, or account controls remain unfinished.
This article is for educational purposes only and does not constitute legal, investment, accounting, tax, or credit advice. Examples may be simplified or fictionalized composites unless otherwise identified as public-source case studies. Author byline: Noah Green CPA CFE, Sheepdog Prosperity Partners LLC.