Can a fully remote company license its operational records?

The short answer: no office is required

Yes. Working remotely does not count against a company in a SourceX review. Qualification looks at size, operating history, the breadth of the records and the company's rights to them, and a headquarters lease is not on that list. A distributed software firm with a registered address and staff in a dozen states is assessed the same way as a company with a campus.

The objection usually comes from one of two places. Owners sometimes assume buyers want a traditional operation, and partners sometimes assume a distributed team means scattered, unusable records. In practice the opposite is often true.

Why remote teams often leave the fullest written record

A remote company cannot rely on hallway conversations, so the work gets written down. Decisions happen in threads, handoffs happen in tickets, and meetings are often recorded or summarized. That is the material AI developers need to train and evaluate agents that carry out multi-step work.

Volume alone is not the point. Connected records, where a thread leads to a ticket that leads to a shipped change, are worth more than any single system. If most of a company's history sits in one tool, read whether one system can be enough before ruling it in or out.

What still has to be true

Remote or not, the company has to clear the same bar. It must be a US company with 50+ full-time employees at peak (contractors excluded), several years of documented operations, the rights to license the records, and an owner, CEO, CFO or authorized representative willing to sponsor the process. The full baseline is on the who qualifies page.

Headcount needs extra care for distributed firms. Many lean on freelancers, agencies or staff engaged through a third-party employer, and those people may not count toward the full-time figure. Give SourceX the numbers by type of engagement rather than one blended total, and let qualification confirm the count.

The remote records check

Run these six questions before you make the introduction. Each one targets a gap that shows up more often in distributed companies than in office-based ones.

• Workspace ownership: are Slack, Google Workspace or Microsoft 365, Zoom and the wiki on company-paid accounts administered by the company, not a founder's personal account?
• Contractor output: was material created by freelancers assigned to the company in writing?
• Multi-state notices: did employees in every state where they work receive the company's monitoring and recording notices?
• Personal devices and accounts: does the real work live in company systems, or partly in personal email, text messages and personal cloud drives?
• Departed staff: when people left, were their accounts archived, or deleted along with their history?
• Export access: can a named admin run full exports today? A company without an in-house IT team can often handle this with its managed service provider.

The contractor question matters because ownership follows employment status. The Copyright Office's Circular 30 on works made for hire explains that an employer owns work an employee prepares within the scope of the job, while a contractor's work counts as made for hire only in limited statutory categories under a signed agreement. Otherwise the company needs a written assignment to own it.

Recording rules also differ by state. Some states require every participant's consent to record, so a team spread across one-party and all-party consent states needs to know which rule its call recordings followed before any of them go into an inventory.

This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

How to answer the remote objection

Keep the reply factual and turn the concern into a quick check.

The guide on how to talk to a company about licensing its data covers the wider conversation, including what not to promise.

When the remote concern is valid

Sometimes the worry points at a real gap. Use this table to decide whether to pause, fix or move on.

How the introduction proceeds

You introduce; the company and SourceX handle everything that touches data.

1. You register and send the company your referral link, which takes them to the application with your code attached, or you submit them through the referral form.
2. SourceX qualifies the company on size, history, data breadth and rights.
3. The company's admin builds a data inventory: each workspace, the years it covers and what can be exported.
4. Price and terms are agreed with the company as one all-in price, SourceX's fee included.
5. AI labs and data buyers review the opportunity.
6. After signature, the data is prepared under the redaction and de-identification rules the company approved, delivered, and the company is paid.
7. Your reward is paid once SourceX has received its fee.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. No reward is guaranteed, and the reward never reduces what the company receives. Licensed professionals should check their own rules on referral fees before registering.

Next step

Run the company through the company fit checker for a preliminary, non-binding read; it needs no contact details. If it looks like a fit, register as a partner and send your referral link, or have the founder apply directly at sourcex.si/apply.