How assignees value and sell intangible assets in an ABC

What intangible assets does an assignee usually hold?#

An assignee usually holds a mix of registered rights, digital accounts and operating records, each with a different natural buyer. The assignment transfers the company's interest in all of them, but transfer mechanics, third-party consents and privacy limits differ by asset.

Build the intangibles schedule early, from the company's registrar accounts, trademark filings, code hosting, SaaS billing and the founders' own knowledge. Assets that are not on the schedule cannot be marketed, and digital accounts left unpaid can disappear before anyone notices them.

How should an assignee lot intangible assets?#

An assignee should lot intangible assets so that each lot matches one kind of buyer and one transfer method. A single lot labeled trade secrets, trademarks, domains and copyrightable information is easy to publish but hard to bid on, because no single buyer wants everything in it at full value.

Allowing combined bids keeps the upside of a whole-company buyer while letting specialists compete on single lots. Compare the best combined bid with the sum of the best single-lot bids before choosing.

• 1Lot A, brand: trademarks, domains, social handles and the website, sold with goodwill.
• 2Lot B, technology: source code, patents, product documentation and build tooling.
• 3Lot C, customer relationships: assignable contracts and the customer list, subject to consents and privacy review.
• 4Lot D, operational records: support, CRM, engineering and project history, offered as a non-exclusive license after preparation.
• 5Combined bids: invite bids on any combination, so a buyer who wants several lots can still bid once.

Why operational records deserve their own lot#

Operational records deserve their own lot because the buyers who license them rarely want the brand or the code, and the buyers who want the code rarely pay for historical support tickets. Mixing them hides the records from one buyer group and adds diligence work for the other.

Records also behave differently as assets. A non-exclusive license lets the estate deliver a prepared copy of support conversations, CRM activity or engineering issues while still selling the underlying IP to someone else. That works only if the IP purchase agreement allows it, so decide before the sale notice whether the IP buyer receives historical records outright or takes them subject to a retained license right.

Engineering history needs extra care. Issue trackers and code review threads often quote source code, so a records license that includes them may need the code buyer's consent or must strip code content out.

Trade secrets need the same care. Under the federal definition, information is a trade secret only if its owner has taken reasonable measures to keep it secret and it derives value from not being generally known. Licensing records that expose pricing logic, formulas or proprietary methods without confidentiality terms can weaken exactly what the technology buyer is paying for, so remove that material from the records lot or license it under strict confidentiality.

How assignees value intangibles without comparable sales#

Assignees value intangibles mostly through the sale process itself, because reliable comparable sales are rare for one company's brand, code or records. Formal methods give a reference point, and the marketing record shows that the market was tested.

The assignor's balance sheet rarely helps. Under US GAAP, costs of internally developing intangibles that are not specifically identifiable or are inherent in the business are expensed as incurred, so a home-grown customer database or records archive usually carries no book value. Accounting for acquisitions points the other way: ASC 805 guidance lists databases and customer lists among intangibles recognized separately from goodwill, which is a fair reminder to creditors that zero book value is not zero market value.

Holding costs belong in the valuation too. Domains, code hosting and the SaaS accounts that store records all keep charging while the sale runs, so weigh the cost of keeping each asset alive against likely bids, and export records before any account is allowed to lapse.

For fiduciary purposes, keep a log of who was contacted, what they were shown, the bids received and why the winning bid was chosen. That log is often the assignee's best answer if a creditor later questions the price.

What the sale notice should say about intangibles#

The sale notice should describe each intangible lot specifically enough for a qualified buyer to decide whether to bid. Vague descriptions draw low bids, and overbroad ones can sweep in records the assignee meant to license separately.

Publish the notice where each buyer group actually looks. Brand and code buyers follow liquidation and IP sale channels, while buyers of operational records are usually reached through managed licensing or direct outreach, so a single notice in one place rarely reaches every lot's audience.

• 1Identify registered rights in an attached schedule, with registration or application details.
• 2State whether each lot is an assignment or a license, and whether any license is exclusive.
• 3List exclusions, such as employee files, privileged communications and customer-owned data.
• 4Describe personal-data conditions the buyer must accept, including use limits and deletion duties.
• 5Set out the as-is basis, bid deadlines and combined-bid rules.

Illustrative: an assignee splits a startup's IP from its records#

Illustrative: a fictional construction scheduling startup makes an assignment for the benefit of creditors after a failed raise. The assignee finds trademarks, a domain, a GitHub organization, Jira projects, a Zendesk instance and a HubSpot CRM with years of pipeline notes.

The assignee sorts four lots. One buyer takes the brand and domain. A competitor wins the code and product documentation under an agreement that leaves the estate free to license historical support and issue records with code excerpts removed.

HubSpot business contacts are kept out of the records lot after a privacy review. The prepared support tickets and Jira issues then move through a rights review as a separate non-exclusive license, and the assignee reports its proceeds to creditors alongside the other lots.

How SourceX works with assignees#

SourceX handles the operational records lot as a licensing transaction under the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The assignee, as holder of the assets, approves each step, and the first fit check uses metadata such as systems, years of history and record families rather than files.

For each package, the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and the assignee's release authorization. The SourceX Enterprise Data Value Framework explains which record features tend to matter to buyers, which helps an assignee describe the lot without promising a price.