saascode

Orphanloom

A lightweight offboarding control plane for organizations with 50–500 employees that turns an authorized leaver event into per-application account candidates, reviewable disable-or-retain decisions, governed provider actions, and signed bounded receipts while keeping employment status, identity match, entitlement, approval, provider acknowledgment, destination readback, data transfer, billing effect, audit conclusion, appeal, and correction separate.

Genesis score6.90/10
Make Orphanloom real.0/500
500 more votes and Orphanloom is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
0Cross-references
1Inbound connections
1Direct connections
The case

Small IT teams can remove central identity access yet leave accounts active in applications that lack standard lifecycle support, use local identities, were purchased outside IT, or require product-specific administration. Orphanloom focuses on the offboarding event, but the source confirms a close competitor already offers broad universal connectors. The product therefore cannot claim a vacant category or rely on connector count alone. It must prove faster per-leaver evidence, precise authority, safe fallback, and bounded receipts. A detected account is a candidate, not proof of ownership; disable is not deletion; provider acknowledgment is not observed destination state; and a signed receipt is not proof that all applications were discovered or that offboarding is compliant.

Who pays — and why

An IT, security, identity, or operations owner at a 50–500 employee organization with a small team, fragmented SaaS ownership, and repeated difficulty proving that leaver accounts were addressed.

What it unlocks
A leaver case linking authoritative worker event, effective time, legal or HR authority, identities and aliases, application discovery sources, account candidates, match evidence, owner, entitlement, data and resource ownership, risk, exception, and correction
A per-account decision model separating discovered, matched, ambiguous, false match, already inactive, disable proposed, retain approved, transfer required, revoke sessions, rotate shared secret, provider instructed, acknowledged, read back, failed, reopened, and corrected
A bounded completion receipt listing covered discovery sources, known gaps, approvals, provider responses, observed destination states, retained exceptions, transferred assets, unresolved items, signature assumptions, expiry, and later correction
How Genesis scored it
6.90across seven criteria
tension 7temporal 8blindspot 6buyer 8leverage 8convergence 5why-not 5
8
Temporal window

Current credential-exposure pressure and mid-market identity demand make lingering accounts salient.

8
Buyer persona

Small IT, security, and identity teams in a defined organization size have a concrete recurring offboarding burden.

5
Why nobody did it

The mechanism is feasible now, but the supplied research shows that an emerging competitor already addresses nonstandard application coverage.

Why it scored well

The source names a 50–500 employee buyer, confirms the nonstandard application offboarding problem, verifies a close competitor with broad connector coverage, and identifies a narrower per-event receipt and self-protection workflow.

What's holding it back

There are no cross-references, a close competitor already serves the seam, connector operations are ongoing grunt work, destructive actions carry high risk, discovery can never prove completeness, and the differentiated pricing and receipt thesis remains unvalidated.

Signals detected4 sources crossed
SignalSource-run competitor verification

SignalSource-run market research

SignalSource-run positioning analysis

SignalSource-run threat signal

Direction brieforphanloom.md
orphanloom.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.