Purpose. The founder's method for finding RDCO's next owned bet is to let a profitable niche emerge from the cross-industry use-cases he encounters at phData (esp. the CAF use-case catalog), rather than pinning it down prematurely (decided 2026-06-15 — see [[2026-06-15-owner-mindset-vs-w2-compounding-reflection]]). This ledger is the quiet observation layer that turns "let it emerge" into "spot it" instead of "hope it shows up."
Ray maintains this. The founder takes no action on it — it surfaces a candidate only when a pattern is strong enough to be worth his judgment.
⚠️ Privacy guardrail (read before every entry)
Capture patterns and archetypes only — industry vertical, agent/use-case shape, rough budget signal, and the ownable-wedge hypothesis. Never log confidential client artifacts, real contract/engagement data, internal phData docs, or non-public client specifics. Publicly-known client relationships and generic use-case shapes are fine (per feedback_employer_client_content_boundary); when in doubt, abstract to the archetype and drop the name.
What makes a niche "ownable" (the filter)
A use-case earns a candidate flag only if it plausibly clears all four:
- Recurs across multiple clients/engagements (not bespoke one-off).
- Carries budget — someone already pays real money for this pain.
- Wedge for a small owned product — a focused tool/agent could own a slice the SI motion doesn't serve well (too small to be a PS engagement, too specific for the platforms).
- Enterprise-shaped is OK — unlike Squarely, the next bet can ride the same enterprise GTM muscle phData is building (the consumer-app skill does NOT transfer; the enterprise one does).
Ledger
| Date | Vertical | Use-case archetype | Recurs? | Budget signal | Ownable-wedge hypothesis | Candidate? |
|---|---|---|---|---|---|---|
| 2026-06-15 | Media / entertainment | Contract & rights-intelligence agent (parse agreements, surface rights/obligations) | TBD (1 seen) | Enterprise PS engagement = real budget | Vertical contract-intelligence SaaS is crowded; possible wedge = a narrow rights/royalty-reconciliation slice | watch |
(Populate as CAF use-cases and phData deal-flow surface. CAF catalog work is currently blocked on the repo landing on the machine — expect volume once unblocked.)
Links
- [[2026-06-15-owner-mindset-vs-w2-compounding-reflection]] — the reflection that spawned this
- [[index]] — phData project index (CAF restructure arc)
- Memory:
project_l5_north_star_strategic_direction·user_money_values_potential_tension