06-reference/concepts

four tier buy build stack soloproneur tam filter

2026-05-14·concept·source: iMessage thread with founder, 2026-05-14 15:02-15:56 ET
agentic-saasbuy-vs-builddefensibilitysoloproneur-tamworld-modelmacramplayered-objective-functionfde-asymmetric-edge

The Four-Tier Buy/Build Stack + Soloproneur-vs-VC TAM Filter

Why this is in the vault

This is the founder's synthesis of the past 3 days of compounding-intelligence cluster work, crystallized through a 5-message iMessage thread on 2026-05-14 triggered by a pasted X take about headless context stores vs agentic workflow startups. The output is two load-bearing primitives: the 4-tier BUY/BUILD stack and the soloproneur-vs-VC TAM filter. Filing as a standalone concept article because it's sharper than any of the 7 cluster pieces it builds on — the founder is doing tier-4 BUILD-world-model work in real time on RDCO's own positioning, and this is the most-current snapshot of where the cluster has landed.

The trigger

Founder pasted an unattributed X take into iMessage at 15:02 ET. Three distinctive-phrase web searches couldn't surface the original author. The take's core claim: dashboard software companies will push to become headless stores (pipes) for two reasons — (A) durable opportunity to be the singular data store for a function or domain; (B) compute/storage pricing compounds with org context growth (Databricks, Datadog as comps). Once they go headless, third-party agents will try to suck context out and reduce them to CRUD. The war between headless context stores and agentic workflow startups just starting. Spolsky 2002's "commoditize your complement" as the strategic mechanic both sides are playing.

Sharp meta-insight but framing was VENDOR-vs-VENDOR (which vendor type wins). Founder reframed it through the BUYER's lens, which produced the 4-tier model.

The 4-tier BUY/BUILD stack

Tier Mode What it is Examples
1 BUY Context stores — the data/plumbing layer Salesforce (going headless), Databricks, Datadog, Snowflake, Notion, Stripe, BigQuery, Postgres
2 BUY Narrow agentic workflow — bought expertise encoded as a workflow product, often dual-purpose as a queryable context store for that domain Ramp (accounting expertise + financial-metrics context store), MAC (data-engineering expertise + data-quality matrix), most vertical AI SaaS
3 BUILD Glue agentic workflows — your composition layer that knits tier-1 + tier-2 pieces into your specific business processes RDCO's skills (process-newsletter, /check-board, etc.), Block's internal workflows, Shopify's River
4 BUILD World model agent — the top-level layered-objective-function that orchestrates the whole stack Block's company world model (per Dorsey/Botha manifesto), RDCO's vault + working-context + decision surface

The load-bearing distinction is between tier-2 and tier-3 — what looks like one "build your own agents" bucket is actually two different concerns:

Why tier 4 is always BUILD (unbuyable)

The world model is layered objective functions. Founder's worked example: P&L is the top optimization target → campaign performance is an input → ad conversion is an input to campaigns. Each layer is necessary but only the company knows the priority stack and how it shifts.

"We can have the best converting ads, but if it is costing us an arm and a leg then we could be bleeding the company dry through the success of the ads." (founder, iMessage 15:29 ET — 28 words; paraphrased below the 15-word ceiling: campaign success can bleed the company dry if not weighted against P&L cost)

Vendors can sell components. Only the company can assemble the objective stack and weight it. This is the durable case for tier-4 being permanently BUILD work, regardless of how good agentic vendors get.

The discipline-encoding-alpha + TAM-generalization filter

The active question for any team building a tier-3 skill: does this BUILD work spawn a tier-2 product?

The filter has two parts:

  1. Encoding YOUR discipline as a skill = always alpha for YOU. Even if it never becomes a product, internalizing your discipline as agentic workflow gives you compounding returns on every future task.
  2. Generalizable across enough orgs = becomes a vendor. But the relevant question is "vendor at what TAM scale?"

Three TAM outcomes, three operating models:

The filter resolves an earlier Ray error in this thread — I claimed RDCO's internal skills "never spawn vendors" which was binary. Founder corrected: most disciplines spawn LOW-TICKET soloproneur products, not VC-fundable companies. Different unit economics, different operating model, different GTM.

Worked examples through the framework

Block (per Dorsey/Botha manifesto): Not Species-A-vendor as Ray initially mis-classified. Block is a BUYER making the BUILD choice at tiers 3 + 4 (their own glue workflows and world model). The published manifesto describes their internal operating model, not a product they're selling. Same operating model as Shopify's River.

Shopify River: Internal Slack-resident agent. ~5,938 employees worked with it in 30 days across 4,450 channels. 1-in-8 merged PRs last week were River-authored, human-reviewed. Public-channels-only design enforces collective learning. This is pure tier-3 + tier-4 BUILD — their discipline (running a giant ecommerce platform) wouldn't generalize to a vendor product, but the alpha for Shopify is enormous.

Ramp: Pure tier-2 BUY. Accounting expertise encoded as workflow + queryable financial-metrics context store. Big enough TAM (every business does monthly close) to support a VC-scale company. Dual-purpose nature (workflow + context store) is interesting — most tier-2 products have this dual character to some degree, which is part of why they're durable.

MAC: Tier-2 BUY for buyers; soloproneur scale for RDCO. Data-quality testing IS broadly applicable across data engineering teams, but the discipline-as-encoded-matrix is narrow enough that it's not a VC opportunity. $350 one-time launchpad pricing locked (see 01-projects/mac/2026-05-14-mac-pricing-intent.md). Sold INTO the internal data engineer ("level up"), not over them.

RDCO's internal skills: Mostly tier-3 BUILD. process-newsletter, sync-contacts, /process-youtube, /check-board are too founder-specific to spawn vendors. They're alpha for RDCO; not commercializable on their own. But the META-PATTERN — "put your agent on an information diet" — could spawn an open-source skill set + a Sanity Check piece (see 01-projects/sanity-check/parked-angles/2026-05-14-agent-on-an-information-diet-parked.md). Not a soloproneur product directly; the value capture is content + brand + adjacent product introductions.

Salesforce going headless: Pure tier-1 BUY play. Trying to be the headless context store of record for customer relationships, and let the agentic workflow vendors at tier-2 + tier-3 build on top. The X take's "war" frame applies most directly here: Salesforce wants their own Agentforce bundled-free as a complement; third-party tier-2 vendors (Ramp's CRM-adjacent extensions, Clay, Apollo) want Salesforce reduced to CRUD.

RDCO's own position in the stack

RDCO is operating all 4 tiers at scale of 1:

RDCO is also building the META-PRODUCT of the 4-tier model: COO-agent productization. Not vendoring the world model itself, but vendoring the OPERATING MODEL of running a company with a tier-3 + tier-4 BUILD stack on tier-1 + tier-2 BUY foundation. That's the FDE asymmetric-edge thesis filed 2026-05-13 — what we're really selling is "here's how a solo operator can run the Block operating model at scale 1, and we'll help you do the same at scale N."

Founder's bias check (load-bearing)

In iMessage 15:19 ET, founder explicitly flagged: "I'm not sure the BUY agentic workflows is a strong position... maybe that's my own bias creeping in thinking ahead to my phData role of deploying these agentic glue workflows within organizations."

This is sharp self-awareness worth preserving in the vault:

Founder asked whether to flag this in the entry or keep private. He green-lit at 15:56 ET so it's IN the entry — calibration discipline marker.

What this changes

  1. MAC pricing locked at $350. Filed separately at 01-projects/mac/2026-05-14-mac-pricing-intent.md.
  2. "Agent on an information diet" queued as Sanity Check candidate. Filed at 01-projects/sanity-check/parked-angles/2026-05-14-agent-on-an-information-diet-parked.md.
  3. The 4-tier model becomes the diligence framework for any AI-native SaaS investment candidate going forward. Applied to longevity roster, applied to investing theses, applied to any new "should we use this" decision.
  4. The soloproneur-vs-VC TAM filter sits next to Amble's defensibility scorecard as the second-level filter for any tier-2 build candidate.
  5. The Block-as-Species-A correction (Ray walked back from earlier) — the manifesto piece needs a follow-up note clarifying Block is BUILDING tier-3 + tier-4 for itself, not vendoring as a tier-1 context store. Updating that file's open-questions section.

Caveats

Related

Open questions