Is it worth a closer look?
Two short sections: legal (can it be licensed, and who signs?) and technical (what still exists, and can anyone reach it?). Answer yes, no or unknown. Each question says who can usually answer it. Nothing you enter here leaves your browser.
A quick go / no-go screen
Use this first. It is how we decide whether a closer look is worth everyone’s time. A “Go” only means we continue screening — it is not a prediction that a buyer will make an offer. Legal questions (who can sign, liens, prior sales) and technical questions (systems, access, counts) stay in separate buckets.
Hard filters, from public information
- Whole-company closure. Every location is closed or closing. A single closed branch of a still-operating company is a no-go.
- 50–1,000 employees at peak or last known. (We raised the floor from 25.)
- 3+ years of operating history.
- United States.
- Written-work-heavy office work — software, advertising, consulting, staffing, business services, insurance agencies, engineering or accounting (SIC 7371–7379, 7311, 8742, 7361, 7389, 6411, 8711, 8721).
- Closed or closing within about the last 24 months, or announced / in Chapter 7 / a WARN notice.
- A clear authority holder — trustee, executor, owner, or counsel who can confirm who signs.
Knockout questions, on the first call
- Do the systems still exist, and can someone log in or export? Help desk, CRM, project tools, shared drives. If everything is wiped, or subscriptions lapsed with no export, we stop.
- Is there real written work, with rough counts? Tickets with replies, project threads, documents. Calendars and email signatures alone are not enough. A rough count is fine; don’t export or send the data yet.
- Can someone sign off — and is there a reason they can’t? Name the person who can approve a license. We hold or stop if a lender lien, a prior sale of the data, or a customer contract already forbids it.
Verdict
Go
- Every hard filter is met (or a close is announced / in Chapter 7 / WARN inside the window).
- Systems are reachable or an export already exists, and there is real written work with at least a rough count or a dashboard screenshot on the way.
- Someone can sign, and no known lien, prior sale, or forbidding contract stands in the way.
- Next step: complete the pre-check, then the checklist below. Do not approach a buyer yet.
Maybe
- Most hard filters are met, but size, years, or the close date still need confirming — or the only date is a deletion code rather than a verified shutdown.
- System access, volume, or the signer is unclear, but there is someone to ask.
- Next step: clear the unknowns. Do not approach a buyer until they are resolved.
No-go
- Any hard filter fails, systems are wiped or lapsed with no export, there is no real written work, no one can sign, or a lien, prior sale, or contract already blocks a license.
- Park the matter politely. Reopen only if the facts change.
There is no published figure for how often a buyer accepts a seller’s sample, and we do not invent one. micro1’s CEO has said the smallest companies rarely make it through, because they lack volume or complexity. A Pewter Data public guide also notes that some sellers receive no offer after review. Those are reasons to screen early — not a percentage we can quote as your odds.
Legal: can it be licensed, and who signs?
Not legal advice. Your counsel confirms these answers for your matter.
Technical: what still exists, and can anyone reach it?
Early technical-access check: we confirm a contact can reach the systems before anyone pays for technical work.
Systems inventory (optional)
List what you know. Rough years and sizes are fine.
| Category | Tool name | Years | Approx. size | Status | Admin holder |
|---|---|---|---|---|---|
| Chat & email Slack, Microsoft Teams, Google Chat; Gmail/Google Workspace, Outlook/Microsoft 365 | |||||
| Support & IT ticketing Zendesk, Freshdesk, ServiceNow, Jira Service Management, Intercom, Help Scout | |||||
| CRM & sales Salesforce, HubSpot, Pipedrive, Zoho, Dynamics | |||||
| Projects & tasks Jira, Asana, Monday.com, Trello, ClickUp, Basecamp, Smartsheet | |||||
| Procedures & playbooks SOPs, process manuals, escalation and exception guides | |||||
| Knowledge base & files Confluence, Notion, SharePoint, Google Drive, Dropbox | |||||
| Finance & operations QuickBooks, NetSuite, Xero; invoicing, work orders, dispatch | |||||
| Code GitHub, GitLab, Bitbucket, with issues and reviews | |||||
| Specialist systems (optional) CAD/BIM (AutoCAD, Revit), ERP, supply-chain, estimating |
What tends to raise interest
- Linked history across tools with stable IDs and timestamps
- Problem → action → outcome visible in the records
- Variety of real work and exceptions, not one huge repetitive dump
- Multi-year, continuous history
- Written procedures plus the real cases that show how they were applied
Protect the records now
- Keep accounts paid and active while you decide
- Keep the admin logins; note renewal dates
- Don't mass-export or delete anything
- Note who has authority to decide
- Confirm any new or changed payment instructions by phone, never by email alone