Building Culture Capital

Culture on-chain — receipts, not vibes

An angel-friendly map of our umbrella brand, product surfaces (app + game), and the Building Culture Dollar (BCD) story inside BUILDCHAIN. Illustrative numbers only—see disclaimers.

Thesis (for discussion)

Collectors and travelers already chase culture — but odds and fulfillment are too often opaque. We combine fair, inspectable drops with an app layer that makes participation legible: wallets, marketplace, missions, and XP tied to Building Culture Dollar (BCD) as the in-app economic story—without claiming guaranteed returns on any token.

Where product lives

Three entry points, one narrative: the Capital umbrella, the live app experience, and the BUILDCHAIN game loop.

buildingculture.capital

Umbrella brand for on-chain culture and savings-club positioning—treasury narrative, compliance-conscious rollout, and room for ecosystem partnerships.

Visit site ↗

App

Primary product surface: wallet, marketplace, missions, XP / points ledger, community profile, and experiments such as x402-protected APIs—where players actually stack BCD story and receipts.

app.buildingculture.capital ↗

Game

BUILDCHAIN loop: fair raffle tickets for real-world assets, drops, leaderboard, and campaigns—designed so odds and settlement stay inspectable on-chain.

game.buildingculture.capital ↗

BCD + BUILDCHAIN (accurate constraints)

BCD is how we discuss value inside the product: balances, “Get BCD” previews, and mission-driven storytelling. Where configured, the UI can read an ERC20 balance; where not, we label demo balances honestly.

Settlement today follows the deployed raffle path in the chain’s native gas token unless and until contracts accept BCD for mints—we say that loudly so expectations stay aligned (FAQ).

Why this can compound

  • On-chain receipts for tickets and campaigns reduce “trust me” moments.
  • Marketplace + campaign surfaces create repeatable fee opportunities when volume follows.
  • Social distribution hooks (e.g. Farcaster / Warpcast flows where configured) can shorten acquisition loops for culture-native audiences.
  • Optional Strapi-backed community content lets partners ship stories without redeploying the core app.

Traction (placeholders)

Replace with counsel-approved metrics. Example labels only.

SignalExample / TBD
Monthly active wallets
Secondary GMV (proxy)
Campaign mint volume
Brand / venue partners

Business model (directional)

Revenue can mirror how culture platforms already monetize—primary mint fees, marketplace fees, sponsored experiences, and eventually premium APIs — while keeping disclosures honest when drops settle in native tokens today.

LineNotes (fill with finance)
Marketplace / protocol feesTBD — attach take rate when stable
Campaign & mint feesTBD — per deployment
Sponsored drops & experiencesTBD — partnership pipeline
API / infra (e.g. x402-style)TBD — optional premium tier

ROI framing & illustrative economics

Angels typically underwrite category creation, distribution, and execution speed—not a spreadsheet cell. Below is a qualitative band, placeholder cap table lines, then a toy scenario you can tune in conversation with advisors.

Illustrative outcome bands (not predictions)

  • Base case story: niche liquidity + steady drops → fees fund core team and infra; token narrative stays subservient to product.
  • Upside story: cultural moments spill into mainstream acquisition; marketplace + campaigns scale GMV; partnerships repeat.
  • Downside risks: regulatory scrutiny on promos, execution on fulfillment, chain / custody dependencies — see risks below.
Cap table linePlaceholder
Founders / early team— %
Seed / angel— %
Option pool— %
Strategic / advisors— %

Illustrative scenario (toy model)

Drag sliders to stress-test stories, not precision. Outputs are rounded bands for conversation with advisors—not projections.

~$2.00M

$0.25M – $20M

~$18.0M

Used only for a coarse “slice of the cap table” story if this round were primary.

~$1.50M
12%

Indicative ownership sold (toy)

11.1%

raise ÷ post-money — simplified; excludes option pools and prior rounds.

Illustrative annual fee revenue

~$2.16M

(Monthly GMV proxy × 12 × take rate). Not profit; excludes infra, grants, and volatility.

Round & use of funds (outline)

  • Product engineering: marketplace reliability, wallet UX, campaign tooling.
  • Growth: creator partnerships, drops programming, community.
  • Compliance & ops: counsel retainer, fulfillment playbooks, accounting.
  • Infrastructure: RPC, indexing, observability, security reviews.

Instrumentation (SAFE vs priced round, jurisdiction, token vs equity) belongs in your term sheet — not on this page.

Risks & mitigations

  • Regulatory: promotions and token mechanics vary by region — run campaigns only with appropriate licenses and disclosures.
  • Execution: real-world fulfillment is operationally heavy — invest in partner SLAs and player support.
  • Market: crypto UX friction and volatility — mitigate with clear settlement messaging and chain choices aligned with users.

Appendix — deeper dives

  • Mission (BCD) — treasury narrative, genesis claim context.
  • About — product thesis and loop.
  • FAQ — mechanics, disclaimers, “what is BUILDCHAIN”.
  • Roadmap — what ships next.