01-projects / positioning

rdco vs naval get rich framework

Mon May 04 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·positioning-assessment ·status: active
navall5-thesispositioningself-assessmentleveragespecific-knowledgemacsanity-check

RDCO execution against Naval’s “How to Get Rich Without Getting Lucky” framework

Founder asked 2026-05-05 16:12 ET: “How can we put it into action, or how well you think we are already executing on the get rich without getting lucky method.” Honest self-assessment graded against the 8 load-bearing pillars Naval names in the 2018 tweetstorm. Underlying source: ../../06-reference/2026-04-03-naval-how-to-get-rich + [../../07-archive/readwise-tweets/How to Get Rich (Without…md](/vault/07-archive/readwise-tweets/How to Get Rich (Without…/).

TL;DR grades

PillarGradeOne-line read
Specific KnowledgeA-Genuinely uncopyable; agentic tooling + data engineering intersection
Leverage (code)A-Ray harness + MAC + verify-action + ~78K lines of MG platform = real durable code
Leverage (media)C+Sanity Check + X exist but audience is too small to be load-bearing yet
Leverage (labor)N/ADeliberately solo per the L5 bet; replacing labor with agent leverage
Leverage (capital)N/ABootstrapped; not yet relevant
Compounding (relationships)AMG send-off proved 8+ multi-year relationships, two senior partners with door-open offers
Compounding (reputation)A-”Set the bar for what an Architect at Mammoth can be” is canonical reference framing
Compounding (knowledge)AVault has 2,150+ docs, daily ingestion discipline, real compound asset
JudgementB+Strong-on-paper, but ahead-of-execution; thoughtful decisions but unvalidated by revenue yet
Equity ownershipB-RDCO is 100% founder-owned, but no live revenue product yet; phData W-2 dilutes the thesis as a bridge
Productizing selfC+Sanity Check started, MAC unshipped, Ray-harness pre-product
Sector pickAAI-tooling at the commoditization moment per Karl Mehta thesis
Uncluttered calendarAHonored faithfully; phData W-2 will reintroduce meeting load

Composite read: STRONG on the input pillars (specific knowledge, code leverage, compounding knowledge, relationships, reputation, sector pick). WEAK on the output pillars (media-leverage audience size, equity-bearing live products, productized-self single flagship).

The framework is honest about this gap: Naval explicitly says you compound the inputs and the outputs follow on a delay. RDCO is in the input-compounding phase. The risk isn’t strategic; it’s patience-vs-execution.

Where execution is STRONG (don’t change)

  1. Compounding the knowledge base. The vault (2,150+ docs as of today, growing daily through process-newsletter, process-youtube, /deep-research) is exactly the “study microeconomics, game theory, psychology, persuasion, ethics, mathematics, and computers” Naval prescribes. Specific knowledge is literally being banked in writing, queryable via QMD and the typed knowledge graph. This is REAL compound.

  2. Code leverage discipline. Ray harness + MAC framework + verify-action + audit-newsletter-outputs.py + the entire ~/.claude/skills/ directory + ~/rdco-video-studio/ + the Ray sprite pipeline are all durable code assets that compound. The MG cc-wrapped platform was the first-time production proof; the RDCO version is the second-time-around build with everything you learned.

  3. Relationship + reputation compounding. Today’s MG send-off captured 8 multi-year relationships AND two senior-leader return offers AND the canonical “set the bar for the role” framing from MG itself. This is high-grade reputation compounding. The phData transition adds another network without burning the MG one.

  4. Sector pick. AI-tooling at the commoditization moment is the correct macro bet per Karl Mehta’s thesis (../../06-reference/2026-05-04-karlmehta-llm-commoditization-intelligence-rails) plus the Stratechery + ASCS confirmations from this week. Durable value is moving up the stack to orchestration, which is exactly where RDCO sits.

  5. Uncluttered calendar. Today’s calendar is empty. Yesterday’s was empty. The “be too busy to do coffee” rule is being honored. PhData W-2 will reintroduce meeting load and is the structural risk to watch.

Where execution is WEAK (the action surface)

1. Media-leverage audience is too thin

Naval’s framework: “If you can’t code, write books and blogs, record videos and podcasts.” (You CAN code, so the ratchet is even higher.) Media leverage compounds slowly and only with consistency. Sanity Check’s subscriber base is small. X follower count is small. The audience asset is real but pre-takeoff.

Action: Increase Sanity Check cadence. Build the public-Ray-build-log content pipeline. The 6% engineering-leverage stat from yesterday’s send-off slide (“78K platform lines / 1.29M total touched”) is the kind of evidence-loaded story that compounds audience faster than thinkpieces.

2. No live equity-bearing revenue product

Naval is explicit: “You’re not going to get rich renting out your time. You must own equity - a piece of a business - to gain your financial freedom.” RDCO owns 100% of itself but RDCO has no revenue product live. Sanity Check is free. Squarely is free (iOS app, no in-app purchase yet). MAC unshipped. The bookstore-for-agents wedge is pre-validation. Personal-library-RAG is concept-only.

Action: Ship MAC v0. The fastest path from specific-knowledge to equity-bearing product. Or activate the Squarely physical-merch wedge as the Shopify learning vehicle (no longer a kids-books detour). Either crosses the “live revenue product” threshold which is the Naval-framework-load-bearing milestone.

3. Specific Knowledge risks dispersion across surfaces

Founder’s specific knowledge is genuinely uncopyable: agentic tooling + multi-client data-engineering + content authoring. But it’s currently dispersed across the vault, Sanity Check, X, MG-internal artifacts, and the RDCO codebase. There’s no single FLAGSHIP public artifact that lets a stranger google “how does Ben think about agentic tooling” and get one thick payload.

Naval’s “productizing yourself” pillar requires a SINGLE concentrated public asset. Could be:

Action: Pick ONE flagship public artifact and orient most output around it for 6-12 months. Don’t disperse. The other surfaces (vault, X, Sanity Check) feed the flagship; they aren’t the flagship.

4. PhData W-2 dilutes equity sovereignty (but is intentional bridge)

Naval: “You must own equity to gain financial freedom.” A W-2 job is renting time. The phData transition is bridge-financing for RDCO bets, explicitly NOT the long-game shape. The risk is the bridge becoming the destination.

Action: Set explicit milestones for when RDCO income exits bridge-mode. Suggested gate: when MAC + Squarely + Sanity Check premium tier combined revenue covers ~50% of phData W-2, founder reassesses the time-allocation split. Until then, phData funds the runway and is OK; just track the metric.

The three load-bearing actions, ranked

  1. Ship MAC v0. Single fastest path to converting specific-knowledge into equity-bearing product. Closes the framework’s biggest gap.
  2. Concentrate the flagship public artifact. Pick MAC OR a book OR a public-build-log series and orient 6-12 months of media output around it. Don’t disperse.
  3. Increase Sanity Check cadence. Audience compounds with consistency. The framework rewards sustained media output more than perfect single posts.

Naval’s “be patient” thread runs through all three. Compounding looks like a flat line for a long time before it doesn’t. RDCO is currently in the flat-line phase, doing the right inputs.