01-projects / positioning

strategy

Thu Apr 30 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·strategy ·status: active
strategybet

RDCO Positioning (Umbrella) — STRATEGY

Problem

Ray Data Co needs to articulate, defend, and operationalize the umbrella thesis that gives every sub-bet (Squarely, Newsletter, MAC, Automated Investing, Data Dots, future) standing to exist as a coordinated portfolio rather than a scattered set of side projects. The canonical thesis crystallized 2026-04-30: “creating targeting systems, instrumenting the process, optionally enabling tools, and closing the recursive feedback loop — applied to a portfolio of small bets across niches.” The bet is whether that articulation can survive contact with both readers (via Sanity Check) and prospects (via raydata.co + downstream sub-properties), and whether the four-layer prioritization filter actually shapes what RDCO does next.

Approach

Treat positioning as a load-bearing operating discipline, not a marketing artifact. Three layers of approach: (1) the canonical thesis page is the single source of truth — every sub-bet, every skill, every capability question gets evaluated against the four-layer filter (“does this tighten targeting / instrumentation / tools / feedback for ANY active niche?”); (2) brand-house architecture — raydata.co is the umbrella (currently legacy “Mr. Ben” personal site, needs rebuild), each substantial bet gets its own brand-distinct sub-property (sc.raydata.co for Sanity Check, hq.raydata.co for HQ, separate domain for MAC per xmrit precedent, TBD for Squarely + Data Dots + future); (3) ground the umbrella claim in conviction-assets — Ben’s six ranked assets (10y of analytics-rot observation, MAC framework, working AI-COO ops, vault-as-loop, operator+builder+writer trifecta, optionality runway) underwrite a category claim (“Architect Mode for mid-market data orgs”) few others can defensibly make. Why-this-not-that: don’t position as “AI consulting” or “data engineering” or “newsletter publisher” — those are sub-implications of the targeting-systems framing, not the thesis.

Personas

Key metrics

Work tracks

  1. raydata.co umbrella rebuild: retire/rebuild legacy Mr. Ben site as Ray Data Co umbrella with thesis articulation + bets list + GEO discipline. Sequence: ship before sc.raydata.co goes public so footer links land on the right brand. Owner: Ray (build) + founder (voice/aim). Status: pending — build-landing-page skill + ray-data-co-design system in place; trigger TBD.
  2. MAC separate-domain launch (May 2026): per umbrella architecture, MAC pack gets brand-distinct domain (candidates: macframework.com, mac.dev, etc.). Owner: founder (domain pick) + Ray (build). Status: planned.
  3. Sanity Check canonical-thesis editorial sequence: 5-piece arc that becomes the spine for “what RDCO actually is” externally. Owner: Ray drafts → founder voice. Status: queued (per thesis doc, founder validation pending).
  4. Conviction-asset inventory founder review: 4 open questions in 2026-04-22-ben-conviction-assets-inventory.md (undervalued/overvalued assets, bet form, closest analog). Owner: founder. Status: draft v1, founder-edit.
  5. Brand-architecture mapping for emergent bets (Data Dots, vertical farming, additional Squarely puzzles): subdomain vs separate domain decision per bet. Owner: founder + Ray. Status: rule defined (“substantial enough to stand on its own brand → its own domain”); per-bet calls TBD.
  6. Cross-bet positioning audits: when new sources enter the bookshelf (Kurian, Ternus, Innermost Loop on harness-thesis cluster — Apr 23 sweep queued in next-moves audit), surface cluster-level positioning implications. Owner: Ray. Status: dispatchable.

Targeting system (RDCO 4-layer thesis)

Sub-process: thesis-articulation quality. Defined operationally as: do downstream readers/prospects/founder-himself converge on the same picture of what RDCO is when given the umbrella surfaces? Proxy signals: founder uses the four-layer filter unprompted (achieved 2026-04-30); Sanity Check readers reflect back the framing in replies; prospect inbounds land on the right bet without re-explanation.

P&L meta-layer: positioning’s P&L is downstream — it isn’t a direct revenue surface. The economic test is whether the canonical thesis lets MAC/services/products convert at higher rates and reduces founder’s distraction-cost on un-anchored shiny objects. Not yet instrumented; would require attribution from positioning surfaces → downstream sub-bet conversion.

Instrumentation (RDCO 4-layer thesis)

Built: vault as the durable artifact (1,800+ docs, typed graph, semantic search via QMD); canonical thesis + bet-architecture playbook as load-bearing concept pages; conviction-asset inventory as standing-to-bet evidence; iMessage/Discord channel as live founder-articulation feed; cross-check skill for contradiction detection; graph-query skill for citation-tree introspection; design-critic for surface-level brand-consistency scoring on shipped surfaces.

Gaps: external positioning-impact measurement (umbrella-site analytics, mention-tracking, inbound-attribution) — not instrumented since umbrella isn’t rebuilt. No structured “positioning-drift” sensor — relies on founder noticing if Ray’s outputs misframe RDCO.

Tools (RDCO 4-layer thesis)

Built: build-landing-page (with 4-layer review loop including design-critic gate); ray-data-co-design umbrella design system (palette, type, motifs, mascot/doodle, asset inventory); sanity-check-design extending the umbrella for SC; compile-vault for index/cross-link upkeep; vault-health for orphan/stale detection; QMD search across the entire knowledge base; paid-ads skill covering all three primary surfaces (Squarely / MAC / SC).

Gaps: GEO-optimization scoring tool (markdown URLs, llms.txt, JSON-LD adoption per 2026-04-23-generative-engine-optimization-geo); cross-property brand-consistency audit at the umbrella level (design-critic operates per-surface).

Feedback loop (RDCO 4-layer thesis)

Partial — formalize. The thesis itself emerged from a closed feedback loop (week of structural work → founder articulation → canonical page → prioritization filter → behavioral memory). What’s NOT formalized: the cadence at which positioning gets re-distilled. The thesis is dated 2026-04-30; without an explicit cadence (“re-distill quarterly”, “re-distill when a new bet enters the portfolio”), it will drift. Recommended cadence: re-distill at every bet-portfolio change AND on a 90-day rolling cadence. Owner + cadence is TBD — needs founder distillation.

Open questions for founder